You are not logged in.
After ppp's upgrade to version 2.5.0, I'm not able to establish VPN tunnels anymore.
Adding ipcp-accept-remote to /etc/ppp/options, tunnels are established, but remote networks are still unreachable.
Downgrading ppp to version 2.4.9 and removing the ipcp-accept-remote option allows openfortivpn to work again, but networkmanager-fortisslvpn depends on ppp 2.5.0 and has been recently moved to AUR.
Last edited by smart2128 (2023-09-11 09:55:18)
Offline
You're not alone, I have the same problem after upgrading today.
I've posted this problem in the networkmanager-fortisslvpn package AUR's page, just in case you want to follow it: https://aur.archlinux.org/packages/netw … ent-933331
Offline
Yup +1 here
Setup 1: Thinkpad T14s G3, 14" FHD - R7 6850U - 32GB RAM - 2TB Solidigm P44 Pro NVME
Setup 2: Thinkpad X1E G1, 15.6" FHD - i7-8850H - 32GB RAM - NVIDIA GTX 1050Ti - 2x 1TB Samsung 970 Pro NVME
Accessories: Filco Majestouch TKL MX-Brown Mini Otaku, Benq XL2420T (144Hz), Lo(w)gitech G400, Puretrak Talent, Sennheiser HD800S + Meier Daccord FF + Meier Classic FF
Offline
Try uncommenting ipcp-accept-remote in /etc/ppp/options
It worked for me
Last edited by niki (2023-09-14 16:05:55)
Offline
Try uncommenting ipcp-accept-remote in /etc/ppp/options
It worked for me
As I wrote in my post, I already tried it.
The VPN tunnel goes up and the routing table is properly populated, but there is no communications with remote networks/hosts.
After downgrading ppp to version 2.4.9, openfortivpn's client works as expected, but networkmanager-fortisslvpn fails to build without ppp 2.5.0.
Offline
Try uncommenting ipcp-accept-remote in /etc/ppp/options
It worked for me
I can confirm. Using ppp=2.5.0-1 and uncommenting the above setting works for me with openfortivpn.
Offline
I can confirm as well.
niki wrote:Try uncommenting ipcp-accept-remote in /etc/ppp/options
It worked for meI can confirm. Using ppp=2.5.0-1 and uncommenting the above setting works for me with openfortivpn.
Offline
Anyone has any updates on this issue? I had the same problem when it happened.. I circumvented it by keeping the old ppp package version installed and ignored it for futured updates.
In the meantime I had to unfortunately completely reinstall my machine and how I'm kinda hoping this issue got sorted in the meantime
Offline
I recently upgraded all my system (including ppp to version 2.5) and started to receive this error when trying to connect:
/usr/bin/openfortivpn: unrecognized option '--pppd-accept-remote'
The solution was pretty easy, I cloned the AUR package for networkmanager-fortisslvpn, and have commented the line 44 of the PKGBUILD file, that have the following content:
sed -i 's/"--no-routes"/"--pppd-accept-remote"/g' src/nm-fortisslvpn-service.
After perform it, I just reinstalled the package by run makepkg -si, and voilá, the connection started to work again! A complete step by step stay bellow:
# Clone and access the directory with package
git clone https://aur.archlinux.org/networkmanager-fortisslvpn.git
cd networkmanager-fortisslvpn
# Search on the file the content i told above and comment the line
vim PKGBUILD
# Compile the package with the option above commented
makepkg -si
I wasn't required to restart the system
Offline
I recently upgraded all my system (including ppp to version 2.5) and started to receive this error when trying to connect:
/usr/bin/openfortivpn: unrecognized option '--pppd-accept-remote'
The solution was pretty easy, I cloned the AUR package for networkmanager-fortisslvpn, and have commented the line 44 of the PKGBUILD file, that have the following content:
sed -i 's/"--no-routes"/"--pppd-accept-remote"/g' src/nm-fortisslvpn-service.
After perform it, I just reinstalled the package by run makepkg -si, and voilá, the connection started to work again! A complete step by step stay bellow:
# Clone and access the directory with package git clone https://aur.archlinux.org/networkmanager-fortisslvpn.git cd networkmanager-fortisslvpn # Search on the file the content i told above and comment the line vim PKGBUILD # Compile the package with the option above commented makepkg -si
I wasn't required to restart the system
Perfect, thank you
Offline