On Tue, Jan 31, 2006 at 09:48:13AM -0600, Miguel wrote:
> Hi, im having serious problems with (i think) arp protocol, my openbsd
> firewall always tries to resolve the arp address, look at this:
>
>
> # ping 200.13.161.2
> PING 200.13.161.2 (200.13.161.2): 56 data bytes
> ping: sendto: No route to host
> ping: wrote 200.13.161.2 64 chars, ret=-1
> ping: sendto: No route to host
> ping: wrote 200.13.161.2 64 chars, ret=-1
> ping: sendto: No route to host
> ping: wrote 200.13.161.2 64 chars, ret=-1
> ping: sendto: No route to host
> ping: wrote 200.13.161.2 64 chars, ret=-1
> ping: sendto: No route to host
> ping: wrote 200.13.161.2 64 chars, ret=-1
> ping: sendto: No route to host
> ping: wrote 200.13.161.2 64 chars, ret=-1
> ping: sendto: No route to host
> ping: wrote 200.13.161.2 64 chars, ret=-1
> 64 bytes from 200.13.161.2: icmp_seq=7 ttl=255 time=0.684 ms
> 64 bytes from 200.13.161.2: icmp_seq=8 ttl=255 time=0.306 ms
> 64 bytes from 200.13.161.2: icmp_seq=9 ttl=255 time=0.494 ms
> 64 bytes from 200.13.161.2: icmp_seq=10 ttl=255 time=0.381 ms
> --- 200.13.161.2 ping statistics ---
> 11 packets transmitted, 4 packets received, 63.6% packet loss
> round-trip min/avg/max/std-dev = 0.306/0.466/0.684/0.143 ms
> # ping 200.13.161.2
> PING 200.13.161.2 (200.13.161.2): 56 data bytes
> ping: sendto: No route to host
> ping: wrote 200.13.161.2 64 chars, ret=-1
> ping: sendto: No route to host
> ping: wrote 200.13.161.2 64 chars, ret=-1
> ping: sendto: No route to host
> ping: wrote 200.13.161.2 64 chars, ret=-1
> ping: sendto: No route to host
> ping: wrote 200.13.161.2 64 chars, ret=-1
> 64 bytes from 200.13.161.2: icmp_seq=4 ttl=255 time=0.717 ms
> 64 bytes from 200.13.161.2: icmp_seq=5 ttl=255 time=0.478 ms
> 64 bytes from 200.13.161.2: icmp_seq=6 ttl=255 time=0.512 ms
> --- 200.13.161.2 ping statistics ---
> 7 packets transmitted, 3 packets received, 57.1% packet loss
> round-trip min/avg/max/std-dev = 0.478/0.569/0.717/0.105 ms
>
>
> first, i get No route to host, after a few seconds i got response, a
> few second later a try again and the same No route to host problem.
> any advise?
There's an arp(8) command you can use to check your suspicions.
Otherwise, I'd like a packet trace - any chance of running tcpdump
-nvvvXs 65535 host 200.13.161.2 while doing the above?
(Though I'm not certain you are right about arp being the problem - if
it was, why'd the second ping have the same problem? Arp is cached.)
Joachim
