TheGreenBow MR504DV IPSec VPN Client Configuration Guide
Below you will find brief information for IPSec VPN Client MR504DV. The document explains how to configure the TheGreenBow IPSec VPN Client with the Omron MR504DV VPN router. It provides details on VPN network topology, OMRON MR504DV Availability, and OMRON MR504DV VPN Gateway product information. The configuration guide covers both the Omron MR540DV VPN configuration and TheGreenBow IPSec VPN Client configuration, including Phase 1 (IKE) and Phase 2 (IPSec) configurations. It also includes instructions on how to open IPSec VPN tunnels and provides troubleshooting tips for common errors.
advertisement
TheGreenBow IPSec VPN Client
Configuration Guide
Omron MR504DV
WebSite:
Contact: http://thegreenbow.com
Configuration Guide written by:
Company: First Choice Internet http://choicenet.ne.jp
IPSec VPN Router Configuration Property of TheGreenBow Sistech SA - © Sistech 2001-2008 1/14
Doc.Ref tgbvpn_cg_omron_mr50
Doc.version
1.0 –
Aug 2008
VPN version 4.x
Table of contents
IPSec VPN Router Configuration Property of TheGreenBow Sistech SA - © Sistech 2001-2008 2/14
Doc.Ref tgbvpn_cg_omron_mr50
Doc.version
1.0 –
Aug 2008
VPN version 4.x
1 Introduction
1.1 Goal of this document
This configuration guide describes how to configure TheGreenBow IPSec VPN Client with a Omron MR504DV
VPN router.
1.2 VPN Network topology
In our VPN network example (diagram hereafter), we will connect TheGreenBow IPSec VPN Client to the LAN behind the Omron MR504DV router. The VPN client is connected to the Internet with an optical fibre connection or through a LAN. All the addresses in this document are given for example purpose.
IPSec VPN Client
(192.168.0.240)
192.168.1.51
122.22.33.4 192.168.1.1
Internet
Omron
MR540DV
Any IP number
192.168.1.7
IPSec VPN Client
(as seen on the LAN)
1.3 OMRON MR504DV Availability
This router is currently sold in Japan and thus it has a Japanese interface.
1.4 OMRON MR504DV VPN Gateway product info
The Omron router is shipped with a manual CD containing the manual in PDF form. In addtion the Omrom website contains configuration examples. http://www.omron.co.jp/ped-j/portal/support/mr504dv.html
IPSec VPN Router Configuration Property of TheGreenBow Sistech SA - © Sistech 2001-2008 3/14
Doc.Ref tgbvpn_cg_omron_mr50
Doc.version
1.0 –
Aug 2008
VPN version 4.x
2 Omron MR540DV VPN configuration
Ensure that you can connect to the Omron MR540DV router (ping) and then start the browser and point it to the
Omron MR540DV routers IP address.
Login (default user is: admin) and process to detailed configuration. Then proceed to VPN (IPSec) 設定。
Don't forget to enable IPSec; you need to check the 使用するfield!
IPSec VPN Router Configuration Property of TheGreenBow Sistech SA - © Sistech 2001-2008 4/14
Doc.Ref tgbvpn_cg_omron_mr50
Doc.version
1.0 –
Aug 2008
VPN version 4.x
As this configuration is for a Road Warrior who may connect from any place the gateway doesn't have a fixed IP address. We check the moving (動的) field.
At the top we enter the IP range for the VPN client (here start address and netmask).
In the second block we use confirmation protocol (ESP), the corresponding algorithm and the encryption algorithm and protocol.
IPSec VPN Router Configuration Property of TheGreenBow Sistech SA - © Sistech 2001-2008 5/14
Doc.Ref tgbvpn_cg_omron_mr50
Doc.version
1.0 –
Aug 2008
VPN version 4.x
In the third block we select IKE (Internet Key Exchange) and we specify that we want to use a preshared key.
This is considerably simpler than using certificates.
We also enter the hash algorithm, encryption algorithm and main mode to be used. Check IKE Keep Alive and enter the remote IP address. Enter other parameters as shown above to use your values.
The router also supports certificates. Certificates can be generated or imported. The configuration file can be exported and when necessary re-imported again.
IPSec VPN Router Configuration Property of TheGreenBow Sistech SA - © Sistech 2001-2008 6/14
Doc.Ref tgbvpn_cg_omron_mr50
Doc.version
1.0 –
Aug 2008
VPN version 4.x
3 TheGreenBow IPSec VPN Client configuration
This section describes the required configuration to connect to a Omron MR504DV 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
Phase 1 configuration
You may use either Preshared, Certificates, USB Tokens or X-Auth for User Authentication with the Omron
MR504DV router. This configuration is one example of what can be accomplished in term of User Authentication.
You may want to refer to either the Omron MR504DV router user guide or TheGreenBow IPSec VPN Client User
Guide for more details on User Authentication options.
IPSec VPN Router Configuration Property of TheGreenBow Sistech SA - © Sistech 2001-2008 7/14
3.2 VPN Client Phase 2 (IPSec) Configuration
Doc.Ref tgbvpn_cg_omron_mr50
Doc.version
1.0 –
Aug 2008
VPN version 4.x
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
Phase 2 – Advanced
3.3 Open IPSec VPN tunnels
Once both Omron MR504DV 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
IPSec VPN Router Configuration Property of TheGreenBow Sistech SA - © Sistech 2001-2008 8/14
Doc.Ref tgbvpn_cg_omron_mr50
Doc.version
1.0 –
Aug 2008
VPN version 4.x
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 Omron MR504 DV VPN router.
IPSec VPN Router Configuration Property of TheGreenBow Sistech SA - © Sistech 2001-2008 9/14
Doc.Ref tgbvpn_cg_omron_mr50
Doc.version
1.0 –
Aug 2008
VPN version 4.x
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/ ).
IPSec VPN Router Configuration Property of TheGreenBow Sistech SA - © Sistech 2001-2008 10/14
Doc.Ref tgbvpn_cg_omron_mr50
Doc.version
1.0 –
Aug 2008
VPN version 4.x
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.
IPSec VPN Router Configuration Property of TheGreenBow Sistech SA - © Sistech 2001-2008 11/14
Doc.Ref tgbvpn_cg_omron_mr50
Doc.version
1.0 –
Aug 2008
VPN version 4.x
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
IPSec VPN Router Configuration Property of TheGreenBow Sistech SA - © Sistech 2001-2008 12/14
Doc.Ref tgbvpn_cg_omron_mr50
Doc.version
1.0 –
Aug 2008
VPN version 4.x
• 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.
IPSec VPN Router Configuration Property of TheGreenBow Sistech SA - © Sistech 2001-2008 13/14
Doc.Ref tgbvpn_cg_omron_mr50
Doc.version
1.0 –
Aug 2008
VPN version 4.x
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]
IPSec VPN Router Configuration Property of TheGreenBow Sistech SA - © Sistech 2001-2008 14/14
advertisement
Key Features
- VPN network topology
- OMRON MR504DV Availability
- OMRON MR504DV VPN Gateway product information
- Omron MR540DV VPN configuration
- TheGreenBow IPSec VPN Client configuration
- Phase 1 (IKE) configuration
- Phase 2 (IPSec) configuration
- Open IPSec VPN tunnels
- Troubleshooting tips
Frequently Answers and Questions
What is the purpose of this document?
What are the key steps involved in configuring the VPN Client?
What are some common troubleshooting tips for VPN connections?
Related manuals
advertisement
