Phil Mendelsohn <mend0070 at tc.umn.edu> wrote: > > 1: > > ipmasqadm portfw -a -P tcp -L (local addr) 80 -R (masq'd addr) 80 > > seems to set up the forward I want. What I read in the docs > indicates that the return ports should already be covered by > the normal masq behavior. Is this true, or do I need to set up > a return path? It worked for me. > 3: > Has anyone noticed / can anyone explain why on a 486 box, when > ipchains or the routing table are listed, at least the first > time, it takes a *really* long time for them to respond with > the table? I mean that ipchains -L gives the headers, but then > waits like a _minute_ or two. If you're patient, it comes, and > after that is fast. What's making it think so hard the first time? It's doing a reverse DNS lookup on the IP addresses. Using `ipchains -L -n' should be a lot faster. -- _ _ _ _ _ ___ _ _ _ ___ _ _ __ Isn't Disney World a / \/ \(_)| ' // ._\ / - \(_)/ ./| ' /(__ people trap operated by \_||_/|_||_|_\\___/ \_-_/|_|\__\|_|_\ __) a mouse? [ Mike Hicks | http://umn.edu/~hick0088/ | mailto:hick0088 at tc.umn.edu ]