[THIN] Re: WHY

  • From: "Berny Stapleton" <berny@xxxxxxxxxxxxxxxxx>
  • To: thin@xxxxxxxxxxxxx
  • Date: Wed, 30 Apr 2008 14:25:49 +0100

OK, maybe this is just me and my limited experience with CAG...

A VPN session which I presume is a connection from the internet (External)
to the CAG, the CAG being a gateway device between external internet and
internal network, when you bring up a VPN session, or in this case I presume
IPSEC policy between the two devices (Client PC and the CAG) which would
give you a IPSEC policy to the CAG and any traffic you send to it through
the IPSEC policy would end up on it's local routing table. At which point it
has to make a routing decision about where to send the traffic, it's an
external address so therefore it would send it to the external interface and
therefore external address.

That seems logical to me. My question to you is, unless the destination
address is the internal network, why SHOULD it send it via the internal
interface? My only educated guess on this one is that you used part of your
INTERNAL address space for the addresses you assigned to the CAG for it to
hand out to clients, when as far as I can see, the clients should have been
treated or thought of as DMZ interfaces / connections.

This is just what I am thinking about having done firewall admin before.

If I am wrong on this one, and completley off base, please let me know, my
experiece with CAG is limited.

Berny

2008/4/30 Chad Schneider (IT) <Chad.M.Schneider@xxxxxxxxxxxxx>:

>  Does a VPN session to the CAG, route external bound internet traffic
> through the CAG external interface, rather than through the CAG Internal
> interface?
>
> I am watching the traffic, from our CAG internal IP range, when making a
> request to google.com, the traffic goes out the CAG INT0(External).
>
>
> Chad Schneider
> Systems Engineer
> ThedaCare IT
> 920-735-7615
>

Other related posts: