Stephen:
Heya. Sounds troubling. :) Try this:
1. Flush all the portfw's:
ipmasqadm portfw -f
ipmasqadm autofw -F
2. Try your "ipfilter reload", then post the results of
the "network ipfilter list autofw".
I seem to recall always being frustrated that it
was hard to see if an autofw setting, as opposed to a portfw
one, was ever active. That is, autofw didn't have an obvious
"-l" switch, and you had to cat the /proc/net process directly
to see if it was in there. Of course, always use the "-l -n"
switch pair when looking to see what's active (else it'll
try to resolve all the IP addresses) in portfw.
Anyhow, post what you have, that'll help.
cheers,
Scott
> Hi,
> I am trying to forward ports 10000-11999 to an internal server with the
> following command:
> ipmasqadm autofw -A -r tcp 10000 11999 -h 192.168.1.1
> It seems to not complain when I enter it manually on the command line.
> It also seems okay if I add it to the bottom (just before the last
> brace) in ipfilter.conf (standard scripts) and running "network
> ipfilter reload". The problem is with "ipfilter reload" - I get notice
> of "Stopping interface:" but then it just locks up at that
> point. "network ipfilter list autofw" does show the opened port
> although I can't tell if they are correct because the numbers are in
> hex. Any suggestions on how to prevent the reload lockup?
>
> Thanks,
> Stephen
_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-user
