Netgate Store

Author Topic: hping3 --udp pfSense no responde  (Read 1418 times)

0 Members and 1 Guest are viewing this topic.

Offline mauricioniņoavella

  • Jr. Member
  • **
  • Posts: 94
  • Karma: +0/-0
    • View Profile
hping3 --udp pfSense no responde
« on: July 25, 2012, 01:29:05 pm »
Compañeros

me pude colaborar con este error, que se me esta presentando, cuando hago un ping de esta forma  hping3 --udp 192.168.17.1  pfSense no responde , pero cuando lo hago a una maquina local si funciona


no tengo rules que bloque esta any-any en la LAN

gracias
« Last Edit: July 25, 2012, 01:32:53 pm by mauricioniņoavella »

Offline periko

  • Hero Member
  • *****
  • Posts: 1260
  • Karma: +25/-2
  • pheriko
    • View Profile
    • Soporte de Pfsense y Linux
Re: hping3 --udp pfSense no responde
« Reply #1 on: July 25, 2012, 06:08:03 pm »
  No creo que vayas a recibir nada de respuesta, pero puedes verificar con tcpdump en pfsense que si le llegan los paquetes, solo que yo lo he visto de otra manera:

  client1:

  hping3 --udp -p 10000 --destport 53 192.168.2.4 (IP Pfsense)

  Pfsense:

  tcpdump -i vr0 -vvv port 53

16:07:49.923099 IP (tos 0x0, ttl 64, id 22542, offset 0, flags [none], proto UDP (17), length 28)
    chiquitin.x.local.2422 > gw.x.local.domain: [udp sum ok] [|domain]
16:07:50.923114 IP (tos 0x0, ttl 64, id 24494, offset 0, flags [none], proto UDP (17), length 28)
    chiquitin..xlocal.2423 > gw.x.local.domain: [udp sum ok] [|domain]
16:07:51.923387 IP (tos 0x0, ttl 64, id 13893, offset 0, flags [none], proto UDP (17), length 28)
    chiquitin.local.2424 > gw.x.local.domain: [udp sum ok] [|domain]
16:07:52.923130 IP (tos 0x0, ttl 64, id 16656, offset 0, flags [none], proto UDP (17), length 28)
    chiquitin..local.2425 > gw.x.local.domain: [udp sum ok] [|domain]
16:07:53.923184 IP (tos 0x0, ttl 64, id 39069, offset 0, flags [none], proto UDP (17), length 28)
    chiquitin.x.local.2426 > gw.x.local.domain: [udp sum ok] [|domain]
16:07:54.923205 IP (tos 0x0, ttl 64, id 64819, offset 0, flags [none], proto UDP (17), length 28)
    chiquitin.x.local.2427 > gw.x.local.domain: [udp sum ok] [|domain]
16:07:55.923241 IP (tos 0x0, ttl 64, id 30111, offset 0, flags [none], proto UDP (17), length 28)
    chiquitin.x.local.2428 > gw.x.local.domain: [udp sum ok] [|domain]
16:07:56.923302 IP (tos 0x0, ttl 64, id 18009, offset 0, flags [none], proto UDP (17), length 28)
    chiquitin.x.local.2429 > gw.x.local.domain: [udp sum ok] [|domain]
16:07:57.923368 IP (tos 0x0, ttl 64, id 747, offset 0, flags [none], proto UDP (17), length 28)
    chiquitin.x.local.venus > gw.x.local.domain: [udp sum ok] [|domain]

 Le llegan por que le llegan!!!
Necesitan Soporte de Pfsense en Mexico?/Need Pfsense Support in Mexico?
https://www.facebook.com/BajaOpenSolutions
https://www.youtube.com/channel/UCrRxfZbTzNwlWpKTjqtDANA
Estamos en Tijuana, pero no es obstaculo para brindarte nuestro servicio.
We are in Tijuana, but is not an obstacle to give you support.

Offline mauricioniņoavella

  • Jr. Member
  • **
  • Posts: 94
  • Karma: +0/-0
    • View Profile
Re: hping3 --udp pfSense no responde
« Reply #2 on: July 31, 2012, 09:06:37 am »
periko
capture esta traza, no se si se este presentando algún problema ya que al parecer no debería ser la respuesta adecuada

#hping3 --udp  192.168.200.1

host que hace hping3 >>>192.168.201.6 al pfsense que tiene la IP 192.168.200.1

y no se que es lo que esta pasando

