pfsync errors

[Bill Marquette]

On 8/27/07, Bill Marquette <bill.marquette at gmail.com> wrote:
> > > Here's what we get with the patch:
> > > pfsync_senddef: ip_output 64
> >
> > that's EHOSTDOWN ... that's strange.  Are you using syncpeer?

After converting both sides to using syncpeer, I now got this in my
dmesg after reboot:
<snip most of dmesg you've already seen>
Trying to mount root from ufs:/dev/da0s2a
pfsync_senddef: ip_output 65
pfsync_senddef: ip_output 65

$ netstat -s -ppfsync && sleep 1 && netstat -s -ppfsync
pfsync:
        699811 packets received (IPv4)
        0 packets received (IPv6)
                0 packets discarded for bad interface
                0 packets discarded for bad ttl
                0 packets shorter than header
                0 packets discarded for bad version
                0 packets discarded for bad HMAC
                0 packets discarded for bad action
                0 packets discarded for short packet
                0 states discarded for bad values
                0 stale states
                61740 failed state lookup/inserts
        46728 packets sent (IPv4)
        0 packets sent (IPv6)
                0 send failed due to mbuf memory error
                23020 send error
pfsync:
        704677 packets received (IPv4)
        0 packets received (IPv6)
                0 packets discarded for bad interface
                0 packets discarded for bad ttl
                0 packets shorter than header
                0 packets discarded for bad version
                0 packets discarded for bad HMAC
                0 packets discarded for bad action
                0 packets discarded for short packet
                0 states discarded for bad values
                0 stale states
                62032 failed state lookup/inserts
        47070 packets sent (IPv4)
        0 packets sent (IPv6)
                0 send failed due to mbuf memory error
                23221 send error

The other pfsyncstats.pfsyncs_oerrors++ is after a IF_HANDOFF macro, I
traced it back to if_handoff() in if.c, but I'm not sure how to track
it down any further as it look like it's _IF_QFULL(ifq) that's
triggering the return 0.

I'm going to toy with some settings for the em(4) driver in
loader.conf and see if I can raise the txd and rxd descriptors since
we're not running on 82542 or 82543 chipped hardware we can go above
256 descriptors.

--Bill