Closed jamesdbrock closed 3 years ago
As a workaround I can set
$ resolvectl dns ppp0 192.168.100.53
$ resolvectl domain ppp0 mydomain
and then the DNS works on my VPN.
Regarding the NetworkManager-fortisslvpn bug and the following commit which closed that bug :
It uses the --pppd-use-peerdns=1
fortisslvpn flag which ends up using pppd's usepeerdns
option, it looks practically the same as NetworkManager-l2tp's commit https://github.com/nm-l2tp/NetworkManager-l2tp/commit/7328971a08d897641661e6d2539bc44351909a1d from 3 years ago (although it was just for adding a conditional), ignore my comment for that commit, it should have read:
If "Automatic (VPN) Addresses Only" mode is disabled in the the IPv4 settings, do not use the pppd usepeerdns option.
Still looking ...
Actually I'm not able to reproduce the issue on Fedora 33. The following is from using the free US server listed on www.freel2tpvpn.com :
$ nmcli
...
DNS configuration:
servers: 10.20.0.1
interface: ppp0
type: vpn
servers: 172.16.244.2
domains: localdomain
interface: ens33
$ resolvectl dns
Global:
Link 2 (ens33): 172.16.244.2
Link 3 (virbr0):
Link 4 (virbr0-nic):
Link 5 (ip_vti0):
Link 7 (ppp0): 10.20.0.1
Actually I'm not able to reproduce the issue on Fedora 33. The following is from using the free US server listed on www.freel2tpvpn.com
Okay, when I connect to the same us.freel2tpvpn.com server, then my VPN totally works. So there must be something else wrong with how our VPN server is configured. Thank you very much for checking!
I just upgraded to Fedora 33, and I'm having trouble with my VPN with __NetworkManager-l2tp-gnome-1.8.2-2.fc33.x86_64 . I guess there were some pretty big changes with systemd-resolved__ https://fedoraproject.org/wiki/Changes/systemd-resolved#Upgrade.2Fcompatibility_impact
To connect to the VPN, I first had to apply this workaround for a libreswan bug https://bugzilla.redhat.com/show_bug.cgi?id=1883666#c4
Now I can connect to the VPN, but my VPN connection is not picking up the DNS server from the Gateway.
The Gateway is definitely still sending the DNS server IP, I can see it in journalctl:
And NetworkManager knows about the DNS server:
But the DNS isn't added to the
ppp0
link in systemd-resolved:This might be a bug in NetworkManager, but I suspect that it's a bug in this VPN plugin, perhaps similar to this bug in the NetworkManager-fortisslvpn plugin https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/513
Thank you for maintaining this plugin!