Re: Nmap or Winpcap Does Not Support USB 3G Modems

[Teo En Ming <teo.en.ming () gmail com>]

It seems that the ethernet interface eth0 belongs to my USB 3G modem. But
why is nmap 6.46 reporting that it failed to open device eth0?

Regards,

Teo En Ming


On Tue, Apr 22, 2014 at 7:57 PM, Teo En Ming <teo.en.ming () gmail com> wrote:

> Dear Gisle Vanem,
>
> Here is the output for the command "nmap --iflist":
>
>
>
> Starting Nmap 6.46 ( http://nmap.org ) at 2014-04-22 19:49 Malay
> Peninsula Standard Time
>
>
> ************************INTERFACES************************
>
> DEV  (SHORT) IP/MASK                      TYPE        UP   MTU  MAC
>
> eth0 (eth0)  171.207.9.111/27             ethernet    up   1500
> 58:2C:80:13:92:63
>
> eth1 (eth1)  fe80::7839:5ef2:f2a6:fc30/64 ethernet    down 1500
> 4C:ED:DE:98:E3:89
>
> eth1 (eth1)  169.254.252.48/4             ethernet    down 1500
> 4C:ED:DE:98:E3:89
>
> eth2 (eth2)  fe80::c8e2:267c:fba8:5297/64 ethernet    down 1500
> E8:11:32:24:B1:2B
>
> eth2 (eth2)  169.254.82.151/4             ethernet    down 1500
> E8:11:32:24:B1:2B
>
> eth3 (eth3)  fe80::61dc:5d59:46e0:9e6/64  ethernet    up   1500
> 08:00:27:00:60:0B
>
> eth3 (eth3)  192.168.56.1/24              ethernet    up   1500
> 08:00:27:00:60:0B
>
> lo0  (lo0)   ::1/128                      loopback    up   -1
>
> lo0  (lo0)   127.0.0.1/8                  loopback    up   -1
>
> tun0 (tun0)  2002:abcf:96f::abcf:96f/16   point2point up   1280
>
> tun1 (tun1)  fe80::200:5efe:abcf:96f/128  point2point down 1280
>
> tun2 (tun2)  (null)/0                     point2point down 1280
>
> tun3 (tun3)  fe80::100:7f:fffe/64         point2point down 1472
>
> tun4 (tun4)  fe80::5efe:c0a8:3801/128     point2point down 1280
>
> tun5 (tun5)  (null)/0                     point2point down 1280
>
>
>
> DEV  WINDEVICE
>
> eth0 <none>
>
> eth1 \Device\NPF_{61B698DB-F5E4-4A91-A46D-92461305D7CC}
>
> eth1 \Device\NPF_{61B698DB-F5E4-4A91-A46D-92461305D7CC}
>
> eth2 \Device\NPF_{9B4B02D1-1CE2-4987-9605-4BF9CC074A2F}
>
> eth2 \Device\NPF_{9B4B02D1-1CE2-4987-9605-4BF9CC074A2F}
>
> eth3 \Device\NPF_{59C0512D-F5AB-4ECF-81C6-515D8F041D2B}
>
> eth3 \Device\NPF_{59C0512D-F5AB-4ECF-81C6-515D8F041D2B}
>
> lo0  <none>
>
> lo0  <none>
>
> tun0 <none>
>
> tun1 <none>
>
> tun2 <none>
>
> tun3 <none>
>
> tun4 <none>
>
> tun5 <none>
>
>
>
> **************************ROUTES**************************
>
> DST/MASK                      DEV  METRIC GATEWAY
>
> 192.168.56.255/32             eth3 276
>
> 255.255.255.255/32            eth2 276
>
> 255.255.255.255/32            eth3 276
>
> 192.168.56.1/32               eth3 276
>
> 255.255.255.255/32            eth1 296
>
> 171.207.9.111/32              eth0 296
>
> 171.207.9.127/32              eth0 296
>
> 255.255.255.255/32            eth0 296
>
> 127.0.0.1/32                  lo0  306
>
> 127.255.255.255/32            lo0  306
>
> 255.255.255.255/32            lo0  306
>
> 171.207.9.96/27               eth0 296
>
> 192.168.56.0/24               eth3 276
>
> 127.0.0.0/8                   lo0  306
>
> 224.0.0.0/4                   eth3 276
>
> 224.0.0.0/4                   eth2 276
>
> 224.0.0.0/4                   eth1 296
>
> 224.0.0.0/4                   eth0 296
>
> 224.0.0.0/4                   lo0  306
>
> 0.0.0.0/0                     eth0 296    171.207.9.97
>
> fe80::61dc:5d59:46e0:9e6/128  eth3 276
>
> fe80::c8e2:267c:fba8:5297/128 eth2 276
>
> 2002:abcf:96f::abcf:96f/128   tun0 296
>
> fe80::7839:5ef2:f2a6:fc30/128 eth1 296
>
> ::1/128                       lo0  306
>
> fe80::200:5efe:abcf:96f/128   tun1 306
>
> fe80::5efe:c0a8:3801/128      tun4 306
>
> fe80::100:7f:fffe/128         tun3 306
>
> fe80::/64                     eth3 276
>
> fe80::/64                     eth2 276
>
> fe80::/64                     eth1 296
>
> fe80::/64                     tun3 306
>
> 2002::/16                     tun0 1040
>
> ff00::/8                      eth2 276
>
> ff00::/8                      eth3 276
>
> ff00::/8                      eth1 296
>
> ff00::/8                      lo0  306
>
> ff00::/8                      tun3 306
>
> Regards,
>
> Teo En Ming
>
>
>
>
>
>
> On Tue, Apr 22, 2014 at 7:40 PM, Gisle Vanem <gvanem () yahoo no> wrote:
>
> > "Teo En Ming" <teo.en.ming () gmail com> wrote:
> >
> >  I think nmap or winpcap does not support USB 3G modem. I get the
> > > following
> > > error with nmap:
> > >
> > > dnet: Failed to open device eth0
> > > QUITTING!
> >
> > What does "nmap --iflist" print?
> >
> > Your USB 3G modem should present a normal NDIS API for WinPcap
> > and Nmap to work with it. Does it? I use a USB-based wireless adapter
> > here. But I''m not sure how a 3G-adapter presents itself to the Windows
> > IP-stack.
> >
> > 'nmap --iflist ' here:
> >
> > Starting Nmap 6.45 ( http://nmap.org ) at 2014-04-22 11:36 CET
> > ************************INTERFACES************************
> > DEV  (SHORT) IP/MASK            TYPE     UP MTU  MAC
> > eth0 (eth0)  10.0.0.5/24        ethernet up 1500 00:18:4D:00:DE:76
> > eth1 (eth1)  10.0.0.6/24        ethernet up 6130 20:CF:30:90:56:99
> > ppp0 (ppp0)  108.171.112.162/32 other    up 1400
> > lo0  (lo0)   127.0.0.1/0        loopback up 1520
> >
> > DEV    WINDEVICE
> > eth0   \Device\NPF_{37FC13D9-2F52-47CA-AB64-32B2B434C749}
> > eth1   \Device\NPF_{8D3A23A7-9C6C-408B-A23B-6736F9E56510}
> > ppp0   <none>
> > lo0    <none>
> > <none> \Device\NPF_{7F56352E-EF2F-49F4-844C-BA1FA0105667}
> > <none> \Device\NPF_GenericDialupAdapter
> > <none> \\.\airpcap00
> >
> > --gv
_______________________________________________
Sent through the dev mailing list
http://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/