[atlas] Network configuration / Multiple VLANs
- Previous message (by thread): [atlas] Network configuration / Multiple VLANs
- Next message (by thread): [atlas] Network configuration / Multiple VLANs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Dario Ciccarone
dario.ciccarone at gmail.com
Wed Feb 26 17:20:22 CET 2014
Then it could be a /30 network, right ? Or even a /31, if both probe and L3 device support RFC-3021 . . . In any case - my suggestion was NOT to deploy the probe on a network segment where, if compromised, could compromise the rest of the network - specially if you're dropping it on a network management / infrastructure segment. On 2/26/14 10:57 AM, "Roman Mamedov" <rm at romanrm.net> wrote: >On Wed, 26 Feb 2014 10:53:39 -0500 >Dario Ciccarone <dario.ciccarone at gmail.com> wrote: > >> FWIW, my probe is sitting on its own "RIPE-ATLAS" VLAN . . . >> >> I have a lot of respect for the RIPE team - but dropping a device from a >> 3rd party, that you *know for a fact* it will get requests for tests >>from >> who-knows-where . . . A bit of a bad idea. >> >> Trust, but verify applies here - segment the probe into its own segment. >> Maybe an IPv6-only one . . . > >AFAIK the probe currently does not support being on an IPv6-only network. >Besides, why voluntarily make it half as useful to the world as it can be. >You got the probe, got IPv4, might as well let the probe measure on >IPv4... > >-- >With respect, >Roman
- Previous message (by thread): [atlas] Network configuration / Multiple VLANs
- Next message (by thread): [atlas] Network configuration / Multiple VLANs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]