On Wed, Jun 29, 2011 at 07:22:24PM +0200, Fabian Keil wrote:
> "Bjoern A. Zeeb" <[email protected]> wrote:
> > In short; please test!
>
> I didn't experience any real problems yet, but running
Hi Bjoern,
Unfortunately I've had MAJOR network problems since the pf upgrade.
Besides getting the "state key linking mismatch!" issue:
pf: state key linking mismatch! dir=OUT, if=fxp0, stored af=2, a0:
208.83.139.205:2703, a1: 74.95.12.85:20474, proto=6, found af=2, a0:
208.83.139.205:2703, a1: 74.95.12.85:20474, proto=6.
pf: state key linking mismatch! dir=OUT, if=fxp0, stored af=2, a0:
87.98.164.164:44387, a1: 74.95.12.85:53, proto=6, found af=2, a0:
87.98.164.164:44387, a1: 74.95.12.85:53, proto=6.
pf: state key linking mismatch! dir=OUT, if=fxp0, stored af=2, a0:
87.98.164.164:44387, a1: 74.95.12.85:53, proto=6, found af=2, a0:
87.98.164.164:44387, a1: 74.95.12.85:53, proto=6.
I found that my kernel (@ r223671) would stop sending packets 3-4 hours
after reboot. New connections could not be established, I could not ping
any of the direct connections on any of my interfaces. Existing
connections would remain established for quite some time (hours) but
eventually close also.
No amount of re-running /etc/rc.d/* scripts ('pf restart', 'netif
restart', 'routing restart', etc...) would bring back working networking.
Since reverting back to r223636, my kernel has had rock solid networking.
I have 'pfctl', 'netstat', 'netstat -rn', and 'sysctl -a' output from one
of these experiences. Would they be useful to you in looking into this?
--
-- David ([email protected])
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-pf
To unsubscribe, send any mail to "[email protected]"
