NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
chiragk11
Nov 23, 2016Aspirant
Restrict User to VLAN after VPN - Not working
Hello, On SRX5308 I have created a IPSec VPN connection using Mode Config and IKE policy. I am able to VPN in. However, I can access all Subnets - even though I have specified the Subnet as 10.5...
chiragk11
Nov 23, 2016Aspirant
FYI - I am using Shrew VPN client.
In the Shrew VPN Client, I noticed that if I have the DNS set to 10.50.10.1, then it works as desired.
However if the DNS is left as "automatic", then the entire network is open to the VPN user. so even though the setting above solves the issue, its a huge security hole, and since DNS Automatic is the default setting, we cannot do this.
I need to be able to enforce the DNS to 10.50.10.1 to the VPN user using Mode Config (I suppose)....
Please advise..
chiragk11
Nov 23, 2016Aspirant
Never mind the last post #2. It seemed to work when I first connected, but after a minute, I was able to access entire network - so I back to square 1.
- DaneANov 28, 2016NETGEAR Employee Retired
Hi chiragk11,
It seems that you are the same person as chirag11. I believe this forum thread is related to this one here.
Let us try this: using 1 IKE policy, create 3 VPN policies that pertains to each VLAN. Do not yet configure mode config record. Let us know your observations and post screenshots of the IKE and VPN policies.
Regards,
DaneA
NETGEAR Community Team
- DaneADec 05, 2016NETGEAR Employee Retired
Hi chiragk11,
Just to add, to possibly set the VPN to access only a specific VLAN other than the default VLAN, the setting for this to work is in the VPN Policy under Traffic Selection. By default, when creating the policy using the VPN wizard, it will use the IP address of the default VLAN. However, if you change this to the network address of the desired VLAN, it will allow access to that VLAN through the VPN. Inter VLAN routing must be turned off in the VLAN settings if the desired effect is to not be able to access other VLAN’s.
On the figure below, from the working policy; note that 192.168.245.0 is the network address of the secondary VLAN and not the LAN IP address of the default VLAN. Also note, Mode Config is not being used. Just use the VPN wizard on both the SRX5308 on each side.
Regards,
DaneA
NETGEAR Community Team
- DaneADec 08, 2016NETGEAR Employee Retired
Hi chiragk11,
I just want to follow-up on this. Referring on my last reply, were you able to try it? If yes, what are your observations?
Regards,
DaneA
NETGEAR Community Team
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!