It is absolutely normal. The host is accessible as usual.
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: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode
DEFAULT group default qlen 1000
link/ether 00:50:56:b1:8e:8a brd ff:ff:ff:ff:ff:ff
3: eth7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode
DEFAULT group default qlen 1000
link/ether 00:50:56:b1:c9:ad brd ff:ff:ff:ff:ff:ff
4: eth0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc mq state
UP mode DEFAULT group default qlen 1000
link/ether 00:50:56:b1:07:4c brd ff:ff:ff:ff:ff:ff
5: eth4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode
DEFAULT group default qlen 1000
link/ether 00:50:56:b1:94:61 brd ff:ff:ff:ff:ff:ff
6: eth8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode
DEFAULT group default qlen 1000
link/ether 00:50:56:b1:a6:3f brd ff:ff:ff:ff:ff:ff
7: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode
DEFAULT group default qlen 1000
link/ether 00:50:56:b1:99:ad brd ff:ff:ff:ff:ff:ff
8: eth5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode
DEFAULT group default qlen 1000
link/ether 00:50:56:b1:83:15 brd ff:ff:ff:ff:ff:ff
9: eth9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode
DEFAULT group default qlen 1000
link/ether 00:50:56:b1:2d:47 brd ff:ff:ff:ff:ff:ff
10: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode
DEFAULT group default qlen 1000
link/ether 00:50:56:b1:c1:ad brd ff:ff:ff:ff:ff:ff
11: eth6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode
DEFAULT group default qlen 1000
link/ether 00:50:56:b1:f2:19 brd ff:ff:ff:ff:ff:ff
On Mon, Nov 7, 2016 at 11:11 AM, Félix Archambault <
[email protected]> wrote:
> 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@it-felix-w530 ~/dotfiles>
>
>
>
> On Mon, Nov 7, 2016 at 10:57 AM, Saint Michael <[email protected]> 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
>> [email protected]
>> http://lists.linuxcontainers.org/listinfo/lxc-users
>>
>
>
>
> --
> Felix Archambault
>
> _______________________________________________
> lxc-users mailing list
> [email protected]
> http://lists.linuxcontainers.org/listinfo/lxc-users
>
_______________________________________________
lxc-users mailing list
[email protected]
http://lists.linuxcontainers.org/listinfo/lxc-users
