[atlas]how big is the limitation imposed by the req. for DHCPv4?
Folks, I'd like to collect input from those interested in principle to deploy groups of probes within their operational environment(s), regarding the requirement to have DHCPv4 available in order to configure the probe (for IPv4). I already came up with a coupe of locations and environments, where such a cute thing would be nice to have, but in most (if not all) of these places, there is no DHCP available (and for good reasons). As an aside to the developers, would it be feasable to connect the probe in network A, configure it for the destination network and then move it over to network B for its happy life? Cheers, Wilfried.
On 21/12/2010 18:30, Wilfried Woeber, UniVie/ACOnet wrote:
Folks,
I'd like to collect input from those interested in principle to deploy groups of probes within their operational environment(s), regarding the requirement to have DHCPv4 available in order to configure the probe (for IPv4).
I already came up with a coupe of locations and environments, where such a cute thing would be nice to have, but in most (if not all) of these places, there is no DHCP available (and for good reasons).
As an aside to the developers, would it be feasable to connect the probe in network A, configure it for the destination network and then move it over to network B for its happy life?
Yes, this is something that was requested by more people, so it is on our list. Our current thinking is along the same lines as what you suggest above. best regards, Emile Aben RIPE NCC
participants (2)
-
Emile Aben -
Wilfried Woeber, UniVie/ACOnet