[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1597806
T
The current mainline kernel is now v4.8 final. That would be better to
test, versus 4.7-rc5:
v4.8: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bu
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.7 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix th
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
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 abou
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 (Et
apport-collect is not really an option on the machine, nor should any of
that really provide any additional information that's not already in the
bug report. holler at me if I missed anything relevant.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug
However, given that eth0.2 is seeing the solicitation, and br0 isn't,
I'm leaning strongly toward the bridge code being slightly buggy.
My next test will be to do a non-promisc tcpdump on eth0.2 and see if
_THAT_ sees the traffic. That may take me a week before I can do it
though, due to schedule
One other tidbit: The gateway in question is using eth0.2 on a trunked
port to a Cisco WS-C2960G-24TC-L running
c2960-lanbasek9-mz.150-2.SE9.bin.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1597806
