Bug #2173
closedpfsync errors
0%
Description
After upgrading from 2.0-RC3 to 2.0.1, the pfsync0 interface started reporting send errors.
[2.0.1-RELEASE][admin@host.name.removed]/root(25): netstat -s -p pfsync
pfsync:
1492961 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
101217 failed state lookup/inserts
482055153 packets sent (IPv4)
0 packets sent (IPv6)
0 send failed due to mbuf memory error
4499736 send error
Manually adjusting the MTU of the pfsync0 and carp interfaces seemed to help. An increase in the number of states seemed to make the problem worse. As far as I can tell the problem appears on systems with a large number of states and/or a large number of state changes. I tried both multicast and unicast settings for pfsync, same problem. The Carp interface does not report any errors, only the pfsync0 interface. I believe the hardware and physical layers are working - the problem started after moving to 2.0.1. I've tried all available configuration options and the forum and have been unable to solve the problem. There may be more information in this forum post:
http://forum.pfsense.org/index.php/topic,45831.0.html