-
Notifications
You must be signed in to change notification settings - Fork 411
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to specify interface on Windows. Tshark works fine #52
Comments
Gimme dat |
Here you go good sir: PS C:\WINDOWS\system32> tshark -v Copyright 1998-2019 Gerald Combs [email protected] and contributors. Compiled (64-bit) with WinPcap SDK (WpdPack) 4.1.2, with GLib 2.52.2, with zlib Running on 64-bit Windows 10 (1903), build 18362, with Intel(R) Core(TM) Built using Microsoft Visual Studio 2017 (VC++ 14.16, build 27030). |
Gimme |
PS C:\WINDOWS\system32> tshark -L ================================= PS C:\WINDOWS\system32> tshark -D
|
Checking for any updates |
What does |
termshark -i 9 and tshark -i 9 both work as expected. Is it normal to need to select the interface number rather than name? |
What's the output of What happens if you use |
netsh interface show interface
|
Hi - if you can give the latest a try, I hope this is now fixed. Something like export GO111MODULE=on
git clone https://github.com/gcla/termshark
cd termshark
go install ./... then termshark will be in |
PS C:\WINDOWS\system32> termshark -i wifi
Could not find network interface wifi
PS C:\WINDOWS\system32> tshark -i wifi
Capturing on 'wifi'
1 0.000000 2600:100f:b01e:92c1:e497:adce:657c:53c1 → 2600:100f:b01e:92c1:6871:3be5:289d:c5f5 ICMPv6 86 Neighbor Solicitation for 2600:100f:b01e:92c1:6871:3be5:289d:c5f5 from 7e:50:49:23:f5:64
2 0.000250 2600:100f:b01e:92c1:6871:3be5:289d:c5f5 → 2600:100f:b01e:92c1:e497:adce:657c:53c1 ICMPv6 86 Neighbor Advertisement 2600:100f:b01e:92c1:6871:3be5:289d:c5f5 (sol, ovr) is at 20:79:18:8d:81:af
3 0.999516 0 40.90.10.180 → 172.20.10.3 TLSv1.2 85 31 Application Data
3 packets captured
The text was updated successfully, but these errors were encountered: