>From : Remko Lodder
To : jh...@socket.net
Subject : Re: IPSec Routing
Date : Sun, 22 May 2011 21:12:24 +0200
>
> Basically what happends is that an IPSEC tunnel looks like this
>
>
> Internal_A -->> Internal F
>If you were using tunnel mode, the encrypted packet would change its
>source and destination IP's, specifying your gateway as the source, and
>your vendor's gateway as the destination, so intervening routers would
>have no difficulty delivering the packet, or routing reply packets back
>to you.
T
jh...@socket.net wrote:
>
> I am using IPSec in transport mode to connect to a vendor's router. The
> connection is established and I am able to see the tunnels are established
> in racoon by the IPsec-SA established: ESP/Tunnel messages. And, my
> vendor has confirmed the connection is up on
jh...@socket.net (jh...@socket.net) [11.05.22 05:31] wrote:
> What I am not understanding is how to add routes correctly when using
> transport mode. I have added the proper incoming/outgoing information
> using setkey. When I display the information using setkey -DP, the routes
> appear corre
On Fri, 18 Jun 2004, Andre Rein wrote:
> I'm able to ping 10.0.0.1 now from my vpnclient and ping the
> vpnclient from 10.0.0.1 without any trouble.
>
> The only problem I get, is to ping the vpnclient from the vpnserver.
> It won't work.
> So how should I setup the server to ping the client?
> Am
