On Fri, Mar 07, 2008 at 02:00:04PM +0900, Pyun YongHyeon wrote:
>On Sun, Mar 02, 2008 at 07:57:28PM -0800, Christopher Cowart wrote:
>> While I have your attention, I am also suffering from a problem that was
>> reported to -questions here[1]. About 3 times a day, I'll see the
>> watchdog timeout (
Am So, 9.03.2008, 12:30, schrieb Wouter de Jong:
> (Sorry for double posting this to freebsd-questions before, but I think
> this
> place might be more appropriate).
indeed it is.
> We have 2 FreeBSD machines running as a firewall in a CARP+pf+pfsync
> setup.
> Worked great, however . last F
Synopsis: [wpi] System reboot after enabling DHCP on bge0 and assigning static
IP on wpi0
Responsible-Changed-From-To: freebsd-net->thompsa
Responsible-Changed-By: thompsa
Responsible-Changed-When: Sun Mar 9 21:20:07 UTC 2008
Responsible-Changed-Why:
I have been working on a wpi patch.
http://w
Synopsis: [patch] extend /sbin/arp to be able to create blackhole records
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: vwe
Responsible-Changed-When: Sun Mar 9 20:46:12 UTC 2008
Responsible-Changed-Why:
Over to maintainer(s).
http://www.freebsd.org/cgi/query-pr.
The following reply was made to PR kern/121518; it has been noted by GNATS.
From: Dimitar Peikov <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Cc:
Subject: Re: kern/121518: [wpi] System reboot after enabling DHCP on bge0
and assigning static IP on wpi0
Date: Sun, 09 Mar 20
Old Synopsis: System reboot after enabling DHCP on bge0 and assigning static IP
on wpi0
New Synopsis: [wpi] System reboot after enabling DHCP on bge0 and assigning
static IP on wpi0
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: S
Synopsis: [patch] ppp(8) lock file should not use symlink name
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: rwatson
Responsible-Changed-When: Sun Mar 9 13:07:30 UTC 2008
Responsible-Changed-Why:
Over to maintainers.
http://www.freebsd.org/cgi/query-pr.cgi?pr=112
Hi,
(Sorry for double posting this to freebsd-questions before, but I think this
place might be more appropriate).
We have 2 FreeBSD machines running as a firewall in a CARP+pf+pfsync setup.
Worked great, however . last Friday I noticed something weird.
I had to reboot the master machine,
On Sun, 9 Mar 2008, Jake Rizzo wrote:
The patch didn't work, but doing this:
sysctl net.inet.tcp.tso=0
sysctl net.inet.tcp.sack.enable=0
Allows the client to connect again. Since my ifconfig doesn't show that my
nic supports TSO then I presume it's the sack sysctl that's making it work.
The
The patch didn't work, but doing this:
sysctl net.inet.tcp.tso=0
sysctl net.inet.tcp.sack.enable=0
Allows the client to connect again. Since my ifconfig doesn't show that my
nic supports TSO then I presume it's the sack sysctl that's making it work.
The machine's a webserver serving almost exclu
10 matches
Mail list logo