https://bugs.winehq.org/show_bug.cgi?id=51680
Bug ID: 51680 Summary: nsi:nsi test_ip_neighbour() fails on unreachable link local entry Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: fgouget@codeweavers.com
nsi:nsi has a failure on cw-rx460 from Windows 1709 to 21H1:
nsi.c:680: Test failed: AF_INET: 0 vs 1
https://test.winehq.org/data/patterns.html#nsi:nsi
The failing test has been introduced by the commit below and failed from the start:
commit c09c65f65c188a1870d279ca793c5ad1fc15440d Author: Huw Davies huw@codeweavers.com AuthorDate: Tue Aug 10 09:20:47 2021 +0100
nsiproxy: Implement IPv4 neighbour enumerate_all.
Signed-off-by: Huw Davies huw@codeweavers.com Signed-off-by: Alexandre Julliard julliard@winehq.org
Adding some traces shows that the failure happens on a link local entry: AF_INET: 5 InterfaceIndex=10 state=0/0 s_addr=169.254.169.254
I have not identified the corresponding network interface. Also, given that cw-rx460 ad cw-gtx560 are very similar I would expect both to have this issue and I don't know why that's not the case.
However what is interesting is that in both cases the state is NlnsUnreachable so I suspect the is_unreachable / IsUnreachable flags are not necessarily meaningful.
https://bugs.winehq.org/show_bug.cgi?id=51680
François Gouget fgouget@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch, source, testcase
https://bugs.winehq.org/show_bug.cgi?id=51680
--- Comment #1 from François Gouget fgouget@codeweavers.com --- Created attachment 70551 --> https://bugs.winehq.org/attachment.cgi?id=70551 Ignore the unreachable flags if the state is NlnsUnreachable.
https://bugs.winehq.org/show_bug.cgi?id=51680
--- Comment #2 from François Gouget fgouget@codeweavers.com --- I have run the test with extra traces on cw-rx460/Windows 10 1507 and it does not have this local link entry:
Windows 10 1507: nsi.c:667: AF_INET: 0 InterfaceIndex=1 state=6/6 s_addr=224.0.0.22 nsi.c:667: AF_INET: 1 InterfaceIndex=1 state=6/6 s_addr=239.255.255.250 nsi.c:667: AF_INET: 2 InterfaceIndex=3 state=5/5 s_addr=10.42.42.1 nsi.c:667: AF_INET: 3 InterfaceIndex=3 state=4/4 s_addr=10.42.42.12 nsi.c:667: AF_INET: 4 InterfaceIndex=3 state=4/4 s_addr=10.42.42.133 nsi.c:667: AF_INET: 5 InterfaceIndex=3 state=6/6 s_addr=10.42.42.255 nsi.c:667: AF_INET: 6 InterfaceIndex=3 state=6/6 s_addr=224.0.0.22 nsi.c:667: AF_INET: 7 InterfaceIndex=3 state=6/6 s_addr=224.0.0.252 nsi.c:667: AF_INET: 8 InterfaceIndex=3 state=6/6 s_addr=239.255.255.250
Windows 10 21H1: nsi.c:667: AF_INET: 0 InterfaceIndex=1 state=6/6 s_addr=224.0.0.22 nsi.c:667: AF_INET: 1 InterfaceIndex=1 state=6/6 s_addr=239.255.255.250 nsi.c:667: AF_INET: 2 InterfaceIndex=10 state=5/5 s_addr=10.42.42.1 nsi.c:667: AF_INET: 3 InterfaceIndex=10 state=4/4 s_addr=10.42.42.12 nsi.c:667: AF_INET: 4 InterfaceIndex=10 state=6/6 s_addr=10.42.42.255
nsi.c:667: AF_INET: 5 InterfaceIndex=10 state=0/0 s_addr=169.254.169.254
nsi.c:667: AF_INET: 6 InterfaceIndex=10 state=6/6 s_addr=224.0.0.22 nsi.c:667: AF_INET: 7 InterfaceIndex=10 state=6/6 s_addr=224.0.0.251 nsi.c:667: AF_INET: 8 InterfaceIndex=10 state=6/6 s_addr=224.0.0.252 nsi.c:667: AF_INET: 9 InterfaceIndex=10 state=6/6 s_addr=239.255.255.250
The only references I have found concerning 169.254.169.254 mention its use on Amazon EC2. So I don't know why it would appear on this machine.
https://bugs.winehq.org/show_bug.cgi?id=51680
François Gouget fgouget@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1| |c09c65f65c188a1870d279ca793 | |c5ad1fc15440d
https://bugs.winehq.org/show_bug.cgi?id=51680
--- Comment #3 from François Gouget fgouget@codeweavers.com --- Created attachment 70553 --> https://bugs.winehq.org/attachment.cgi?id=70553 Some additional traces
https://bugs.winehq.org/show_bug.cgi?id=51680
François Gouget fgouget@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |huw@codeweavers.com
https://bugs.winehq.org/show_bug.cgi?id=51680
François Gouget fgouget@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED
--- Comment #4 from François Gouget fgouget@codeweavers.com --- nsi:nsi still regularly gets a single failure but it turns out it is unrelated to this bug. Also there is no instance of this failure in the available history so I am going to consider this failure to be fixed some time before 2022-03-14.
https://bugs.winehq.org/show_bug.cgi?id=51680
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #5 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 7.9.
-
WineHQ Bugzilla