Re: TCP options order changed in FreeBSD 7, incompatible with some routers

2008-03-12 Thread Andre Oppermann
Kip Macy wrote: Are you running 7.0-RELEASE? What I believe was this issue was a showstopper for it, so I'm surprised to hear of it now. No, this is a different issue and not really the fault of TCP but of certain cable modem vendors with broken code in their devices. FreeBSD is fully compliant

Re: TCP options order changed in FreeBSD 7, incompatible with some routers

2008-03-12 Thread Jake Rizzo
Exact same problem that i'm having. I confirmed it exists in 7.0 only since downgrading one of our servers back to 6.3 stable allowed the same clients to connect again. This seems to work for us as a workaround: sysctl net.inet.tcp.sack.enable=0 On 3/12/08, d.s. al coda <[EMAIL PROTECTED]>

Re: TCP options order changed in FreeBSD 7, incompatible with some routers

2008-03-12 Thread Robert Watson
On Wed, 12 Mar 2008, Andre Oppermann wrote: Kip Macy wrote: Are you running 7.0-RELEASE? What I believe was this issue was a showstopper for it, so I'm surprised to hear of it now. No, this is a different issue and not really the fault of TCP but of certain cable modem vendors with broken c

VLAN trunking and fragmentation

2008-03-12 Thread Giulio Ferro
I need to configure ports to work with multiple vlan on my redundant freebsd router/firewall. In order to setup my test environment I have 2 freebsd boxes 7.0 STABLE amd64 both with gigabit realtek (re0). According to what the man says, these cards should support vlan in hardware. These PCs ar

Re: TCP options order changed in FreeBSD 7, incompatible with some routers

