Problem: VPN Conflicts with Docker Networking
I was experiencing the same issue where my VPN wouldn't connect properly
when Docker was running. The problem was related to conflicts between
the Docker-managed network interfaces and NetworkManager. Specifically,
NetworkManager was trying to manage Docker’s interfaces (docker0 and
br-*), leading to duplicate configurations and routing conflicts.
I’m not sure if the rest of you are experiencing the same issue, but I hope my
solution can help someone.
Solution: Exclude Docker Interfaces from NetworkManager
To resolve the issue, I excluded Docker’s network interfaces from being
managed by NetworkManager. This prevents NetworkManager from interfering
with Docker's networking and allows the VPN to work correctly.
Here’s how to do it:
Edit the NetworkManager Configuration
Add a rule to ignore Docker interfaces. Open the configuration file:
sudo nano /etc/NetworkManager/NetworkManager.conf
Add the Following Lines
Insert the following under the [keyfile] section:
[keyfile]
unmanaged-devices=interface-name:docker0;interface-name:br-*
docker0: The default Docker bridge network interface.
br-*: Custom bridge networks created by Docker.
Restart NetworkManager
Apply the changes by restarting NetworkManager:
sudo systemctl restart NetworkManager
Restart Docker
After restarting NetworkManager, restart Docker to ensure the interfaces
are configured correctly:
sudo systemctl restart docker
Source:
https://community.fortinet.com/t5/Support-Forum/config-DNS-failed/m-p/364789
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089930
Title:
NetworkManager crashes when modifying connection (ipv4.ignore-auto-
routes yes) -- using forticlient SSL-VPN
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2089930/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
