Open VPN reinstallation required each time after system restart - Very Strange
-
HI,
We are using PfSense 2.1-BETA1 (amd64) FreeBSD 8.3-RELEASE-p8, Road warrior is configured & was working perfectly. My issue is - OPEN VPN will not communicate tunnel n/w after the system is shutdown / restarted. The only work around is we need to uninstall existing OPEN VPN client & install it again. This is disgusting, could anybody suggest a valuable solution for this ?Note: The strange part is this is not happening to all machines >:( >:( >:( >:(
-
When you install it, do you install it by right clicking the install file and running as Administrator? What is the OS you installed on?
-
HI,
Thanks for your response, usually when i install, i do run as admin as you mentioned below. The strange thing is it will work initially with out any issue only after each fresh installation & when ever the system is restarted / shutdown, i again need to uninstall the complete setup & install it again. I will describe my situation.1. I installed open VPN package by run as administrator
2. I am able to connect my tunnel network & able to communicate without any issues.
3. I shutdown / restart my machine.
4. I had run VPN again, it will show the connection is up & i also got one virtual ip. Even i can see my status as connected on my PfSense dashboard.
Here comes the real issue even though the tunnel is showing connected, i am unable to communicate to my tunnel network.
5. I reinstalled without uninstalling the existing application - the result was same.
6. Finally i had done a complete uninstall, [removed both TAP & VPN, deleted the open VPN config files]
7. install the program again - it will work
8. Again it will not work after system restartThe OS which i installed is Win 7, but the same issue happens for some of my XP machine as well.
The other strange thing i noticed is this is not happening to all machines, the same package will work with out any issue on some other machines [both Win 7, Win8, Win Xp]
This issue happens only for couple of machines, I Doubt some conflict but don't know where. There is no VPN program none other than this.
-
I had also tried, Management Interface Open VPN Manager but no hope. Still the issue is there
-
Does not make much sense… Post the output of
netsh int ipv4 show routeboth when it is working and when it is not working.
-
Just for encouragement - I use the OpenVPN Manager install package on Win7 and Win8 and it works. It does sound very much like the route is not getting added, the result of doktornotor command will tell.
-
Just for encouragement - I use the OpenVPN Manager install package on Win7 and Win8 and it works. It does sound very much like the route is not getting added, the result of doktornotor command will tell.
FWIW, I've seen one weird machine where there route (and IP) was not getting deleted for some weird reason… the disconnect script was crashing on that. The route wouldn't matter much (no def1 option) but the IPs kept accummulating and exhausting the entire /24 eventually. I hate Windows.
-
Perhaps there is something wrong with the machine's OS? Its hard to know but sounds like some corruption there. When I have one machine that is not like the others, I wipe and restore and usually these sorts of inconsistencies disappear.
-
Perhaps there is something wrong with the machine's OS? Its hard to know but sounds like some corruption there. When I have one machine that is not like the others, I wipe and restore and usually these sorts of inconsistencies disappear.
Well yeah, definitely… the issue I mentioned above vanished after reimaging the box. It could probably be solved in another way, but was just not worth wasting the time.
-
I only have two items in my bag of tricks:
Shut down and restart
Wipe and reinstallIf you take those away I have nothing :'(