2008-03-12 Thread Mike Silbersack
On Tue, 11 Mar 2008, d.s. al coda wrote: Hi, We recently upgraded one of our webservers to FreeBSD 7, and we started receiving complaints from some users not able to connect to that server anymore. On top of that, users were saying that the problem only occurred on Windows (at least, the ones w

Re: TCP options order changed in FreeBSD 7, incompatible with some routers

2008-03-12 Thread Bjoern A. Zeeb
On Tue, 11 Mar 2008, d.s. al coda wrote: - FreeBSD 7 has (there is of course an aligning nop after the eol, which tcpdump skips) Which is a bug (the nop after the EOL) that I recently fixed in HEAD. I am still curious to know if it's only ordering or the invalid padding or both that keeps cli

FYI: inpcb/pcbinfo mutex -> rwlock at some point in the mid-distant future

2008-03-12 Thread Robert Watson
FYI: Kris Kennaway and I have been working on diagnosing and addressing network stack contention and scheduling issues for high performance DNS serving with nsd and bind9. One of the changes in the pipeline is converting from using a mutex to protect the pcbinfo and inpcb data structures to

Re: TCP options order changed in FreeBSD 7, incompatible with some routers

2008-03-12 Thread Matt Reimer
On Tue, Mar 11, 2008 at 5:56 PM, d.s. al coda <[EMAIL PROTECTED]> wrote: > Hi, > We recently upgraded one of our webservers to FreeBSD 7, and we started > receiving complaints from some users not able to connect to that server > anymore. On top of that, users were saying that the problem only oc

Re: TCP options order changed in FreeBSD 7, incompatible with some routers

2008-03-12 Thread Kip Macy
On Wed, Mar 12, 2008 at 1:48 AM, Andre Oppermann <[EMAIL PROTECTED]> wrote: > Kip Macy wrote: > > Are you running 7.0-RELEASE? What I believe was this issue was a > > showstopper for it, so I'm surprised to hear of it now. > > No, this is a different issue and not really the fault of TCP but >

Re: VLAN trunking and fragmentation

2008-03-12 Thread Sean Chittenden
interface ethernet 1/g1 switchport mode trunk switchport trunk allowed vlan add 10 exit I think this is an issue with default VLAN membership. I have this config running on *hundreds* of servers without issue. Since Dell should be a cisco rip-off, on your switchport config, throw in (hav

FreeBSD 6.3 fxp0 MBUF and PAE

2008-03-12 Thread Daniel Dias Gonçalves
Hi, When using the interface fxp0 with PAE enable in kernel, occurs the following error: fxp0: can't map mbuf (error 12) ... it repeats, repeats and lost communication. Information: 6.3-RELEASE [EMAIL PROTECTED]:4:0: class=0x02 card=0x00708086 chip=0x12298086 rev=0x10 hdr=0x00 vend

Re: VLAN trunking and fragmentation

2008-03-12 Thread Remko Lodder
On Wed, March 12, 2008 8:38 pm, Sean Chittenden wrote: >> interface ethernet 1/g1 >> switchport mode trunk >> switchport trunk allowed vlan add 10 >> exit > > I think this is an issue with default VLAN membership. I have this > config running on *hundreds* of servers without issue. Since Dell >

Re: VLAN trunking and fragmentation

2008-03-12 Thread Giulio Ferro
Sam Leffler wrote: You failed to provide the output of ifconfig on your running system. Be sure any checksum offload is disabled (should be by the bridge). Sam My bad. I switched off checksum offload in /etc/rc.conf like this: ifconfig_re0="inet 192.168.60.1 netmask 255.255.255.0 -rxcsum

Re: VLAN trunking and fragmentation

2008-03-12 Thread Giulio Ferro
Sean Chittenden wrote: interface ethernet 1/g1 switchport mode trunk switchport trunk allowed vlan add 10 exit I think this is an issue with default VLAN membership. I don't think it's where the problem lies, otherwise even a simple ping wouldn't work. The problem here explicitly arises whe

Re: VLAN trunking and fragmentation

2008-03-12 Thread Ingo Flaschberger
Dear Giuilio, Sean Chittenden wrote: interface ethernet 1/g1 switchport mode trunk switchport trunk allowed vlan add 10 exit I think this is an issue with default VLAN membership. I don't think it's where the problem lies, otherwise even a simple ping wouldn't work. The problem here explic

Re: VLAN trunking and fragmentation

2008-03-12 Thread Andrew Thompson
On Wed, Mar 12, 2008 at 12:38:06PM -0700, Sean Chittenden wrote: >> interface ethernet 1/g1 >> switchport mode trunk >> switchport trunk allowed vlan add 10 >> exit > > I think this is an issue with default VLAN membership. I have this config > running on *hundreds* of servers without issue. Sin

Re: VLAN trunking and fragmentation

2008-03-12 Thread Sean Chittenden
interface ethernet 1/g1 switchport mode trunk switchport trunk allowed vlan add 10 exit I think this is an issue with default VLAN membership. I don't think it's where the problem lies, otherwise even a simple ping wouldn't work. The problem here explicitly arises when packets are fragmented

Re: TCP options order changed in FreeBSD 7, incompatible with some routers

2008-03-12 Thread Andre Oppermann
d.s. al coda wrote: Hi, We recently upgraded one of our webservers to FreeBSD 7, and we started receiving complaints from some users not able to connect to that server anymore. On top of that, users were saying that the problem only occurred on Windows (at least, the ones who had more than on OS

Re: VLAN trunking and fragmentation

2008-03-12 Thread Brooks Davis
On Thu, Mar 13, 2008 at 11:13:14AM +1300, Andrew Thompson wrote: > On Wed, Mar 12, 2008 at 12:38:06PM -0700, Sean Chittenden wrote: > >> interface ethernet 1/g1 > >> switchport mode trunk > >> switchport trunk allowed vlan add 10 > >> exit > > > > I think this is an issue with default VLAN membersh

Re: [Wireless] Can't connect to wlan

2008-03-12 Thread Yousif Hassan
On Wed, 2008-03-12 at 08:06 +1030, Benjamin Close wrote: > Alphons "Fonz" van Werven wrote: > > Mel wrote: > > > >>> Do the recent patches by Andrew make a difference? > >>> > >>> http://people.freebsd.org/~thompsa/wpi_head.diff > >>> http://people.freebsd.org/~thompsa/wpi_releng7.diff > > (c

Re: FreeBSD 6.3 fxp0 MBUF and PAE

2008-03-12 Thread Pyun YongHyeon
On Wed, Mar 12, 2008 at 04:53:18PM -0300, Daniel Dias Gon?alves wrote: > Hi, > > When using the interface fxp0 with PAE enable in kernel, occurs the > following error: > > fxp0: can't map mbuf (error 12) > ... > > it repeats, repeats and lost communication. > error 12 means ENOMEM.

Re: kern/121374: [ipsec] SP refcnt increases with each packet in ipv6 with new IPSEC

2008-03-12 Thread Cyrus Rahman
> Synopsis: [ipsec] SP refcnt increases with each packet in ipv6 with new IPSEC > > Wait for feedback if the patch presented is fine. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=121374 Ok, I've tested this patch. Exchanging packets through a policy works after a fashion, but after sending on

Re: [Wireless] Can't connect to wlan

2008-03-12 Thread Sam Leffler
Yousif Hassan wrote: On Wed, 2008-03-12 at 08:06 +1030, Benjamin Close wrote: Alphons "Fonz" van Werven wrote: Mel wrote: Do the recent patches by Andrew make a difference? http://people.freebsd.org/~thompsa/wpi_head.diff http://people.freebsd.org/~thompsa/wpi_releng7.diff

Re: VLAN trunking and fragmentation

2008-03-12 Thread Pyun YongHyeon
On Wed, Mar 12, 2008 at 10:22:34PM +0100, Giulio Ferro wrote: > Sam Leffler wrote: > >You failed to provide the output of ifconfig on your running system. > >Be sure any checksum offload is disabled (should be by the bridge). > > > >Sam > My bad. > > I switched off checksum offload i

Re: FYI: inpcb/pcbinfo mutex -> rwlock at some point in the mid-distant future

2008-03-12 Thread Bruce M. Simpson
Robert Watson wrote: One of those issues is that we need to demonstrate to ourselves that exclusive access contention is managed as well with rwlocks as with sleep mutexes, as these locks would continue to be fairly highly contended in TCP. The other issue is that rwlocks don't support full p

Re: TCP options order changed in FreeBSD 7, incompatible with some routers

2008-03-12 Thread Mike Silbersack
On Tue, 11 Mar 2008, d.s. al coda wrote: - FreeBSD 7 has (there is of course an aligning nop after the eol, which tcpdump skips) Jake Rizzo sent me some updated tcpdumps comparing 6.3 vs 7.0, and that aligning NOP that tcpdump (and wireshark) omit seems to be the only difference. Here's

Re: TCP options order changed in FreeBSD 7, incompatible with some routers

2008-03-12 Thread Mike Silbersack
On Wed, 12 Mar 2008, Mike Silbersack wrote: I think we will need to fix tcpdump before trying to finish diagnosing this problem. We were missing key information before. -Mike Hm, that was far easier than expected. Patch attached. Here's what the two tcpdumps show now: 6.3: IP A > B : S

Re: TCP options order changed in FreeBSD 7, incompatible with some routers

2008-03-12 Thread Mike Silbersack
On Wed, 12 Mar 2008, Bjoern A. Zeeb wrote: On Tue, 11 Mar 2008, d.s. al coda wrote: - FreeBSD 7 has (there is of course an aligning nop after the eol, which tcpdump skips) Which is a bug (the nop after the EOL) that I recently fixed in HEAD. I am still curious to know if it's only ordering