Posted: Tue Feb 20, 2018 18:56 Post subject: Can't get OpenVPN server to work...
Hi guys,
Might be my first post here, but been lurking on this forum for a while now.
I have a WRT3200ACM here. First, I had the VPN setup throughout the Linksys firmware, which was pretty easy, a few buttons and you were done.
Which helps me a lot. But still, it doesn't seem to work, that's why I've added the client log here too.
I have a modem, which has the IP of 192.168.2.254. My WRT is connected on it, LAN wise, with 192.168.2.1. The router has it's own subnet of 192.168.1.0, where the router is 192.168.1.1
Still, with in my opinion, proper settings, reading through the guide, it doesn't seem to work at all. I've tried it on 1194 and 443, same results. Keep getting TLS errors, I've searched for that, but can't get a straight answer out of that.
Are there certain settings that have to be made when having a modem in front of it? Am I missing something else?
Maybe somebody has the golden nugget.. I keep searching and trying..
Having too many firewall rules and Additional Configs will make it a lot harder, and more difficult. I agree in that.
Ah okay. Thought, might be usefull to add them anyway.. Only thing what triggers me is the TLS line, the fact the server is seeing the hosts WAN IP, and that it keeps restarting..
As far as I can see, when I look at the OpenVPN status tab in the Web Gui, There is a client, which has the laptop's WAN address. It's only sending, not receiving.
Client Remote IP:Port Bytes Received Bytes Sent Connected Since
UNDEF 62.72.193.60:17113 0 70 160
I cannot change the firewall on the ISP's router, since it's fixed.
What should be blocking it, when I've opened the ports on both routers?
I don't have that file, I only have nf_conntrack files.
I have tested it from the PC (where I made the keys and certs) and changed the WAN IP to the 192.168.1.1 and 192.168.2.1 IP's, and that worked both times.
So, to me it looks like the certs and stuff are okay, right? Otherwise, that wouldn't work either... But when I change the IP to my real WAN, then I get those TLS errors again..