The following reply was made to PR kern/121955; it has been noted by GNATS.
From: Alexander Shulikov [EMAIL PROTECTED]
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Cc:
Subject: Re: kern/121955: [ipfw] [panic] freebsd 7.0 panic with mpd
Date: Mon, 24 Mar 2008 10:07:14 +0200
I receive new dump with
On Monday 24 March 2008 07:11:15 Andrey V. Elsukov wrote:
Alexander Shulikov wrote:
For bug kern/121955: ([ipfw] [panic] freebsd 7.0 panic with mpd)
I receive new dump with mpd-4.4 and FreeBSD 7.0-RELEASE:
Did you reset sysctl variable `net.inet.ip.fw.one_pass` into zero?
There is well
On Monday 24 March 2008 12:46:41 Alexander Shulikov wrote:
Interesting changelog in cvs:
Revision 1.114: download - view: text, markup, annotated - select for diffs
Tue Dec 25 09:36:51 2007 UTC (2 months, 4 weeks ago) by oleg
Branches: MAIN
Diff to: previous 1.113: preferred, colored
here are some of my ideas for ipfw changes:
1/ redo locking so that packets do not have to get locks on the
structure... I have several ideas on this
2/ allow separate firewalls to be used at different parts of the
network stack (i.e allow multiple taboe sto co-exist)
3/ possibly keeping
By default I have:
# sysctl kern.ipc.nmbclusters
kern.ipc.nmbclusters: 25600
# sysctl net.inet.ip.intr_queue_maxlen
net.inet.ip.intr_queue_maxlen: 50
What range of value is optimal to try?
Also I add to loader.conf:
kern.maxusers=1536
kern.ipc.maxpipekva=3200
net.graph.maxalloc=2048
(but it
On Monday 24 March 2008 16:08:10 Alexander Shulikov wrote:
By default I have:
# sysctl kern.ipc.nmbclusters
kern.ipc.nmbclusters: 25600
hard to say, do you checked netstat -m if you get to your limit? If you get
there set it higher
# sysctl net.inet.ip.intr_queue_maxlen
On Monday 24 March 2008 17:00:43 Alexander Shulikov wrote:
2008/3/24, AT Matik [EMAIL PROTECTED]:
On Monday 24 March 2008 16:08:10 Alexander Shulikov wrote:
By default I have:
# sysctl kern.ipc.nmbclusters
kern.ipc.nmbclusters: 25600
hard to say, do you checked netstat -m
