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

[Félix Archambault]

Hi,

I use ubuntu 16.04. I'd look at net dev naming convention and your static
configurations

for instance:

ip link:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP mode DEFAULT group default qlen 1000
    link/ether 3c:97:0e:e7:5b:04 brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP
mode DORMANT group default qlen 1000
    link/ether e0:9d:31:09:96:9c brd ff:ff:ff:ff:ff:ff
archf at it-felix-w530 ~/dotfiles>



On Mon, Nov 7, 2016 at 10:57 AM, Saint Michael <venefax at gmail.com> wrote:

> ​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
>



-- 
Felix Archambault
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20161107/e1ef63a0/attachment.html>