IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 16 January 2023 (all times are UTC)
| 01:17 | wyre is now away: Auto away at Mon Jan 16 01:16:37 2023 UTC | |
| 03:13 | vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:40, Quit: leaving) | |
| 06:21 | woernie has joined IRC (woernie!~werner@p5ddecd2a.dip0.t-ipconnect.de) | |
| 06:31 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 06:34 | denispyr[m] has joined IRC (denispyr[m]!~denispyrm@2001:470:69fc:105::1:5545) | |
| 06:56 | wyre is back | |
| 09:12 | wyre is now away: Auto away at Mon Jan 16 09:11:36 2023 UTC | |
| 09:14 | wyre is back | |
| 09:20 | jason has joined IRC (jason!~jason@98.97.140.75) | |
| 09:23 | jason has left IRC (jason!~jason@98.97.140.75, Client Quit) | |
| 09:23 | jason has joined IRC (jason!~jason@98.97.140.75) | |
| 09:24 | jason__ has joined IRC (jason__!~jason@98.97.140.75) | |
| 09:25 | wyre is now away: Auto away at Mon Jan 16 09:24:49 2023 UTC | |
| 09:25 | jason__ has left IRC (jason__!~jason@98.97.140.75) | |
| 09:27 | joris is back | |
| 09:27 | jason has left IRC (jason!~jason@98.97.140.75, Client Quit) | |
| 09:27 | tadaensylvermane has joined IRC (tadaensylvermane!~tadaen_s@98.97.140.75) | |
| 09:27 | wyre is back | |
| 09:49 | wyre is now away: Auto away at Mon Jan 16 09:49:00 2023 UTC | |
| 09:52 | wyre is back | |
| 09:58 | wyre is now away: Auto away at Mon Jan 16 09:57:19 2023 UTC | |
| 10:00 | wyre is back | |
| 10:10 | tadaensylvermane has left IRC (tadaensylvermane!~tadaen_s@98.97.140.75, Remote host closed the connection) | |
| 10:22 | tadaensylvermane has joined IRC (tadaensylvermane!~tadaen_s@98.97.140.75) | |
| 10:54 | wyre is now away: Auto away at Mon Jan 16 10:53:24 2023 UTC | |
| 10:56 | wyre is back | |
| 11:02 | wyre is now away: Auto away at Mon Jan 16 11:01:42 2023 UTC | |
| 11:04 | wyre is back | |
| 11:47 | joris has left IRC (joris!~joris@145.102.247.36, Ping timeout: 268 seconds) | |
| 12:22 | tadaensylvermane has left IRC (tadaensylvermane!~tadaen_s@98.97.140.75, Remote host closed the connection) | |
| 13:25 | tadaensylvermane has joined IRC (tadaensylvermane!~tadaen_s@98.97.140.75) | |
| 14:08 | eu^ip-209-124-24 has joined IRC (eu^ip-209-124-24!~eu^ip-209@2600:8807:3d07:9100:3b39:3f57:4f39:5a13) | |
| 14:10 | <eu^ip-209-124-24> I have a question. My ltsp setup was working just fine, but today when i boot my clients am getting "PXE-E32: TFTP open timeout", and on others "NBP filesize is 0 Bytes" "PXE-E18: server response timeout", can someone help please?
| |
| 14:12 | I have looked at the status of dnsmasq, it hands ot the ips but it stopes at DHCP(Ack), then the client requests again and it fails to boot.
| |
| 15:31 | yopla has joined IRC (yopla!~yopla@82-64-126-99.subs.proxad.net) | |
| 15:38 | <alkisg> eu^ip-209-124-24: so none of the client works? Can you send a screenshot of the client?
| |
| 15:56 | <yopla> Hello there, long time not been here. I still use LTSP for years now. Time goes fast. Have you ever consider boot kernels and initrd via http ? It boost client boot time. Full boot : 2m02s with tftp vs 1m17s with http.
| |
| 15:57 | <alkisg> Hi yopla , that requires one line in dnsmasq; the user can put that in a local.conf file
| |
| 15:58 | <yopla> OK, thought it was ltsp.ipxe role. Which line should I use then ?
| |
| 15:59 | <alkisg> It's listed in the "boot via http" discussion or issue or pull request, please have a look at github
| |
| 15:59 | It's certainly also doable via ltsp.ipxe, but if your bios supports it, you can completely avoid tftp
| |
| 16:02 | I've been postponing the tasks that require an http server for the case when I have plenty of free time and decide to implement a custom http server that would dynamically create/fetch all the required stuff, from ltsp.ipxe to kernel/initrd to ltsp.conf
| |
| 16:11 | <yopla> OK thank you ! I'll have a look in discussions
| |
| 16:11 | wyre is now away: Auto away at Mon Jan 16 16:11:01 2023 UTC | |
| 16:13 | <alkisg> 👍️
| |
| 17:26 | eu^ip-209-124-24 has left IRC (eu^ip-209-124-24!~eu^ip-209@2600:8807:3d07:9100:3b39:3f57:4f39:5a13, Quit: Client closed) | |
| 17:38 | yopla has left IRC (yopla!~yopla@82-64-126-99.subs.proxad.net, Quit: Client closed) | |
| 17:44 | <vsuojanen[m]> <eu^ip-209-124-24> "I have looked at the status of..." <- Could there be another DHCP server in your network or router? It sounds like the clients are getting a DHCP offer from another address, perhaps some old router/switch was plugged somewhere
| |
| 17:50 | Is it normal for ltsp clients to request twice ?
| |
| 17:56 | tadaensylvermane has left IRC (tadaensylvermane!~tadaen_s@98.97.140.75, Remote host closed the connection) | |
| 18:01 | tadaen has joined IRC (tadaen!~tadaensyl@98.97.140.75) | |
| 18:06 | <alkisg> Yes, once for ipxe and once by ipconfig or dhclient
| |
| 18:12 | tadaen has left IRC (tadaen!~tadaensyl@98.97.140.75, Remote host closed the connection) | |
| 18:34 | <vsuojanen[m]> Thanks, so before the kernel it should not request twice ;) assuming the link stays up. Btw I have never seen the pxe recover If the link goed down... was there in ipxe something like ipv4 link down start over loop?
| |
| 19:03 | wyre is back | |
| 19:15 | vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:40) | |
| 19:27 | <alkisg> No idea, I haven't tested with link up/down events while ipxe loads the kernel, it's just for a few seconds anyway...
| |
| 19:40 | eu^ip-209-124-24 has joined IRC (eu^ip-209-124-24!~eu^ip-209@2600:8807:3d07:9100:3b39:3f57:4f39:5a13) | |
| 19:41 | eu^ip-209-124-24 has left IRC (eu^ip-209-124-24!~eu^ip-209@2600:8807:3d07:9100:3b39:3f57:4f39:5a13, Client Quit) | |
| 19:41 | <vsuojanen[m]> Neither do I have. It's some other issue then pxe boot If The link shut downs. Just thinking because i recently setup a bridge to laptop with netplan. when The bridge link interface goes down/up The address renew work quite fast
| |
| 19:41 | eu^ip-209-124-24 has joined IRC (eu^ip-209-124-24!~eu^ip-209@2600:8807:3d07:9100:3b39:3f57:4f39:5a13) | |
| 19:44 | <eu^ip-209-124-24> Hey, i lost my chat of the problem abot TFTP TIMEOUT and server response timeout. How do i send a screenshot here
| |
| 19:44 | <vsuojanen[m]> I configured the netplan bridge with link-local and rendering in NetworkManager. I
| |
| 19:47 | this channel has Matrix clients users and IRC users. And then there's discussions open on github page
| |
| 19:56 | I need to go now, I hope you find out the issue tomorrow.
| |
| 19:57 | <alkisg> eu^ip-209-124-24: you're now connected over IRC, so one way is to use a site:
| |
| 19:57 | !photo
| |
| 19:57 | <ltspbot> I do not know about 'photo', but I do know about these similar topics: 'paste'
| |
| 19:57 | <alkisg> !screenshot
| |
| 19:57 | <ltspbot> screenshot: to upload a screenshot use a site like https://prnt.sc/ or https://snag.gy/ and then paste the URL here
| |
| 19:57 | <alkisg> eu^ip-209-124-24: while if you connect over the matrix protocol, you can copy/paste images directly, see https://ltsp.org/guides/chat-room/
| |
| 19:58 | <eu^ip-209-124-24> https://prnt.sc/k1d42S2o4Rof
| |
| 19:58 | I have uploaded a photo
| |
| 19:59 | <alkisg> eu^ip-209-124-24: what's the output of: ls -l /srv/tftp/ltsp | nc termbin.com 9999
| |
| 20:03 | Also send the output of this one: ( journalctl -b -u dnsmasq -n 300; ip a ) | nc termbin.com 9999
| |
| 20:08 | Guest284 has joined IRC (Guest284!~Guest284@66.207.221.237) | |
| 20:20 | <eu^ip-209-124-24> https://prnt.sc/bVmhTuJRKijD
| |
| 20:23 | https://prnt.sc/0z2vnC_YlXx-
| |
| 20:24 | The first for the first command and the second for the second respectively
| |
| 20:27 | I have uploaded the screenshots, sorry for the delay.
| |
| 20:38 | Guest284 has left IRC (Guest284!~Guest284@66.207.221.237, Quit: Client closed) | |
| 20:40 | <eu^ip-209-124-24> alkisg have you seen the output?
| |
| 20:47 | alkisg https://prnt.sc/0z2vnC_YlXx-
| |
| 20:48 | alkisg https://prnt.sc/0z2vnC_YlXx-
| |
| 20:48 | alkisg https://prnt.sc/bVmhTuJRKijD
| |
| 21:24 | seanjohnstontips has joined IRC (seanjohnstontips!~seanjohns@2001:470:69fc:105::2:f685) | |
| 21:52 | <alkisg> eu^ip-209-124-24: you're using dnsmasq wrong, you have two dhcp servers on the same network
| |
| 21:52 | vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:40, Quit: leaving) | |
| 21:53 | <alkisg> Your main dhcp server gave .172 to the client, but dnsmasq is configured to give IPs up to .169
| |
| 21:53 | Run this to reset the dnsmasq settings: sudo ltsp dnsmasq
| |
| 21:53 | This will use the "proxydhcp" method in your main network, so that the main dhcp server gives the IPs, and dnsmasq gives the boot filename
| |
| 22:00 | sunweaver is back | |
| 22:04 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
| 22:22 | sunweaver is now away: not here ... | |
| 22:27 | <eu^ip-209-124-24> Alright thanks! I am trying that now.
| |
| 22:29 | alkisg, you said am using dnsmasq wrong, which is the other dhcp server?
| |
| 22:47 | alkisg i dont want it to use a proxydhcp so i have disabled that. I have given the dnsmasq a range of the ip i want, and restarted it but the same thing happens. sending a screenshot shortly.
| |
| 22:50 | alkisg I gave it the ip range i wanted but when i run the comads you sent above i get this, which is not making sense to me.
| |
| 22:51 | alkisg https://prnt.sc/ho4OKg28bsXq
| |
| 22:53 | alkisg https://prnt.sc/FAtNQgAH5Ujv
| |
| 22:57 | I have changes the dhcp range in the this file /etc/dnsmasq.d/ltsp-dnsmasq.conf but when i run the command above the ip range does not coresspond to what i have just given it.
| |
| 23:16 | wyre is now away: Auto away at Mon Jan 16 23:15:19 2023 UTC | |