On Tue, 3 Nov 2009, John Baldwin wrote:
Several years ago Dillon added a feature to TCP that casued soreceive() to
send an ACK right away if data was drained from a TCP socket that had
previously advertised a zero-sized window. The current code requires the
receive window to be exactly zero for
Several years ago Dillon added a feature to TCP that casued soreceive() to
send an ACK right away if data was drained from a TCP socket that had
previously advertised a zero-sized window. The current code requires the
receive window to be exactly zero for this to kick in. If window scaling is
On Tue, Nov 03, 2009 at 12:45:52AM -0500, kalin m wrote:
>
> hi pyun... and all
>
> after a few hours i'm sorry to report that the card is visible but not
> usable (yet?!). here is what i have done so far:
>
> 1. got the files from http://svn.freebsd.org/viewvc/base/head/sys/dev/
> 2. app
On Nov 3, 2009, at 8:27, Barney Wolff wrote:
Power-cycle your cable box, leaving it off for a few minutes.
Cable co's seem to check the MAC, and take a while to forget
the previous one.
Hah - yeah, I tried that, too. No difference. (Plugging in one of
the macs and then another seems to wo
On Nov 3, 2009, at 8:21, JASSAL Aman wrote:
Hello,
The logs display something that I find very disturbing.
In the dhcpdump log, the DHCPDISCOVER message your interface sends an
erroneous MAC address, there is a "01:" that is added in front of the
actual MAC address of your interface. What is s
Power-cycle your cable box, leaving it off for a few minutes.
Cable co's seem to check the MAC, and take a while to forget
the previous one.
On Tue, Nov 03, 2009 at 07:47:14AM -0800, Ask Bjrn Hansen wrote:
> Hi everyone,
>
> After years with Speakeasy at home I'm trying out Time Warner Cable
>
Hello,
The logs display something that I find very disturbing.
In the dhcpdump log, the DHCPDISCOVER message your interface sends an
erroneous MAC address, there is a "01:" that is added in front of the
actual MAC address of your interface. What is sent in the discover message
is "01:00:..." inste
Hi everyone,
After years with Speakeasy at home I'm trying out Time Warner Cable
(we live too far from the CO to get good DSL speeds).
On OS X I plug-in and get an IP from their DHCP server:
http://dl.getdropbox.com/u/25895/dhcp/dhcp-osx.txt
On FreeBSD their DHCP server seems to jus
On Nov 1, 2009, at 19:09, Ask Bjørn Hansen wrote:
On a set of gw boxes I have 5 carp interfaces. 4 are working fine,
but on one for some reason the advskew setting isn't "sticking" (and
I get carp2: incorrect hash). I'm running 7.2-STABLE from a few
days ago.
gw-a# ifconfig carp2 vhid
Old Synopsis: Kernel panic during network activity on device ath in
7.2-RELEASE-p4
New Synopsis: [ath] [panic] Kernel panic during network activity on device ath
in 7.2-RELEASE-p4
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Tue
The following reply was made to PR kern/138999; it has been noted by GNATS.
From: dfil...@freebsd.org (dfilter service)
To: bug-follo...@freebsd.org
Cc:
Subject: Re: kern/138999: commit references a PR
Date: Tue, 3 Nov 2009 12:52:49 + (UTC)
Author: kib
Date: Tue Nov 3 12:52:35 2009
New
- Original Message
> From: VANHULLEBUS Yvan
> To: Gabe
> Cc: freebsd-net@freebsd.org
> Sent: Tue, November 3, 2009 2:41:14 AM
> Subject: Re: IPSEC NAT-T
>
> On Sun, Nov 01, 2009 at 09:00:30AM -0800, Gabe wrote:
> > Hello,
>
> Hi.
>
>
> > What's the latest "stable" patch available for
On Sun, Nov 01, 2009 at 09:00:30AM -0800, Gabe wrote:
> Hello,
Hi.
> What's the latest "stable" patch available for the latest 7.x source?
Stable patches, to be used with ipsec-tools 0.7 branch, are available
here:
http://people.freebsd.org/~vanhu/NAT-T/
As we're working on backporting FreeBSD
13 matches
Mail list logo
