<div dir="ltr"><div class="gmail_default" style="font-size:small">It is absolutely normal. The host is accessible as usual.<br></div><div class="gmail_default" style="font-size:small"><br> ip link<br>1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1<br> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00<br>2: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000<br> link/ether 00:50:56:b1:8e:8a brd ff:ff:ff:ff:ff:ff<br>3: eth7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000<br> link/ether 00:50:56:b1:c9:ad brd ff:ff:ff:ff:ff:ff<br>4: eth0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000<br> link/ether 00:50:56:b1:07:4c brd ff:ff:ff:ff:ff:ff<br>5: eth4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000<br> link/ether 00:50:56:b1:94:61 brd ff:ff:ff:ff:ff:ff<br>6: eth8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000<br> link/ether 00:50:56:b1:a6:3f brd ff:ff:ff:ff:ff:ff<br>7: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000<br> link/ether 00:50:56:b1:99:ad brd ff:ff:ff:ff:ff:ff<br>8: eth5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000<br> link/ether 00:50:56:b1:83:15 brd ff:ff:ff:ff:ff:ff<br>9: eth9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000<br> link/ether 00:50:56:b1:2d:47 brd ff:ff:ff:ff:ff:ff<br>10: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000<br> link/ether 00:50:56:b1:c1:ad brd ff:ff:ff:ff:ff:ff<br>11: eth6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000<br> link/ether 00:50:56:b1:f2:19 brd ff:ff:ff:ff:ff:ff<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 7, 2016 at 11:11 AM, Félix Archambault <span dir="ltr"><<a href="mailto:fel.archambault@gmail.com" target="_blank">fel.archambault@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi,<br><br></div><div>I use ubuntu 16.04. I'd look at net dev naming convention and your static configurations<br><br></div><div>for instance:<br><br>ip link:<br><br>1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1<br> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00<br>2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_<wbr>UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000<br> link/ether 3c:97:0e:e7:5b:04 brd ff:ff:ff:ff:ff:ff<br>3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_<wbr>UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000<br> link/ether e0:9d:31:09:96:9c brd ff:ff:ff:ff:ff:ff<br>archf@it-felix-w530 ~/dotfiles> <br><br><br></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Mon, Nov 7, 2016 at 10:57 AM, Saint Michael <span dir="ltr"><<a href="mailto:venefax@gmail.com" target="_blank">venefax@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr"><div>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.<br><br></div><div>My networking at the container level is:<br><br>lxc.network.type=macvlan<br>lxc.network.macvlan.mode=bridg<wbr>e<br>lxc.network.link=eth0<br><a href="http://lxc.network.name" target="_blank">lxc.network.name</a> = eth1<br>lxc.network.flags=up<br>lxc.network.hwaddr = mac.add.re.ss<br>lxc.network.ipv4 = <a href="http://0.0.0.0/24" target="_blank">0.0.0.0/24</a><br></div><br><div>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.<br></div><div>Any idea?<br></div><div><br></div><br></div>
<br></div></div>______________________________<wbr>_________________<br>
lxc-users mailing list<br>
<a href="mailto:lxc-users@lists.linuxcontainers.org" target="_blank">lxc-users@lists.linuxcontainer<wbr>s.org</a><br>
<a href="http://lists.linuxcontainers.org/listinfo/lxc-users" rel="noreferrer" target="_blank">http://lists.linuxcontainers.o<wbr>rg/listinfo/lxc-users</a><span class="HOEnZb"><font color="#888888"><br></font></span></blockquote></div><span class="HOEnZb"><font color="#888888"><br><br clear="all"><br>-- <br><div class="m_-4527691390842705525gmail_signature" data-smartmail="gmail_signature">Felix Archambault</div>
</font></span></div></div>
<br>______________________________<wbr>_________________<br>
lxc-users mailing list<br>
<a href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.<wbr>linuxcontainers.org</a><br>
<a href="http://lists.linuxcontainers.org/listinfo/lxc-users" rel="noreferrer" target="_blank">http://lists.linuxcontainers.<wbr>org/listinfo/lxc-users</a><br></blockquote></div><br></div>