lxc network error

[huky]

I have two lxc on the same node, one networking normal and the other networking wrong.

# cat /etc/pve/lxc/103.conf
...
net0: name=eth0,bridge=vmbr1,firewall=1,gw=192.168.10.254,hwaddr=0E:BB:3B:B6:A4:E6,ip=192.168.10.70/24,tag=300,type=veth
...

# cat /etc/pve/lxc/202.conf
...
net0: name=eth0,bridge=vmbr1,firewall=1,gw=192.168.10.254,hwaddr=E6:AA:CC:B7:F1:12,ip=192.168.10.102/24,tag=300,type=veth
...
root@node007:~#

the 192.168.10.102 work normal,

# ping 192.168.10.254
PING 192.168.10.254 (192.168.10.254) 56(84) bytes of data.
64 bytes from 192.168.10.254: icmp_seq=1 ttl=255 time=0.931 ms
64 bytes from 192.168.10.254: icmp_seq=2 ttl=255 time=0.866 ms
64 bytes from 192.168.10.254: icmp_seq=3 ttl=255 time=0.758 ms
64 bytes from 192.168.10.254: icmp_seq=4 ttl=255 time=0.746 ms
64 bytes from 192.168.10.254: icmp_seq=5 ttl=255 time=0.756 ms
^C
--- 192.168.10.254 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4055ms
rtt min/avg/max/mdev = 0.746/0.811/0.931/0.078 ms

# ping 192.168.10.70
PING 192.168.10.70 (192.168.10.70) 56(84) bytes of data.
^C
--- 192.168.10.70 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2039ms

but 192.168.10.70 wrong:

# ping 192.168.10.254
PING 192.168.10.254 (192.168.10.254) 56(84) bytes of data.
^C
--- 192.168.10.254 ping statistics ---
16 packets transmitted, 0 received, 100% packet loss, time 15364ms

# ping 192.168.10.70
PING 192.168.10.70 (192.168.10.70) 56(84) bytes of data.
^C
--- 192.168.10.70 ping statistics ---
11 packets transmitted, 0 received, 100% packet loss, time 10244ms

# ping 127.0.0.1
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
^C
--- 127.0.0.1 ping statistics ---
15 packets transmitted, 0 received, 100% packet loss, time 14339ms

how to resolve it?

 

[fiona]

Hi,
what is the OS of the container where it doesn't work? Is the firewall active and is there any rule that might affect the problematic container? What is the output of ip a inside the container?

 

[sb-jw]

Maybe you have a duplicate MAC Address in your Network? Check ip r too.

Did you already tried to stop the Container and start it again or maybe the Node itself?