> If Tomasz is doing what we were doing before, this is just changing the> sysctl setting. Very easy to reverse, which within GCE would only make senseOk, so it only is for GCE and nothing else then and in the plugin for GCE?
> to do if you wanted to use IPv6 within Linux's internal networking stack
> (e.g. use LXC within the VM and have the different containers communicate
> over IPv6).
Well, that is unfortunate but a useful solution then.
> Even now, not all software reacts well when IPv6 is enabled but notOk, good to know, as IPv6 is important for me.
> available. We encountered real-world cases where this caused a bad user
> experience, fixed by disabling IPv6. (I'd have to look up the details - this
> was a while ago.) Of course it makes sense to enable IPv6 wherever that is
> available, but unfortunately that's not currently supported in the GCE
> network.
Would be good to know what software and what problem it was, if you
have time to look it up, and if not just ignore it. Just curious. ;-)
> - Jimmy
/Anders
Archive: [🔎] CACXJ-BjB9kKjS=p2kvAF6PhZzJUrCC1iAMubQ5GkJP0kh49BYw@mail.gmail.com" target="_blank">https://lists.debian.org/[🔎] CACXJ-BjB9kKjS=p2kvAF6PhZzJUrCC1iAMubQ5GkJP0kh49BYw@mail.gmail.com
--
To UNSUBSCRIBE, email to debian-cloud-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org