enlaces:utilidades_de_red
Diferencias
Muestra las diferencias entre dos versiones de la página.
Ambos lados, revisión anteriorRevisión previaPróxima revisión | Revisión previa | ||
enlaces:utilidades_de_red [2010/12/17 18:06] – cayu | enlaces:utilidades_de_red [2019/01/22 15:34] (actual) – [Parser y formateador de salida NMap] cayu | ||
---|---|---|---|
Línea 2: | Línea 2: | ||
===== Conectividad ===== | ===== Conectividad ===== | ||
+ | |||
+ | ==== Agregar ruta estatica ==== | ||
+ | |||
+ | < | ||
+ | ip route add 192.168.55.0/ | ||
+ | </ | ||
+ | |||
+ | < | ||
+ | route add -net 192.168.55.0 netmask 255.255.255.0 gw 192.168.1.254 dev eth1 | ||
+ | </ | ||
==== Forzar el modo ethernet ==== | ==== Forzar el modo ethernet ==== | ||
Línea 10: | Línea 20: | ||
ethtool -s eth0 speed 100 duplex full autoneg off | ethtool -s eth0 speed 100 duplex full autoneg off | ||
</ | </ | ||
- | |||
==== Conectarse a redes Wi Fi ==== | ==== Conectarse a redes Wi Fi ==== | ||
Primero bajamos el servicio de Network Manager si es que lo tenemos instalado | Primero bajamos el servicio de Network Manager si es que lo tenemos instalado | ||
Línea 336: | Línea 345: | ||
- | ===== Sniffers ===== | + | ===== Sniffers |
http:// | http:// | ||
- | |||
- | ==== Network Grep - ngrep ==== | ||
- | |||
- | Muestra y busca paquetes. Ngrep se esfuerza por proveer de la mayoría de características comunes del " | ||
- | |||
- | |||
- | http:// | ||
- | |||
- | |||
- | Un posteo interesante en un blog : http:// | ||
- | |||
Línea 364: | Línea 362: | ||
# tcptrack -i eth0 port 80 | # tcptrack -i eth0 port 80 | ||
# tcptrack -i eth0 host 192.168.2.110 and port 8080 | # tcptrack -i eth0 host 192.168.2.110 and port 8080 | ||
+ | # | ||
</ | </ | ||
Línea 394: | Línea 393: | ||
http:// | http:// | ||
+ | |||
+ | |||
+ | ==== Hydra ==== | ||
+ | |||
+ | A very fast network logon cracker which support many different services | ||
+ | |||
+ | |||
+ | Currently this tool supports: | ||
+ | TELNET, FTP, HTTP, HTTPS, HTTP-PROXY, SMB, SMBNT, MS-SQL, MYSQL, REXEC, | ||
+ | RSH, RLOGIN, CVS, SNMP, SMTP-AUTH, SOCKS5, VNC, POP3, IMAP, NNTP, PCNFS, | ||
+ | ICQ, SAP/R3, LDAP2, LDAP3, Postgres, Teamspeak, Cisco auth, Cisco enable, | ||
+ | AFP, Subversion/ | ||
+ | |||
+ | For HTTP, POP3, IMAP and SMTP, several login mechanisms like plain and MD5 digest are supported. | ||
+ | |||
+ | |||
+ | |||
+ | http:// | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ==== Python Proxy ==== | ||
+ | |||
+ | Mini Proxy en Python | ||
+ | |||
+ | http:// | ||
+ | |||
+ | < | ||
+ | sergio@sergio-thinkcentre-a70z: | ||
+ | Serving on 0.0.0.0: | ||
+ | GET http:// | ||
+ | GET http:// | ||
+ | GET http:// | ||
+ | </ | ||
+ | |||
+ | |||
+ | |||
+ | ==== Parser y formateador de salida NMap ==== | ||
+ | |||
+ | Algo muy útil a la hora de hacer reporte de servidores en base a un archivo de lista de servidores, ej nmap-report.pl servidores.txt, | ||
+ | |||
+ | <code perl> | ||
+ | # | ||
+ | BEGIN { | ||
+ | eval "use Nmap:: | ||
+ | if ( $@ ) { | ||
+ | warn "Error to load module: Nmap:: | ||
+ | . " | ||
+ | . " | ||
+ | exit (); | ||
+ | } | ||
+ | } | ||
+ | |||
+ | use POSIX qw(strftime); | ||
+ | my $scanner = new Nmap:: | ||
+ | $scanner-> | ||
+ | $scanner-> | ||
+ | $scanner-> | ||
+ | $scanner-> | ||
+ | my $lista = $ARGV[0]; | ||
+ | my $opciones_scan = "-sS -A -vv -p0-65535 -sV -O -iL $lista"; | ||
+ | print " | ||
+ | print " | ||
+ | $scanner-> | ||
+ | |||
+ | sub scan_started { | ||
+ | my $self = shift; | ||
+ | my $host = shift; | ||
+ | $hostname = $host-> | ||
+ | $addresses = join(',', | ||
+ | my $status = $host-> | ||
+ | # print " | ||
+ | } | ||
+ | |||
+ | sub port_found { | ||
+ | my $self = shift; | ||
+ | my $host = shift; | ||
+ | my $port = shift; | ||
+ | no warnings; | ||
+ | my $name = $host-> | ||
+ | my $puerto = $port-> | ||
+ | if ($puerto eq " | ||
+ | elsif($puerto eq " | ||
+ | my $proto= $port-> | ||
+ | if ($proto eq " | ||
+ | elsif($proto eq " | ||
+ | my $salida_puerto = join(''," | ||
+ | print " | ||
+ | } | ||
+ | |||
+ | sub scan_complete { | ||
+ | my $self = shift; | ||
+ | my $host = shift; | ||
+ | no warnings; | ||
+ | |||
+ | for my $match ($host-> | ||
+ | print " | ||
+ | } | ||
+ | |||
+ | for my $c ($host-> | ||
+ | # print "-- " . $c-> | ||
+ | print "- OS generation: " . $c-> | ||
+ | print "- OS family: | ||
+ | print "- OS Type: " | ||
+ | } | ||
+ | } | ||
+ | </ | ||
+ | |||
+ | ==== hping3 ==== | ||
+ | **hping3** is a free packet generator and analyzer for the TCP/IP protocol. Hping is one of the de-facto tools for security auditing and testing of firewalls and networks, and was used to exploit the Idle Scan scanning technique now implemented in the Nmap port scanner. The new version of hping, hping3, is scriptable using the Tcl language and implements an engine for string based, human readable description of TCP/IP packets, so that the programmer can write scripts related to low level TCP/IP packet manipulation and analysis in a very short time. | ||
+ | |||
+ | Like most tools used in computer security, hping3 is useful to security experts. | ||
+ | |||
+ | hping3 should be used to… *Traceroute/ | ||
+ | |||
+ | == Few commands == | ||
+ | Finding Hping3 | ||
+ | < | ||
+ | hping3 –h | ||
+ | </ | ||
+ | hping3 Default | ||
+ | < | ||
+ | hping3 -S 192.168.1.105 -p 80 | ||
+ | </ | ||
+ | Fragment Packets with hping3 | ||
+ | < | ||
+ | hping3 -f 192.168.1.105 -p 80 | ||
+ | </ | ||
+ | Sending Data with hping3 | ||
+ | < | ||
+ | hping3 -f 192.168.1.105 -p 80 -d 10 -E malware | ||
+ | </ | ||
+ | Traceroute with hping3 | ||
+ | < | ||
+ | hping3 -z -t 1 -S google.com -p 80 | ||
+ | </ | ||
+ | Predicting Sequence Numbers with hping3 | ||
+ | < | ||
+ | hping3 -Q -S google.com -p 80 | ||
+ | </ | ||
+ | hping3 for Uptime | ||
+ | < | ||
+ | hping3 --tcp-timestamp -S google.com -p 80 | ||
+ | </ | ||
+ | |||
+ | Ref.: @cyberhawksecurity | ||
+ |
enlaces/utilidades_de_red.txt · Última modificación: 2019/01/22 15:34 por cayu