Conectei-me com êxito a uma vpn do meu laptop Windows e quero ver quais hosts estão no grupo de trabalho chamado "Boston". Atualmente, o DNS do grupo de trabalho não está configurado para listar a maioria dos nomes de computador, então estou apenas tentando endereços IP. Quando digito ipconfig , vejo o seguinte (entre várias outras interfaces):
Ethernet adapter Ethernet 2:
Connection-specific DNS Suffix . : Boston.local
Link-local IPv6 Address . . . . . : fe80::2c21:fcc4:3359:e748%55
IPv4 Address. . . . . . . . . . . : 10.1.1.132
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Acabei de sair em um membro e assumi "Ethernet 2" implica interface eth2, então eu tentei o seguinte no Zenmap
nmap -sn -T4 -e eth2 10.1.1.0/24
Mas tudo que consigo são linhas como as seguintes:
Starting Nmap 7.12 ( https://nmap.org ) at 2018-09-20 15:12 Mountain Daylight Time
setup_target: failed to determine route to 10.1.1.0
setup_target: failed to determine route to 10.1.1.1
setup_target: failed to determine route to 10.1.1.2
setup_target: failed to determine route to 10.1.1.3
para todos os endereços, incluindo o meu. Eu também obtenho os mesmos resultados quando tento 10.0.1.0/24 e 10.1.0.0/24, apesar de todas as três sub-redes estarem em minhas rotas
route PRINT
===========================================================================
Interface List
55...00 60 73 3b 9d 0b ......SonicWALL Virtual NIC
12...28 f1 0e 09 37 a6 ......Killer e2400 Gigabit Ethernet Controller
11...e6 b3 18 67 40 17 ......Microsoft Wi-Fi Direct Virtual Adapter #2
8...00 50 56 c0 00 01 ......VMware Virtual Ethernet Adapter for VMnet1
16...00 50 56 c0 00 08 ......VMware Virtual Ethernet Adapter for VMnet8
17...e4 b3 18 67 40 17 ......Intel(R) Dual Band Wireless-AC 8260
6...e4 b3 18 67 40 1b ......Bluetooth Device (Personal Area Network)
1...........................Software Loopback Interface 1
===========================================================================
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.240 35
10.0.1.0 255.255.255.0 On-link 10.1.1.132 2
10.0.1.6 255.255.255.255 On-link 10.1.1.132 2
10.0.1.255 255.255.255.255 On-link 10.1.1.132 257
10.1.0.0 255.255.255.0 On-link 10.1.1.132 2
10.1.0.255 255.255.255.255 On-link 10.1.1.132 257
10.1.1.0 255.255.255.0 On-link 10.1.1.132 257
10.1.1.132 255.255.255.255 On-link 10.1.1.132 257
10.1.1.255 255.255.255.255 On-link 10.1.1.132 257
10.5.0.0 255.255.255.0 On-link 10.1.1.132 2
10.5.0.255 255.255.255.255 On-link 10.1.1.132 257
10.8.0.0 255.255.255.0 On-link 10.1.1.132 2
10.8.0.255 255.255.255.255 On-link 10.1.1.132 257
10.8.1.0 255.255.255.0 On-link 10.1.1.132 2
10.8.1.255 255.255.255.255 On-link 10.1.1.132 257
70.91.168.73 255.255.255.255 192.168.1.1 192.168.1.240 35
127.0.0.0 255.0.0.0 On-link 127.0.0.1 331
127.0.0.1 255.255.255.255 On-link 127.0.0.1 331
127.255.255.255 255.255.255.255 On-link 127.0.0.1 331
172.16.0.0 255.255.255.0 On-link 10.1.1.132 2
172.16.0.255 255.255.255.255 On-link 10.1.1.132 257
172.16.1.0 255.255.255.0 On-link 10.1.1.132 2
172.16.1.255 255.255.255.255 On-link 10.1.1.132 257
172.16.31.0 255.255.255.0 On-link 10.1.1.132 2
172.16.31.255 255.255.255.255 On-link 10.1.1.132 257
192.168.1.0 255.255.255.0 On-link 192.168.1.240 291
192.168.1.240 255.255.255.255 On-link 192.168.1.240 291
192.168.1.255 255.255.255.255 On-link 192.168.1.240 291
192.168.47.0 255.255.255.0 On-link 192.168.47.1 291
192.168.47.1 255.255.255.255 On-link 192.168.47.1 291
192.168.47.255 255.255.255.255 On-link 192.168.47.1 291
192.168.80.0 255.255.255.0 On-link 192.168.80.1 291
192.168.80.1 255.255.255.255 On-link 192.168.80.1 291
192.168.80.255 255.255.255.255 On-link 192.168.80.1 291
192.168.100.0 255.255.255.0 On-link 10.1.1.132 2
192.168.100.255 255.255.255.255 On-link 10.1.1.132 257
192.168.101.0 255.255.255.0 On-link 10.1.1.132 2
192.168.101.255 255.255.255.255 On-link 10.1.1.132 257
192.168.150.0 255.255.255.0 On-link 10.1.1.132 2
192.168.150.255 255.255.255.255 On-link 10.1.1.132 257
224.0.0.0 240.0.0.0 On-link 127.0.0.1 331
224.0.0.0 240.0.0.0 On-link 192.168.47.1 291
224.0.0.0 240.0.0.0 On-link 192.168.80.1 291
224.0.0.0 240.0.0.0 On-link 192.168.1.240 291
224.0.0.0 240.0.0.0 On-link 10.1.1.132 257
255.255.255.255 255.255.255.255 On-link 127.0.0.1 331
255.255.255.255 255.255.255.255 On-link 192.168.47.1 291
255.255.255.255 255.255.255.255 On-link 192.168.80.1 291
255.255.255.255 255.255.255.255 On-link 192.168.1.240 291
255.255.255.255 255.255.255.255 On-link 10.1.1.132 257
===========================================================================
Persistent Routes:
None
Usar eth1 fornece os mesmos resultados e usar eth0 dá
Starting Nmap 7.12 ( https://nmap.org ) at 2018-09-20 16:27 Mountain Daylight Time
dnet: Failed to open device eth0
QUITTING!
Atualização 1
Estou completamente perplexa - apenas corri nmap --iflist e obtive a seguinte saída, mas ainda reclama sobre eth0 (se eu especifico com -e ou não)
Starting Nmap 7.12 ( https://nmap.org ) at 2018-09-21 13:21 Mountain Daylight Time
************************INTERFACES************************
DEV (SHORT) IP/MASK TYPE UP MTU MAC
eth0 (eth0) fe80::2c21:fcc4:3359:e748/64 ethernet up 1418 00:60:73:3B:9D:0B
eth0 (eth0) 10.1.1.132/24 ethernet up 1418 00:60:73:3B:9D:0B
eth1 (eth1) fe80::91aa:d87e:1a49:4d58/64 ethernet down 1500 28:F1:0E:09:37:A6
eth1 (eth1) 169.254.77.88/4 ethernet down 1500 28:F1:0E:09:37:A6
eth2 (eth2) fe80::956:1f96:1f35:8785/64 ethernet down 1500 E6:B3:18:67:40:17
eth2 (eth2) 169.254.135.133/4 ethernet down 1500 E6:B3:18:67:40:17
eth3 (eth3) fe80::350a:77b7:3bc8:3e99/64 ethernet up 1500 00:50:56:C0:00:01
eth3 (eth3) 192.168.47.1/24 ethernet up 1500 00:50:56:C0:00:01
eth4 (eth4) fe80::1c8e:b518:9d75:dc50/64 ethernet up 1500 00:50:56:C0:00:08
eth4 (eth4) 192.168.80.1/24 ethernet up 1500 00:50:56:C0:00:08
eth5 (eth5) fe80::11db:9e0a:4913:3823/64 ethernet up 1500 E4:B3:18:67:40:17
eth5 (eth5) 192.168.1.240/24 ethernet up 1500 E4:B3:18:67:40:17
eth6 (eth6) fe80::1560:3bf9:44e8:c2d5/64 ethernet down 1500 E4:B3:18:67:40:1B
eth6 (eth6) 169.254.194.213/4 ethernet down 1500 E4:B3:18:67:40:1B
lo0 (lo0) ::1/128 loopback up -1
lo0 (lo0) 127.0.0.1/8 loopback up -1
DEV WINDEVICE
eth0 <none>
eth0 <none>
eth1 \Device\NPF_{8A8B5341-C773-4892-8D8F-C1DC84272FD6}
eth1 \Device\NPF_{8A8B5341-C773-4892-8D8F-C1DC84272FD6}
eth2 \Device\NPF_{8A1E85B7-D29F-4346-B4ED-E52F8558DFF3}
eth2 \Device\NPF_{8A1E85B7-D29F-4346-B4ED-E52F8558DFF3}
eth3 \Device\NPF_{6771C502-791A-42C4-8769-1835C8194B3E}
eth3 \Device\NPF_{6771C502-791A-42C4-8769-1835C8194B3E}
eth4 \Device\NPF_{B5851DDD-8079-43BB-A5EB-3249ABF478E7}
eth4 \Device\NPF_{B5851DDD-8079-43BB-A5EB-3249ABF478E7}
eth5 \Device\NPF_{BBD3B26B-B578-4E49-82C0-132666231D08}
eth5 \Device\NPF_{BBD3B26B-B578-4E49-82C0-132666231D08}
eth6 \Device\NPF_{5E60BD83-E486-4881-A7E1-79F498E06387}
eth6 \Device\NPF_{5E60BD83-E486-4881-A7E1-79F498E06387}
lo0 <none>
lo0 <none>
**************************ROUTES**************************
DST/MASK DEV METRIC GATEWAY
10.0.1.6/32 eth0 2
70.91.168.73/32 eth5 35 192.168.1.1
192.168.150.255/32 eth0 257
255.255.255.255/32 eth0 257
10.8.0.255/32 eth0 257
10.1.0.255/32 eth0 257
172.16.0.255/32 eth0 257
10.1.1.132/32 eth0 257
10.1.1.255/32 eth0 257
192.168.101.255/32 eth0 257
10.5.0.255/32 eth0 257
10.8.1.255/32 eth0 257
172.16.1.255/32 eth0 257
192.168.100.255/32 eth0 257
172.16.31.255/32 eth0 257
10.0.1.255/32 eth0 257
255.255.255.255/32 eth1 261
255.255.255.255/32 eth2 281
255.255.255.255/32 eth3 291
192.168.47.255/32 eth3 291
255.255.255.255/32 eth5 291
192.168.80.1/32 eth4 291
255.255.255.255/32 eth4 291
192.168.80.255/32 eth4 291
192.168.47.1/32 eth3 291
192.168.1.255/32 eth5 291
192.168.1.240/32 eth5 291
255.255.255.255/32 eth6 321
255.255.255.255/32 lo0 331
127.255.255.255/32 lo0 331
127.0.0.1/32 lo0 331
10.1.0.0/24 eth0 2
10.0.1.0/24 eth0 2
172.16.31.0/24 eth0 2
172.16.0.0/24 eth0 2
10.8.1.0/24 eth0 2
10.8.0.0/24 eth0 2
10.5.0.0/24 eth0 2
172.16.1.0/24 eth0 2
192.168.101.0/24 eth0 2
192.168.100.0/24 eth0 2
192.168.150.0/24 eth0 2
10.1.1.0/24 eth0 257
192.168.47.0/24 eth3 291
192.168.1.0/24 eth5 291
192.168.80.0/24 eth4 291
127.0.0.0/8 lo0 331
224.0.0.0/4 eth0 257
224.0.0.0/4 eth1 261
224.0.0.0/4 eth2 281
224.0.0.0/4 eth5 291
224.0.0.0/4 eth3 291
224.0.0.0/4 eth4 291
224.0.0.0/4 eth6 321
224.0.0.0/4 lo0 331
0.0.0.0/0 eth5 35 192.168.1.1
fe80::91aa:d87e:1a49:4d58/128 eth1 261
fe80::956:1f96:1f35:8785/128 eth2 281
fe80::1c8e:b518:9d75:dc50/128 eth4 291
fe80::350a:77b7:3bc8:3e99/128 eth3 291
fe80::2c21:fcc4:3359:e748/128 eth0 291
fe80::11db:9e0a:4913:3823/128 eth5 291
fe80::1560:3bf9:44e8:c2d5/128 eth6 321
::1/128 lo0 331
fe80::/64 eth1 261
fe80::/64 eth2 281
fe80::/64 eth0 291
fe80::/64 eth5 291
fe80::/64 eth4 291
fe80::/64 eth3 291
fe80::/64 eth6 321
ff00::/8 eth1 261
ff00::/8 eth2 281
ff00::/8 eth0 291
ff00::/8 eth5 291
ff00::/8 eth4 291
ff00::/8 eth3 291
ff00::/8 eth6 321
ff00::/8 lo0 331
Atualização nº 2
Depois de examinar esta discussão sobre a confusão na nomeação de interfaces, fiz o download e executei a o mais recente instalador do zenmap para a versão 7.70. Agora, a saída de nmap -sn -T4 10.0.1.0/24 produz o seguinte
Starting Nmap 7.70 ( https://nmap.org ) at 2018-09-21 14:44 Mountain Daylight Time
Nmap scan report for 10.0.1.0
Host is up (0.00s latency).
MAC Address: 00:60:73:3B:9D:0C (Redcreek Communications)
Nmap scan report for 10.0.1.1
Host is up (0.00s latency).
MAC Address: 00:60:73:3B:9D:0C (Redcreek Communications)
Nmap scan report for 10.0.1.2
Host is up (0.00s latency).
MAC Address: 00:60:73:3B:9D:0C (Redcreek Communications)
...[snip]...
Nmap scan report for 10.0.1.254
Host is up (0.00s latency).
MAC Address: 00:60:73:3B:9D:0C (Redcreek Communications)
Nmap scan report for 10.0.1.255
Host is up (0.00s latency).
MAC Address: 00:60:73:3B:9D:0C (Redcreek Communications)
Nmap done: 256 IP addresses (256 hosts up) scanned in 17.56 seconds
Então, estou mais um passo mais perto, mas sei que não há 256 hosts na sub-rede e observe que o endereço MAC é sempre o mesmo (e é o que está listado na saída de ipconfig /all
Ethernet adapter Ethernet 2:
Connection-specific DNS Suffix . : Boston.local
Description . . . . . . . . . . . : SonicWALL Virtual NIC
Physical Address. . . . . . . . . : 00-60-73-3B-9D-0B
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::2c21:fcc4:3359:e748%55(Preferred)
IPv4 Address. . . . . . . . . . . : 10.1.1.132(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, September 20, 2018 2:17:55 PM
Lease Expires . . . . . . . . . . : Saturday, September 22, 2018 12:48:30 PM
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 10.1.1.1
DHCPv6 IAID . . . . . . . . . . . : 922771571
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-EE-C8-89-28-F1-0E-09-37-A6
DNS Servers . . . . . . . . . . . : 10.0.1.6
204.130.255.3
75.75.75.75
NetBIOS over Tcpip. . . . . . . . : Enabled