[lxc-users] Something catastrophic just happened to LXC networking

[Saint Michael]

I am not complaining about the master host, I cannot contact the containers
from the same network. That is the issue. The host is irrelevant. This
issue cannot be. It voids the whole technology.

On Mon, Nov 7, 2016 at 10:11 PM, Christian Tardif <
christian.tardif at servinfo.ca> wrote:

> Just want to point out that the restriction only occurs between the host
> and its containers. Outside of it, it can talk without problems.
> ------------------------------
>
> *Christian Tardif*
>
>
>
> ------ Message d'origine ------
> De: "Christian Tardif" <christian.tardif at servinfo.ca>
> À: "LXC users mailing-list" <lxc-users at lists.linuxcontainers.org>
> Envoyé : 2016-11-07 22:09:40
> Objet : Re: [lxc-users] Something catastrophic just happened to LXC
> networking
>
> This is normal behavior with both macvlan's and ipvlan's
>
> Even if I have seen it working a few times, I can't explain the exact
> details. But normally, MACVLAN and IPVLAN do not support communications
> from and to the master host:
>
> https://people.netfilter.org/pablo/netdev0.1/papers/IPVLAN-
> The-beginning.pdf
>
> ------------------------------
>
> *Christian Tardif*
>
>
>
> ------ Message d'origine ------
> De: "Saint Michael" <venefax at gmail.com>
> À: "LXC users mailing-list" <lxc-users at lists.linuxcontainers.org>
> Envoyé : 2016-11-07 10:57:43
> Objet : [lxc-users] Something catastrophic just happened to LXC networking
>
> ​Since the last update to Ubuntu, now I cannot ping or ssh into any
> container, from the same network. It seems the packets go to the router​,
> for I can ping and communicate to the containers from outside my network.
> This problem did not happen until a few days ago.
>
> My networking at the container level is:
>
> lxc.network.type=macvlan
> lxc.network.macvlan.mode=bridge
> lxc.network.link=eth0
> lxc.network.name = eth1
> lxc.network.flags=up
> lxc.network.hwaddr = mac.add.re.ss
> lxc.network.ipv4 = 0.0.0.0/24
>
> ​on the host, the interface eth0 is also used by the host, but I tried
> with another interface which is UP but it has no IP, and it still does not
> allow me to reach my containers, in fact taking my business down since I
> execute a lot of stuff remotely.
> Any idea?
>
> ​
>
>
> _______________________________________________
> lxc-users mailing list
> lxc-users at lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20161107/0c012781/attachment.html>