NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
morrisonkena
Mar 20, 2017Aspirant
VPN MacOS client setup
Working to setup up a IPv4 Client-to-Gateway VPN tunnel for MacOS clients configuring the MacOS native VPN client (Network Settings, VPN Interface, Cisco IPSec type). It appears I have been successfu...
- May 21, 2017
I apologize for this is the only time I got back on this. Is your network setup as well as the settings on your FVS336Gv3 and MAC OS X Sierra the same as indicated on the article below?
Mac OS X VPN Client install with ProSAFE VPN Firewall/Router
Regards,
DaneA
NETGEAR Community Team
DaneA
May 21, 2017NETGEAR Employee Retired
I apologize for this is the only time I got back on this. Is your network setup as well as the settings on your FVS336Gv3 and MAC OS X Sierra the same as indicated on the article below?
Mac OS X VPN Client install with ProSAFE VPN Firewall/Router
Regards,
DaneA
NETGEAR Community Team
morrisonkena
May 22, 2017Aspirant
DaneA,
Thank you for sharing this document, "Mac OS X VPN Client install with ProSAFE VPN Firewall/Router". I had not seen that in my searches.
Since I already had an IKE Policy set I did not use the VPN WIzard, but did edit my existing IKE Policy configuration to match that shown in the document. I then created a VPN Policy that matched that shown in the document. Then I downloaded and installed the IPSecuritas VPN client for Mac, configuring it also as shown in the document. Running the client from a different, outside network, testing the VPN connection back to my work network fronted by the ProSAFE FVS336Gv3 I could *not* connect.
I verified the settings and tried again. No luck. The error log generated by IPSecuritas shows me this message:
Connection KennyNetVPN is not started because of address collision between local (( "127.0.0.1/8", "::1/128", "fe80::1/64", "fe80::aede:48ff:fe00:1122/64", "fe80::47e:6959:af4c:25c5/64", "192.168.1.93/24", "fe80::4422:cdff:fe7e:f936/64", "fe80::dd35:9b1a:7cf6:2221/64", "fe80::7ab7:4e99:2578:c3df/64", "fe80::c0f:a40b:f157:9d6c/64", "fd28:7e35:d34b:5f8:c0f:a40b:f157:9d6c/64" )) and remote (( "192.168.1.0/24" )) networks
Any idea about this failure? Should I delete my policies completely and start over, using the wizard?
Thanks, Ken
- DaneAMay 23, 2017NETGEAR Employee Retired
Kindly delete the existing IKE & VPN policies then start over use the VPN Wizard.
Let us know result.
Regards,
DaneA
NETGEAR Community Team
- morrisonkenaMay 23, 2017Aspirant
DaneA -
Did as you asked, deleted existing IKE and VPN policies then started over using the VPN Wizard. Verified all settings, including those of the IPSecuritas client. From an outside LAN I initiated a connection, the color indicator turned yellow, then red. Opening the log I noticed these errors:
TIme Severity Src Message
11:42:37 Error IKE phase 2 negotiation failed due to time up waiting for phase1. ESP 136.24.0.247[500]->10.10/10/115[510]
11:42:38 Error IKE phase 1 negotiation failed due to time up. fc325fd40062cb8c:0000000000000000
136.24.0.247 is the public IP address of my FVS336Gv3. 10.10.10.115 is my LAN address of the outside network from which I am connectted back to my home network. I can sent the full error log if you wish. Any ideas?
- Ken
- DaneAJun 06, 2017NETGEAR Employee Retired
Thanks for the update. I apologize for the late response.
I found another article online which is a bit different to the first one I've shared with regard to some settings configured. Kindly access it below and try to follow the steps:
IP Securitas Os X – Netgear FVS336G VPN Settings
Kindly delete the existing IKE & VPN policies then start over again. Let us know the result.
Regards,
DaneA
NETGEAR Community Team
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!