Running TonidoPlug app in lxc on Arch Linux Arm

[phireph0x]

I've recently stumbled across an older post where a user described getting the TonidoPlug OS and app running in an LXC container in ALARM. I'm trying to do this myself on my TonidoPlug (1), whereas the user had a gen 2 TonidoPlug. http://archlinuxarm.org/forum/viewtopic.php?f=30&t=5098

The step that's confounding me is the bridged network interface -- whenever I start the br0 interface, eth0 stops responding and I lose access to the plug. I have to manually reboot to get it back up and running. Is there something I'm missing regarding configuring a bridged interface for LXC containers? Thanks.

[WarheadsSE]

If possible, consider using a tap. But, using a bridge, you have to have your primary OS also using that bridge. It's how they work.

[phireph0x]

$this->bbcode_second_pass_quote('WarheadsSE', 'I')f possible, consider using a tap. But, using a bridge, you have to have your primary OS also using that bridge. It's how they work.

[pepedog]

Why didn't you look at example /etc/netctl/examples/bridge?
BindsToInterfaces=(eth0)
brackets!!!

[phireph0x]

$this->bbcode_second_pass_quote('pepedog', 'W')hy didn't you look at example /etc/netctl/examples/bridge?
BindsToInterfaces=(eth0)
brackets!!!

[phireph0x]

Including the parens (eth0) made no difference and the network still hangs.

[phireph0x]

Any other ideas as to why the bridge device is causing eth0 to halt? The guide for LXC containers seems to assume that the user is on a typical desktop/laptop/server with console access instead of a headless device such as the TonidoPlug.

[moonman]

Ssh daemon may be bound to whatever interfaces were up when it started. The solution to test may be a script that you run within "screen" that enables the bridge and then restarts the sshd. Don't know if it will work though. Another solution is to make the changes permanent and then reboot. But then if you make a mistake you end up with an unaccessible device.
The best solution is to get a serial.

[WarheadsSE]

Essentially, your bridge is taking over eth0, thus essentially disconnecting all services from that interface. Your OS will need to be configured to also use the br0 interface. Like I said.

Consider spawning a tap, or use not eth0, but an alias like eth0:1 etc.