IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 5 June 2022 (all times are UTC)
| 02:09 | vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20, Quit: leaving) | |
| 14:06 | vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20) | |
| 14:25 | Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Quit: Ping timeout (120 seconds)) | |
| 14:26 | Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas) | |
| 17:10 | <daniel891[m]> Now I was testing on phisical devices cause its working fine with a vm as client. But for some reason it doesnt go any further the dhcp. Any idea what could be the problem?
| |
| 17:52 | <vsuojanen[m]> Hi, i can try to help some, how did you setup The server nic interfaces?
| |
| 17:52 | Proxydhcp or real DHCP?
| |
| 18:21 | <daniel891[m]> Proxydhcp. And it seems that works but after trying at least 3 times. So I guess its just a very slow dhcp server?
| |
| 18:30 | <vsuojanen[m]> Is it virtualbox vm?
| |
| 18:49 | i had client machines that did not boot from My ltsp server on a laptop in hyper-v vm, vm was uefi. It just never received DHCP broadcast from The clients. The Client machines work fine elsewhere without hyper-v vm. I think it's The vm fault
| |
| 19:15 | <daniel891[m]> I tried ltsp server on vms and on my bare pc and ltsp clients on vms and bare machines. I have the problem on bare machine clients
| |
| 19:24 | <vsuojanen[m]> use systemctl status dnsmasq.service to follow up pxe on The server and You can see If the DHCP server sends The client pxe to tour server and offered pxe to The DHCP offer
| |
| 19:28 | If that doesn't show specific clients when They boot then problems are on The hardware/firmware
| |
| 19:30 | Assuming that other clients/vm clients in The same network boot succesful
| |