[atlas] Network configuration / Multiple VLANs

Hi,

That's was not much a debate on doing dual stack on the same VLAN (we already do that), but to be able to put the IPv6 interface on a dedicated subnet for this kind of purpose, when you won't do that in your IPv4 network.

I prefer to think where would be the right place for a thing in an IPv6 network rather than planning a network only on the IPv4 constraints. We can all do our IPv6 subnetting based on what we have done in IPv4, but that would mostly be a bad idea.

Regards.


-----Message d'origine-----
De : ripe-atlas-bounces at ripe.net [mailto:ripe-atlas-bounces at ripe.net] De la part de Alex Saroyan
Envoyé : mercredi 26 février 2014 15:05
À : ripe-atlas at ripe.net
Objet : Re: [atlas] Network configuration / Multiple VLANs

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 at romanrm.net] Envoyé : mercredi 26 
> février 2014 14:24 À : Guillaume Sachot Cc : ripe-atlas at ripe.net Objet 
> : Re: [atlas] Network configuration / Multiple VLANs
>
> On Wed, 26 Feb 2014 12:28:14 +0100
> Guillaume Sachot <gsachot at 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
>