Reviews & Opinions
Independent and trusted. Read before buy Netgear FVX538V2!

Netgear FVX538V2

TOP | Manual | User Opinions | Documents

 Bookmark
Netgear FVX538V2

Bookmark and Share

 

Netgear FVX538V2About Netgear FVX538V2
Here you can find all about Netgear FVX538V2 like manual and other informations. For example: review.

Netgear FVX538V2 manual (user guide) is ready to download for free.

On the bottom of page users can write a review. If you own a Netgear FVX538V2 please write about it to help other people.
[ Report abuse or wrong photo | Share your Netgear FVX538V2 photo ]

 

 

Manual

TOP | Manual | User Opinions | Documents

Preview of first few manual pages (at low quality). Check before download. Click to enlarge.
Manual - 1 page  Manual - 2 page  Manual - 3 page 

Download (English)
Netgear FVX538V2, size: 1.6 MB

 

Netgear FVX538V2

TOP | Manual | User Opinions | Documents

 

 

User reviews and opinions

TOP | Manual | User Opinions | Documents

<== Click here to post a new opinion, comment, review, etc.

No opinions have been provided. Be the first and add a new opinion/review.

 

Documents

TOP | Manual | User Opinions | Documents
doc0

FVX538v2 - 3.0.3-17 ModeConfig VPN Client Setup to SafeNet SoftRemote 10.8.3 Build 6

Scenario:

Local: WAN IP LAN IP Gateway WINS Server DNS Server VPN Pool 1.1.1.1 10.0.0.0 10.0.0.1 10.0.0.2 10.0.0.2 255.255.255.0
192.168.110.1 192.168.110.5 (as many as you might need)
Remote User: WAN IP LAN IP Gateway Remote PC 2.2.2.2 192.168.0.0 192.168.0.1 192.168.0.2 (so you can understand the logs) 255.255.255.0

Notes:

Compatible Routers: FVX538 FVX538v2 FVS338 FVS336G DGFV338 with 3.0.3-17 with 3.0.3-17 with 3.0.3-17 with 3.0.3-13.4 with 3.0.3-18
Compatible SafeNet VPN Clients: 10.3.5 10.5.1 10.7.2 10.8.0 10.8.3 This setup may be compatible with other routers, firmware, and client software versions.
These configs worked for me and may or may not work for you as well. Have questions, ask them on the Netgear User Forum. Good Luck, ADIT.
Last Updated 7/1/2008 12:14 PM

Router Setup:

First add your Mode Config Record. Make sure that there isnt a VPN Client Policy under VPN/Policies/IKE and VPN/Policies/VPN. Be sure to remove both if you are switching to Mode Config.
Next add the IKE Policy as follows and Apply.

VPN Client Setup:

Setup the Client Policy as follows: (for DynDNS change ID Type to Gateway Hostname and enter Hostname in place of 1.1.1.1)
Logs Files upon Successful Connection:

Router Log:

