This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas]DHCP behaviour of the probe on startup
- Previous message (by thread): [atlas]how big is the limitation imposed by the req. for DHCPv4?
- Next message (by thread): [atlas]DHCP behaviour of the probe on startup
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wilfried Woeber, UniVie/ACOnet
Woeber at CC.UniVie.ac.at
Wed Dec 22 12:28:17 CET 2010
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...
- Previous message (by thread): [atlas]how big is the limitation imposed by the req. for DHCPv4?
- Next message (by thread): [atlas]DHCP behaviour of the probe on startup
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]