Packet Loss on FW1 but not FW2 (CARP + PF on FBSD8)
Pyun YongHyeon
pyunyh at gmail.com
Mon May 17 17:33:18 UTC 2010
On Fri, May 14, 2010 at 05:27:25PM -0400, list at cykotix.com wrote:
> Quoting Pyun YongHyeon <pyunyh at gmail.com>:
> >>>Show me the output of "sysctl dev.vr.0.stats=1" and "netstat -ndI vr0".
> >>
> >>soekris1# sysctl dev.vr.0.stats=1
> >>dev.vr.0.stats: -1 -> -1
> >>
> >
> >Please check the output of console. It would have printed some MAC
> >counters maintained in driver.
>
> >>soekris1# netstat -ndI vr0
> >>Name Mtu Network Address Ipkts Ierrs Opkts
> >>Oerrs Coll Drop
> >>vr0 1500 <Link#1> 00:00:24:cc:cb:94 17491 0 14993
> >> 0 0 0
> >>vr0 1500 98.xxx.xxx.56 98.xxx.xxx.59 992 - 9374
> >> - - -
> >>
>
> FW1:
> vr0 statistics:
> Outbound good frames : 14992
> Inbound good frames : 17486
> Outbound errors : 0
> Inbound errors : 0
> Inbound no buffers : 0
> Inbound no mbuf clusters: 0
> Inbound FIFO overflows : 0
> Inbound CRC errors : 0
> Inbound frame alignment errors : 0
> Inbound giant frames : 0
> Inbound runt frames : 0
> Outbound aborted with excessive collisions : 0
> Outbound collisions : 0
> Outbound late collisions : 0
> Outbound underrun : 0
> PCI bus errors : 0
> driver restarted due to Rx/Tx shutdown failure : 0
>
I thought it could be a bug in vr(4) but it seems vr(4) had zero
dropped packets. Let pf(4) log dropped packet with pflog(4) and see
why pf(4) dropped packets.
>
> >No Ierrs, so MAC counters would be more helpful here.
>
> >>soekris2# sysctl dev.vr.0.stats=1
> >>dev.vr.0.stats: -1 -> -1
> >>
> >>soekris2# netstat -ndI vr0
> >>Name Mtu Network Address Ipkts Ierrs Opkts
> >>Oerrs Coll Drop
> >>vr0 1500 <Link#1> 00:00:24:ca:40:60 575909 0 588703
> >> 0 0 0
> >>vr0 1500 98.xxx.xxx.56 98.xxx.xxx.60 10029 - 53106
> >> - - -
>
> FW2:
> vr0 statistics:
> Outbound good frames : 588054
> Inbound good frames : 575353
> Outbound errors : 0
> Inbound errors : 0
> Inbound no buffers : 0
> Inbound no mbuf clusters: 0
> Inbound FIFO overflows : 0
> Inbound CRC errors : 0
> Inbound frame alignment errors : 0
> Inbound giant frames : 0
> Inbound runt frames : 0
> Outbound aborted with excessive collisions : 0
> Outbound collisions : 0
> Outbound late collisions : 0
> Outbound underrun : 0
> PCI bus errors : 0
> driver restarted due to Rx/Tx shutdown failure : 0
>
> Patrick
More information about the freebsd-net
mailing list