[Users] Ping doesn't work anymore after the tunnel is up.

Dear all,

Regarding my previous msg, I assume my tunnel is working now. However I got problem regarding my network traffic after the tunnel is established.

here is my network diag again

192.168.0.1(eth1) <- no PC attached here right now

      ( A )
 192.170.10.11 (eth0)

|

ipsec.conf

|

 192.170.10.1(eth1)

     ( B name: toowoomba)
 137.111.220.150 (eth0)

Do you need help?

In addition to our free technical library, Pantek provides professional IT services to companies who utilize Open Source software: Learn more about Pantek's Technical Support offerings Place an order for 24/7/365 Technical Support here Learn more about Pantek, who we are, and what we do Chat with a Live Operator Related lists.freeswan.org Links 1998-fall 1998-spring 1998-summer 1998-winter 1999-winter announce briefs bugs design freeswan-list hipsec ietf-sectest users users-admin Request more information about Pantek

|
|

 ( LAN ) my problem is.
Once both of the GW(a,b) boot up. A can ping to both B's eth0/1, but not anyone beyond B's eth0. so I run a iptables script on B, the script i copy fomr redhat mini-howto:

iptables -F
iptables -t nat -F
iptables -t mangle -F
iptables -t nat -A POSTROUTING -o eth0 -j SNAT --to 137.111.220.150

iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
iptables -A INPUT -m state --state NEW -i ! eth0 -j ACCEPT
iptables -P INPUT DROP
iptables -A FORWARD -i eth0 -o eth0 -j REJECT

After running this and setting /etc/resolv.conf on nameserver on A to make it became same as the one in B, A can ping any PC on the (LAN) beyond B's eth0 now.

The problem comes when I bring up the freeswan betweeen A and B. AFter I brough it up, A can only ping B's eth1, an nothing else, not even B's eth0.

ANyone can point me out what's wrong?

Again, Thanks very much with your help...

Calvin