netgear fvx538 router & greenbow vpn software configuration

IPSec VPN Router Configuration Property of TheGreenBow Sistech SA - © Sistech 2001-2008 1/17

TheGreenBow IPSec VPN Client Configuration Guide

NETGEAR FVX538

WebSite: http://www.thegreenbow.com

Contact: [email protected]

Configuration Guide written by: Writer: TheGreenBow Engineering Team Company: www.thegreenbow.com

http://www.thegreenbow.com/

mailto:[email protected]


Doc.Ref tgbvpn_ug_NETGEAR FVX538_en Doc.version 3.0 – Jul 2008 VPN version 4.x


Table of contents

1 Introduction .................................................................................................................................................... 3 1.1 Goal of this document ............................................................................................................................ 3 1.2 VPN Network topology ........................................................................................................................... 3 1.3 NETGEAR FVX538 Restrictions ............................................................................................................ 3 1.4 NETGEAR FVX538 VPN Gateway ........................................................................................................ 3 1.5 NETGEAR FVX538 VPN Gateway product info ..................................................................................... 3

2 NETGEAR FVX538 VPN configuration .......................................................................................................... 4 3 TheGreenBow IPSec VPN Client configuration ............................................................................................. 9

3.1 VPN Client Phase 1 (IKE) Configuration ................................................................................................ 9 3.2 VPN Client Phase 2 (IPSec) Configuration .......................................................................................... 11 3.3 Open IPSec VPN tunnels ..................................................................................................................... 11

4 Tools in case of trouble ................................................................................................................................ 13 4.1 A good network analyser: Wireshark ................................................................................................... 13

5 VPN IPSec Troubleshooting ........................................................................................................................ 14 5.1 « PAYLOAD MALFORMED » error (wrong Phase 1 [SA]) ................................................................. 14 5.2 « INVALID COOKIE » error .................................................................................................................. 14 5.3 « no keystate » error ............................................................................................................................ 14 5.4 « received remote ID other than expected » error ................................................................................ 14 5.5 « NO PROPOSAL CHOSEN » error .................................................................................................... 15 5.6 « INVALID ID INFORMATION » error .................................................................................................. 15 5.7 I clicked on “Open tunnel”, but nothing happens. ................................................................................. 15 5.8 The VPN tunnel is up but I can’t ping ! ................................................................................................. 15

6 Contacts ....................................................................................................................................................... 17



1 Introduction

1.1 Goal of this document This configuration guide describes how to configure TheGreenBow IPSec VPN Client with a NETGEAR FVX538 VPN router.

th a NETGEAR FVX538 VPN router.

1.2 VPN Network topology 1.2 VPN Network topology In our VPN network example (diagram hereafter), we will connect TheGreenBow IPSec VPN Client to the LAN behind the NETGEAR FVX538 router. The VPN client is connected to the Internet with a DSL connection or through a LAN. All the addresses in this document are given for example purpose.

In our VPN network example (diagram hereafter), we will connect TheGreenBow IPSec VPN Client to the LAN behind the NETGEAR FVX538 router. The VPN client is connected to the Internet with a DSL connection or through a LAN. All the addresses in this document are given for example purpose.

Internet NETGEAR FVX538

192.168.13.78

192.168.13.1 194.145.236.119 IPSec VPN Client

(Remote) 192.168.13.3

IPSec VPN Client

(as seen on the LAN)

1.3 NETGEAR FVX538 Restrictions 1.3 NETGEAR FVX538 Restrictions There is no Netgear Restrictions. There is no Netgear Restrictions.

1.4 NETGEAR FVX538 VPN Gateway 1.4 NETGEAR FVX538 VPN Gateway Our tests and VPN configuration have been conducted with NETGEAR FVX538 firmware release 3.0.3-13. Our tests and VPN configuration have been conducted with NETGEAR FVX538 firmware release 3.0.3-13.

1.5 NETGEAR FVX538 VPN Gateway product info 1.5 NETGEAR FVX538 VPN Gateway product info It is critical that users find all necessary information about NETGEAR FVX538 VPN Gateway. All product info, User Guide and knowledge base for the NETGEAR FVX538 VPN Gateway can be found on the NETGEAR website: http://www.netgear.com

