chrisspen
I inherited an OpenVPN setup that was working quite well, until an associate performed a hard reset on my cable modem. Unfortunately, the custom settings on the cable modem weren't documented, so I've been spending a lot of time reverse engineering the setup. The downtime also apparently caused Comcast to assign me a new IP, and now no one can access the VPN.
I have a Linux machine running DNS and OpenVPN at IP 10.157.10.12 behind the modem. On a test laptop outside my network, I updated its openvpn.conf to use the new IP (e.g. remote 123.456.789.123 1194). I also added a port forwarding rule on the modem to forward port 1194 to the OpenVPN server at 10.157.10.12.
After this, I was able to partially connect, with openvpn reporting "Initialization Sequence Completed". However, I'm unable to ping or otherwise access any servers on the VPN.
What else am I missing? Does OpenVPN require any other ports to be forwarded, or does the server have to be reconfigured for the new IP?
maikcat
hi there,
>The downtime also apparently caused Comcast to assign me a new IP, and now no one can access the VPN.
maybe your predeccesor used dyndns..?
>However, I'm unable to ping or otherwise access any servers on the VPN.
without configs,logs info ,dont think that i can help you much
(unless i work in the same company with you 😃 )
cheers,
Michael.
chrisspen
I know we're running our own DNS server. Nothing's changed on our internal servers, but obviously, something might have depended on the old IP. I'm able to connect to the OpenVPN server. I'm just not able to connect to any of the servers once I'm connected to the VPN, so I can only imagine there's some setting on the cable modem I'm missing that's causing the traffic to be blocked.
