I have finally upgraded to 1.6.1 for OpenVPN
Prob 1 (small and easy): The text problem on the config page is not rendering the & sign properly
Prob 2: If I have a config on the server router, it does not get cleared when I remove it.
- I disable VPN
- I press the "Clear All Existing VPN Keys"
- It spins while saving
- (I can optionally hit SAVE)
- I select VPN server
- My old settings and allowed clients are visible
I think a good goal would be that the vpn config files and certificates are carefully overwritten (in place) first and then unlinked/deleted. (This may also have something to do with GUI caching though.)
Prob 3: When I try to use AES 256 on the server, the client did not accept the configuration zip as valid. The error message is a bit vague:
More OpenVPN gui bugs in 1.6.1
Moderator: Moderators
Re: More OpenVPN gui bugs in 1.6.1
I will investigate, thanks for the heads-up.
-
- Posts: 89
- Joined: Thu Apr 22, 2010 3:24 pm
Re: More OpenVPN gui bugs in 1.6.1
I am happy to provide more details as required. (I now have a setup which enables me to do testing more easily and more quickly)
-
- Posts: 89
- Joined: Thu Apr 22, 2010 3:24 pm
Re: More OpenVPN gui bugs in 1.6.1
The Block NonOpenVPN traffic option does not work as I expect.not expect to be able to do.
I have router A facing the internet. My OpenVPN client is running on Router B which is plugged into router A. With the VPN running, I am still able to connect to the gargoyle web page of router A, which I would -
- Posts: 89
- Joined: Thu Apr 22, 2010 3:24 pm
Re: More OpenVPN gui bugs in 1.6.1
I did some more testing.throughwalls wrote:The Block NonOpenVPN traffic option does not work as I expect.not expect to be able to do.I have router A facing the internet. My OpenVPN client is running on Router B which is plugged into router A. With the VPN running, I am still able to connect to the gargoyle web page of router A, which I would
If the router is not able to contact the VPN server, then it correctly blocks connections to other internet hosts but does not block access to the router's gateway (or likely any host on the WAN subnet)