This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

No traffic over SSH Sentinel link... Help please.

I have established a VPN link to my home box using SSH Sentinel 1.4.1 build 98.

My ASL version is 4.015

ASL VPN reports:
000 "TestSSHSentinel_1"[3]: 192.168.2.0/24===203.15.140.27:4500...203.153.227.210:4500[sss@micromine.com.au]===10.0.10.100/32

VPN Routes Font size:   Large Normal Small Very Large

371 192.168.2.0/24:0   -> 10.0.10.100/32:0   => tun0x1002@203.153.227.210:0

So the VPN appears to be up.
However I cannot ping or otherwise access any boxes on the internal LAN on the remote side of the VPN.  I have a box at 192.168.2.201 and I cannot ping it or anything.

Do I need to define packet filter rules ?  I cannot see any packets being dropped in the Packet Filter violation logging.

At the moment for testing I have set Any Any Any rule...  Still no good.

Anyone know whats happening ?

The network setup is this:

VPN Client - ASL - INTERNET - ASL - Remote LAN

NAT-T is enabled on both sides.
Auto packet filter is also enabled in the VPN settings.
VPN type is Roadwarrior.

This thread was automatically locked due to age.

Parents

0 Tmor over 22 years ago

bump.

same problem. only seems to be an issue when deny-tunnel splitting is activated in the SSH Sentinal
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 Tmor over 22 years ago

bump.

same problem. only seems to be an issue when deny-tunnel splitting is activated in the SSH Sentinal
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 Marco Maus over 21 years ago in reply to Tmor

If you use "Auto Packet Filter" you have to define Packet Filter Rules for this VPN so that the Ping or other Traffic will work!!! Second your Netmask 255.255.255.255 will not work. This is a bug in SSH Sentinel use 255.255.255.0 or other e.g. 25.255.255.252.
Regards
Cancel
Vote Up 0 Vote Down

Cancel