Name of interface on Windows

[Carter Bullard via Argus-info]

Hey František,
You said in your last email that you would describe your methods, after your exams ???
As you can see, windows doesn't have a naming convention.  Libpcap does.  You didn't try index numbers ????   argus -i 1  ... there is an interfaces list command in argus ???

Carter

> On Aug 7, 2016, at 6:55 AM, Frenky via Argus-info <argus-info at lists.andrew.cmu.edu> wrote:
> 
> Hi Carter,
> Some time ago I asked you for building argus on windows. Now it is fine.
> 
> However I have new issue and it is a name of interface on Windows. For Wifi interface on Linux "./argus -i wlan0" works, but as far as windows, any type of interface name does not work for me.
> 
> I will write few steps that I have done.
> 
> 1.
> To view these names of interfaces on windows I have used "ipconfig". However it gives unusable names such as:
> "Ethernet adapter Npcap Loopback Adapter", "Wireless LAN adapter Wi-Fi", etc.
> 
> 2.
> Next I have tried a command "netsh interface ipv4 show interfaces" and it shows:
> "
> Idx     Met         MTU          State                Name
> ---  ----------  ----------  ------------  ---------------------------
> 1          50  4294967295  connected     Loopback Pseudo-Interface 1
> 5          25        1500  connected     Wi-Fi
> 6           5        1500  disconnected  Ethernet
> 3           5        1500  disconnected  Local Area Connection* 2
> 11           5        1500  disconnected  Local Area Connection* 5
> 8          10       65536  connected     Npcap Loopback Adapter
> "
> It looks much more better! So I have tried: "./argus -i Wi-Fi -P 561"
> But it returned:
> "ArgusError: 08 Jul 16 14:50:00.645803 setArgusDevice: no interfaces"
> 
> 3.
> So I have tried to start Wireshark from console, because wireshark needs winpcap as well:
> "wireshark -i Wi-Fi -k"
> where "i" means name of interface and "k" means start of capturing.
> And it works! Wireshark starts to capture from "Wi-Fi".
> So the interface name "Wi-Fi" is right name of interface for Wi-Fi !!
> 
> 4. Next I have tried python library "netifaces", which gives me the name of interface in special face.
> I have got:
> "
> ['{451B6BDC-66DE-47DF-9399-F6F356D90F55}', '{197678FB-3B21-4629-9380-FEAEB7CCE776}', '{96589868-9F1F-4DD9-AF2D-137960397925}', '{63982163-F049-481B-AA75-2399892ED186}', '{3DFDB405-AEAE-475B-871F-CE4312FF4CF5}', '{AD59608F-D4FB-11E5-9014-806E6F6E6963}', '{ABE5A3E0-2340-4E6A-B15A-E3FCB42266FC}', '{0BE19EA5-8690-439E-9E60-74DB56288BCE}']
> "
> So I have tried few ways:
> "./argus -i 451B6BDC-66DE-47DF-9399-F6F356D90F55 -P 561"
> "./argus -i {451B6BDC-66DE-47DF-9399-F6F356D90F55} -P 561"
> "./argus -i '{451B6BDC-66DE-47DF-9399-F6F356D90F55}' -P 561"
> "./argus -i \Device\NPF_{451B6BDC-66DE-47DF-9399-F6F356D90F55} -P 561"
> but it still gives me:
> "ArgusError: 08 Jul 16 14:50:00.645803 setArgusDevice: no interfaces"
> 
> 
> Do you know which name of interface I can use? Where can be problem?
> 
> Thank you for your time!
> František Střasák
> CTU FEE, Prague
> 
> 
> 
> 
> 
>