Oleg Bulyzhin wrote:
Next time this happen check following sysctls:
net.inet.ip.fw.dyn_max
net.inet.ip.fw.dyn_count
I guess you've hit the limit.
If so, is it safe to increase dyn_max to, for example, 8192?
___
freebsd-stable@freebsd.org mailing
On Wed, Apr 26, 2006 at 01:01:32PM +0200, Ivan Voras wrote:
Oleg Bulyzhin wrote:
Next time this happen check following sysctls:
net.inet.ip.fw.dyn_max
net.inet.ip.fw.dyn_count
I guess you've hit the limit.
If so, is it safe to increase dyn_max to, for example, 8192?
Sure.
P.S. if you
I've just had a weird transient problem on a (very loaded) 2 CPU web
server. Suddenly it stopped wanting to connect to the database server
with access denied error. Looking at security log (I have ipfw logging
enabled), I found this:
Apr 25 14:17:17 duality kernel: ipfw: 65400 Deny TCP
I forgot to add, here is the ipfw ruleset:
00500 691658783 639225488899 allow ip from any to any via lo0
01000 99014 6833994 allow icmp from any to any
05000 160430605 76502643136 allow tcp from me to any setup keep-state
05100 1002529109535100 allow udp from me to any
On Tue, Apr 25, 2006 at 02:34:03PM +0200, Ivan Voras wrote:
I forgot to add, here is the ipfw ruleset:
00500 691658783 639225488899 allow ip from any to any via lo0
01000 99014 6833994 allow icmp from any to any
05000 160430605 76502643136 allow tcp from me to any setup
Original Message
On 10/16/00, 11:22:48 PM, Salvo Bartolotta [EMAIL PROTECTED] wrote
regarding ipfw problems with -STABLE sources as of 15/10/2000, 9.30
GMT:
Dear FreeBSD'ers,
After I had made and configured the world, on rebooting I was welcomed
by the following message:
[...]
Oct 16
