On 2016-06-09 12:10, Rainer Weikusat wrote:
[snip]
> The additional two lines disable the spanning-tree protocol. That's
> usually sensible unless one deal with a complicated, physicial topology
> which may or does contain loops. Then, it's needed so that the bridge
> can work out a loop-less v
Simon Walter writes:
> After some testing, I have a question about an option in
> /etc/default/shorewall:
> wait_interface
> If I add the bridge interface to that line, shorewall will not start
> unless a container is brought up. I suppose that is why I was thinking
> of bridging the bridge inerfa
