04:00 | vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20, Quit: leaving) | |
04:06 | quinox has left IRC (quinox!~quinox@ghost.qtea.nl, Quit: WeeChat 3.5) | |
04:08 | quinox has joined IRC (quinox!~quinox@ghost.qtea.nl) | |
05:38 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
05:45 | woernie has joined IRC (woernie!~werner@pd9e8b6c1.dip0.t-ipconnect.de) | |
05:57 | <alkisg> muhwalt: I just tested Ubuntu 22.04 with proxyDHCP+UEFI, it worked fine; something else is wrong at your side
| |
07:12 | woernie has left IRC (woernie!~werner@pd9e8b6c1.dip0.t-ipconnect.de, Ping timeout: 264 seconds) | |
07:12 | woernie has joined IRC (woernie!~werner@p5ddec136.dip0.t-ipconnect.de) | |
07:26 | woernie has left IRC (woernie!~werner@p5ddec136.dip0.t-ipconnect.de, Quit: http://quassel-irc.org - Chat comfortably. Anywhere.) | |
07:28 | woernie has joined IRC (woernie!~werner@p5ddec136.dip0.t-ipconnect.de) | |
11:18 | <muhwalt> ugh, great. thanks!
| |
12:03 | shored1 has left IRC (shored1!~shored@user/shored, Quit: ZNC 1.8.2+deb2 - https://znc.in) | |
12:04 | shored has joined IRC (shored!~shored@user/shored) | |
12:11 | eu^186-224-38-18 has joined IRC (eu^186-224-38-18!~eu^186-22@186-224-38-18.ftth.medianeira.com.br) | |
12:12 | eu^186-224-38-18 has left IRC (eu^186-224-38-18!~eu^186-22@186-224-38-18.ftth.medianeira.com.br, Client Quit) | |
13:16 | <muhwalt> alkisg: is your 22.04 environment from the official installer or ubuntu-mate.org?
| |
13:35 | vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20) | |
14:20 | <muhwalt> nvm, seeing the same behavior in a "normal" 22.04 install, which I figured would be the case
| |
14:22 | <alkisg> muhwalt: I'm online now if you need any help. So to summarize, you're able to netboot all BIOS devices, but no UEFI devices, either VM or real ones?
| |
14:31 | <muhwalt> bios ones blow up too
| |
14:31 | It's a goofy setup. I'm assuming it's something to do with my net config
| |
14:32 | bios clients get the bootfile name, but fail to load it
| |
14:32 | ltsp is a libvirt VM on a 22.04 server host... with a bunch of bridges to different vlans
| |
14:33 | I had a lot of trouble getting that set up on 22.04 vs 20.04 or 18.04
| |
14:33 | <alkisg> Does that mean that 20.04 and 18.04 worked fine, while 22.04 has the issue?
| |
14:34 | <muhwalt> So, I know I tested with 20.04 on a bench, but that wasn't a complicated network set up like this one
| |
14:34 | that was basically it's own little network
| |
14:34 | <alkisg> OK then let's assume for now that this isn't related to any OS or LTSP versions, and it's just an issue with your VM setup
| |
14:34 | <muhwalt> *but* I set up a similar network stack on an 18.04 server, with a 22.04 VM and a coworker got it to work
| |
14:35 | <alkisg> !tftp
| |
14:35 | <ltspbot`> tftp: 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
| |
14:35 | <muhwalt> (with ltsp on the 22.04 VM)
| |
14:35 | I'm able to download the images, yes
| |
14:35 | from a different vlan even
| |
14:36 | <alkisg> Didn't you say that BIOS clients won't read from tftp?
| |
14:36 | <muhwalt> they complain about not being able to reach the host
| |
14:36 | despite being on the same vlan/network 🤷
| |
14:36 | I'm putting a full system on that net now to dig into it
| |
14:36 | <alkisg> Right, so boot them from a live CD and see if they can reach tftp
| |
14:39 | <muhwalt> can't even ping the box from the same network outside of the VM host 🤣
| |
14:39 | it's weird how broadcasts seem to in/out
| |
14:39 | I'm sure I just have some goofy firewall rule
| |
14:40 | s/box/ltspserver
| |
14:44 | I'm like 3 switches away from it to... I bet I have my vlan config screwed up
| |
14:44 | Sigh. Thanks for your insight. Sorry it didn't have anything to do with LTSP, probably
| |
14:45 | <alkisg> Yeh, I'd suggest that you test without LTSP and resolve all those issues before testing netbooting, as it's more difficult to test there
| |
14:45 | 👍️
| |
14:45 | <muhwalt> That's what's funny... from another vlan/network... everything is accessible 🤷
| |
15:48 | well, it was my link aggregation settings on the switch. LACP wasn't enabled, so the bond wasn't negotiating properly
| |
15:49 | Hopefully no one heard the long stream of obscenities being said from my office 🤣
| |
15:51 | I guess the bond and the switch were playing random interface roulette and things just randomly got lost
| |
16:00 | both bios and efi clients work fine now
| |
16:01 | Again, thanks for your help troubleshooting. It really didn't seem like it could be a networking issue, given I could access both the host and the ltsp vm... very odd behavior
| |
16:05 | <alkisg> Great, all good :)
| |
17:54 | <vagrantc> heh. heard rumours of LTSP by the sea in november ...
| |
18:07 | anyone know how to get a hold of jim or scotty?
| |
18:07 | their @ltsp.org addresses bounce
| |
18:11 | * vagrantc tries another address | |
18:18 | shored1 has joined IRC (shored1!~shored@user/shored) | |
18:19 | shored has left IRC (shored!~shored@user/shored, Ping timeout: 246 seconds) | |
19:21 | Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection) | |
19:21 | Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas) | |
19:39 | <muhwalt> I have userlist in lightdm disabled, and it doesn't show up on server, but it keeps appearing on client's lightdm (the manual login shows up too)... is there some trick to this?
| |
19:39 | I don't want the user list on clients, to be clear
| |
19:41 | (i'm certain I've run both `ltsp image /` and `ltsp initrd` since disabling it
| |
19:42 | oh, I see custom lightdm settings in ltsp.conf now
| |
20:16 | <alkisg> vagrantc: no idea, I did leave the mx records of ltsp.org as they were, but I don't know if they would still work or not
| |
20:16 | muhwalt: it's documented in ltsp.conf
| |
20:16 | !ltsp.conf
| |
20:16 | <ltspbot`> ltsp.conf: Configuration file for LTSP: https://ltsp.org/man/ltsp.conf/
| |
20:16 | <alkisg> LIGHTDM_CONF="greeter-hide-users=true"
| |
21:05 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
21:41 | shored has joined IRC (shored!~shored@user/shored) | |
21:42 | shored1 has left IRC (shored1!~shored@user/shored, Ping timeout: 272 seconds) | |
23:47 | vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20, Quit: leaving) | |