1998 13:00:56 -0700
To: [EMAIL PROTECTED] (Nelson Minar)
From: "David A. Ranch" [EMAIL PROTECTED]
Subject: Re: [masq] Strange Masq problem
Cc: Jason Beazell [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED]
Can you give us a reference? I found something recent
Hello all,
I have a strange problem on my Slackware 3.2 system, running a 2.0.34
kernal. After about 2 hours of standard activity, and without any
precipitating actions, my machine will suddenly 'forget' Where it's traffic
is supposed to originate from. See below:
:~$ netstat -M
IP
:~$ netstat -M
IP masquerading entries
prot expire sourcedestination ports
tcp 14:53.70 192.168.1.4 localhost2660 - telnet (2660)
tcp 9:24.47 192.168.1.2 scuzzlebutt.XXX.com 1034 - 21234 (62405)
udp 4:58.02 192.168.1.2
Thats the URL. Yes.. IPPORTFW is just more stable and Steven keeps
it running smoothly. To be honest.. it doesn't allow to do port RANGES
like IPAUTOFW (that would be a really nice new feature Steven!!!) but at
least it won't kill your Linux box like IPAUTOFW.
I'm at a loss here.. Could
I can't explain what is happening. When I was using IPAUTOFW, after
about 4-5 days, the machine would start to screw up MASQing connections.
My only solution was to reboot the box. Once I removed IPAUTOFW,
everything would work forever.
I think one thing that varies here is WHAT you are
Can you give us a reference? I found something recent at
http://www.monmouth.demon.co.uk/ipsubs/portfw-2.0.30.html
is that what you have in mind? It looks to be exactly the exactly the
same thing as ipautofw, except without control ports. How is it
different? Is it just more stable?
Thats