Hi Kevin, Although there is probably a solution using NAT, the easiest way to do what you want is to just create another tunnel. Tunnels restrict by their subnets so you can't reach an IP the tunnel doesn't know about.
I have never used the IPcop interface but for freeswan (which is what IPcop uses) you would have something like: #tunnel_1 left EXTIP leftsubnet 192.168.14.0/24 right EXTIP2 right subnet 192.168.13.0/24 Create another one with the server as the right subnet: #tunnel_2 left EXTIP leftsubnet 192.168.14.0/24 right EXTIP2 right subnet 204.239.225.162/32 You still need the routing on IPcop2 and 3 to get to the server. You also have to make sure you are SNATing at IPcop3 for the 14.0/24 subnet. Wade. On Tue, 2003-02-11 at 16:14, Kevin Anderson wrote: > So I mentioned a little while ago that I was having a bit of a routing > problem here that I can't resolve. > > I've tried the IPcop newsgroup, and again, nothing. > > So I'll try this a different way. > > Can anyone recommend a newsgroup that'll be good at both routing, > IPtables and VPNs? I think I'll need someone with knowledge of all 3 > before this will get resolved. > > I don't really want to be a dick and crosspost all over the place. > > Any suggestions would be great. > > Kev.
