I tracked the issue down to the following point: Networking works only for native containers with my usual local setup made up of a bridge configured in /etc/network/interfaces, dnsmasq listing on that bridge and arno-iptables-firewall doing the masquerading and forwarding.
Networking works for native and armhf containers with using lxc-net and my firewall disabled. Networking fails for native and armhf containers with using lxc-net and my firewall enabled. So my questions are: What's the difference between using lcx-net alone and my home-grown setup (which works perfectly well also for qemu and virtualbox VMs) with regards to non-native containers? Does lxc-net anything specific regarding a containers architecture? Should this be a bug against lxc then? Off-topic: At present my email provider does not handle sender validiation properly, so the mail server for debian.org refuses my mails. Luckily they are accepted at bugs.debian.org. Sven
signature.asc
Description: This is a digitally signed message part
