Prev: email notification for unreachable switch
Next: inter-vlan routing on switch 3560 SMI?
From: Chris on 7 Mar 2007 08:08
On Mar 6, 1:57 pm, "chris" <mandrake...(a)nospam.hotmailDOTcom> wrote:
> "Havoc 25" <havo...(a)gmail.com> wrote in message
>
> news:eskcih$d1i$1(a)ss408.t-com.hr...
>
> > Hello,
>
> > What you have to do is to define with ACL which traffic goes to the VPN
> > (should be encrypted). PIX can't route packets throught the same port, so
> > I presume that your VPN connection is made on your outside port.
>
> What he is trying to do is have the Pix as the default gateway on
> 172.16.1.181 but then have that route traffic destined for the remote
> network back inside to a different gateway, 172.16.188 (doesn't say what
> that is). The pix won't 'route on a stick'.

Is another name for this a "hairpin" connection? It seems unfortunate
that I can't get this accomplished... :-( having to add 10 static
routes to 100 client machines is a lot more work than adding one
static route on a PIX!


Chris

First  |  Prev  | 
Pages: 1 2
Prev: email notification for unreachable switch
Next: inter-vlan routing on switch 3560 SMI?