sudo systemctl enable dhcpcd.service
Now I can ping the workstation by both name and ip address and the dhcp log shows the network name being correctly assigned.
]]>sudo systemctl restart dhcpcd
It all works correctly:
Jan 8 09:05:28 shorewall dhcpd: DHCPDISCOVER from 00:26:82:5d:d1:bd via br0
Jan 8 09:05:28 shorewall dhcpd: Abandoning IP address 192.168.0.218: pinged before offer
Jan 8 09:05:31 shorewall dhcpd: DHCPDISCOVER from 00:26:82:5d:d1:bd via br0
Jan 8 09:05:32 shorewall dhcpd: DHCPOFFER on 192.168.0.219 to 00:26:82:5d:d1:bd (sooty) via br0
Jan 8 09:05:32 shorewall named[10976]: client 192.168.0.1#60355: signer "rndc-key" approved
Jan 8 09:05:32 shorewall named[10976]: client 192.168.0.1#60355: updating zone 'bantercat.co.uk/IN': adding an RR at 'sooty.bantercat.co.uk' A
Jan 8 09:05:32 shorewall named[10976]: client 192.168.0.1#60355: updating zone 'bantercat.co.uk/IN': adding an RR at 'sooty.bantercat.co.uk' TXT
Jan 8 09:05:32 shorewall dhcpd: Added new forward map from sooty.bantercat.co.uk to 192.168.0.219
Jan 8 09:05:32 shorewall named[10976]: client 192.168.0.1#47941: signer "rndc-key" approved
Jan 8 09:05:32 shorewall named[10976]: client 192.168.0.1#47941: updating zone '0.168.192.in-addr.arpa/IN': deleting rrset at '219.0.168.192.in-addr.arpa' PTR
Jan 8 09:05:32 shorewall named[10976]: client 192.168.0.1#47941: updating zone '0.168.192.in-addr.arpa/IN': adding an RR at '219.0.168.192.in-addr.arpa' PTR
Jan 8 09:05:32 shorewall dhcpd: added reverse map from 219.0.168.192.in-addr.arpa. to sooty.bantercat.co.uk
Jan 8 09:05:32 shorewall dhcpd: DHCPREQUEST for 192.168.0.219 (192.168.0.1) from 00:26:82:5d:d1:bd (sooty) via br0
Jan 8 09:05:32 shorewall dhcpd: DHCPACK on 192.168.0.219 to 00:26:82:5d:d1:bd (sooty) via br0
As an experiment I set up another Arch install on a separate box connecting via cable. This displays exactly the same symptoms. This leads me to think that either something has changed in the basic Arch setup, or I have made a configuration mistake. I have three other Arch boxes, which have been around sometime and which all play nicely with my DHCP server.
I tried assigning the experimental problem box a fixed ip on the dhcp server, using its mac address. I can now ping this by name. However, if I let the dhcp server assign an address from the pool, I can ping it by ip, but not by name.
]]># Generated by NetworkManager
domain bantercat.co.uk
search bantercat.co.uk
nameserver 192.168.0.1
nameserver 192.168.0.8
Which appears correct.
dhcp servers option-nameservers
option domain-name-servers 192.168.0.1, 192.168.0.8;
I don't think the problem is at the dhcp server end, as all other dhcp clients, including several arch ones, work as expected.
]]>Jan 7 09:15:04 shorewall dhcpd: DHCPREQUEST for 192.168.0.182 from 00:1d:7d:95:b0:da via br0
Jan 7 09:15:04 shorewall dhcpd: DHCPACK on 192.168.0.182 to 00:1d:7d:95:b0:da via br0
Jan 7 09:15:15 shorewall dhcpd: DHCPREQUEST for 192.168.0.129 from 00:01:6c:6c:cb:4c (myth3) via br0
Jan 7 09:15:15 shorewall dhcpd: DHCPACK on 192.168.0.129 to 00:01:6c:6c:cb:4c (myth3) via br0
Jan 7 09:15:51 shorewall dhcpd: DHCPREQUEST for 192.168.0.132 from 00:01:6c:6c:c7:6b (myth2) via br0
Jan 7 09:15:51 shorewall dhcpd: DHCPACK on 192.168.0.132 to 00:01:6c:6c:c7:6b (myth2) via br0
Jan 7 09:15:52 shorewall kernel: [477481.010900] Shorewall:net2fw:DROP:IN=ppp0 OUT= MAC= SRC=46.218.85.108 DST=46.33.134.31 LEN=48 TOS=0x00 PREC=0x00 TTL=119 ID=18789 PROTO=TCP SPT=59436 DPT=22 WINDOW=65535 RES=0x00 SYN URGP=0
Jan 7 09:16:54 shorewall dhcpd: DHCPDISCOVER from 00:26:82:5d:d1:bd via br0
Jan 7 09:16:55 shorewall dhcpd: DHCPOFFER on 192.168.0.218 to 00:26:82:5d:d1:bd via br0
Jan 7 09:16:55 shorewall dhcpd: DHCPREQUEST for 192.168.0.218 (192.168.0.1) from 00:26:82:5d:d1:bd via br0
Jan 7 09:16:55 shorewall dhcpd: DHCPACK on 192.168.0.218 to 00:26:82:5d:d1:bd via br0
The problem computer is 192.168.0.218.
Here is the hosts file:
127.0.0.1 sooty.bantercat.co.uk sooty localhost
::1 sooty localhost
hostname -f on the computer returns the expected result of sooty.bantercat.co.uk.
Since dhcp works correctly for all my other boxes, I am assuming that this is a problem with the configuration on the arch box. However, I can't work out what the problem is.
]]>