It is critical that users find all necessary information about NETGEAR FVX538 VPN Gateway. All product info, User Guide and knowledge base for the NETGEAR FVX538 VPN Gateway can be found on the NETGEAR website: http://www.netgear.com NETGEAR FVX538 Product page http://www.netgear.com/Products/VPNandSSL/WiredVPNFirewallRouters/

FVX538.aspx

http://www.netgear.com/




http://www.netgear.com/Products/VPNandSSL/WiredVPNFirewallRouters/FVX538.aspx

http://www.netgear.com/Products/VPNandSSL/WiredVPNFirewallRouters/FVX538.aspx



2 NETGEAR FVX538 VPN configuration This section describes how to build an IPSec VPN configuration with your NETGEAR FVX538 VPN router. Once connected to your NETGEAR FVX538 VPN gateway, you must select “VPN”, “Policies” and then “IKE Policies”.

Click on the “Add” button in order to add a VPN configuration.



This will bring you to this “Edit IKE policy” page:



In this configuration, we’ve selected the Aggressive Mode and chose for the local ID (fvx_local.com) and Remote ID(fvx_remote.com) an FQDN Identifier (it shall match respectively to Remote ID and Local ID for the VPN Client software). Also, we set a Preshared Key (1234567890) and chose the different algorithms for IKE (i.e. 3DES, SHA which shall match the IKE part in Phase 1 of the VPN Client software). Click on “Apply” once you finished configuring “IKE Policies”. Now you go to “VPN Policies”, and as for the “IKE Policies”, you add to the VPN configuration.



This will bring you to this “Edit VPN policy” page:

In “Traffic Selection” area, you select Subnet Address (e.g. 192.168.13.0), which shall match the “Remote LAN Address” in the VPN Software.



In “Auto Policy Parameters” area, select “vpntracker” as “IKE Policy”. Then you click on “Apply”. You’ve just finished building the VPN Configuration for the NETGEAR FVX538 VPN gateway.



3 TheGreenBow IPSec VPN Client configuration This section describes the required configuration to connect to a NETGEAR FVX538 VPN router. To download the latest release of TheGreenBow IPSec VPN Client software, please go to http://www.thegreenbow.com/vpn_down.html.

3.1 VPN Client Phase 1 (IKE) Configuration

The remote VPN Gateway IP address is either an explicit IP address, or a DNS Name

1234567890

1234567890

Phase 1 configuration We put the same parameters as in the router : Preshared Key, Algorithms and Remote Gateway. Then click on P1 Advanced.

http://www.thegreenbow.com/vpn_down.html



Don’t forget to select aggressive mode and to fill in values for “Local and Remote ID”.



3.2 VPN Client Phase 2 (IPSec) Configuration

You may define a static virtual IP address here.

If you use 0.0.0.0, you will have error “Local-ID” is missing. It does not prevent you from establishing a tunnel

Enter the IP address (and subnet mask) of the remote LAN.

Phase 2 Configuration This part ESP should match values from “Auto Policy Parameters” area in the NETGEAR FVX538 router.

3.3 Open IPSec VPN tunnels Once both NETGEAR FVX538 router and TheGreenBow IPSec VPN Client software have been configured accordingly, you are ready to open VPN tunnels. First make sure you enable your firewall with IPSec traffic. 1. Click on "Save & Apply" to take into account all modifications we've made on your VPN Client configuration 2. Click on "Open Tunnel", or generate traffic that will automatically open a secure IPSec VPN Tunnel (e.g. ping, IE browser) 3. Select "Connections" to see opened VPN Tunnels 4. Select "Console" if you want to access to the IPSec VPN logs and adjust filters to display less IPSec messaging. The following example shows a successful connection between TheGreenBow IPSec VPN Client and a NETGEAR FVX538 VPN router.



4 Tools in case of trouble Configuring an IPSec VPN tunnel can be a hard task. One missing parameter can prevent a VPN connection from being established. Some tools are available to find source of troubles during a VPN establishment.

