How to allow SSL VPN client to access remote VLAN (RV340)?

[LechK]

Hello

My VLAN1 config is like below:

192.168.17.1/24
DHCP Server: 192.168.17.100-192.168.17.149

and my SSL VPN pool is:
10.0.0.0/24

How to allow SSL VPN user to access to remote VLAN?

Thanks in advance
LK

[Reza Sharifi]

Hi,

Not familiar with RV430 but if the clients get IPs in the range of 10.0.0.0/24 from the DHCP server after they login to the SSL-VPN device, than the VPN device needs to perform routing between 10.0.0.0/24 and 192.167.17.0/24 subnet or point to another device that performs the routing task.

HTH 

[Cristian Matei]

Hi,

     If you use split-tuneling, it's a matter of allowing access to 192.168.17.0/24 network. If you use full-tunnelling, there are no requirements, as long as the RV340 can route to 192.168.17.0/24, which is a requirement in the first case as well, anyways. Here's a reference document:

https://www.cisco.com/c/en/us/support/docs/smb/routers/cisco-rv-series-small-business-routers/smb5529-configure-group-policies-on-the-rv34x-series-router.html

Regards,

Cristian Matei.

[LechK]

Hi,

Disabled split-tunneling but still I can't ping any other address that 192.168.17.1 (router address) from VPN ;(

Thanks in advancee.

L.

[Reza Sharifi]

Hi,

Does the VPN device have a default route or default-gateway towards the router?

Also, the router needs a static route towards the VPM device.

HTH

[LechK]

Router provides SSL VPN access. I have no other ACL because they don't work.

While configuring SSL VPN on RV340 router there is no any default gateway or route typed.

Thanks

LK

EDIT:

I have done some checking and there is something strange.

Looks like I can't ping for example Cisco switch SG-250 (192.168.17.2) and other network hardware like kind of TP-LINK AP with static IP (192.168.17.5) and I can't ping workstations (but it can be because of firewall and I will check it) but I CAN ping other stuff like Hikvision NVR and Cisco SPA112... weird for me. Any idea anyone?