Hi, I only saw your replies in the mailing archives, I probably was not signed up to the list correctly when you answered. The issue is resolved now but that is why I am breaking my own thread.
> what about bridging the real interface that you want to use for the mesh > in the container and then load batman-adv inside LXC ? this is in fact what I tried first. But bridiging the interface causes the batman-adv information in /sys/class/net to get lost. Maybe because I have to do things in a different order or because veth is really not the right interface type. > > I started by loading batman-adv on the host and bridging it into the > > container. After adding the interfaces inside the container where > > meshing should happen I cannot add a gateway because batctl > > complains that /sys/class/net/bat0/mesh does not exist. Indeed, in > > the container it does not exist. > > > > How can batman-adv be used from an lxc-container? > What I usually did was configuring batman-adv properly on the host via > batctl. And only in the end adding it to the lxc-container. That > seemed to work for me (except the reboot crash noted above). what do you mean by "adding it to the lxc container"? I tried bridging the bat0 interface into the container as a separate nic. That did not yield positive results. Unfortunately if I risk crashing the host, this option is not viable for me yet as I cannot simply restart the machine once it crashed. Christof -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments
signature.asc
Description: This is a digitally signed message part.
