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
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
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
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
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
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
> 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
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.
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
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
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
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
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
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
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
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
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
>
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
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
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
>
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
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
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
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
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
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
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]>
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
28 matches
Mail list logo