Re: tcp md5 checksums broken in 7.0-beta3

t-tcp-syncache.c-20071126-01.diff I'll try to find your bug the next days (in case you find anything let me know). I don't know how much quagga does these days but policies are setup correctly on both machines and you are not finding any failed SADB lookup warninge in dmesg on the 7 mach

Re: Switch pfil(9) to rmlocks

* Robert Watson <[EMAIL PROTECTED]> [071126 12:37] wrote: > > On Fri, 23 Nov 2007, Max Laier wrote: > > >attached is a diff to switch the pfil(9) subsystem to rmlocks, which are > >more suited for the task. I'd like some exposure before doing the switch, > >but I don't expect any fallout. Thi

Re[2]: Broadcom NetXtreme II BMC5708 no carrier

Hello PY> It seems that mii_ticks is not kicked at all in auto-negotiation PY> phase. From the output of forced 1000baseSX media configuration I PY> guess BRGPHY_BMSR_ACOMP bit in BRGPHY_MII_BMSR is not updated on PY> 5708S. Mabe davidch know better what's going on 5708S. (CCed) PY> How about atta

Re: Switch pfil(9) to rmlocks

On Fri, 23 Nov 2007, Max Laier wrote: attached is a diff to switch the pfil(9) subsystem to rmlocks, which are more suited for the task. I'd like some exposure before doing the switch, but I don't expect any fallout. This email is going through the patched pfil already - twice. FYI, since

tcp md5 checksums broken in 7.0-beta3

Hi, Are TCP MD5 checksums working at all in freebsd7.0-beta3? I've got two physically identical machines, one running 6.2 and the other 7.0-beta3. Both are running quagga 0.99.9 with the md5 patch. On the 6.2 box, packets are being correctly tagged, according to tcpdump (with the print-tcp.c memc

6.2+pf+CARP bandwidth issues

Happy monday folks! We have a couple of Dell PowerEdge 1650 systems in a CARP setup with pf as our firewall cluster. I've noticed that if I connect my laptop behind these systems, I can achieve about 600kbps down and about 1100kpbs upload. If I connect to the other side, bypassing these

Re: TCP ECN patch for review

Ok, after two changes, the implementation seems ready. You can grab the new diff at the same location: http://people.freebsd.org/~rpaulo/tcp_ecn.diff I tested this on the netperf cluster using pf/altq as the "congested" router. The following configuration was used: altq on em0

Current problem reports assigned to freebsd-net@FreeBSD.org

Current FreeBSD problem reports Critical problems S Tracker Resp. Description f kern/115360 net[ipv6] IPv6 address and if_bridge don't play well toge 1 problem total. Serious problems S Tracker