https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3047
--- Comment #1 from Stephen Fisher <[EMAIL PROTECTED]> 2008-11-27 01:13:43 PDT
---
This is interesting because you say that you've disabled IPv4 on the interface.
Wireshark queries the possible interfaces by calling the dumpcap.exe program
with the arguments "-D -M" Can you try running that from a command-line and
see what addresses it prints out for the interface in question? The format
will be similar to this from my Win2008 Server VM:
1. \Device\NPF_{B63B0AED-0DF1-4D90-8781-822AD85B80D4} MS Tunnel Interface
Driv
er
fe80::3c71:9c:f52c:c8fa,2001:0:4137:9e50:3c71:9c:f52c:c8fa,fe80::3c71:9c
:f52c:c8fa,2001:0:4137:9e50:3c71:9c:f52c:c8fa network
2. \Device\NPF_{90C77D2F-7BF4-4D1C-9451-D8EB91648547} Parallels Ethernet
Adapt
er fe80::3096:6cb2:127:98f2,10.211.55.5 network
See how it shows the IPv6 link-local address (I'm not using IPv6 on this
interface, but it is enabled) and then the actual IPv4 address. Wireshark's
GUI will only display the first address listed there.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Wireshark-bugs mailing list
Wireshark-bugs@wireshark.org
https://wireshark.org/mailman/listinfo/wireshark-bugs
