Orbi WiFi 7 RBE973
Reply

fvs336gv2 firmware updrade (3.1.1-08 to 4.3.3.x) ipsec tunnel issue

Titoun
Aspirant

fvs336gv2 firmware updrade (3.1.1-08 to 4.3.3.x) ipsec tunnel issue

Hi,
I'm using shrew vpn to connect fvs336gv2 (firmare 3.1.1-08) but I need features includded in 4.3.x version.
then factory reset, upgrade and then, configuration (the same as it was).
Shrew vpn client shows "tunnel enabled" but the router connection status doesn't show any connection.
Here are parts of the log...:


Tue Apr 25 21:13:18 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Received attribute type "ISAKMP_CFG_REPLY" from X.X.X.X[4500]
Tue Apr 25 21:13:18 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: ISAKMP-SA established for Y.Y.Y.Y[4500]-X.X.X.X[4500] with spi:55f0d92399c9ce32:5630244817702a22
Tue Apr 25 21:13:18 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Sending Xauth request to X.X.X.X[4500]
Tue Apr 25 21:13:18 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: NAT detected: Local is behind a NAT device. and alsoPeer is behind a NAT device
Tue Apr 25 21:13:18 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: NAT-D payload does not match for X.X.X.X[4500]
Tue Apr 25 21:13:18 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: NAT-D payload does not match for Y.Y.Y.Y[4500]
Tue Apr 25 21:13:17 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: For X.X.X.X[500], Selected NAT-T version: RFC 3947Tue Apr 25 21:13:18 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Floating ports for NAT-T with peer X.X.X.X[4500]
Tue Apr 25 21:13:17 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Received unknown Vendor ID
Tue Apr 25 21:13:17 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Received unknown Vendor ID
Tue Apr 25 21:13:17 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Received unknown Vendor ID
Tue Apr 25 21:13:17 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Received Vendor ID: DPD
Tue Apr 25 21:13:17 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Received Vendor ID: DPD
Tue Apr 25 21:13:17 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Received unknown Vendor ID
Tue Apr 25 21:13:17 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Received Vendor ID: RFC 3947
Tue Apr 25 21:13:17 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Received unknown Vendor ID
Tue Apr 25 21:13:17 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
Tue Apr 25 21:13:17 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Received unknown Vendor ID
Tue Apr 25 21:13:17 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Received unknown Vendor ID
Tue Apr 25 21:13:17 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Received Vendor ID: draft-ietf-ipsra-isakmp-xauth-06.txt
Tue Apr 25 21:13:17 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Beginning Aggressive mode.
Tue Apr 25 21:13:17 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Received request for new phase 1 negotiation: Y.Y.Y.Y[500]<=>X.X.X.X[500]
Tue Apr 25 21:13:17 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Remote configuration for identifier "fvs_remote.com" found
Tue Apr 25 21:12:15 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: ISAKMP-SA deleted for Y.Y.Y.Y[4500]-X.X.X.X[4500] with spi:43ad7010b0fea3b9:855be3fc3cb1bed1
Tue Apr 25 21:12:14 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: XAuthUser Thierry Logged Out from IP Address X.X.X.X
Tue Apr 25 21:12:14 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Purged ISAKMP-SA with proto_id=ISAKMP and spi=43ad7010b0fea3b9:855be3fc3cb1bed1.
Tue Apr 25 21:11:10 2017 (GMT +0200): [FVS336Gv2] [IKE] ERROR: Failed to get IPsec SA configuration for: 0.0.0.0/0<->172.26.1.192/32 from fvs_remote.com
Tue Apr 25 21:11:10 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Responding to new phase 2 negotiation: Y.Y.Y.Y[0]<=>X.X.X.X[0]
Tue Apr 25 21:11:05 2017 (GMT +0200): [FVS336Gv2] [IKE] ERROR: Failed to get IPsec SA configuration for: 0.0.0.0/0<->172.26.1.192/32 from fvs_remote.com
Tue Apr 25 21:11:05 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Responding to new phase 2 negotiation: Y.Y.Y.Y[0]<=>X.X.X.X[0]
Tue Apr 25 21:10:59 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: XAuthUser Thierry Logged In from IP Address X.X.X.X
Tue Apr 25 21:10:59 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Login succeeded for user "Thierry"
Tue Apr 25 21:10:59 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Received attribute type "ISAKMP_CFG_REPLY" from X.X.X.X[4500]
Tue Apr 25 21:10:59 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: ISAKMP-SA established for Y.Y.Y.Y[4500]-X.X.X.X[4500] with spi:43ad7010b0fea3b9:855be3fc3cb1bed1
Tue Apr 25 21:10:59 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Sending Xauth request to X.X.X.X[4500]
Tue Apr 25 21:10:59 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: NAT detected: Local is behind a NAT device. and alsoPeer is behind a NAT device
Tue Apr 25 21:10:59 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: NAT-D payload does not match for X.X.X.X[4500]
Tue Apr 25 21:10:59 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: NAT-D payload does not match for Y.Y.Y.Y[4500]
Tue Apr 25 21:10:49 2017 (GMT +0200): [FVS336Gv2] [IKE] ERROR: Ignore information because ISAKMP-SA has not been established yet.
Tue Apr 25 21:10:48 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: For X.X.X.X[500], Selected NAT-T version: RFC 3947Tue Apr 25 21:10:49 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Floating ports for NAT-T with peer X.X.X.X[4500]
Tue Apr 25 21:10:48 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Received unknown Vendor ID
Tue Apr 25 21:10:48 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Received unknown Vendor ID
Tue Apr 25 21:10:48 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Received unknown Vendor ID
Tue Apr 25 21:10:48 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Received Vendor ID: DPD
Tue Apr 25 21:10:48 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Received Vendor ID: DPD
Tue Apr 25 20:20:48 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Received unknown Vendor ID
Tue Apr 25 20:20:48 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Received Vendor ID: RFC 3947
Tue Apr 25 20:20:48 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Received unknown Vendor ID
Tue Apr 25 20:20:48 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
Tue Apr 25 20:20:48 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Received unknown Vendor ID
Tue Apr 25 20:20:48 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Received unknown Vendor ID
Tue Apr 25 20:20:48 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Received Vendor ID: draft-ietf-ipsra-isakmp-xauth-06.txt
Tue Apr 25 20:20:48 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Beginning Aggressive mode.
Tue Apr 25 20:20:48 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Received request for new phase 1 negotiation: Y.Y.Y.Y[500]<=>X.X.X.X[500]
Tue Apr 25 20:20:48 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Remote configuration for identifier "fvs_remote.com" found
Tue Apr 25 20:20:04 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Adding IKE configuration with identifier "Tunnel_Rec"
Tue Apr 25 20:20:04 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: Adding IPSec configuration with identifier "Tunnel_Rec"
Tue Apr 25 20:02:38 2017 (GMT +0200): [FVS336Gv2] [IKE] ERROR: Could not find configuration for X.X.X.X[500]
Tue Apr 25 20:02:33 2017 (GMT +0200): [FVS336Gv2] [IKE] ERROR: Could not find configuration for X.X.X.X[500]
Tue Apr 25 20:02:28 2017 (GMT +0200): [FVS336Gv2] [IKE] ERROR: Could not find configuration for X.X.X.X[500]
Tue Apr 25 20:02:23 2017 (GMT +0200): [FVS336Gv2] [IKE] ERROR: Could not find configuration for X.X.X.X[500]
Tue Apr 25 20:01:10 2017 (GMT +0200): [FVS336Gv2] [IKE] ERROR: Could not find configuration for X.X.X.X[500]
Tue Apr 25 20:01:05 2017 (GMT +0200): [FVS336Gv2] [IKE] ERROR: Could not find configuration for X.X.X.X[500]
Tue Apr 25 20:01:00 2017 (GMT +0200): [FVS336Gv2] [IKE] ERROR: Could not find configuration for X.X.X.X[500]
Tue Apr 25 20:00:55 2017 (GMT +0200): [FVS336Gv2] [IKE] ERROR: Could not find configuration for X.X.X.X[500]
Tue Apr 25 20:00:38 2017 (GMT +0200): [FVS336Gv2] [IKE] ERROR: Could not find configuration for X.X.X.X[500]
Tue Apr 25 20:00:33 2017 (GMT +0200): [FVS336Gv2] [IKE] ERROR: Could not find configuration for X.X.X.X[500]
Tue Apr 25 20:00:28 2017 (GMT +0200): [FVS336Gv2] [IKE] ERROR: Could not find configuration for X.X.X.X[500]
Tue Apr 25 20:00:23 2017 (GMT +0200): [FVS336Gv2] [IKE] ERROR: Could not find configuration for X.X.X.X[500]
Tue Apr 25 19:59:56 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: clock skew detected, restarting racoon
Tue Apr 25 19:59:56 2017 (GMT +0200): [FVS336Gv2] [IKE] INFO: clock skew detected, restarting racoon
Thu Jan 01 01:03:28 1970 (GMT +0100): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 01:03:28 1970 (GMT +0100): [FVS336Gv2] [IKE] ERROR: setsockopt(UDP_ENCAP_ESPINUDP): Protocol not available
Thu Jan 01 01:03:28 1970 (GMT +0100): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 01:03:28 1970 (GMT +0100): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 01:03:28 1970 (GMT +0100): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 01:02:12 1970 (GMT +0100): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 01:02:12 1970 (GMT +0100): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 01:02:12 1970 (GMT +0100): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 01:02:12 1970 (GMT +0100): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 01:02:12 1970 (GMT +0100): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 01:02:12 1970 (GMT +0100): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 01:02:12 1970 (GMT +0100): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 01:02:12 1970 (GMT +0100): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 01:02:12 1970 (GMT +0100): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 01:02:12 1970 (GMT +0100): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 01:02:12 1970 (GMT +0100): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 01:02:12 1970 (GMT +0100): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 01:02:07 1970 (GMT +0100): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 01:02:07 1970 (GMT +0100): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 01:02:07 1970 (GMT +0100): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 01:02:07 1970 (GMT +0100): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 01:02:06 1970 (GMT +0100): [FVS336Gv2] [IKE] ERROR: setsockopt(UDP_ENCAP_ESPINUDP): Protocol not available
Thu Jan 01 01:02:06 1970 (GMT +0100): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 01:02:06 1970 (GMT +0100): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 01:02:06 1970 (GMT +0100): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 00:01:13 1970 (GMT +0000): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 00:01:13 1970 (GMT +0000): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 00:01:13 1970 (GMT +0000): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 00:01:13 1970 (GMT +0000): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 00:01:13 1970 (GMT +0000): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 00:01:13 1970 (GMT +0000): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 00:01:13 1970 (GMT +0000): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 00:01:13 1970 (GMT +0000): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 00:01:13 1970 (GMT +0000): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 00:01:13 1970 (GMT +0000): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 00:01:13 1970 (GMT +0000): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 00:01:13 1970 (GMT +0000): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 00:01:11 1970 (GMT +0000): [FVS336Gv2] [IKE] ERROR: setsockopt(UDP_ENCAP_ESPINUDP): Protocol not available
Thu Jan 01 00:01:11 1970 (GMT +0000): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 00:01:11 1970 (GMT +0000): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 00:01:11 1970 (GMT +0000): [FVS336Gv2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 00:00:52 1970 (GMT +0000): [FVS336GV2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 00:00:52 1970 (GMT +0000): [FVS336GV2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 00:00:52 1970 (GMT +0000): [FVS336GV2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 00:00:49 1970 (GMT +0000): [FVS336GV2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 00:00:49 1970 (GMT +0000): [FVS336GV2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 00:00:49 1970 (GMT +0000): [FVS336GV2] [IKE] ERROR: failed to bind (Address already in use).
Thu Jan 01 00:00:27 1970 (GMT +0000): [FVS336GV2] [IKE] ERROR: setsockopt(UDP_ENCAP_ESPINUDP): Protocol not available
Thu Jan 01 00:00:27 1970 (GMT +0000): [FVS336GV2] [IKE] ERROR: setsockopt(UDP_ENCAP_ESPINUDP): Protocol not available
Thu Jan 01 00:00:27 1970 (GMT +0000): [FVS336GV2] [IKE] ERROR: setsockopt(UDP_ENCAP_ESPINUDP): Protocol not available
Thu Jan 01 00:00:26 1970 (GMT +0000): [FVS336GV2] [IKE] INFO: IKE started


So I'm obliged to downgrade the firmware...
Any idea ?

Regards.

Model: FVS336Gv2|PROSAFE DUAL WAN GIGABIT FIREWALL WITH SSL & IPSEC VPN
Message 1 of 5
DaneA
NETGEAR Employee Retired

Re: fvs336gv2 firmware updrade (3.1.1-08 to 4.3.3.x) ipsec tunnel issue

Hi Titoun,

 

Welcome to the community! 🙂 

 

It is best to perform  a factory reset on the FVS336Gv2 after doing a firmware upgrade then reconfigure it from scratch.

 

 About setting up a client-to-box IPSec VPN between the FVS336Gv2 and Shrew VPN client, let me share this article as reference guide.  Hope it helps.

 

 

Regards,

 

DaneA
NETGEAR Community Team

Message 2 of 5
Titoun
Aspirant

Re: fvs336gv2 firmware updrade (3.1.1-08 to 4.3.3.x) ipsec tunnel issue

Hi,

 

Thank you for your answer.

 

I still can't set up ipsec tunnel when I create IKE Policy and VPN Policy.

 

With your answer, I can now use the "mode config" to set up ipsec tunnel... BUT, I'm obliged to change parameters on each clients... not so easy.

 

That's the reason why I yould like to recreate VPN parameters in my FVS336Gv2 with firmware 4.x same as they are in firmware 3.x (no need to change anything in client side).

 

Can you explain me why

with firmware 3.x after reboot the "VPN status" shows:

 

INFO:  IKE started_

 

And with the 4.x firmware:

 

[IKE] ERROR:  setsockopt(UDP_ENCAP_ESPINUDP): Protocol not available
[IKE] ERROR:  setsockopt(UDP_ENCAP_ESPINUDP): Protocol not available
[IKE] ERROR:  setsockopt(UDP_ENCAP_ESPINUDP): Protocol not available
[IKE] ERROR:  setsockopt(UDP_ENCAP_ESPINUDP): Protocol not available
[IKE] ERROR:  setsockopt(UDP_ENCAP_ESPINUDP): Protocol not available
[IKE] INFO:  IKE started

 

And after that I have phase 2 errors ( possibly ESP in UDP on port 4500):

 

[IKE] ERROR:  Failed to get IPsec SA configuration for: 172.20.0.0/24<->192.168.0.12/32 from remote.com
[IKE] INFO:  Responding to new phase 2 negotiation: X.X.X.X[0]<=>Y.Y.Y.Y[0]
[IKE] ERROR:  Failed to get IPsec SA configuration for: 172.20.0.0/24<->192.168.0.12/32 from remote.com
[IKE] INFO:  Responding to new phase 2 negotiation: X.X.X.X[0]<=>Y.Y.Y.Y[0]
[IKE] ERROR:  Failed to get IPsec SA configuration for: 172.20.0.0/24<->192.168.0.12/32 from remote.com
[IKE] INFO:  Responding to new phase 2 negotiation: X.X.X.X[0]<=>Y.Y.Y.Y[0]
[IKE] INFO:  XAuthUser Thierry Logged In from IP Address Y.Y.Y.Y
[IKE] INFO:  Login succeeded for user  "Thierry"
[IKE] INFO:  Received attribute type "ISAKMP_CFG_REPLY" from Y.Y.Y.Y[4500]
[IKE] INFO:  ISAKMP-SA established for X.X.X.X[4500]-Y.Y.Y.Y[4500] with spi:61873cb53fdd164f:94d8996491636659
[IKE] INFO:  Sending Xauth request to Y.Y.Y.Y[4500]
[IKE] INFO:  NAT detected: Local is behind a NAT device. and alsoPeer is behind a NAT device
[IKE] INFO:  NAT-D payload does not match for Y.Y.Y.Y[4500]
[IKE] INFO:  NAT-D payload does not match for X.X.X.X[4500]
[IKE] INFO:  For Y.Y.Y.Y[500], Selected NAT-T version: RFC 3947
[IKE] INFO:  Floating ports for NAT-T with peer Y.Y.Y.Y[4500]

 

What's wrong ??

Any idea ??

 

Thank you for your help.

 

Regards.

 

Message 3 of 5
DaneA
NETGEAR Employee Retired

Re: fvs336gv2 firmware updrade (3.1.1-08 to 4.3.3.x) ipsec tunnel issue

@Titoun,

 

Based from the logs you've posted, it seems to indicate that there is a wrong remote traffic selection.  Kindly try setting up a client-to-box IPSec VPN between the FVS336Gv2 and Shrew VPN client without using mode config to isolate the problem.  

 

Let me share these links below which I found online and this might help as a guide:

 

Client-to-box IPSec VPN between FVS318v3 and Shrew VPN Client - on this link, it uses the FVS318v3 which is already End-of-Life (EOL) and I'm not sure if the Shrew VPN client used here is an old version. 

 

Client-to-box IPSec VPN between FVS336G and Shrew VPN Client - on this link, it seems to use the FVS336Gv1 which is already End-of-Life (EOL).  You might need to translate this page to English language.

 

Client-to-box IPSec VPN between SRX5308 and Shrew VPN Client - on this link, it uses the SRX5308. 

 

Hope it helps. 🙂 

 

 

Regards,

 

DaneA

NETGEAR Community Team

Message 4 of 5
DaneA
NETGEAR Employee Retired

Re: fvs336gv2 firmware updrade (3.1.1-08 to 4.3.3.x) ipsec tunnel issue

@Titoun,

 

I just want to follow-up on this.  Were you able to access the links I've shared and use it as a guide?  

 

 

Regards,

 

DaneA
NETGEAR Community Team

Message 5 of 5
Discussion stats
  • 4 replies
  • 2967 views
  • 0 kudos
  • 2 in conversation
Announcements