Setting up a dial-up VPN to connect to a Netscreen
Posted by Michael Dale on Fri, 01 Sep 2006 6:59 PMI've been getting lots of hits to the post about a site to site VPN setup with a netscreen. So I've decided to do one for a dial-up VPN user connecting to a netscreen.
A dial-up user is anyone who needs access into the network and has a dynamic ip address. We don't wish to be able to access them (the dial-up user) from within the network. This is how we setup most connections at work. This allows people to access file shares and outlook (without the need to setup RPC over HTTP).
Background
- Netscreen 5GT running ScreenOS 5.4.0r1 (Should be the same process for any netscreen running ScreenOS 5.x)
- Netscreen Remote 8.7 (The Windows VPN client)
- Local Network (the one in which the vpn users want to access) of 10.0.0.0/22 (10.0.0.0 - 10.0.3.255)
- External Address of 59.167.253.89
Setting up the Netscreen
1) First we need to create a user. This can be found in Objects -> Users -> Local (Note: Follow the screen shot below, you don't need a password here, you do need the IKE User info though)
So we have our user, Test.User
2) Create Phase 1 of the VPN tunnel. This can be found in VPNs -> AutoKey Advanced -> Gateway (Note: Security level is set to custom, password for VPN is entered here, Outgoing interface is your untrust interface).
3) Now we'll modify the advanced settings. Click Advanced (Note: We're using DES and MD5 here. Mode is set to Aggressive)
Now click return and okay to save your settings.
4) Now we'll create the Phase 2 information. This can be found in VPNs -> AutoKey IKE (Note: Security level is set to custom, Remote Gateway is set to "Test.UserP1")
5) Now we'll modify the advanced settings. Click Advanced (Note: We're using DES and MD5 here. Replay Protection is on)
Now click return and okay to save your settings.
6) Now we'll need to create a policy. This will go from untrust to trust. This can be found in Policies.
Click new (Note: Source Address is Any-IPv4 or just Any if IPv6 is disabled, Destination Address is your local subnet, tunnel the connection though the VPN user "Test.UserP2")
Now the Netscreen has been setup.
Setting up Netscreen Remote
1) Open the policy editor in Netscreen Remote
2) Create a new connection (Note: Type in the remote subnet details and set the secure gateway to your netscreens external address)
3) Now we'll setup the login details (Note: The Certificate is None, The ID Type is Domain Name and the value is "Test.User")
4) Now click Pre-Shared Key (Note: Type in the password you used when setting up the connection in the netscreen)
5) Now we'll set the connection to aggressive (Note: Enable PFS, DH is Group 2 and Enable Replay Dection)
6) Now we'll setup the Phase 1 details (Note: We're using DES and MD5 here. SA Life is 28800 seconds)
7) Now we'll setup the Phase 2 details (Note: The SA Life here is 3600 Seconds)
8) Save the settings and Test!
That should be all you need to do.
Notes
- The VPN may not work behind some NAT routers. You can try turning on NAT-T within the netscreen, although I find it doesn't normally work (newer versions such as 5.4 and 6.x seem to work just fine).
- Make sure the details in the Netscreen and Netscreen Remote Match (i.e Phase 1 policies etc)
- You can check the logs from both Netscreen and Netscreen Remote
- You cannot connect to the VPN while within the local subnet
- Netscreen Remote should be disabled when you're directly connected to the network
- Only traffic for the subnet is passed over the VPN.
On Fri, 14 Sep 2007 at 7:21 PM, Michael Dale wrote:
Make sure your VPN policies are before the standard ANY-ANY rule.
On Tue, 12 Feb 2008 at 5:28 AM, Adi wrote:
Hi,
Extremely helpful tutorial. However I came into a problem: after the connection, the IP address from my laptop (the remote client) is inside the company's LAN = my laptop is not seen inside company's LAN with an IP address within the LAN subnet. Because of that I do not have access to servers, for example, that are in other subnet, behind another firewall... Is there anything I can do to receive a LAN IP address when the connection is completed?
Thanks
On Wed, 13 Feb 2008 at 5:03 PM, Michael Dale wrote:
Yes it is possible but I haven't done it myself. If I do I'll write a tutorial for it.
The easiest way to get it working is to make sure the laptop is on a different subnet. For most company LANs I try and use a fairly unique IP range such as 172.25.25.x.
On Fri, 22 Feb 2008 at 3:25 AM, Jaska wrote:
Hi everyone!
I haven't had this problem with my netscreen. Although when I setup a VPN netscreen remote client, icmp goes fine(lan and outside) and i can see all my computers lan. but web traffic is not working over vpn. i dont know what is problem. i think that is something with route... i allmost try everything but is not working... maybe somebody can help me :)
On Thu, 06 Mar 2008 at 9:11 AM, Jason Ellison wrote:
In response to Adi's comment:
I recently had a situation where roadwarriors needed to communicate with routers and systems beyond our administrative scope. I used the information listed here... but under your VPN policy goto advanced and you can use source NAT (SNAT) to make the connections appear to come from the local interface of the NetScreen. I would not advise this for more than a few users doing light tcp/udp work. My situation was this: 5 remote users need telnet access to an internal rehat server (large car dealership). The other locations have networks that were large enough for us to have coporate add routes back.
On Fri, 14 Mar 2008 at 6:15 AM, Adi wrote:
Thank you Jason,
I made the configuration as you explained and indeed the packets coming from a connected client were seen inside the Lan with the IP address of the internal interface of the firewall so it was a step forward.
However, I realized that this was not the solution I needed; any client that gets into the LAN via de VPN will have the same IP address and I also have to make new sets of policies that will allow access from this ip (firewall's internal IP) to the resources that need to be accessed.
1. I do not have traceability (I do not know which client connected, with which IP address - knowing this would help a lot in identifying possible problems not only attacks)
2. I do not want to make all resources available to all clients coming through the VPN.
To achieve that I would need a way of assigning specific, LAN, reserved IP addresses to incoming clients so that each IP address would be an identifier of the client.
Or maybe there is another way to have the same result and I am not aware of it.
Any idea would be much appreciated as usual.
Thank you,
On Fri, 04 Apr 2008 at 5:08 AM, Joe VOirol wrote:
This is set up with a static IP address in the netscreen. What changes do you need to make to get it to work with a dynamic IP address pointed to a name with dnyDNS such as dyndns.org or homedns.org?
On Thu, 05 Jun 2008 at 11:16 PM, Robert BECKERS wrote:
MANY MANY MANY MANY Thank's for your explanation about the setting-up of the VPN Connection with a 5GT
I search a lot and your configuration work very fine !!!!
Regards !
On Sat, 05 Jul 2008 at 5:45 AM, Jim wrote:
I am trying to get the dial up users to have access to another remote network but cannot seem to get it to work. Basically, Lan1=home office, Lan2=remote office. Lan1 has a static vpn connection to Lan2. Dial up users connect directly to Lan1 but cannot get any traffic to Lan2, is this just a policy that needs to be implemented or should the Nat get by this?
Comments?
HTML allowed: <a href="" title="" rel=""></a> <b></b> <blockquote cite=""></blockquote> <em></em> <i></i> <strike></strike> <strong></strong> <li></li> <ol></ol> <ul></ul>
ie: <b>bold</b>
Your comment may need to be reviewed before it is published.
Hi
Thahnks for your post. I have a problem. I esatblished a dial-up VPN as you showed here. VPN connects OK but i can't ping the hosts in LAN. Cannot communicate. Any idea?