Sam Leffler wrote:
Darren Pilgrim wrote:
Are you referring to the problem in cvsup tests where it will suddenly
stop with a "Network write failure" error?
Yes. The issue was that when crypto was done in the host it was
sometimes being done in-place on mbufs still owned by the socket
(exactly when depended on a lot of things but turning down the mtu
increased the likelihood). If this happened and tcp retransmitted the
previously encrypted data then it would send garbage.
As Max said this was in the net80211 layer and affected all drivers
depending on the host to do crypto. It'll get mfc'd this week (re
permitting).
I'm glad to hear I finally have a driver for my wireless NIC that's as
stable it (currently) gets, since the above is the only problem I've been
able to coax out of my machine. So Max... great job!
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
