Request for RIPE Atlas probe DHCP change.
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. -- Leo Bicknell - bicknell@ufp.org - CCIE 3440 PGP keys at http://www.ufp.org/~bicknell/
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.
Yes, that you be possible. I'll look into getting this changed.
Good idea! +1 (Sent from my mobile device) Anurag Bhatia http://anuragbhatia.com On Apr 21, 2012 3:48 PM, "Philip Homburg" <philip.homburg@ripe.net> wrote:
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.
Yes, that you be possible. I'll look into getting this changed.
+1 and if it is not too complicated include the probe-id please. Daniel host to more than 1 probe On 21.04.2012, at 12:18, Philip Homburg wrote:
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.
Yes, that you be possible. I'll look into getting this changed.
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.
In a message written on Mon, Apr 23, 2012 at 03:31:48PM +0200, Philip Homburg wrote:
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.
Client ID is what most of the home gateways present. I can think of three ways it could be done: 1) Just use "ripeatlas" or a similar fixed string, and yes, there will be "collisions". Plenty of other devices use this method and they seem to work, although it's not the most RFC-complaint way to do things. 2) Use a fixed string and part of the MAC. I've seen a number of embedded devices use this method. "atlas-12:AB:56" or similar. 3) Actually set it based on the probe ID. I think this would be the coolest option. "atlas-1234" or similar. I would think this could be super-useful for folks setting up and testing more than one probe, since all of the UI references them by probe ID. I've never seen a home gateway display vendor class, but setting it properly would also be a nice thing to do. :) -- Leo Bicknell - bicknell@ufp.org - CCIE 3440 PGP keys at http://www.ufp.org/~bicknell/
participants (4)
-
Anurag Bhatia -
Daniel Karrenberg -
Leo Bicknell -
Philip Homburg