[2.0.1-RELEASE][root@mypfsense.carron.com.co]/root(6): tcpdump -n -i em1 src host 192.168.201.6
tcpdump: verbose output suppressed, use -v oryum groupinstall "Desktop" "Desktop Platform" "X Window System" "Fonts" -vv for full protocol decode
listening on em1, link-type EN10MB (Ethernet), capture size 96 bytes
09:05:21.114337 IP 192.168.201.6.49263 > 192.168.200.1.22: Flags [.], ack 3139953988, win 380, options [nop,nop,TS val 51524691 ecr 4054034989], length 0
09:05:21.181049 IP 192.168.201.6.2900 > 192.168.200.1.0: UDP, length 0
09:05:22.114755 IP 192.168.201.6.49263 > 192.168.200.1.22: Flags [.], ack 193, win 391, options [nop,nop,TS val 51524791 ecr 4054035989], length 0
09:05:22.114767 IP 192.168.201.6.49263 > 192.168.200.1.22: Flags [.], ack 305, win 391, options [nop,nop,TS val 51524791 ecr 4054035989], length 0
09:05:22.181341 IP 192.168.201.6.2901 > 192.168.200.1.0: UDP, length 0
09:05:23.115672 IP 192.168.201.6.49263 > 192.168.200.1.22: Flags [.], ack 641, win 402, options [nop,nop,TS val 51524891 ecr 4054036989], length 0
09:05:23.115686 IP 192.168.201.6.49263 > 192.168.200.1.22: Flags [.], ack 753, win 402, options [nop,nop,TS val 51524891 ecr 4054036989], length 0
09:05:23.181759 IP 192.168.201.6.2902 > 192.168.200.1.0: UDP, length 0
09:05:24.116715 IP 192.168.201.6.49263 > 192.168.200.1.22: Flags [.], ack 1169, win 414, options [nop,nop,TS val 51524991 ecr 4054037989], length 0
09:05:24.182052 IP 192.168.201.6.2903 > 192.168.200.1.0: UDP, length 0
09:05:25.117633 IP 192.168.201.6.49263 > 192.168.200.1.22: Flags [.], ack 1425, win 425, options [nop,nop,TS val 51525091 ecr 4054038989], length 0
09:05:25.182470 IP 192.168.201.6.2904 > 192.168.200.1.0: UDP, length 0
09:05:26.118551 IP 192.168.201.6.49263 > 192.168.200.1.22: Flags [.], ack 1681, win 436, options [nop,nop,TS val 51525191 ecr 4054039989], length 0
09:05:26.182764 IP 192.168.201.6.2905 > 192.168.200.1.0: UDP, length 0
09:05:27.119468 IP 192.168.201.6.49263 > 192.168.200.1.22: Flags [.], ack 1937, win 447, options [nop,nop,TS val 51525291 ecr 4054040988], length 0
09:05:27.183056 IP 192.168.201.6.2906 > 192.168.200.1.0: UDP, length 0
09:05:28.119636 IP 192.168.201.6.49263 > 192.168.200.1.22: Flags [.], ack 2193, win 459, options [nop,nop,TS val 51525391 ecr 4054041988], length 0
09:05:28.183473 IP 192.168.201.6.2907 > 192.168.200.1.0: UDP, length 0
09:05:29.120429 IP 192.168.201.6.49263 > 192.168.200.1.22: Flags [.], ack 2449, win 470, options [nop,nop,TS val 51525491 ecr 4054042987], length 0
09:05:29.183766 IP 192.168.201.6.2908 > 192.168.200.1.0: UDP, length 0
09:05:30.120597 IP 192.168.201.6.49263 > 192.168.200.1.22: Flags [.], ack 2705, win 481, options [nop,nop,TS val 51525591 ecr 4054043987], length 0
09:05:30.184184 IP 192.168.201.6.2909 > 192.168.200.1.0: UDP, length 0
09:05:31.121514 IP 192.168.201.6.49263 > 192.168.200.1.22: Flags [.], ack 2961, win 492, options [nop,nop,TS val 51525691 ecr 4054044986], length 0
09:05:31.184602 IP 192.168.201.6.2910 > 192.168.200.1.0: UDP, length 0
^C
24 packets captured
7867 packets received by filter
0 packets dropped by kernel

gracias por tu colaboración

Mauricio Niño
« Last Edit: July 31, 2012, 09:55:42 am by mauricioniņoavella »