00:01 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
04:11 | shrenik has joined IRC (shrenik!6ee344d2@110.227.68.210) | |
04:25 | shrenik has left IRC (shrenik!6ee344d2@110.227.68.210, Ping timeout: 240 seconds) | |
04:49 | shrenik has joined IRC (shrenik!6ee344d2@110.227.68.210) | |
05:38 | <shrenik> Hi alkisg. I don't think pxe-service entries should be part of ltsp-dnsmasq.conf when the dhcp is working in proxy mode. Have not come across any explicit documentation which states that pxe-service shall be auto ignored if dnsmasq's dhcp is not working in proxy mode. Rather have come across statements that pxe-service should only be included when
| |
05:38 | using proxy. Hence it seems a logical error in the ltsp dnsmasq applet.
| |
05:39 | <alkisg> Hi shrenik
| |
05:39 | Dnsmasq can send different replies based on conditions
| |
05:39 | If a client asks from 192.168.67.x, it sends a real dhcp answer
| |
05:39 | If a client asks from e.g. 10.161.254.x, it sends a proxy dhcp answer, AND a pxe-service
| |
05:40 | You're saying that when a client asks from 192.168.67.x, it also sends a pxe-service. According to the tags, this isn't correct. Do you see such a reply in the dnsmasq dhcp logs?
| |
05:41 | When you boot a client in 192.168.67.x, do you see "tag:proxy" in the dnsmasq logs?
| |
05:41 | <shrenik> Not that I noticed. I shall check again.
| |
05:42 | <alkisg> See my comment there:
| |
05:42 | # PXE services in non proxy subnets sometimes break UEFI netboot, so tag:proxy.
| |
05:42 | <shrenik> I went through this to understand the process - https://www.richud.com/wiki/Network_iPXE_dnsmasq_Examples_PXE_BOOT#dnsmasq.conf_proxy_DHCP_server
| |
05:42 | <alkisg> This is the reason that pxe-services have a tag
| |
05:42 | If the tag isn't there, then the pxe-services do nothing, they shouldn't be offered to the client
| |
05:42 | If they ARE offered, then that's a dnsmasq bug and we should report it to its developer, Simon, not try to solve it in ltsp
| |
05:43 | <shrenik> okay
| |
05:43 | <alkisg> I.e. please investigate a bit more, I don't think this is an issue in ltsp
| |
05:43 | If it is, sure, let's fix it, but I don't think it is
| |
05:43 | <shrenik> I shall log-queries and log-dhcp and revert.
| |
05:44 | <alkisg> Great, thank you
| |
05:44 | <shrenik> Thank you for your prompt response. :)
| |
05:45 | <alkisg> :)
| |
06:03 | <shrenik> https://pastebin.com/e5YxhkBG - non-proxy + legacy boot works but no-proxy + UEFI doesn't. So pxe-service is being ignored.
| |
06:08 | alkisg ^
| |
06:27 | <alkisg> shrenik: eeeh not sure what you mean there, I'm booting UEFI+proxy in many schools here with the default ltsp setup
| |
06:27 | I don't see a proxy subnet in your paste
| |
06:31 | <shrenik> sorry was away
| |
06:31 | this is a non-proxy boot
| |
06:31 | <alkisg> Oh sorry I misred
| |
06:31 | <shrenik> UEFI + proxy definitely works.
| |
06:32 | <alkisg> shrenik: can we do screen sharing? I think it'll make things faster
| |
06:33 | <shrenik> would a cli to the ltsp server suffice?
| |
06:33 | <alkisg> Yes of course
| |
06:33 | Do you have epoptes-client installed there?
| |
06:34 | If so, you can share the terminal with: /usr/share/epoptes-client/share-terminal 81.186.20.0
| |
06:34 | <shrenik> I am currently on Windows. The ltsp server is not connected to the internet to test in non-proxy mode.
| |
06:34 | <alkisg> Is it a VM?
| |
06:34 | <shrenik> no
| |
06:34 | <alkisg> Your windows pc has 2 nics?
| |
06:34 | <shrenik> no
| |
06:34 | <alkisg> one for internet, one to join the ltsp subnet?
| |
06:35 | How are you accessing the ltsp server?
| |
06:35 | <shrenik> yes, wifi for internet and another for ltsp subnet
| |
06:35 | I can share my windows screen. wait a min.
| |
06:35 | <alkisg> Anydesk for that would be fine
| |
06:36 | <shrenik> have zoho assist, sharing a link
| |
06:36 | <alkisg> You could also do some ssh port forwarding and share only the windows terminal, but it's harder...
| |
06:36 | OK
| |
06:36 | I don't know zoho, you'll have to guide me :D
| |
06:37 | <shrenik> https://assist.zoho.com/attend/678089692
| |
06:38 | <alkisg> And you'll send me a password in a pm?
| |
06:39 | <shrenik> 8759
| |
06:40 | <alkisg> Screen Sharing is about to begin... for a minute now :D
| |
06:44 | <shrenik> need to pass -b -t , check history
| |
06:44 | <alkisg> I 'll check the diff
| |
06:46 | shrenik: I don't see any diff in the clean conf vs your older conf
| |
06:46 | <shrenik> yes, ignore the -t -b bit
| |
06:46 | <alkisg> OK
| |
06:46 | <shrenik> so yes, we have the default file generated
| |
06:46 | <alkisg> Now please try to boot an uefi client
| |
06:48 | shrenik: I see it offers an ip
| |
06:48 | <shrenik> i will let you know
| |
06:48 | making changes in bios
| |
06:48 | <alkisg> OK
| |
06:49 | <shrenik> now
| |
06:50 | <alkisg> shrenik: and now , the dell doesn't boot? Try it
| |
06:50 | Let's see what the logs say about it
| |
06:55 | shrenik: it's confusing, better here
| |
06:55 | Let me ask a couple of questions first
| |
06:56 | So, the clients do get an ip offer, but they don't boot?
| |
06:56 | What message do they show?
| |
06:56 | (IRC also helps if I want to keep logs to remember what the problem is, when I try to solve it later)
| |
06:56 | <shrenik> agreed
| |
06:57 | yes, from logs it seems that an IP is offered but nothing as such is visible on the client side.
| |
06:57 | <alkisg> And you're saying that if we remove pxe-service, and restart dnsmasq, it will work?
| |
06:57 | <shrenik> Sorry IP is received
| |
06:57 | then we get PXE-E21: Remote boot cancelled
| |
06:58 | Yes, If I remove pxe-service or comment them, then it works. tried several times yesterday.
| |
06:58 | let's try now again.
| |
06:58 | <alkisg> Wait
| |
07:00 | shrenik: and now it boots?
| |
07:00 | try it
| |
07:01 | <shrenik> no it didn't
| |
07:01 | <alkisg> (you may join irc from your phone if you want, from webchat.freenode.net, if it helps you)
| |
07:02 | shrenik: now?
| |
07:02 | <shrenik> yes
| |
07:03 | <alkisg> shrenik: ok, I think we have enough information
| |
07:03 | I think that now you should now do these:
| |
07:04 | shrenik36 has joined IRC (shrenik36!6ee344d2@110.227.68.210) | |
07:04 | <alkisg> shrenik36: you may go to your windows pc, as we don't need more screen sharing,
| |
07:04 | I propose that you do these:
| |
07:05 | 1) Clean up the /etc/dnsmasq.d/logs dir that I created, so that it only contains the success/failure logs, not "the last 100 or 1000 lines"
| |
07:05 | 2) Then, attach them to the PR that you did; 4 files there: success.conf, success.log, failure.conf, failure.log
| |
07:06 | 3) Then, please send a mail about it to the dnsmasq mailing list, and cc me at alkisg at gmail, and also mention the PR for the files,
| |
07:06 | And then, we'll see what simon has to say. If it's fixable in dnsmasq, done. If not, then please make the PR so that it comments-out pxe-services when --proxy=0
| |
07:07 | <shrenik> I will change the PR also, instead of the code change done yesterday, will have to change in proxy_dhcp()
| |
07:07 | <alkisg> Ah btw, was the ltsp-dnsmasq.conf the stock one, or did we use modified, non-upstream ltsp code?
| |
07:07 | <shrenik> stock
| |
07:07 | <alkisg> ok
| |
07:08 | <shrenik> only when it "comments-out pxe-services when --proxy=0"?
| |
07:08 | <alkisg> I haven't read the PR code in detail, but what we want is, when the user passes --proxy-dhcp=0, to comment out pxe-service lines
| |
07:08 | I don't know if you're already doing that
| |
07:08 | (closed screen sharing)
| |
07:08 | <shrenik> I was doing this only
| |
07:09 | <alkisg> Btw, are you working with cyberorg?
| |
07:09 | <shrenik> but would like to take it to this section
| |
07:09 | case "$subnet" in
| |
07:09 | 127.0.0.1|169.254.0.0|192.168.67.0|*[!0-9.]*)
| |
07:09 | continue
| |
07:09 | ;;
| |
07:09 | yes
| |
07:09 | <alkisg> I haven't heard of him for a while, it's good to know you're still using ltsp :)
| |
07:10 | shrenik36 has left IRC (shrenik36!6ee344d2@110.227.68.210, Quit: Connection closed) | |
07:10 | <alkisg> Tell him I sent my regards :)
| |
07:10 | <shrenik> Sure. :)
| |
07:10 | <alkisg> OK, let's see what the dnsmasq developer has to say about this issue, and we'll see about the PR details later
| |
07:11 | <shrenik> Okay. Am submitting another PR for what I believe is a typo in ipxe applet for replacing /srv/ltsp
| |
07:11 | Thanks for your guidance.
| |
07:11 | <alkisg> Sure, thank you
| |
07:12 | shrenik: do you mind if I push these upstream in Autumn? As I'm trying to finish with my phd and I'd like to minimize disruptions... :D
| |
07:12 | I'm too easily distracted!
| |
07:12 | <shrenik> Sure. No problem. I will just manage these changes on a manual basis till then.
| |
07:12 | <alkisg> Around next Christmas, I'll publish a big new ltsp version, in time for Ubuntu 22.04
| |
07:13 | Great, thanks
| |
07:13 | <shrenik> (y)
| |
07:14 | Do you suggest that I try transferring the ltsp image over http or is the existing method efficient enough for 30-40 simultaneous clients?
| |
07:15 | <alkisg> Do you mean image_to_ram?
| |
07:15 | I think that's only really useful if the server is going to go offline, e.g. for kiosks, with no authentication and server-side /home
| |
07:16 | Otherwise it just wastes ram
| |
07:16 | <shrenik> no, https://www.richud.com/wiki/Network_iPXE_dnsmasq_Examples_PXE_BOOT#pxelinux
| |
07:17 | <alkisg> ah, you mean the kernel and initrd, not the image
| |
07:17 | If tftp is < 10 seconds, it's not worth it. In some cases, tftp is > 10 seconds and http is < 3 seconds; then, it's worth it
| |
07:17 | <shrenik> seems i am confusing it all
| |
07:18 | just a min
| |
07:18 | <alkisg> Measure how long it shows "loading kernel/loading initrd"
| |
07:18 | If ipxe needs less than 10 minutes to load the kernel, then it's not worth it
| |
07:18 | <shrenik> yes just kernel and initrd
| |
07:19 | <alkisg> Normally you don't need http
| |
07:19 | In a long distant future version, ltsp will have a web server, THEN it will be the default instead of tftp
| |
07:19 | <shrenik> "If ipxe needs less than 10 minutes to load the kernel, then it's not worth it" ? 10 minutes?
| |
07:19 | <alkisg> 10 seconds, sorry
| |
07:19 | <shrenik> ah!!
| |
07:19 | <alkisg> (09:17:55 AM) alkisg: If tftp is < 10 seconds, it's not worth it. In some cases, tftp is > 10 seconds and http is < 3 seconds; then, it's worth it
| |
07:20 | I wrote it correctly there ^
| |
07:20 | And wrongly afterwards :)
| |
07:20 | <shrenik> yes
| |
07:20 | will check with 30-40 clients, then will know better
| |
07:20 | <alkisg> OK
| |
07:20 | <shrenik> that's it for now, getting on with the PRs
| |
07:20 | <alkisg> In a setup, we have more than 100 clients, all with tftp
| |
07:20 | <shrenik> great then
| |
07:20 | <alkisg> Cheers :)
| |
07:21 | <shrenik> Cheers
| |
07:36 | RaphGro has joined IRC (RaphGro!~raphgro@fedora/raphgro) | |
07:46 | <shrenik> alkisg Just discovered https://github.com/alkisg/ltsp5-uefi . Actually this was my present need and I ended up trying the new LTSP. :)
| |
07:49 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
07:54 | <alkisg> shrenik: hehe :)
| |
08:00 | <shrenik> There are several servers in schools which are currently using ltsp5. Can just try with ltsp5-uefi so that they can use newer systems that do not support legacy boot any more. Any specific PAA to add to install the required ltsp-binaries ?
| |
08:00 | PPA
| |
08:00 | <alkisg> shrenik: in all Ubuntu systems, I recommend the greek schools ppa
| |
08:00 | LTS versions only
| |
08:01 | Even if they're not using ltsp
| |
08:01 | We only upload fixed and new packages there, so it only does good, no harm :D
| |
08:01 | E.g. fixed x11vnc, new ltsp-binaries...
| |
08:01 | sudo add-apt-repository ppa:ts.sch.gr => should do it
| |
08:03 | <shrenik> Great. Thanks. (y)
| |
08:05 | woernie has joined IRC (woernie!~werner@pd9e8b5cc.dip0.t-ipconnect.de) | |
09:22 | <shrenik> alkisg: Does the ltsp5-uefi only support proxy mode? It seems so from these lines - https://github.com/alkisg/ltsp5-uefi/blob/856339f472f76a60a169a74e273a05ff56491eec/ltsp5-uefi#L63-L67
| |
09:23 | <alkisg> shrenik: no; see https://raw.githubusercontent.com/alkisg/ltsp5-uefi/master/ltsp-server-dnsmasq.conf
| |
09:23 | dhcp-range=192.168.67.20,192.168.67.250,12h
| |
09:23 | This range doesn't need to be changed; only the proxy range needs a "sed"
| |
09:27 | <shrenik> I had seen. But where are you commenting out the line with set:proxy for a no proxy case?
| |
09:27 | <alkisg> shrenik: ah, I haven't implemented all the options in that little shell script there
| |
09:28 | You'll need to edit the file if you want to disable proxy
| |
09:28 | <shrenik> Got it. Just needed this confirmation.
| |
10:22 | sfrank has joined IRC (sfrank!5a5595b4@90.85.149.180) | |
10:24 | <sfrank> hello I have to add the proxy settings for my raspberries
| |
10:24 | I can't get back to nfs_rw mode
| |
10:26 | <alkisg> sfrank: you don't need the nfs_rw mode; you need an administrative rpi
| |
10:26 | As I don't have a lot of time currently, if you want my help, I could do it via screen sharing...
| |
10:37 | Aison0 has joined IRC (Aison0!~Asion0@2a02:168:200f:110:69c6:120a:877c:5a19) | |
10:41 | shrenik has left IRC (shrenik!6ee344d2@110.227.68.210, Ping timeout: 240 seconds) | |
11:09 | sfrank has left IRC (sfrank!5a5595b4@90.85.149.180, Ping timeout: 240 seconds) | |
11:24 | antares2021 has joined IRC (antares2021!bc4ed3f5@245.211.78.188.dynamic.jazztel.es) | |
11:32 | Aison0 has left IRC (Aison0!~Asion0@2a02:168:200f:110:69c6:120a:877c:5a19, Ping timeout: 264 seconds) | |
11:51 | sfrank has joined IRC (sfrank!5a5595b4@90.85.149.180) | |
12:01 | Aison0 has joined IRC (Aison0!~Asion0@2a02:168:200f:110:69c6:120a:877c:5a19) | |
12:18 | sfrank has left IRC (sfrank!5a5595b4@90.85.149.180, Quit: Ping timeout (120 seconds)) | |
12:49 | <antares2021> Hello. I just wrote something about yesterday's discussion on administrative RPis at https://github.com/ltsp/ltsp/wiki/Installing-software-in-your-Raspberry-Pis
| |
12:49 | I hope it is understable, just check it out
| |
12:55 | chef has joined IRC (chef!6c221082@gw.monkberry.com) | |
12:55 | chef is now known as Guest59625 | |
12:55 | Guest59625 has left IRC (Guest59625!6c221082@gw.monkberry.com, Client Quit) | |
12:59 | sfrank has joined IRC (sfrank!5a5595b4@90.85.149.180) | |
13:02 | woernie has left IRC (woernie!~werner@pd9e8b5cc.dip0.t-ipconnect.de, Ping timeout: 240 seconds) | |
13:03 | woernie has joined IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de) | |
13:34 | <vsuojanen> hello, I have Ubuntu 18.04.5 and LTSP 20.01 (PPA) in test and I can't get hostname sections ex. [testme*] work anymore when managing multiple hosts. i tried to use INCLUDE= but the section was not found
| |
13:35 | https://pastebin.com/jZ90nTqe
| |
13:39 | the section I have there currently in LTSP 19.01 is single guest session, https://github.com/ltsp/ltsp/wiki/Single-guest-session-over-NFS
| |
13:40 | (with LTSP 19.01 works fine)
| |
13:44 | does anyone have similar hostname sections configured (succesfully)?
| |
13:48 | woernie has left IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de, Ping timeout: 265 seconds) | |
13:48 | woernie has joined IRC (woernie!~werner@pd9e8b5cc.dip0.t-ipconnect.de) | |
14:06 | sfrank has left IRC (sfrank!5a5595b4@90.85.149.180, Quit: Connection closed) | |
14:12 | Aison0 has left IRC (Aison0!~Asion0@2a02:168:200f:110:69c6:120a:877c:5a19, Ping timeout: 265 seconds) | |
14:13 | <alkisg> vsuojanen: hello; first, put MENU_TIMEOUT in a [server] section
| |
14:15 | vsuojanen: hmm, I'm not sure that setting the hostname in [clients] and THEN sourcing [hostname*] sections will work
| |
14:15 | <vsuojanen> thanks, sure, I don't need MENU_TIMEOUT there
| |
14:15 | <alkisg> You may set it in DHCP or you may set it in [MAC:ADDRESS] sections, but maybe in [clients] it's already too late
| |
14:16 | Was it working before?
| |
14:18 | re section_call unnamed $clients_section common $server_section "$MAC_ADDRESS" "$IP_ADDRESS"
| |
14:18 | # MAC/IP sections are allowed to set HOSTNAME
| |
14:18 | re section_call "$HOSTNAME"
| |
14:18 | So ok it should work
| |
14:18 | What's the resulting hostname?
| |
14:19 | ltsp1.2.3.4 ?
| |
14:19 | or e.g. ltsp123?
| |
14:19 | <vsuojanen> yes it's working [clients] HOSTNAME=pc%{IP}, [xx:xx:xx:xx:xx] some other monitor/xrand settings, then the single guest session is under hostname section [pc*]
| |
14:20 | hostname works. HOSTNAME=testme%[IP]. let's use this now on in the topic
| |
14:20 | <alkisg> vsuojanen: is there a syntax error in line 40, missing the closing " ?
| |
14:21 | <vsuojanen> no. it's mssing only from paste
| |
14:21 | <alkisg> OK. In 21.01, what's the resulting hostname?
| |
14:22 | It does have the correct testme%{ip}, and the problem is that its' not sourcing the include?
| |
14:23 | <vsuojanen> sorry. HOSTNAME=testme%{IP} under [client] section sets the hostname for the client succesfully.
| |
14:23 | testme108
| |
14:24 | <alkisg> I suspect this: https://github.com/ltsp/ltsp/issues/343
| |
14:24 | Are you able to undo that patch, and run ltsp initrd, and test if reverting fixes the issue?
| |
14:24 | <vsuojanen> but I can't get the [testme] or [testme*] sections to set anything
| |
14:25 | ok
| |
14:37 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
14:39 | <vsuojanen> I'm test booting now
| |
14:42 | yes. that previous e1cbfef3 commit works with ltsp.conf HOSTNAME sections. [testme*] AUTOLOGIN=guest
| |
14:42 | <alkisg> vsuojanen: can you comment there, and I'll have a look in Autumn? (sorry, phd this year :))
| |
14:43 | Hmm moment...
| |
14:44 | Yeah it's a bit complicated to work on that now, sorry
| |
14:44 | Patches welcome of course
| |
14:44 | <vsuojanen> I'm sorry I did not have time to test on January
| |
14:45 | but I add at least comment. here in the same issue ? https://github.com/ltsp/ltsp/issues/343
| |
14:45 | <alkisg> No worries; it's an edge use case, setting hostname with %ip and THEN sourcing the result, so I never tested that either, not even 100% sure that it should be supported
| |
14:45 | <vsuojanen> it did not work without %IP eithere
| |
14:47 | <alkisg> vsuojanen: yes comment there, and click reopen if you have the permissions to do so; otherwise I'll reopen it
| |
14:48 | <vsuojanen> I will.need to sign up first
| |
14:48 | take well
| |
14:48 | <alkisg> Thanks, you too
| |
14:48 | <vsuojanen> thanks
| |
15:09 | antares2021 has left IRC (antares2021!bc4ed3f5@245.211.78.188.dynamic.jazztel.es, Quit: Connection closed) | |
15:10 | RaphGro has left IRC (RaphGro!~raphgro@fedora/raphgro, Quit: Please remember your own message. It'll be read as soon as possible.) | |
17:51 | woernie has left IRC (woernie!~werner@pd9e8b5cc.dip0.t-ipconnect.de, Remote host closed the connection) | |
17:55 | GodFather has left IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net, Ping timeout: 246 seconds) | |
19:57 | Aison0 has joined IRC (Aison0!~Asion0@2a02:168:200f:110:69c6:120a:877c:5a19) | |
20:25 | dsj2 has left IRC (dsj2!~David@70-237-72-173.lightspeed.chrlnc.sbcglobal.net, Quit: Terminated with extreme prejudice - dircproxy 1.0.5) | |
20:29 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
20:32 | dsj2 has joined IRC (dsj2!~David@70-237-72-173.lightspeed.chrlnc.sbcglobal.net) | |
21:57 | dsj2 has left IRC (dsj2!~David@70-237-72-173.lightspeed.chrlnc.sbcglobal.net, Ping timeout: 256 seconds) | |
22:12 | ltspbot` has joined IRC (ltspbot`!~supybot@devs.ts.sch.gr) | |
22:12 | ltspbot has left IRC (ltspbot!~supybot@devs.ts.sch.gr, Remote host closed the connection) | |
22:53 | GodFather has left IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net, Ping timeout: 240 seconds) | |
22:56 | GodFather has joined IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net) | |
23:14 | GodFather has left IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net, Ping timeout: 240 seconds) | |
23:49 | GodFather has joined IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net) | |