Hi all,<div><br></div><div>Yup. Route back from the edge router worked.</div><div><br></div><div>Thanks,</div><div><br></div><div>Aaron.<br><br><div class="gmail_quote">2008/11/26 Paul Wouters <span dir="ltr"><<a href="mailto:paul@xelerance.com">paul@xelerance.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="Ih2E3d">On Wed, 26 Nov 2008, Aaron Hicks wrote:<br>
<br>
> The Openswan VPN tunnel starts automatically at start up and attaches itself<br>
> to br0 (i.e. there is no ipsec0 interface), and the bridge can ping servers<br>
> on the remote network. It seems to have valid routes to the remote network.<br>
> Unfortunatly I can't seem to get it to forward packets from other hosts on<br>
> our network to the remote network. Tracert shows that requests just head<br>
> straight to the edge router, and aren't being redirected by the bridge into<br>
> the ipsec tunnel.<br>
<br>
</div>Indeed. a route from the edge router back to the bridge's IP address<br>
resolved this issue :)<br>
<font color="#888888"><br>
Paul<br>
</font></blockquote></div><br></div>