Iroute issue?
-
Have an 2.0 server setup accepting connections from 1.2 boxes. Occasionally the iroute isn't kicking in for the client it seems like. Can't ping the client from the server or either of the LANs from one another. If I edit and save the client override with the iroute and then edit and save the server config all the clients will reconnect and I can happily route back and forth. Just restarting the server or just saving the override is not sufficient. Not sure if it's an interface issue in 2.0 or some config issue. Let me know if you need any config files.
-andy
-
If you were on an older BETA image, upgrade to a new snap and then edit/save all of the CSC entries again, unchecking "disabled" when you do.
In older beta images, the GUI thought the settings were active, but the backend thought they were disabled, and if the backend refreshed the openvpn settings (say if your WAN reconnected or refreshed its dhcp lease) the CSC entries would be gone.
-
If you were on an older BETA image, upgrade to a new snap and then edit/save all of the CSC entries again, unchecking "disabled" when you do.
In older beta images, the GUI thought the settings were active, but the backend thought they were disabled, and if the backend refreshed the openvpn settings (say if your WAN reconnected or refreshed its dhcp lease) the CSC entries would be gone.
Ok, I'm on the 21-June build and I've toggled all of my CS overrides. The disabled check box is checked every time the entry is edited but they do show as all enabled when I check, just have to be careful to uncheck that again if we happen to hit save.
thanks
-andy
-
I found another bug in how that box was getting checked. It should be OK in snapshots dated after this post.
