dnsmasq.conf with no effect

Rolf-Werner Eilert <[email protected]> Wed, 25 Nov 2020 08:50:43 +0100
Newsgroups gmane.linux.terminal-server.general
Message-ID <[email protected]>
This is a problem under LTSP5 with Ubuntu Mate 18.

To make things short: I have a 2 NIC setup, and on the inner line with 
192.168.67.x is the LTSP network. There is a long list in dnsmasq.conf 
with each client to have fixed MAC-to-IP-to-LTSP numbers (so I am able 
to identify each client).

The list works well, but now I put one of the clients to another lab to 
replace a defective one. The numbers were changed in dnsmasq.conf, but 
the client is still identified under its former IP. Rebooting didn't fix it.

Here is an excerpt of the list. I used 140 to replace 104:

dhcp-host=94:C6:91:14:FC:30,ws001,192.168.67.101,infinite
dhcp-host=94:C6:91:15:F7:3A,ws002,192.168.67.102,infinite
dhcp-host=94:C6:91:15:41:1E,ws003,192.168.67.103,infinite
#dhcp-host=94:C6:91:14:E3:87,ws004,192.168.67.104,infinite
dhcp-host=94:C6:91:15:A8:96,ws004,192.168.67.104,infinite

and down in the list where 140 came from:

#dhcp-host=94:C6:91:15:A8:96,ws040,192.168.67.140,infinite

The strange thing is, the whole setup keeps running as if I had never 
changed anything on dnsmasq.conf. Is there a another list? I couldn't 
find any. One clue might be that from day one, my naming "ws..." was 
ignored and all clients are named "LTSP...". But if dnsmasq.conf doesn't 
have any effect, where have the correct IPs come from since then?

Setting "#" should work as a comment, shouldn't it? (Otherwise down in 
the list the old 140 entry would overwrite the new one above, of course 
that would explain it, but there are lots of more comments in the file...)

Maybe someone here with an idea?

Regards
Rolf


_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net