Following apw's excellent advice pointing to https://www.v13.gr/blog/?p=378 and abusing another ipv6 address on the afflicted host:
tcpdump -npi br0 ip6 and not port 22 | grep -i neigh tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on br0, link-type EN10MB (Ethernet), capture size 262144 bytes [ fire up ping6 2601:282:8100:3500:641d:9dd0:5b50:46e6 on the gateway.] [ no traffic shows up on the bridge ] [ echo 0 > /sys/devices/virtual/net/br0/bridge/multicast_snooping ] 09:40:49.260756 IP6 fe80::1 > ff02::1:ff50:46e6: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:641d:9dd0:5b50:46e6, length 32 09:40:49.260813 IP6 2601:282:8100:3500:641d:9dd0:5b50:46e6 > fe80::1: ICMP6, neighbor advertisement, tgt is 2601:282:8100:3500:641d:9dd0:5b50:46e6, length 32 Looks like bridge multicast_snooping causes ipv6 neighbor discovery to break. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1597806 Title: ipv6 neighbor discovery broken (on a bridge) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597806/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
