You have been subscribed to a public bug: Using version 2.0.3-0ubuntu2~ubuntu16.04.1~ppa1
I created a container, and then put a tagged vlan on top of lxdbr0 so that I can talk to the host and other containers on a second network. I gave the host's lxdbr0.1215 an IP address, and made eth0.1215 in the container also with its own IP address. After removing the container, I can still ping the address on the VLAN! It also responds with duplicates: $ arping -I lxdbr0.1215 192.168.15.20 ARPING 192.168.15.20 from 192.168.15.1 lxdbr0.1215 Unicast reply from 192.168.15.20 [00:16:3E:B1:9B:0C] 0.599ms Unicast reply from 192.168.15.20 [00:16:3E:B1:9B:0C] 0.607ms Unicast reply from 192.168.15.20 [00:16:3E:B1:9B:0C] 0.609ms Unicast reply from 192.168.15.20 [00:16:3E:B1:9B:0C] 0.534ms Unicast reply from 192.168.15.20 [00:16:3E:B1:9B:0C] 0.541ms $ ping 192.168.15.20 PING 192.168.15.20 (192.168.15.20) 56(84) bytes of data. 64 bytes from 192.168.15.20: icmp_seq=1 ttl=64 time=0.108 ms 64 bytes from 192.168.15.20: icmp_seq=1 ttl=64 time=0.126 ms (DUP!) 64 bytes from 192.168.15.20: icmp_seq=1 ttl=64 time=0.144 ms (DUP!) 64 bytes from 192.168.15.20: icmp_seq=2 ttl=64 time=0.051 ms Bizarrely: $ nmap 192.168.15.20 Starting Nmap 7.01 ( https://nmap.org ) at 2016-07-21 19:01 AEST Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn Nmap done: 1 IP address (0 hosts up) scanned in 3.02 seconds (Supplying -Pn shows all ports are closed.) ** Affects: lxd Importance: Unknown Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- Can still ping container IP address after removing container https://bugs.launchpad.net/bugs/1605137 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
