[atlas]DHCP behaviour of the probe on startup
Hi folks, while debugging some non-probe-related issues here at my ADSL'd net @home, I was told by the provider's techie, that the probe tries to grab *two* addresses at startup. He was monitoring the ARP table in the router, saw a DHCP request and the address assigned by the DHCP Server, and immediately asfterwards, the probe sent a request for an additional address, which was granted by the server. Trying to verify that, I later found out that I can ping the probe only on the second address. [1] Has anyone seen such a behaviour? Unfortunately, I don't have access to the router (cisco 800 series) as it is fully managed by the ISP, and for my other probe we had the IP-Address hard-wired into the DHCP server for the MAC address. Thanks, Wilfried. [1] this is particularly nasty for home networks with a very small number of addresses available (a bock of 8 in may case) and a long timeout...
On Wed, Dec 22, 2010 at 11:28:17AM +0000, Wilfried Woeber, UniVie/ACOnet wrote:
Hi folks,
while debugging some non-probe-related issues here at my ADSL'd net @home, I was told by the provider's techie, that the probe tries to grab *two* addresses at startup.
I noticed the probe does a BOOTP-request on startup, and later a DHCP-request. Any decent DHCP-server should handle both, and see that is is a repeated request from the same mac-address. Real world implementation may be different, though. Would puzzles me wrt to bootup-behaviour is that I see the initial bootp on both the vlan assigned to the probe and the native lan, i.e. both tagged and untagged. This might however be more related to flaky network equipment. Bye, Joerg
participants (2)
-
Joerg Dorchain
-
Wilfried Woeber, UniVie/ACOnet