Hi Paul, thanks for responding. I actually quoted the ticket earlier in this thread, but it says no more than what you said.
Do you have access to the Hetzner "robot" for this container? Hetzner by default assigns each physical host a 64-block of IPv6 addresses, and a specific IPv6 address to use as the gateway. Then we would need to know how the LAN for the VMs inside the container is configured. I am clueless about how all those things work in IPv6. Ian's code from interfaces that you quoted is probably handling all of those things, but I'm guessing that the actual addresses were never updated when we moved to the new container. Also, all the things Ian is doing manually probably can be done much more simply in a modern OS. Then again, this isn't exactly a modern OS. It's Debian Lenny, which has been unsupported for almost 2.5 years. Weren't we going to update this server to Ubuntu LTS so that it would quit going EOL on us so often? Thanks, YItz On Wed, Jun 11, 2014 at 8:56 PM, Paul Heinlein <[email protected]> wrote: > On Wed, 11 Jun 2014, Yitzchak Gale wrote: > >> We received a report of trouble with IPv6 on c.h.o.: >> >> http://rt.haskell.org/Ticket/Display.html?id=1795 > > > I don't have an RT login, so I can't see the ticket, but I can verify that > IPv6 from lun is broken. > > The IPv6 gateway is not reachable via ping6. I don't know the process by > which lun was assigned its static IPv6 address, so I'm unclear what would > break if we turned on autoconf. > > Here are the bits in /etc/network/interfaces: > > iface eth0 inet6 static > address 2a01:4f8:121:6::1:10 > netmask 64 > pre-up echo 0 > /proc/sys/net/ipv6/conf/eth0/autoconf > up ip -6 route add 2a01:4f8:121::1 dev eth0 > up ip -6 route add default via 2a01:4f8:121::1 > down ip -6 route del default via 2a01:4f8:121::1 > down ip -6 route del 2a01:4f8:121::1 dev eth0 > > -- > Paul Heinlein Galois, Inc. > Systems Administrator 421 SW Sixth Avenue, Suite 300 > [email protected] Portland, Oregon 97204 > +1 503 626-6616 x140 http://corp.galois.com/ _______________________________________________ haskell-infrastructure mailing list [email protected] http://community.galois.com/mailman/listinfo/haskell-infrastructure
