Container routing issues after update #2904
Comments
|
Here is output with the environment variable Specifically: I am not sure why the interface is being specified as |
|
Hi, this thread seems to indicate this can be resolved by updating your config: https://sourceforge.net/p/openvpn/mailman/openvpn-users/thread/[email protected] You could try to establish a connection with the specified config but without using a container to verify that the config is indeed the issue. |
|
Thank you for the reply and my apologies @DriesSchaumont, that page is a 404 error for me. |
Ah, my bad. Updated the link! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there a pinned issue for this?
Is there an existing or similar issue/discussion for this?
Is there any comment in the documentation for this?
Is this related to a provider?
Are you using the latest release?
Have you tried using the dev branch latest?
Docker run config used
Current Behavior
When moving from old version (4.1) to a newer version (latest) the container attempts to come up and fails to stay up due to failing the network ping test.
Expected Behavior
The web interface is available on the expected IP (192.168.0.37) and is stable.
How have you tried to solve the problem?
devrelease..ovpnfile is good by running with older container.settings.jsonfile by running with older container.Log output
Newer (latest), failing:
Older (4.2), working:
HW/SW Environment
Anything else?
It seems to me that something changed with the network routing application between the versions in this issue (4.1, latest). Specifically, we can see the routes being added in the older container version logs:
However, in the newer (latest) version, we can see this failing:
It looks like the deep dive portion of the networking info in the support pages are being worked on, so I don't have a huge insight into how this is different or should be working.
The text was updated successfully, but these errors were encountered: