| 1 |
On Tue, 21 Mar 2017 20:25:18 +0100, Kai Krakow wrote: |
| 2 |
|
| 3 |
> If it's systemd-networkd, you could check those logs after the problem |
| 4 |
> occurred: |
| 5 |
> |
| 6 |
> # journalctl -b -u systemd-networkd.service | fgrep -i dhcpv4 |
| 7 |
> |
| 8 |
> Apparently, it doesn't tell you what the DHCP server is by MAC address, |
| 9 |
> but the reported "via" at least tells you the IP. |
| 10 |
> |
| 11 |
> It looks like this: |
| 12 |
> |
| 13 |
> Mar 17 19:21:33 jupiter systemd-networkd[680]: enp5s0: DHCPv4 address |
| 14 |
> 192.168.4.102/24 via 192.168.4.254 |
| 15 |
|
| 16 |
That doesn't appear to be as helpful as you would think, I just tried it |
| 17 |
and got |
| 18 |
|
| 19 |
Mar 21 09:02:56 fenchurch systemd-networkd[495]: wlan0: DHCPv4 address |
| 20 |
192.168.1.6/24 via 192.168.1.42 |
| 21 |
|
| 22 |
Which looks fine and 192.168.1.42 is the address of my router, but that |
| 23 |
router is not my DHCP server. I double checked and |
| 24 |
|
| 25 |
1) DHCP is turned off on the router |
| 26 |
2) The dnsmasq log on my DHCP server box shows it issuing that address at |
| 27 |
that time. |
| 28 |
|
| 29 |
|
| 30 |
-- |
| 31 |
Neil Bothwick |
| 32 |
|
| 33 |
Pedestrians come in two types: Quick or Dead. |
Archives