IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 14 December 2019 (all times are UTC)
| 02:34 | yanu has left IRC (yanu!~yanu@178-116-54-5.access.telenet.be, Ping timeout: 245 seconds) | |
| 04:36 | Ark74 has left IRC (Ark74!~Luis@177.238.145.140, Quit: Leaving) | |
| 06:25 | yanu has joined IRC (yanu!~yanu@178-116-54-5.access.telenet.be) | |
| 06:53 | gdi2k has joined IRC (gdi2k!~gdi2k@175.176.64.1) | |
| 07:13 | vsuojanen has left IRC (vsuojanen!~vsuojanen@cable-hml-58568e-245.dhcp.inet.fi, Ping timeout: 246 seconds) | |
| 07:23 | gdi2k has left IRC (gdi2k!~gdi2k@175.176.64.1, Ping timeout: 250 seconds) | |
| 07:28 | gdi2k has joined IRC (gdi2k!~Android@175.176.64.1) | |
| 07:36 | gdi2k has left IRC (gdi2k!~Android@175.176.64.1, Quit: -a- IRC for Android 2.1.55) | |
| 07:39 | gdi2k has joined IRC (gdi2k!~Android@175.176.64.1) | |
| 07:49 | kjackal has joined IRC (kjackal!~quassel@2a02:587:3109:4a00:8951:4cce:8d0:539a) | |
| 08:04 | gdi2k has left IRC (gdi2k!~Android@175.176.64.1, Read error: Connection reset by peer) | |
| 08:07 | gdi2k has joined IRC (gdi2k!~Android@122.52.152.138) | |
| 08:17 | gdi2k_ has joined IRC (gdi2k_!~Android@175.176.64.1) | |
| 08:21 | gdi2k has left IRC (gdi2k!~Android@122.52.152.138, Ping timeout: 265 seconds) | |
| 08:29 | kjackal has left IRC (kjackal!~quassel@2a02:587:3109:4a00:8951:4cce:8d0:539a, Ping timeout: 276 seconds) | |
| 09:19 | kjackal has joined IRC (kjackal!~quassel@2a02:587:3109:4a00:8951:4cce:8d0:539a) | |
| 09:59 | eu^195128893revs has joined IRC (eu^195128893revs!5d0880c3@195.128.8.93.rev.sfr.net) | |
| 10:10 | eu^195128893revs has left IRC (eu^195128893revs!5d0880c3@195.128.8.93.rev.sfr.net, Remote host closed the connection) | |
| 10:51 | adrianor1 has joined IRC (adrianor1!~adrianorg@177.204.79.114.dynamic.adsl.gvt.net.br) | |
| 10:54 | adrianorg has left IRC (adrianorg!~adrianorg@186.213.155.172, Ping timeout: 245 seconds) | |
| 11:39 | Nikoh77 has left IRC (Nikoh77!~Nikoh77@host148-135-static.9-79-b.business.telecomitalia.it, Remote host closed the connection) | |
| 13:58 | vsuojanen has joined IRC (vsuojanen!~vsuojanen@cable-hml-585697-106.dhcp.inet.fi) | |
| 14:29 | gdi2k_ has left IRC (gdi2k_!~Android@175.176.64.1, Read error: Connection reset by peer) | |
| 14:30 | gdi2k has joined IRC (gdi2k!~Android@49.145.67.147) | |
| 14:37 | kjackal has left IRC (kjackal!~quassel@2a02:587:3109:4a00:8951:4cce:8d0:539a, Ping timeout: 276 seconds) | |
| 15:11 | gdi2k_ has joined IRC (gdi2k_!~gdi2k@180.190.180.122) | |
| 15:12 | gdi2k has left IRC (gdi2k!~Android@49.145.67.147, Ping timeout: 268 seconds) | |
| 16:31 | <alkisg> !learn ltsp5-uefi as Unofficial UEFI netbooting support for LTSP5: https://github.com/alkisg/ltsp5-uefi
| |
| 16:31 | <ltspbot> The operation succeeded.
| |
| 17:36 | kjackal has joined IRC (kjackal!~quassel@2a02:587:3109:4a00:8951:4cce:8d0:539a) | |
| 18:04 | Tottle has joined IRC (Tottle!5496eb1d@p5496EB1D.dip0.t-ipconnect.de) | |
| 18:21 | <Tottle> Hello, i have Ubuntu 18.04 and i installed ltsp using https://ltsp.org/docs/installation/. I want to maintain my client image chrootless and network-boot it via my ThinkCenter M93P. Both, my host and client computer are connected to my OpenWrt/LEDE power Linksys Rounter. The client computer gets the host systems ip, but than fails with:
| |
| 18:21 | "Auto-select: undionly.kpxe. BOOT SERVER IP: 192.168.XXX.YYY. TFTP.... TFTP open timeout. Exiting Intel Boot Agent". Can you help me fixing that? Is there some other good explaining LTSP 2019 Resource?
| |
| 18:22 | <alkisg> Tottle: try this:
| |
| 18:23 | !tftp
| |
| 18:23 | <ltspbot> tftp: Here's a page to help you troubleshoot TFTP problems in Ubuntu: https://help.ubuntu.com/community/UbuntuLTSP/Troubleshooting/TFTP
| |
| 18:23 | <alkisg> Hmm no
| |
| 18:24 | From the server: busybox tftp -g -r /ltsp/undionly.kpxe -l /tmp/undionly.kpxe
| |
| 18:24 | Does this work?
| |
| 18:30 | busybox tftp -g -r /ltsp/undionly.kpxe -l /tmp/undionly.kpxe localhost
| |
| 18:31 | <Tottle> I try this out
| |
| 18:32 | I ran " busybox tftp -g -r /ltsp/undionly.kpxe -l /tmp/undionly.kpxe localhost" from my host system. That doen't helped
| |
| 18:33 | <alkisg> What was the output of the command?
| |
| 18:33 | <Tottle> Nothing
| |
| 18:37 | https://help.ubuntu.com/community/UbuntuLTSP/Troubleshooting/TFTP Doesn't help me, because this is not for the new LTSP 2019 and not for Ubuntu 18.04
| |
| 18:38 | <alkisg> Yes that's why I said "hmm no"
| |
| 18:38 | Tottle: do you have firewall running, e.g. ufw?
| |
| 18:42 | !forget tftp
| |
| 18:42 | <ltspbot> The operation succeeded.
| |
| 18:42 | <alkisg> !learn tftp as To test if your TFTP server is working, try this on the server (or from another PC): busybox tftp -g -r /ltsp/ltsp.ipxe -l /tmp/ltsp.ipxe localhost
| |
| 18:42 | <ltspbot> The operation succeeded.
| |
| 18:43 | <alkisg> Tottle: also, is your tftp server IP there correct, or does it point to e.g. the router?
| |
| 18:44 | <Tottle> Ah see. ufw seems to be installed, but i never used that. Iptables says that INPUT, FORWARD and OUTPUT has ACCEPT Policy without any rules.
| |
| 18:46 | Do you reference "BOOT SERVER IP: 192.168.XXX.YYY"? Than: Yeah the 192.168.XXX.YYY-part is my enp4s0-interface address
| |
| 18:46 | (Of my host system)
| |
| 18:46 | <alkisg> 192.168 are internal addresses, no need to hide them, they're not secret
| |
| 18:46 | Can I see with VNC?
| |
| 18:46 | !vnc-edide
| |
| 18:46 | <ltspbot> vnc-edide: To share your screen with me, open Epoptes → Help menu → Remote support → Host: srv1-dide.ioa.sch.gr, and click the Connect button
| |
| 18:46 | <Tottle> I know, but it seems to be irrelevant. If it would be better, i can post them
| |
| 18:47 | <alkisg> No, it sometimes makes chatting easier
| |
| 18:47 | No big deal
| |
| 18:47 | <Tottle> Ok, no problem, i will post them
| |
| 18:48 | <alkisg> So if I understood this correctly, your client cannot even get undionly.kpxe, it times out before it gets it
| |
| 18:48 | This can only be due to server tftp issues (you said no issues there), firewall, or wrong client ip
| |
| 18:49 | I would test with a VM client next, to see if it works with that. E.g. virtualbox client.
| |
| 18:49 | <Tottle> Hmm probably i have to configure something in my OpenWRT/LEDE router?
| |
| 18:50 | <alkisg> Normally, you should leave the router completely unconfigured, so send IPs but not boot filename or root-path etc
| |
| 18:50 | And you should use the proxydhcp mode of the ltsp server, which would take care of everything automatically
| |
| 18:51 | What's the output of this, on the server? sudo /usr/lib/klibc/bin/ipconfig -n enp4s0 | nc termbin.com 9999
| |
| 18:51 | This does a fake dhcp request
| |
| 18:51 | So that we see if your router does send a boot filename etc
| |
| 18:52 | <Tottle> https://termbin.com/bv2i
| |
| 18:52 | <alkisg> It's fine
| |
| 18:53 | I would suggest either VNC'ing to me (I'm an ltsp developer btw), or using a VirtualBox client
| |
| 18:53 | as the next step
| |
| 18:56 | <Tottle> I can try to connect with VirtualBox
| |
| 18:59 | <alkisg> Put the vbox client lan to bridged mode, and use boot.ipxe.org/ipxe.iso as the boot source
| |
| 19:04 | <Tottle> I have VirtualBox 5.2.34. I tried to connect via network-brigde to enp4s0 and deny promiscuous-mode. Than i booted via lan. There it also times out. I will try with boot.ipxe.org/ipxe.iso as boot source
| |
| 19:07 | Where can i specify boot.ipxe.org/ipxe.iso as network boot source?
| |
| 19:08 | <alkisg> download it, it's an iso
| |
| 19:08 | <Tottle> Ah ok, will do it
| |
| 19:14 | The output looks quite, but not completly, similar to the regular lan boot option from VirtualBox. The output is: ... Booting from PXE menu\n PXE\n PXEBS ... ok\n Next server: 192.168.1.121\n Filename: ltsp/ltsp.ipxe.0\n tftp://192.168.1.121/lsp/ltsp.ipxe.0.... Connection timed out
| |
| 19:14 | <alkisg> And is .121 your ltsp server?
| |
| 19:15 | <Tottle> Yeah thats my Ubuntu host system, on which I installed ltsp etc.
| |
| 19:17 | <alkisg> OK something is indeed very wrong there, if your client from localhost can't use tftp
| |
| 19:17 | Is dnsmasq running?
| |
| 19:17 | Ah you said that "busybox tftp" worked
| |
| 19:19 | Yeah at that point I'd want to see all these with my own eyes, over vnc
| |
| 19:24 | <Tottle> I will configure a tunnel, that you can see it
| |
| 19:26 | Or bother you if we could use TeamViewer, because I have chrooted my ssh, and i would have to modify it back to normal?
| |
| 19:27 | <alkisg> If the ltsp server has internet access, it can reach me
| |
| 19:27 | No need for tunnels etc
| |
| 19:28 | Teamviewer has blacklisted me because of "commercial use" somehow, so I stopped using it
| |
| 19:28 | I applied once to revoke that status, they did, then it was back the next time I used teamviewer again, so I stopped bothering with it
| |
| 19:30 | kjackal has left IRC (kjackal!~quassel@2a02:587:3109:4a00:8951:4cce:8d0:539a, Ping timeout: 252 seconds) | |
| 19:30 | <Tottle> Ok, i understand. So i would have setup x11vnc with ssh tunnel, but you said, ltsp server with internet access. So what should i do? Somehow forward ltsp?
| |
| 19:30 | <alkisg> Did you install epoptes when you installed ltsp?
| |
| 19:31 | <Tottle> Yeah, but i never used it
| |
| 19:31 | <alkisg> OK, then just do this: x11vnc -connect srv1-dide.ioa.sch.gr
| |
| 19:31 | This should connect to me, if your ltsp server has xorg and internet access
| |
| 19:33 | (08:21:29 PM) Tottle: Hello, i have Ubuntu 18.04 ==> it's 16.04
| |
| 19:38 | Tottle: ok, the problem was network-manager in 16.04
| |
| 19:38 | It has a lot of bugs that prevent dnsmasq from working properly
| |
| 19:38 | You'd better use 18.04 instead of 16.04...
| |
| 19:38 | (or even 20.04 should be better than 16.04 :D)
| |
| 19:40 | (I closed VNC)
| |
| 19:44 | <Tottle> Oh i use different versions at different computers, I really thought that was 18.04. I will upgrade soon, but this is so errorprone and its an production system. Someone in the internet suggested that one can disable dnsmasq with #port=0. I thought that this would only be to be able to manipulate dns requests but have nothing to do with the
| |
| 19:44 | routing, because with it, i haven't internet anymore. Probably because of NetworkManger-Bug. So how can I avoid the NetworkManager bug?
| |
| 19:44 | <alkisg> Just reboot your pc now, it should be ok
| |
| 19:44 | port=0 disables dns, which is the default
| |
| 19:45 | By uncommenting it, you made it worse
| |
| 19:45 | The "bind-interfaces" that /etc/dnsamsq.d/network-manager had, was the main problem
| |
| 19:46 | It makes dnsmasq unstable; fortunately, systemd-networkd came along and ubuntu dropped their stupid hacks
| |
| 19:46 | So 18.04 doesn't have these problems at all
| |
| 19:49 | <Tottle> Ok. Than I will upgrade as soon as possible. Thank you for your great help!
| |
| 19:51 | Tottle has left IRC (Tottle!5496eb1d@p5496EB1D.dip0.t-ipconnect.de, Remote host closed the connection) | |
| 19:51 | <alkisg> np
| |
| 21:02 | pppingme has left IRC (pppingme!~pppingme@unaffiliated/pppingme, Ping timeout: 240 seconds) | |
| 21:13 | pppingme has joined IRC (pppingme!~pppingme@unaffiliated/pppingme) | |
| 21:25 | pppingme has left IRC (pppingme!~pppingme@unaffiliated/pppingme, Ping timeout: 240 seconds) | |
| 23:29 | pppingme has joined IRC (pppingme!~pppingme@unaffiliated/pppingme) | |