[lxc-users] Assigning IPv6 to a container + lxc-net config question

[Robert Pendell]

Alright I figured out the lxc-net bits.  I added an upstart job to run when
lxc-net kicks in and to cleanup before lxc-net has a chance to disappear.
This is what I wrote up.  I'm sure there must be a better way but this is
the cleanest route I can find.  I'm always open to suggestions.  On that
note I noticed some promising changes in the future for lxc-net.  Maybe
someone can give me some insight on those plans. :)

description "custom additions for lxc-net"
author "Robert Pendell <shinji at elite-systems.org>"

start on started lxc-net
stop on stopping lxc-net

pre-start script
  (additional addresses -- like ipv6 and routing gets put here)
end script

pre-stop script
  (cleanup that stuff here)
end script

Robert Pendell
shinji at elite-systems.org
A perfect world is one of chaos.
Keybase: http://keybase.io/shinji257

On Thu, May 14, 2015 at 10:55 PM, Robert Pendell <shinji at elite-systems.org>
wrote:

> Thanks for the info.  I ended up going a bit of a different route.
> Since I was planning to manually assign I didn't need radvd or to
> proxy ndp or even neighbor proxy.  I just assigned an ipv6 to the
> lxcbr0 interface then setup ipv6 in the container with the gateway
> pointing at the lxcbr0 ipv6 address.  Oh and of course forwarding was
> enabled.
>
> Anyways I still have my other question unanswered.
>
> What's the best way to add parameters to lxcbr0 like additional ips.
>
> I essentially need to do this somehow at boot time but I don't see a
> way to do this easily without just creating the interface manually in
> the network config
> sudo ip -6 addr add 2600:xxxx:xxxx:4b:0:0:xxxx:1/112 dev lxcbr0
> sudo ip route add to aaa.bbb.ccc.ddd dev lxcbr0
> Robert Pendell
> shinji at elite-systems.org
> A perfect world is one of chaos.
> Keybase: http://keybase.io/shinji257
>
>
> On Thu, May 14, 2015 at 8:31 AM, brian mullan <bmullan.mail at gmail.com>
> wrote:
> > Robert
> >
> > I've been learning how to do this over the past week or so.
> >
> > I've found a few good write-ups which may help you out:
> >
> > I have only found 1 online write-up about LXC & IPv6.    This one seems
> to
> > cover most of the configuration aspects & I thought it was pretty good:
> > LXC Host featuring IPv6 connectivity
> >
> > Although this is not LXC specific it helps gain a good understanding of
> IPv6
> > configuration in Linux & fairly comprehensive in its description of the
> > terms, configuration options, and usage refer to:     IPv6 – Set UP An
> IPv6
> > LAN with Linux
> >
> > Although my own interest was related to using full mesh vpn to
> interconnect
> > lxc containers on remote servers I soon decided IPv6 would make
> everything
> > much easier to implement.
> >
> > This is because unlike IPv4 use for a mesh vpn IPv6 would eliminate any
> > problems with duplicate IP addresses in LXC containers on multiple remote
> > hosts without resorting to figuring out a centralized IPAM solution etc.
> >
> > I'm trying to document what I have done so far with mesh vpn & lxc on my
> > wordpress blog but understand its just a proof-of-concept document and
> > although I've tested it with IPv4 I haven't had time to test IPv6 in the
> > containers yet.   Also, I mention some other caveats
> >
> > Remember this is only a "draft" writeup that I started this week but you
> can
> > read it here:
> >
> > Proof-of-Concept – Using Mesh VPN to interconnect LXC containers on
> Multiple
> > Hosts on Multiple Clouds
> >
> > If anyone takes a look and has any suggestions or config ideas for the
> IPv6
> > and/or LXC information pieces feel free to let me know as I'm just
> beginning
> > with IPv6 myself and still learning more about LXC and linux everyday.
> >
> > Brian
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20150515/f4fc1b7b/attachment.html>