A mí me pasa igual, me lista los 255 (lo hago desde una kali en VBox y tengo el slash en adaptador puente).
Me sale algo así:
nmap -sP 192.168.1.1-255Starting Nmap 7.60 ( https://nmap.org ) at 2017-09-05 16:31 EDT
Nmap scan report for 192.168.1.1
Host is up (0.0052s latency).
Nmap scan report for 192.168.1.2
Host is up (0.00090s latency).
Nmap scan report for 192.168.1.3
Host is up (0.00041s latency).
Nmap scan report for 192.168.1.4
Host is up (0.00033s latency).
Nmap scan report for 192.168.1.5
Host is up (0.00025s latency).
Nmap scan report for 192.168.1.6
Host is up (0.00058s latency).
Nmap scan report for 192.168.1.7
Host is up (0.00050s latency).
Nmap scan report for 192.168.1.8
Host is up (0.00019s latency).
Nmap scan report for 192.168.1.9
Host is up (0.00011s latency).
Nmap scan report for 192.168.1.10
Host is up (0.00040s latency).
Nmap scan report for 192.168.1.11
Host is up (0.00031s latency).
Nmap scan report for 192.168.1.12
Host is up (0.00069s latency).
Nmap scan report for 192.168.1.13
Host is up (0.00060s latency).
Nmap scan report for 192.168.1.14
Host is up (0.00034s latency).
Nmap scan report for 192.168.1.15
Host is up (0.00028s latency).
Nmap scan report for 192.168.1.16
Host is up (0.00020s latency).
Nmap scan report for 192.168.1.17
Host is up (0.00047s latency).
Nmap scan report for 192.168.1.18
Host is up (0.00040s latency).
Nmap scan report for 192.168.1.19
Host is up (0.00032s latency).
Nmap scan report for 192.168.1.20
Host is up (0.00024s latency).
Nmap scan report for 192.168.1.21
Host is up (0.00016s latency).
Nmap scan report for 192.168.1.22
Host is up (0.000082s latency).
Nmap scan report for 192.168.1.23
Host is up (0.00092s latency).
Nmap scan report for 192.168.1.24
Host is up (0.00060s latency).
Nmap scan report for 192.168.1.25
Host is up (0.00052s latency).
Nmap scan report for 192.168.1.26
Host is up (0.00044s latency).
Nmap scan report for 192.168.1.27
Host is up (0.00036s latency).
Nmap scan report for 192.168.1.28
Host is up (0.00085s latency).
Nmap scan report for 192.168.1.29
Host is up (0.00077s latency).
Nmap scan report for 192.168.1.30
Host is up (0.00067s latency).
Nmap scan report for 192.168.1.31
Host is up (0.00083s latency).
Nmap scan report for 192.168.1.32
Host is up (0.00075s latency).
Nmap scan report for 192.168.1.33
Host is up (0.00067s latency).
[b].....
hasta el 255
Si hago un ifconfig (no estoy en Windows) me sale esto:[/b]
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.0.2.15 netmask 255.255.255.0 broadcast 10.0.2.255
inet6 fe80::a00:27ff:fea1:b6e6 prefixlen 64 scopeid 0x20<link>
ether 08:00:27:a1:b6:e6 txqueuelen 1000 (Ethernet)
RX packets 1184707 bytes 344420526 (328.4 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 880489 bytes 255387658 (243.5 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 448 bytes 22676 (22.1 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 448 bytes 22676 (22.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Es decir, no aparece por ninguna parte el slack.
Sin embargo, tanto desde el Windows anfitrión como desde el kali si pongo
192.168.1.100 se me abre la web sin problema. Por lo que he seguido el taller (pero en la vida real obviamente no voy a probar los 255, o si...vete a saber) cuando escaneo específicamente el 192.168.1.100 con el nmap para ver que puertos abiertos me sale un pantallazo distinto de lo que debería salirme, aunque sí que me sale que el ssh está abierto, me sale esto:
nmap -sV -O 192.168.1.100[/b]
Starting Nmap 7.60 ( https://nmap.org ) at 2017-09-05 16:32 EDT
Nmap scan report for 192.168.1.100
Host is up (0.0089s latency).
Not shown: 992 filtered ports
PORT STATE SERVICE VERSION
20/tcp closed ftp-data
21/tcp open ftp?
22/tcp open ssh OpenSSH 4.3 (protocol 1.99)
25/tcp open smtp Sendmail 8.13.7/8.13.7
80/tcp open http Apache httpd 2.0.55 ((Unix) PHP/5.1.2)
110/tcp open pop3 Openwall popa3d
143/tcp open imap UW imapd 2004.357
443/tcp closed https
1 service unrecognized despite returning data. If you know the service/version, please submit the following fingerprint at https://nmap.org/cgi-bin/submit.cgi?new-service :
SF-Port21-TCP:V=7.60%I=7%D=9/5%Time=59AF0A0C%P=x86_64-pc-linux-gnu%r(NULL,
SF:2F,"00\x20OOPS:\x20could\x20not\x20bind\x20listening\x20IPv4\x20socket\
SF:r\n");
Device type: bridge|general purpose
Running (JUST GUESSING): Oracle Virtualbox (99%), QEMU (99%)
OS CPE: cpe:/o:oracle:virtualbox cpe:/a:qemu:qemu
Aggressive OS guesses: Oracle Virtualbox (99%), QEMU user mode network gateway (99%)
No exact OS matches for host (test conditions non-ideal).
Service Info: Host: slax.example.net; OS: Unix
OS and Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 60.86 seconds
Así que sigo y estoy ahora con los diccionarios, a ver si encuentro la clave.
Por cierto, he preparado un programita en Python para convertir un diccionario en minúsculas a mayúsculas, es una tontería pero a alguien le puede servir.
entrada=open('diccionario.txt','r')
salida=open('DICCIONARIO.txt','w')
for linea in entrada:
salida.write(linea.upper())
entrada.close()
salida.close()