IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 14 April 2022 (all times are UTC)
| 03:13 | vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20, Quit: leaving) | |
| 06:42 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 14:29 | vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20) | |
| 16:21 | lucascastro has joined IRC (lucascastro!~lucascast@192-140-51-210.static.oncabo.net.br) | |
| 18:40 | jeremy_walker has joined IRC (jeremy_walker!~jeremy_wa@14.96.108.88) | |
| 18:41 | <jeremy_walker> LTSP clients don't register their hostnames with the DNS server on the network, is there a way to fix that? The LTSP server is running DNSMASQ, but DHCP is provided by a router on the network.
| |
| 18:50 | <alkisg> jeremy_walker: if you're using real dhcp and not proxydhcp, you can add their names to dnsmasq
| |
| 18:50 | Ah, proxy
| |
| 18:51 | Then no, you'll need to add dns entries in dnsmasq, not dhcp entries
| |
| 18:51 | And of course there's also mdns (ping ltsp123.local)
| |
| 18:54 | lucascastro has left IRC (lucascastro!~lucascast@192-140-51-210.static.oncabo.net.br, Remote host closed the connection) | |
| 18:54 | <jeremy_walker> I have HOSTNAME=c%{IP} configured under the [clients] section in /etc/ltsp/ltsp.conf. The DHCP service is provided by the network router. Since the hostname is set after the client gets the DHCP lease, I guess the network DNS does not receive the hostname and thus doesn't know about it.
| |
| 18:55 | <alkisg> Yup
| |
| 18:56 | <jeremy_walker> I reckon there's really no simple way around that
| |
| 18:56 | <alkisg> Also ipconfig doesn't do DNS updates anyway; you'd need to configure that on the server, not on the client
| |
| 18:56 | (on the DHCP/DNS server, that is)
| |
| 18:56 | lucascastro has joined IRC (lucascastro!~lucascast@192-140-51-210.static.oncabo.net.br) | |
| 18:56 | <jeremy_walker> ipconfig? Isn't that a windows command?
| |
| 19:01 | Btw, there does seem to be a (presumably silly) workaround. One could in theory just run the dhclient command again in some init script. That would cause the client to re-acquire the DHCP lease, but since by now the client already has a hostname, it will report that hostname to the DHCP server which will in turn update the DNS server
| |
| 19:03 | <quinox> if it works it's not silly :)
| |
| 19:05 | <jeremy_walker> I just tested it manually, by logging in to a LTSP client that was running but not resolving, and running the dhclient command in a terminal. The command ran fine, and a second later, the hostname was resolvable from another machine on the network. I'm using Ubuntu 20.04, so a oneshot systemd service unit that calls dhclient could accomplish the
| |
| 19:05 | desired result.
| |
| 19:06 | <vagrantc> it could get ugly if the router ends up giving you a different ip address on the second call and assigns your hostname to that
| |
| 19:07 | but there might be options you could pass to dhclient to handle that potential corner-case
| |
| 19:07 | really depends on the DHCP server implementation
| |
| 19:14 | jeremy_walker has left IRC (jeremy_walker!~jeremy_wa@14.96.108.88, Ping timeout: 250 seconds) | |
| 19:26 | woernie has left IRC (woernie!~werner@p5b296e29.dip0.t-ipconnect.de, Ping timeout: 256 seconds) | |
| 19:28 | woernie has joined IRC (woernie!~werner@p5b296e29.dip0.t-ipconnect.de) | |
| 19:32 | <quinox> depending on the DHCP server building a local dyndns kind of thing wouldn't be too hard either
| |
| 20:18 | lucascastro has left IRC (lucascastro!~lucascast@192-140-51-210.static.oncabo.net.br, Remote host closed the connection) | |
| 21:11 | woernie has left IRC (woernie!~werner@p5b296e29.dip0.t-ipconnect.de, Remote host closed the connection) | |
| 22:09 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |