Re: PCAnywhere and IPCHAINS

2003-01-07 Thread Simon Tneoh Chee-Boon
Hello nate, It works now!! Thanks. It's caused by my ipchains rule, I was confused with packet that go into internal network from the FW server itself. I allowed "FW (unprivport) -> PCAHostInternalIP (5632/5631)" only, after I change it to "PCAExternalIP (unprivport) -> PCAHostInternalIP (5632/

Re: PCAnywhere and IPCHAINS

2003-01-06 Thread nate
Simon Tneoh Chee-Boon said: > Hello nate, > 'Coz ipchains always displays that message, so I've commented the > REDIRECT > rule. > So for my objective, the important parts are the ipchains, ipmasqadm > portfw and route table, right? yep, don't need redirect at all > For my case, do I need any

Re: PCAnywhere and IPCHAINS

2003-01-06 Thread Simon Tneoh Chee-Boon
Hello nate, 'Coz ipchains always displays that message, so I've commented the REDIRECT rule. So for my objective, the important parts are the ipchains, ipmasqadm portfw and route table, right? For my case, do I need any settings like CONFIG_IP_TRANSPARENT_PROXY=y? And will ipchains' MASQ rule a

Re: PCAnywhere and IPCHAINS

2003-01-06 Thread nate
Simon Tneoh Chee-Boon said: > Hello nate, >When I try to some REDIRECT in ipchains, I got the following message: > ipchains: No target by that name (Maybe this kernel doesn't support > transparent proxying?) > Could this cause the problem? > I'm using Linux wira 2.2.20 #1 Sat Apr 20 11:45:28 ES

Re: PCAnywhere and IPCHAINS

2003-01-06 Thread Simon Tneoh Chee-Boon
Hello nate, When I try to some REDIRECT in ipchains, I got the following message: ipchains: No target by that name (Maybe this kernel doesn't support transparent proxying?) Could this cause the problem? I'm using Linux wira 2.2.20 #1 Sat Apr 20 11:45:28 EST 2002 i686 unknown. I've executed tc

Re: PCAnywhere and IPCHAINS

2003-01-06 Thread nate
Simon Tneoh Chee-Boon said: > Hello nate, > I suspect could it be my ipchains rule block the internal > connections? >>From internal network, when I try to PCAnywhere external PCAnywhere > Host, I > can something like the following in the syslog file: > 1) internalIP (unprivportA) -> externalHo

Re: PCAnywhere and IPCHAINS

2003-01-06 Thread Simon Tneoh Chee-Boon
Hello nate, I suspect could it be my ipchains rule block the internal connections? >From internal network, when I try to PCAnywhere external PCAnywhere Host, I can something like the following in the syslog file: 1) internalIP (unprivportA) -> externalHostIP (5632) 2) fwexternalIP (unprivportB)

Re: PCAnywhere and IPCHAINS

2003-01-05 Thread Simon Tneoh Chee-Boon
Hello nate, The PCAnywhere Host has the FW server as the default gateway. I have installed TDIMon, no traffic going to server P when I executed PCAnywhere at external client PC. One question, must it be NAT, i.e. extra external IP required? What I'm trying to achieve is port forwarding only.

Re: PCAnywhere and IPCHAINS

2003-01-05 Thread nate
Simon Tneoh Chee-Boon said: > Hello nate, > Thanks for your reply. > I saw some examples using both portfw and autofw, that's why I was > trying > both. > I've removed autofw but it still failed. > My machine details: > server FW (IP: x.x.x.a interfaces: x.x.x.x/29 and 192.168.1.0/24 >

Re: PCAnywhere and IPCHAINS

2003-01-05 Thread Simon Tneoh Chee-Boon
Hello nate, Thanks for your reply. I saw some examples using both portfw and autofw, that's why I was trying both. I've removed autofw but it still failed. My machine details: server FW (IP: x.x.x.a interfaces: x.x.x.x/29 and 192.168.1.0/24 ipchains running on it) pc C (IP: x.x.x.b PCA

Re: PCAnywhere and IPCHAINS

2003-01-02 Thread Simon Tneoh Chee-Boon
Hello nate, Thanks for your reply. I saw some examples using both portfw and autofw, that's why I was trying both. I've removed autofw but it still failed. My machine details: server FW (IP: x.x.x.a interfaces: x.x.x.x/29 and 192.168.1.0/24 ipchains running on it) pc C (IP: x.x.x.b PCAn

Re: PCAnywhere and IPCHAINS

2003-01-02 Thread nate
Simon Tneoh Chee-Boon said: > >I've executed the following commands: > ipmasqadm portfw -a -P tcp -L externalip 5631 -R internalip 5631 > ipmasqadm portfw -a -P udp -L externalip 5631 -R internalip 5631 > ipmasqadm portfw -a -P tcp -L externalip 5632 -R internalip 5632 > ipmasqadm portfw -a -P

PCAnywhere and IPCHAINS

2003-01-02 Thread Simon Tneoh Chee-Boon
Hello all, Thanks in advance for any helps. I've searched through the internet to find information on how to allow PCAnywhere connection from external interface into an internal server under ipchains' control. The server running the ipchains has MASQ running on it already, the internal server