up to the plate and this support will be
integrated into -current.
--
othermark
atkin901 at nospam dot yahoo dot com
(!wired)?(coffee++):(wired);
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
6))
> + if (memcmp(rcvsig, sig, TCP_SIGLEN) == 0)
> return (SIGNATURE_VALID);
> else
> return (SIGNATURE_INVALID);
The original code there certainly looks wrong! After patching, FreeBSD's
checksum returns valid. I'll have to see what's up with the originating
check
72.16.18.164.50850: S
3974454780:3974454780(0) ack 371298115 win 65535
Now it could be that the tcp stack is just sending garbage for the MD5
option when it receives it on a socket that doesn't have some sort of
socket option configured (which would be bad).
othermark
atkin901 at nospam dot yaho
