On Wed, Nov 07, 2012 at 10:36:14AM +0100, Philip Homburg wrote:
When a probe knows it probe ID, it changes its DHCP client-id. See https://atlas.ripe.net/faq#how-does-the-probe-connect
Thanks for the suggestion - I had seen that but didn't have the stanza matching by client ID as I didn't think it was necessary (MAC address alone should be sufficient, I would've thought?). I have added it now, but it hasn't helped.
Maybe you can capture the dhcp traffic with tcpdump to see if the server sends something the probe doesn't like?
Sure. I've placed a copy of the the request/reply at http://dl.rsx11.net/misc/atlas_probe_dhcp.txt. I've redacted the MAC addresses (aa:bb:cc... is the MAC of the probe) but everything else is unchanged. I don't see anything unusual - please let me know if you'd like a copy of the raw tcpdump output. I also received an off-list suggestion regarding a possible duplicate IP so I've changed the IP assigned to the probe without it making any difference. Not sure if it makes a difference, but I do also have rtavd and DHCPv6 servers running on the same network (IPv6 connectivity to/from the probe was working fine until this problem started). -mj -- Michael-John Turner mj@mjturner.net <> http://mjturner.net/