4.1 A good network analyser: Wireshark Wireshark is a free software that can be used for packet and traffic analysis. It shows IP or TCP packets received on a network card. This tool is available on website http://www.wireshark.org. It can be used to follow protocol exchange between two devices. For installation and use details, read its specific documentation (http://www.wireshark.org/docs/).

http://www.wireshark.org/

http://www.wireshark.org/docs/



5 VPN IPSec Troubleshooting

5.1 « PAYLOAD MALFORMED » error (wrong Phase 1 [SA]) 114920 Default (SA CNXVPN1-P1) SEND phase 1 Main Mode [SA][VID] 114920 Default (SA CNXVPN1-P1) RECV phase 1 Main Mode [NOTIFY] 114920 Default exchange_run: exchange_validate failed 114920 Default dropped message from 195.100.205.114 port 500 due to notification type PAYLOAD_MALFORMED 114920 Default SEND Informational [NOTIFY] with PAYLOAD_MALFORMED error

If you have an « PAYLOAD MALFORMED » error you might have a wrong Phase 1 [SA], check if the encryption algorithms are the same on each side of the VPN tunnel.

5.2 « INVALID COOKIE » error 115933 Default message_recv: invalid cookie(s) 5918ca0c2634288f 7364e3e486e49105 115933 Default dropped message from 195.100.205.114 port 500 due to notification type INVALID_COOKIE 115933 Default SEND Informational [NOTIFY] with INVALID_COOKIE error

If you have an « INVALID COOKIE » error, it means that one of the endpoint is using a SA that is no more in use. Reset the VPN connection on each side.

5.3 « no keystate » error 115315 Default (SA CNXVPN1-P1) SEND phase 1 Main Mode [SA][VID] 115317 Default (SA CNXVPN1-P1) RECV phase 1 Main Mode [SA][VID] 115317 Default (SA CNXVPN1-P1) SEND phase 1 Main Mode [KEY][NONCE] 115319 Default (SA CNXVPN1-P1) RECV phase 1 Main Mode [KEY][NONCE] 115319 Default (SA CNXVPN1-P1) SEND phase 1 Main Mode [ID][HASH][NOTIFY] 115319 Default ipsec_get_keystate: no keystate in ISAKMP SA 00B57C50

Check if the preshared key is correct or if the local ID is correct (see « Advanced » button). You should have more information in the remote endpoint logs.

5.4 « received remote ID other than expected » error 120348 Default (SA CNXVPN1-P1) SEND phase 1 Main Mode [SA][VID] 120349 Default (SA CNXVPN1-P1) RECV phase 1 Main Mode [SA][VID] 120349 Default (SA CNXVPN1-P1) SEND phase 1 Main Mode [KEY][NONCE] 120351 Default (SA CNXVPN1-P1) RECV phase 1 Main Mode [KEY][NONCE] 120351 Default (SA CNXVPN1-P1) SEND phase 1 Main Mode [ID][HASH][NOTIFY] 120351 Default (SA CNXVPN1-P1) RECV phase 1 Main Mode [ID][HASH][NOTIFY] 120351 Default ike_phase_1_recv_ID: received remote ID other than expected [email protected]

The « Remote ID » value (see « Advanced » Button) does not match what the remote endpoint is expected.




5.5 « NO PROPOSAL CHOSEN » error 115911 Default (SA CNXVPN1-P1) SEND phase 1 Main Mode [SA][VID] 115913 Default (SA CNXVPN1-P1) RECV phase 1 Main Mode [SA][VID] 115913 Default (SA CNXVPN1-P1) SEND phase 1 Main Mode [KEY][NONCE] 115915 Default (SA CNXVPN1-P1) RECV phase 1 Main Mode [KEY][NONCE] 115915 Default (SA CNXVPN1-P1) SEND phase 1 Main Mode [ID][HASH][NOTIFY] 115915 Default (SA CNXVPN1-P1) RECV phase 1 Main Mode [ID][HASH][NOTIFY] 115915 Default phase 1 done: initiator id c364cd70: 195.100.205.112, responder id c364cd72: 195.100.205.114, src: 195.100.205.112 dst: 195.100.205.114 115915 Default (SA CNXVPN1-CNXVPN1-P2) SEND phase 2 Quick Mode [SA][KEY][ID][HASH][NONCE] 115915 Default RECV Informational [HASH][NOTIFY] with NO_PROPOSAL_CHOSEN error 115915 Default RECV Informational [HASH][DEL] 115915 Default CNXVPN1-P1 deleted

