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] Request for RIPE Atlas probe DHCP change.
- Previous message (by thread): [atlas] Request for RIPE Atlas probe DHCP change.
- Next message (by thread): [atlas] Request for RIPE Atlas probe DHCP change.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Mon Apr 23 15:31:48 CEST 2012
On 4/21/12 1:02 , Leo Bicknell wrote: > Could the RIPE Atlas probe DHCP client please be configured to send > a ClientID, perhaps "RIPEAtlasProbe"? > > Many home gateways show a list of DHCP clients and list the client ID. > It would make it much easier to identify which device is which using > these tools. > Looking into it. Client ID or Vendor Class? You are not supposed to set Client ID to something generic because it has to unique identify the device. Vendor Class is safe. For Daniel, I changed the Vendor Class for probe 19.
- Previous message (by thread): [atlas] Request for RIPE Atlas probe DHCP change.
- Next message (by thread): [atlas] Request for RIPE Atlas probe DHCP change.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]