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]DHCP behaviour of the probe on startup
- Next message (by thread): [atlas]Geo-location
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Joerg Dorchain
joerg at dorchain.net
Wed Dec 22 12:36:07 CET 2010
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 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 267 bytes Desc: Digital signature URL: </ripe/mail/archives/ripe-atlas/attachments/20101222/1e4644ab/attachment.sig>
- Previous message (by thread): [atlas]DHCP behaviour of the probe on startup
- Next message (by thread): [atlas]Geo-location
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]