If you have an « NO PROPOSAL CHOSEN » error, check that the « Phase 2 » encryption algorithms are the same on each side of the VPN Tunnel. Check « Phase 1 » algorithms if you have this: 115911 Default (SA CNXVPN1-P1) SEND phase 1 Main Mode [SA][VID] 115911 Default RECV Informational [NOTIFY] with NO_PROPOSAL_CHOSEN error

5.6 « INVALID ID INFORMATION » error 122623 Default (SA CNXVPN1-P1) SEND phase 1 Main Mode [SA][VID] 122625 Default (SA CNXVPN1-P1) RECV phase 1 Main Mode [SA][VID] 122625 Default (SA CNXVPN1-P1) SEND phase 1 Main Mode [KEY][NONCE] 122626 Default (SA CNXVPN1-P1) RECV phase 1 Main Mode [KEY][NONCE] 122626 Default (SA CNXVPN1-P1) SEND phase 1 Main Mode [ID][HASH][NOTIFY] 122626 Default (SA CNXVPN1-P1) RECV phase 1 Main Mode [ID][HASH][NOTIFY] 122626 Default phase 1 done: initiator id c364cd70: 195.100.205.112, responder id c364cd72: 195.100.205.114, src: 195.100.205.112 dst: 195.100.205.114 122626 Default (SA CNXVPN1-CNXVPN1-P2) SEND phase 2 Quick Mode [SA][KEY][ID][HASH][NONCE] 122626 Default RECV Informational [HASH][NOTIFY] with INVALID_ID_INFORMATION error 122626 Default RECV Informational [HASH][DEL] 122626 Default CNXVPN1-P1 deleted

If you have an « INVALID ID INFORMATION » error, check if « Phase 2 » ID (local address and network address) is correct and match what is expected by the remote endpoint. Check also ID type (“Subnet address” and “Single address”). If network mask is not check, you are using a IPV4_ADDR type (and not a IPV4_SUBNET type).

5.7 I clicked on “Open tunnel”, but nothing happens. Read logs of each VPN tunnel endpoint. IKE requests can be dropped by firewalls. An IPSec Client uses UDP port 500 and protocol ESP (protocol 50).

5.8 The VPN tunnel is up but I can’t ping ! If the VPN tunnel is up, but you still cannot ping the remote LAN, here are a few guidelines:

• Check Phase 2 settings: VPN Client address and Remote LAN address. Usually, VPN Client IP address should not belong to the remote LAN subnet

• Once VPN tunnel is up, packets are sent with ESP protocol. This protocol can be blocked by firewall. Check that every device between the client and the VPN server does accept ESP

• Check your VPN server logs. Packets can be dropped by one of its firewall rules. • Check your ISP support ESP



• If you still cannot ping, follow ICMP traffic on VPN server LAN interface and on LAN computer interface (with Wireshark for example). You will have an indication that encryption works.

• Check the “default gateway” value in VPN Server LAN. A target on your remote LAN can receive pings but does not answer because there is a no “Default gateway” setting.

• You cannot access to the computers in the LAN by their name. You must specify their IP address inside the LAN.

• We recommend you to install Wireshark (http://www.wireshark.org) on one of your target computer. You can check that your pings arrive inside the LAN.

http://www.wireshark.org/



6 Contacts News and updates on TheGreenBow web site: http://www.thegreenbow.com Technical support by email at [email protected] Sales contacts by email at [email protected]



mailto:[email protected]?subject=Please%20call%20me%20back

netgear fvx538 router & greenbow vpn software configuration

Documents