2007 Oct 31 00:33:42 [FVX538] [IKE] Remote configuration for identifier "fvx_remote.com" found_ 2007 Oct 31 00:33:42 [FVX538] [IKE] Received request for new phase 1 negotiation: 1.1.1.1[500]<=>2.2.2.2[500]_ 2007 Oct 31 00:33:42 [FVX538] [IKE] Beginning Aggressive mode._ 2007 Oct 31 00:33:42 [FVX538] [IKE] Received unknown Vendor ID_ - Last output repeated 2 times 2007 Oct 31 00:33:42 [FVX538] [IKE] Received Vendor ID: draft-ietf-ipsra-isakmp-xauth-06.txt_ 2007 Oct 31 00:33:42 [FVX538] [IKE] Received unknown Vendor ID_ 2007 Oct 31 00:33:42 [FVX538] [IKE] Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02__ 2007 Oct 31 00:33:42 [FVX538] [IKE] For 2.2.2.2[500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02_ 2007 Oct 31 00:33:43 [FVX538] [IKE] Floating ports for NAT-T with peer 2.2.2.2[4500]_ 2007 Oct 31 00:33:43 [FVX538] [IKE] NAT-D payload matches for 1.1.1.1[4500]_ 2007 Oct 31 00:33:43 [FVX538] [IKE] NAT-D payload does not match for 2.2.2.2[4500]_ 2007 Oct 31 00:33:43 [FVX538] [IKE] Ignore REPLAY-STATUS notification from 2.2.2.2[4500]._ 2007 Oct 31 00:33:43 [FVX538] [IKE] Ignore INITIAL-CONTACT notification from 2.2.2.2[4500] because it is only accepted after phase1._ 2007 Oct 31 00:33:43 [FVX538] [IKE] NAT detected: Peer is behind a NAT device_ 2007 Oct 31 00:33:43 [FVX538] [IKE] 192.168.110.1 IP address is assigned to remote peer 2.2.2.2[4500]_ 2007 Oct 31 00:33:43 [FVX538] [IKE] ISAKMP-SA established for 1.1.1.1[4500]-2.2.2.2[4500] with spi:bcb53003ca47b59a:034dce1b4e4c8d0c_ 2007 Oct 31 00:33:43 [FVX538] [IKE] Sending Informational Exchange: notify payload[INITIAL-CONTACT]_ 2007 Oct 31 00:33:43 [FVX538] [IKE] Responding to new phase 2 negotiation: 1.1.1.1[0]<=>2.2.2.2[0]_ 2007 Oct 31 00:33:43 [FVX538] [IKE] Failed to get IPsec SA configuration for: 10.0.0.0/24<->192.168.0.2/32 from fvx_remote.com_ 2007 Oct 31 00:33:45 [FVX538] [IKE] Responding to new phase 2 negotiation: 1.1.1.1[0]<=>2.2.2.2[0]_ 2007 Oct 31 00:33:45 [FVX538] [IKE] Using IPsec SA configuration: 10.0.0.0/24<->192.168.110.0/24_ 2007 Oct 31 00:33:45 [FVX538] [IKE] Adjusting peer's encmode 61443(61443)->Tunnel(1)_ 2007 Oct 31 00:33:45 [FVX538] [IKE] IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 2.2.2.2->1.1.1.1 with spi=26748601(0x19826b9)_ 2007 Oct 31 00:33:45 [FVX538] [IKE] IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 1.1.1.1->2.2.2.2 with spi=1768758296(0x696d1c18)_

VPN Client Log:

10-30: 23:33:42.460 10-30: 23:33:42.460 My Connections\ADIT-FVX538v2-ModeConfig - Initiating IKE Phase 1 (IP ADDR=1.1.1.1) 10-30: 23:33:42.761 My Connections\ADIT-FVX538v2-ModeConfig - SENDING>>>> ISAKMP OAK AG (SA, KE, NON, ID, VID 6x) 10-30: 23:33:43.161 My Connections\ADIT-FVX538v2-ModeConfig - RECEIVED<<< ISAKMP OAK AG (SA, KE, NON, ID, HASH, VID 3x, NAT-D 2x, VID) 10-30: 23:33:43.161 My Connections\ADIT-FVX538v2-ModeConfig - Peer is NAT-T draft-02 capable 10-30: 23:33:43.161 My Connections\ADIT-FVX538v2-ModeConfig - NAT is detected for Client 10-30: 23:33:43.161 My Connections\ADIT-FVX538v2-ModeConfig - Floating to IKE non-500 port 10-30: 23:33:43.362 My Connections\ADIT-FVX538v2-ModeConfig - SENDING>>>> ISAKMP OAK AG *(HASH, NAT-D 2x, NOTIFY:STATUS_REPLAY_STATUS, NOTIFY:STATUS_INITIAL_CONTACT) 10-30: 23:33:43.362 My Connections\ADIT-FVX538v2-ModeConfig - Established IKE SA 10-30: 23:33:43.362 My Connections\ADIT-FVX538v2-ModeConfig - MY COOKIE bc b3 ca 47 b5 9a 10-30: 23:33:43.362 My Connections\ADIT-FVX538v2-ModeConfig - HIS COOKIE 3 4d ce 1b 4e 4c 8d c 10-30: 23:33:43.672 My Connections\ADIT-FVX538v2-ModeConfig - Initiating IKE Phase 2 with Client IDs (message id: C349D28C) 10-30: 23:33:43.672 My Connections\ADIT-FVX538v2-ModeConfig - Initiator = IP ADDR=192.168.0.2, prot = 0 port = 0 10-30: 23:33:43.672 My Connections\ADIT-FVX538v2-ModeConfig - Responder = IP SUBNET/MASK=10.0.0.0/255.255.255.0, prot = 0 port = 0 10-30: 23:33:43.672 My Connections\ADIT-FVX538v2-ModeConfig - SENDING>>>> ISAKMP OAK QM *(HASH, SA, NON, KE, ID 2x) 10-30: 23:33:43.672 My Connections\ADIT-FVX538v2-ModeConfig - RECEIVED<<< ISAKMP OAK TRANS *(HASH, ATTR) 10-30: 23:33:43.672 My Connections\ADIT-FVX538v2-ModeConfig - Received DNS Address = IP ADDR=10.0.0.2 10-30: 23:33:43.672 My Connections\ADIT-FVX538v2-ModeConfig - Received Private IP Address = IP ADDR=192.168.110.1 10-30: 23:33:43.672 My Connections\ADIT-FVX538v2-ModeConfig - Abandoning IPSec SA negotiation (message id: C349D28C) 10-30: 23:33:43.672 My Connections\ADIT-FVX538v2-ModeConfig - SENDING>>>> ISAKMP OAK TRANS *(HASH, ATTR) 10-30: 23:33:43.672 My Connections\ADIT-FVX538v2-ModeConfig - RECEIVED<<< ISAKMP OAK INFO *(HASH, NOTIFY:STATUS_INITIAL_CONTACT) 10-30: 23:33:45.264 My Connections\ADIT-FVX538v2-ModeConfig - Initiating IKE Phase 2 with Client IDs (message id: B4D37338) 10-30: 23:33:45.264 My Connections\ADIT-FVX538v2-ModeConfig - Initiator = IP ADDR=192.168.110.1, prot = 0 port = 0 10-30: 23:33:45.264 My Connections\ADIT-FVX538v2-ModeConfig - Responder = IP SUBNET/MASK=10.0.0.0/255.255.255.0, prot = 0 port = 0 10-30: 23:33:45.264 My Connections\ADIT-FVX538v2-ModeConfig - SENDING>>>> ISAKMP OAK QM *(HASH, SA, NON, KE, ID 2x) 10-30: 23:33:45.535 My Connections\ADIT-FVX538v2-ModeConfig - RECEIVED<<< ISAKMP OAK QM *(HASH, SA, NON, KE, ID 2x) 10-30: 23:33:45.535 My Connections\ADIT-FVX538v2-ModeConfig - Filter entry 19 added: SECURE 192.168.000.002&255.255.255.255 010.000.000.000&255.255.255.000 001.001.001.001 10-30: 23:33:45.535 My Connections\ADIT-FVX538v2-ModeConfig - SENDING>>>> ISAKMP OAK QM *(HASH) 10-30: 23:33:45.645 My Connections\ADIT-FVX538v2-ModeConfig - Loading IPSec SA (Message ID = B4D37338 OUTBOUND SPI = 19826B9 INBOUND SPI = 696D1C18) 10-30: 23:33:45.645 10-30: 23:37:03.259 Inbound packet failed validation: 1.1.1.1 -> 192.168.0.2

Extended Authentication (Optional):
This provides an additional layer of security over the VPN Client Policy. You can use the built-in User Database or use a Radius Server. This will cover the User Database.
Router Setup: Create your User Accounts.
Select Edge Device at bottom and choose User Database on right. Click Apply.
Change your Authentication Method as seen below. Click Save. Connect away.

doc1

FVX538v2 - 3.0.3-17 VPN Client Setup to SafeNet SoftRemote 10.8.3 Build 6

Scenario:

Local: WAN IP LAN IP Gateway WINS Server DNS Server VPN Pool VPN Policy 1.1.1.1 10.0.0.0 10.0.0.1 10.0.0.2 10.0.0.2 255.255.255.0
192.168.110.1 192.168.110.5 RVPN
these can be any unused Blackhole IP addresses
Remote User: WAN IP LAN IP Gateway Remote PC 2.2.2.2 192.168.0.0 192.168.0.1 192.168.0.2 (so you can understand the logs) 255.255.255.0

Notes:

Compatible Routers: FVX538 FVX538v2 FVS338 FVS336G DGFV338 with 2.1.3-17 with 2.1.3-17 with 2.1.3-17 with 3.0.3-13.4 with 3.0.3-18
Compatible SafeNet VPN Clients: 10.3.5 10.5.1 10.7.2 10.8.0 10.8.3 This setup may be compatible with other routers, firmware, and client software versions.
These configs worked for me and may or may not work for you as well. Have questions, ask them on the Netgear User Forum. Good Luck, ADIT.
Last Updated 7/1/2008 12:13 PM

Router Setup:

Make sure that there isnt a VPN Client Policy under VPN/Policies/IKE and VPN/Policies/VPN. Be sure to remove both if you do. Start with the VPN Wizard.
Next view and edit the VPN Policy as follows and Apply.
Next view and edit the IKE Policy as follows and Apply. You may need to disable to the VPN Policy first to make changes.

VPN Client Setup:

Setup the Client Policy as follows: (for DynDNS change ID Type to Gateway Hostname and enter Hostname in place of 1.1.1.1)
Here you specify the Internal Network IP Address, 1 IP per person connecting, next policy would be 192.168.110.2
Showing here Optional Extended Authentication, see last 2 pages.
Logs Files upon Successful Connection:

Router Log:

2007 Oct 31 23:01:54 [FVX538] [IKE] Remote configuration for identifier "fvx_remote.com" found_ 2007 Oct 31 23:01:54 [FVX538] [IKE] Received request for new phase 1 negotiation: 1.1.1.1[500]<=>2.2.2.2[500]_ 2007 Oct 31 23:01:54 [FVX538] [IKE] Beginning Aggressive mode._ 2007 Oct 31 23:01:54 [FVX538] [IKE] Received unknown Vendor ID_ - Last output repeated 2 times 2007 Oct 31 23:01:54 [FVX538] [IKE] Received Vendor ID: draft-ietf-ipsra-isakmp-xauth-06.txt_ 2007 Oct 31 23:01:54 [FVX538] [IKE] Received unknown Vendor ID_ 2007 Oct 31 23:01:54 [FVX538] [IKE] Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02__ 2007 Oct 31 23:01:54 [FVX538] [IKE] For 2.2.2.2[500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02_ 2007 Oct 31 23:01:54 [FVX538] [IKE] Floating ports for NAT-T with peer 2.2.2.2[4500]_ 2007 Oct 31 23:01:54 [FVX538] [IKE] NAT-D payload matches for 1.1.1.1[4500]_ 2007 Oct 31 23:01:54 [FVX538] [IKE] NAT-D payload does not match for 2.2.2.2[4500]_ 2007 Oct 31 23:01:54 [FVX538] [IKE] Ignore REPLAY-STATUS notification from 2.2.2.2[4500]._ 2007 Oct 31 23:01:54 [FVX538] [IKE] Ignore INITIAL-CONTACT notification from 2.2.2.2[4500] because it is only accepted after phase1._ 2007 Oct 31 23:01:54 [FVX538] [IKE] NAT detected: Peer is behind a NAT device_ 2007 Oct 31 23:01:54 [FVX538] [IKE] Sending Xauth request to 2.2.2.2[4500]_ 2007 Oct 31 23:01:54 [FVX538] [IKE] ISAKMP-SA established for 1.1.1.1[4500]-2.2.2.2[4500] with spi:0cb01cfa7c65e562:1df3185c139a81c3_ 2007 Oct 31 23:02:01 [FVX538] [IKE] Received attribute type "ISAKMP_CFG_REPLY" from 2.2.2.2[4500]_ 2007 Oct 31 23:02:01 [FVX538] [IKE] Login succeeded for user "testuser"_ 2007 Oct 31 23:02:01 [FVX538] [IKE] Responding to new phase 2 negotiation: 1.1.1.1[0]<=>2.2.2.2[0]_ 2007 Oct 31 23:02:01 [FVX538] [IKE] Using IPsec SA configuration: 10.0.0.0/24<->0.0.0.0/0 from fvx_remote.com_ 2007 Oct 31 23:02:01 [FVX538] [IKE] No policy found, generating the policy : 192.168.110.1/32[0] 10.0.0.0/24[0] proto=any dir=in_ 2007 Oct 31 23:02:01 [FVX538] [IKE] Adjusting peer's encmode 61443(61443)->Tunnel(1)_ 2007 Oct 31 23:02:01 [FVX538] [IKE] IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 2.2.2.2->1.1.1.1 with spi=44726019(0x2aa7703)_ 2007 Oct 31 23:02:01 [FVX538] [IKE] IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 1.1.1.1->2.2.2.2 with spi=2893135612(0xac71befc)_

VPN Client Log:

10-31: 22:01:54.392 10-31: 22:01:54.392 My Connections\ADIT-FVX538v2 - Initiating IKE Phase 1 (IP ADDR=1.1.1.1) 10-31: 22:01:54.713 My Connections\ADIT-FVX538v2 - SENDING>>>> ISAKMP OAK AG (SA, KE, NON, ID, VID 6x) 10-31: 22:01:55.143 My Connections\ADIT-FVX538v2 - RECEIVED<<< ISAKMP OAK AG (SA, KE, NON, ID, HASH, VID 3x, NAT-D 2x, VID) 10-31: 22:01:55.143 My Connections\ADIT-FVX538v2 - Peer is NAT-T draft-02 capable 10-31: 22:01:55.143 My Connections\ADIT-FVX538v2 - NAT is detected for Client 10-31: 22:01:55.143 My Connections\ADIT-FVX538v2 - Floating to IKE non-500 port 10-31: 22:01:55.354 My Connections\ADIT-FVX538v2 - SENDING>>>> ISAKMP OAK AG *(HASH, NAT-D 2x, NOTIFY:STATUS_REPLAY_STATUS, NOTIFY:STATUS_INITIAL_CONTACT) 10-31: 22:01:55.354 My Connections\ADIT-FVX538v2 - Established IKE SA 10-31: 22:01:55.354 My Connections\ADIT-FVX538v2 - MY COOKIE c b0 1c fa 7c 65 e10-31: 22:01:55.354 My Connections\ADIT-FVX538v2 - HIS COOKIE 1d f5c 13 9a 81 c3 10-31: 22:01:55.474 My Connections\ADIT-FVX538v2 - RECEIVED<<< ISAKMP OAK TRANS *(HASH, ATTR) 10-31: 22:02:01.793 My Connections\ADIT-FVX538v2 - SENDING>>>> ISAKMP OAK TRANS *(HASH, ATTR) 10-31: 22:02:01.853 My Connections\ADIT-FVX538v2 - RECEIVED<<< ISAKMP OAK TRANS *(HASH, ATTR) 10-31: 22:02:01.863 My Connections\ADIT-FVX538v2 - IKE Extended Authentication successful. 10-31: 22:02:01.863 My Connections\ADIT-FVX538v2 - SENDING>>>> ISAKMP OAK TRANS *(HASH, ATTR) 10-31: 22:02:02.194 My Connections\ADIT-FVX538v2 - Initiating IKE Phase 2 with Client IDs (message id: 82790ED) 10-31: 22:02:02.194 My Connections\ADIT-FVX538v2 - Initiator = IP ADDR=192.168.110.1, prot = 0 port = 0 10-31: 22:02:02.194 My Connections\ADIT-FVX538v2 - Responder = IP SUBNET/MASK=10.0.0.0/255.255.255.0, prot = 0 port = 0 10-31: 22:02:02.194 My Connections\ADIT-FVX538v2 - SENDING>>>> ISAKMP OAK QM *(HASH, SA, NON, KE, ID 2x) 10-31: 22:02:02.494 My Connections\ADIT-FVX538v2 - RECEIVED<<< ISAKMP OAK QM *(HASH, SA, NON, KE, ID 2x) 10-31: 22:02:02.504 My Connections\ADIT-FVX538v2 - Filter entry 4 added: SECURE 192.168.000.002&255.255.255.255 010.000.000.000&255.255.255.000 001.001.001.001 10-31: 22:02:02.504 My Connections\ADIT-FVX538v2 - SENDING>>>> ISAKMP OAK QM *(HASH) 10-31: 22:02:02.604 My Connections\ADIT-FVX538v2 - Loading IPSec SA (Message ID = 82790ED OUTBOUND SPI = 2AA7703 INBOUND SPI = AC71BEFC) 10-31: 22:02:02.604

Extended Authentication (Optional):
This provides an additional layer of security over the VPN Client Policy. You can use the built-in User Database or use a Radius Server. This will cover the User Database.
Router Setup: Create your User Accounts.
Select Edge Device at bottom and choose User Database on right. Click Apply.

 

Tags

VT 6041 ADZ625 Microwave Kodak C122 RSH5ubmh Europe Fender 3208 AV-R710 YDP2006 CCD-TRV328 HTC 3600 1900-101 TLP-S10 Elyseo 150 PRE 2 PL-42P5H Dragoon II DVD-K32 Universal Triax 50LX Specs F6C800-UNV Scanmaker 3840 LN46C650 CLP-50 Scubapro R390 EZ-AG Travelmate-C100 Ms702H 5482N RSA1ztvg TK-2302 LN46A550p3F Elura 40MC SY-6ZB DC 2300 50 R UN46C6300 Alesis SR16 1 SKY DM-3200 UE37C6000RW FW-C10 RC68221 19LG30 Review GBU421 OT-E227A KH 3461 DSR-450wspl 50PG4500 CP-S210W LT 9988 Widl 106 AN-TNT KC 350 WD-80291TP 6109 M-DK Suite 6408D Plus LE40A330j1 3735 KIT Presenter Trioset PS-LX300H Hiphone I32 T Zoom HQ6940 HVR-A1U LG U880 VSX-D912K NV-GS120GC Warranty DSR9500 FTF2140ES Rooster SDM-X93 CA-R-pi 962 SA-HE70K 19LG31 32LB2R SX-KN7000 E70-1 DP271B Version 2 FZ6-2008 BV8965B Chain SAW Qprint FM Photosmart 1300 ML-2851NDR RNC-100 Motorola H680 LV2775 Stralis Standard Aerodr LSJ090H-1 2126I World 25PT4521

 

manuel d'instructions, Guide de l'utilisateur | Manual de instrucciones, Instrucciones de uso | Bedienungsanleitung, Bedienungsanleitung | Manual de Instruções, guia do usuário | инструкция | návod na použitie, Užívateľská príručka, návod k použití | bruksanvisningen | instrukcja, podręcznik użytkownika | kullanım kılavuzu, Kullanım | kézikönyv, használati útmutató | manuale di istruzioni, istruzioni d'uso | handleiding, gebruikershandleiding

 

Sitemap

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101