I'm running an ASL 3.200 with IPSEC Roadwarrior.
What's working:
Client can connect using sentinel across internet.
Client can ping internal resources on home lan
Not working:
I cannot ping sentinel client from home lan when client is connected.
tracert shows ping going from home lan to asl eth0 then eth1 then upstream isp ip.
Facts:
Sentinel client using static public IP
ASL Using static public IP on eth1
ASL using 192.168.2.100/24 on Eth0
Sentinel client gets 192.168.0.1 IP upon connect
This is done without any masq or specific routing rules.
My guess is that I need to tell me ASL to send that info over the tunnel or something. Since client can ping my internalresource ASL must now how to find its way back when client initiates. I cant really see the difference when home lan machine initiates ping.
If anyone answers with a tip, please be very specific and don't just answer you need to put a routing rule up etc. Give an example with given parameters.
Regards Shikyo
This thread was automatically locked due to age.