At 08:27 AM 6/25/2007, Bill Moran wrote:
In response to Bill Moran <[EMAIL PROTECTED]>:
> In response to Adam McDougall <[EMAIL PROTECTED]>:
>
> > On Tue, Jun 12, 2007 at 10:19:49AM -0400, Bill Moran wrote:
> >
> >
> > This one has got me pretty befuddled.
> >
> > We're seeing some really od
In response to Bill Moran <[EMAIL PROTECTED]>:
> In response to Adam McDougall <[EMAIL PROTECTED]>:
>
> > On Tue, Jun 12, 2007 at 10:19:49AM -0400, Bill Moran wrote:
> >
> >
> > This one has got me pretty befuddled.
> >
> > We're seeing some really odd behaviour with FreeBSD ignoring S
In response to Adam McDougall <[EMAIL PROTECTED]>:
> On Tue, Jun 12, 2007 at 10:19:49AM -0400, Bill Moran wrote:
>
>
> This one has got me pretty befuddled.
>
> We're seeing some really odd behaviour with FreeBSD ignoring SYN packets.
> I've been trying to diagnose this for a couple o
David Cornejo wrote:
This may not be related, but I have a Soekris 4801 running CURRENT that
with a GENERIC kernel exhibits the behavior where TCP connects don't
happen. If I switch to an old kernel config file, it works..
This failure happens between this box and a RELENG_6 (updated last
we
This may not be related, but I have a Soekris 4801 running CURRENT
that with a GENERIC kernel exhibits the behavior where TCP connects
don't happen. If I switch to an old kernel config file, it works..
This failure happens between this box and a RELENG_6 (updated last
week), another CURRENT b
Bill Moran wrote this message on Tue, Jun 12, 2007 at 13:13 -0400:
> > b) you may run out of socket on the client side and reuse them
> > too fast. Try to lower net.inet.ip.portrange.first to 30,000
> > or so.
>
> I find that unlikely. The problem usually occurs reliably after less
>
On Tue, Jun 12, 2007 at 10:19:49AM -0400, Bill Moran wrote:
This one has got me pretty befuddled.
We're seeing some really odd behaviour with FreeBSD ignoring SYN packets.
I've been trying to diagnose this for a couple of weeks now, and my current
guess is that there's something wron
In response to Andre Oppermann <[EMAIL PROTECTED]>:
>
> Before we go into more detail:
>
> a) the em(4) driver is most likely totally unrelated to this
Are you saying it's more likely to be a tcp stack problem? As an experiment,
I tried to reproduce it over the loopback and was unable to, whi
Bill Moran wrote:
This one has got me pretty befuddled.
We're seeing some really odd behaviour with FreeBSD ignoring SYN packets.
I've been trying to diagnose this for a couple of weeks now, and my current
guess is that there's something wrong with the em driver. Here's a narrowed
down list of
Brief update to add another item to the list of things I've tried:
*) The problem occurs whether the em device is polling or not.
In response to Bill Moran <[EMAIL PROTECTED]>:
>
> This one has got me pretty befuddled.
>
> We're seeing some really odd behaviour with FreeBSD ignoring SYN packets.
This one has got me pretty befuddled.
We're seeing some really odd behaviour with FreeBSD ignoring SYN packets.
I've been trying to diagnose this for a couple of weeks now, and my current
guess is that there's something wrong with the em driver. Here's a narrowed
down list of what I've ruled out
11 matches
Mail list logo
