[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: pf pauses in sending traffic



On the pf box itself, running a ping to a directly connected box, I get:
64 bytes from 116.23.162.6: icmp_seq=1134 ttl=128 time=0.427 ms
ping: sendto: No route to host
ping: wrote 116.23.162.6 64 chars, ret=-1
ping: sendto: No route to host
ping: wrote 116.23.162.6 64 chars, ret=-1
ping: sendto: No route to host
ping: wrote 116.23.162.6 64 chars, ret=-1
64 bytes from 116.23.162.6: icmp_seq=1138 ttl=128 time=0.493 ms
What would cause that?  The physical interface never drops.
On Mon, 13 Sep 2004 10:47:09 -0700, matthew zeier <[email protected]> wrote:
> I'm seeing sporadic packet loss through an openbsd 3.5 box running pf.
> 
> While running 'tcpdump -n -e -ttt -i pflog0' on the pf box and a ping
> on another box, I see:
> 
> 64 bytes from 116.23.162.6: icmp_seq=103. time=0. ms
> 64 bytes from 116.23.162.6: icmp_seq=104. time=0. ms
> 64 bytes from 116.23.162.6: icmp_seq=105. time=0. ms
> 64 bytes from 116.23.162.6: icmp_seq=124. time=1. ms
> 64 bytes from 116.23.162.6: icmp_seq=125. time=1. ms
> 64 bytes from 116.23.162.6: icmp_seq=126. time=3. ms
> 
> And the tcpdump window stops logging, although the box itself is still
> responsive.  This is manifesting itself in slow http connections and
> RDP session resets.  Site performance is now considered "slow".
> 
> Both fxp0 (outside) and fxp1 (inside interface) are trunks with
> various vlan interfaces and carp interfaces with it's standby unit.
> 
> I'm stumped where else to look.  Any clues?
> 
> --
> matthew zeier - "But if you only have love for your own race, Then you only
> leave space to discriminate, And to discriminate only generates hate." - BEP
> 
-- 
--
matthew zeier - "But if you only have love for your own race, Then you only     
leave space to discriminate, And to discriminate only generates hate." - BEP