<pre>Greetings fellow travellers. I have an interesting problem that I<br>hope someone can help illuminate.<br><br> We have a 'working' tunnel. The remote site (192.168.50.xx, Cisco<br>ASA 3000 series) is able to ping the local gateway box (Suse<br>
Enterprise Linux 11, kernel 2.6.27.19-5-pae) at 172.38.xx.xxx, but<br>nothing beyond the gateway on the local side; we cannot ping any IP<br>(including the Cisco ASA) at the remote site. The suse firewall is<br>disabled in favour of a more customizable iptables script that bridges<br>
the WAN to the local network. Using the on-board firewall isn't really<br>an option.<br><br> So, openswan is sitting right on the edge of the network and is<br>able to establish a tunnel. No traffic (that I am aware of) is being<br>
restricted either which way. However, still no joy pinging either side<br>of the tunnel from either site, save for pinging the Suse Gateway from<br>the remote site. From what I describe, what are the possible errors,<br>
oversights, or just plain bad luck that could be causing this problem?<br>
I've already pursued every avenue I can think of, and I'm fresh out of<br>ideas. I'd be happy to provide more information for whomever seeks it.<br>Thanks for your time and patience.<br></pre><br clear="all">
Sincerely, <br>
<br>Jay<br><br><br>