Hi, You don't need to waste IPv4, just enable IPv6 in vlan where you already have IPv4 running. This is common deployment way - dual stack. And you don't waste IPv4 in this case. Regards. /Alex Saroyan On 02/26/2014 05:54 PM, Guillaume Sachot wrote:
You don't have a "guest" VLAN for "here any visitor can plug in their laptop, and have internet-only (no internal services whatsoever) IPv4+IPv6 access"? The guest network is WiFi based.
Also having IPv4 and IPv6 in separate VLANs seems like a sign that whoever did the v6 deployment had little idea of wtf they are even doing. I wonder if many people have such a wretched configuration that it would warrant adding the whole VLAN option to the interface. That's a bit presumptuous. Maybe the IPv6 VLAN is dedicated to this kind of external probes, and that we don't want to waste IPv4 by creating a dedicated one for the IPv4 counterpart when it can be put on an existing public range.
-----Message d'origine----- De : Roman Mamedov [mailto:rm@romanrm.net] Envoyé : mercredi 26 février 2014 14:24 À : Guillaume Sachot Cc : ripe-atlas@ripe.net Objet : Re: [atlas] Network configuration / Multiple VLANs
On Wed, 26 Feb 2014 12:28:14 +0100 Guillaume Sachot <gsachot@oceanet-technology.com> wrote:
I also thought of that, but I cannot adapt a datacenter network only for one probe :) You don't have a "guest" VLAN for "here any visitor can plug in their laptop, and have internet-only (no internal services whatsoever) IPv4+IPv6 access"? Just place the probe into that same VLAN, it can't be trusted as it communicates with an external server and unconditionally accepts firmware upgrades from it anyway.
Also having IPv4 and IPv6 in separate VLANs seems like a sign that whoever did the v6 deployment had little idea of wtf they are even doing. I wonder if many people have such a wretched configuration that it would warrant adding the whole VLAN option to the interface.
-- With respect, Roman