[atlas] BOOTP/DHCP on a probe with static network configuration

On 13-June-2013, Jay Borkenhagen writes:
 > Hi,
 > 
 > I have two brand new RIPE Atlas probes.  Both are reported as
 > 'connected' on my My Atlas page, both run the 4520 firmware, and both
 > correctly report and use the static network configurations I gave them
 > per the instructions at https://atlas.ripe.net/doc/static-config
 > 
 > However, both probes still send BOOTP/DHCP requests every 3 seconds. 
 > 
 > Are others seeing this behavior with their probes that have static
 > network configurations?  Can this behavior be changed?
 > 

Hi again,

Philip from the RIPE Atlas team replied to a query I sent to
atlas at ripe.net:

 > The way it is supposed to work is that the probe verifies its
 > static config by pinging the configured default router. When that
 > works (i.e., the ping results in an ARP entry), the probe kills the
 > dhcp client.

 > I have no idea why that doesn't work in your case.

I've tried making some minor configuration adjustments with the above
in mind, but no change.

For some admittedly silly reasons, this minor nit is something I will
need to address.  But before I set about doing that, I would really
like to know whether anyone else is seeing the same behavior:
continual DHCP requests being emitted from their RIPE Atlas probes
with static network configuration.

FWIW my probes are both version 3 (Architecture TP-Link) running
Firmware Version 4520.

Thanks.

						Jay B.