Got it working using a RT-AC68U with DD-WRT v3.0-r35030M kongac (02/19/1
I figured it out using Kong's guide for my iOS devices. However, I can not figure out how to use the native Windows 10 client to connect.
Has anyone been able to get that working? In Kong's guide he talks about windows 7 but doesn't elaborate... I've got the certificates but there are too many choices for connection types and I've tried almost all of them twice...
OK. So managed to follow the ipsec guide Kong posted and can connect remotely to my home network. Great.
However, local DNS is not working when connecting through the VPN. I can access devices using IP address but not hostname. Any tips or something I'm missing?
Using DD-WRT v3.0-r36070M kongac (05/31/1 on R7000.
Got it working using a RT-AC68U with DD-WRT v3.0-r35030M kongac (02/19/1
I figured it out using Kong's guide for my iOS devices. However, I can not figure out how to use the native Windows 10 client to connect.
Has anyone been able to get that working? In Kong's guide he talks about windows 7 but doesn't elaborate... I've got the certificates but there are too many choices for connection types and I've tried almost all of them twice...
@superdupe - did you ever figure it out for windows 10? I just tried to set it up myself and I'm a bit stumped on how to get it working correctly, too?
Joined: 08 Jun 2010 Posts: 109 Location: New Zealand
Posted: Wed Sep 26, 2018 20:00 Post subject:
Anyone got a good guide and tips for connecting to IPsec server from Windows 10 using certificates? I cannot get it to work. I know my Kong IPSEC server is working fine because my iPhone can connect with no problem, but I can't seem to get it configured and working properly from my Win10 laptop and I'm completely befuddled.
Kong posted in the Atheros section, his new beta firmware r39715M had IPSEC fixed. I tried this version for my (5) r7000's and (1) r6400 and IPSEC appears to still be broken... (Yes I used the correct firmware for my devices) Wondering if he fixed it only in the Atheros firmware?
Using the new firmware returns an "Invalid Payload Received" error on Windows and IOS gives a generic error before quitting.