Perhaps a quick "fix" to the bug would be to output a message to the console
when somebody tried to set the tcp.sendspace or tcp.recvspace space > 65535
* 2.
Regards,
Dave Seddon
Pieter de Boer writes:
Mike Silbersack wrote:
net.inet.tcp.sendspace=1024000
net.inet.tcp.recvspace=102400
Hi all,
I'm having a bit of a problem running 5.4-RELEASE and carp. All the
documentation that I read (man carp and other web based sources)
indicate to simply create my carp interface as follows:
ifconfig carp0 create
However when I run this... I get the following error:
# ifconfig carp
On Tue, 2 Aug 2005, Ed Maste wrote:
Spl-related cleanups (no longer useful documentation of old
synchronization in many places), lock order hard-coded into WITNESS
order rather than dynamically detected.
Have you had a chance to run with this patch as yet? If possible, I'd
like to get it me
On Tue, Aug 02, 2005 at 08:51:55PM +, Bjoern A. Zeeb wrote:
[IPSec, NAT-T, IPR]
> do you have more info about this?
I asked for more informations from NetBSD team, waiting for answers.
For ipsec-tools project, our decision for such IPR potential problems
was to provide features as optionnal,
Synopsis: FreeBSD advertises wrong window scale in some situations
Responsible-Changed-From-To: freebsd-net->silby
Responsible-Changed-By: rwatson
Responsible-Changed-When: Wed Aug 3 09:13:49 GMT 2005
Responsible-Changed-Why:
Chown to silby, who has recently been spending some quality time with T
Mike Silbersack wrote:
net.inet.tcp.sendspace=1024000
net.inet.tcp.recvspace=1024000
kern.ipc.maxsockbuf=2048
I don't think large socket buffers have been tested well, it's possible
that you're exhausting almost all of your mbufs with just a few
connections - if you're really stuffing that
Greetings,
Thanks to everybody for their quick responces before. (I've also had
another crack at my TMDA filter so hopefully my reply address will work this
time).
Last time I forgot to mention I was pulling the datafiles from a compaq raid
system (ciss0: ). I had a large number of files w
