Hi, can you please open a bug on https://github.com/lxc/lxc ? Please specify your operating system version and how to reproduce.
Thanks. :) Christian On Wed, Nov 09, 2016 at 01:33:55AM -0500, Saint Michael wrote: > It was working fine until a week ago. > I have two sites, it happened on both, so the issue is not on my router or > my switch, since they are different sites and we did not upgrade anything. > Ubuntu 16.04.1 LTS (GNU/Linux 4.4.0-45-generic x86_64) > LXC installed from apt-get install lxc1 > iptables off in both hosts and containers. I protect my network at the > perimeter. > > All my container networking is defined > > lxc.network.type=macvlan > lxc.network.macvlan.mode=bridge > lxc.network.link=eth1 > lxc.network.name = eth0 > lxc.network.flags=up > lxc.network.hwaddr = XX:XX:XX:XX:XX:XX > lxc.network.ipv4 = 0.0.0.0/24 > > Now suppose I have a machine, not a container, in the same broadcast domain > as the containers, same subnet. > It cannot ping or ssh into a container, which is accessible from outside my > network. > However, from inside the container the packets come and go perfectly, when > the connection is originated by the container. > A container can ping that host I mentioned, but the host cannot ping back > the container. > It all started a few days ago. > Also, from the host, this test works > arping -I eth0 (container IP address) > it shows that we share the same broadcast domain. > > My guess is that the most recent kernel update in the LXC host, is blocking > the communication to the containers, but it allows connections from the > containers or connections from IP addresses not on the same broadcast > domain. > Any idea? > _______________________________________________ > lxc-devel mailing list > lxc-de...@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-devel On Mon, Nov 14, 2016 at 03:18:54AM -0500, Saint Michael wrote: > In LXC networking type phys, the network interface correctly disappears > from the host, but the container never "returns" the device when it gets > stopped, and it never starts again, unless the host is rebooted, since the > device is not there. > I think the device should go back to the host so the container may start > again. > _______________________________________________ > lxc-devel mailing list > lxc-de...@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-devel _______________________________________________ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
