Bug#928680: [openfortivpn] Since switching to buster openfortivpn can't connect to vpn anymore

[Michael Meier]

Ok, i've updated my whole system again. And now it seems to work.

You can close the bug.

Thanks a lot for your efforts.

On 08.05.19 23:05, Daniel Echeverry wrote:

tags 928680 + moreinfo unreproducible
severity 928680 normal
thanks

Hi!

El mié., 8 de may. de 2019 a la(s) 14:15, Michael Meier (c...@rmm.li 
) escribió:


Package: openfortivpn
Version: 1.8.1-1
Severity: normal

I've installed the fortivpn package in debian stable (stretch), and
managed to get it working with a vpn connection.
Somewhen I updated my System to buster and now realized that
openfortivpn can't connect to the vpn anymore. While another computer
which is still running on stretch connects to the same vpn without
any
problems with exactly the same config parameters. Also
openfortivpn and
ppp are the same version on both systems.
As it seems it doesn't manage to configure the ppp interface
correctly.
Maybe in buster something changed the way interfaces are
configured? No
idea.

Thanks for your report!! Unfortunately, I can't reproduce this bug, I 
tried openfortivpn package in 2 differents machines with buster and 
works fine, Could you upgrade your system? I think that you dont have 
the last versions of dependencies.


Regards

--
Daniel Echeverry
Debian Developer
https://wiki.debian.org/DanielEcheverry
Linux user: #477840
GPG Fingerprint:
D0D0 85B1 69C3 BFD9 4048 58FA 21FC 2950 4B52 30DB

Bug#928680: [openfortivpn] Since switching to buster openfortivpn can't connect to vpn anymore

[Michael Meier]

ok. I will upgrade my system, but it could take a bit. I'm on an island 
right now with internet connections of about 10kB/s...


meanwhile I managed to convince openfortivpn that the tunnel is working.

While it was waiting for ppp0 to become up, I configured ppp0 manually 
by executing:


ip addr add 192.168.0.231/24 peer 192.0.2.1/32 dev ppp0
ip link set up ppp0

openfortivpn afterwards set the routes correctly. And as least as far as 
I can see, then ppp0 and the routes are
configured exactly the same, as on the machine where it is working. But 
unfortunately no data goes through the tunnel.


But I'll try with an update (my last system update was about one week ago).

Log would look like that:

INFO:   Connected to gateway.
INFO:   Authenticated.
INFO:   Remote gateway has allocated a VPN.
INFO:   Got addresses: [192.168.0.231], ns [0.0.0.0, 0.0.0.0]
INFO:   negotiation complete
INFO:   Got addresses: [192.168.0.231], ns [0.0.0.0, 0.0.0.0]
INFO:   negotiation complete
INFO:   Got addresses: [192.168.0.231], ns [0.0.0.0, 0.0.0.0]
INFO:   negotiation complete
INFO:   Got addresses: [192.168.0.231], ns [0.0.0.0, 0.0.0.0]
INFO:   negotiation complete
INFO:   Got addresses: [192.168.0.231], ns [0.0.0.0, 0.0.0.0]
INFO:   negotiation complete
< at that moment I configured ppp0 manually >
INFO:   Interface ppp0 is UP.
INFO:   Setting new routes...
INFO:   Tunnel is up and running.


On 08.05.19 22:05, Daniel Echeverry wrote:

tags 928680 + moreinfo unreproducible
severity 928680 normal
thanks

Hi!

El mié., 8 de may. de 2019 a la(s) 14:15, Michael Meier (c...@rmm.li 
) escribió:


Package: openfortivpn
Version: 1.8.1-1
Severity: normal

I've installed the fortivpn package in debian stable (stretch), and
managed to get it working with a vpn connection.
Somewhen I updated my System to buster and now realized that
openfortivpn can't connect to the vpn anymore. While another computer
which is still running on stretch connects to the same vpn without
any
problems with exactly the same config parameters. Also
openfortivpn and
ppp are the same version on both systems.
As it seems it doesn't manage to configure the ppp interface
correctly.
Maybe in buster something changed the way interfaces are
configured? No
idea.

Thanks for your report!! Unfortunately, I can't reproduce this bug, I 
tried openfortivpn package in 2 differents machines with buster and 
works fine, Could you upgrade your system? I think that you dont have 
the last versions of dependencies.


Regards

--
Daniel Echeverry
Debian Developer
https://wiki.debian.org/DanielEcheverry
Linux user: #477840
GPG Fingerprint:
D0D0 85B1 69C3 BFD9 4048 58FA 21FC 2950 4B52 30DB

Bug#928680: [openfortivpn] Since switching to buster openfortivpn can't connect to vpn anymore

[Daniel Echeverry]

tags 928680 + moreinfo unreproducible
severity 928680 normal
thanks

Hi!

El mié., 8 de may. de 2019 a la(s) 14:15, Michael Meier (c...@rmm.li)
escribió:

> Package: openfortivpn
> Version: 1.8.1-1
> Severity: normal
>
> I've installed the fortivpn package in debian stable (stretch), and
> managed to get it working with a vpn connection.
> Somewhen I updated my System to buster and now realized that
> openfortivpn can't connect to the vpn anymore. While another computer
> which is still running on stretch connects to the same vpn without any
> problems with exactly the same config parameters. Also openfortivpn and
> ppp are the same version on both systems.
> As it seems it doesn't manage to configure the ppp interface correctly.
> Maybe in buster something changed the way interfaces are configured? No
> idea.
>
>
Thanks for your report!! Unfortunately, I can't reproduce this bug, I tried
openfortivpn package in 2 differents machines with buster and works fine,
Could you upgrade your system? I think that you dont have the last versions
of dependencies.

Regards

-- 
Daniel Echeverry
Debian Developer
https://wiki.debian.org/DanielEcheverry
Linux user: #477840
GPG Fingerprint:
D0D0 85B1 69C3 BFD9 4048 58FA 21FC 2950 4B52 30DB

Bug#928680: [openfortivpn] Since switching to buster openfortivpn can't connect to vpn anymore

[Michael Meier]

Package: openfortivpn
Version: 1.8.1-1
Severity: normal

I've installed the fortivpn package in debian stable (stretch), and 
managed to get it working with a vpn connection.
Somewhen I updated my System to buster and now realized that 
openfortivpn can't connect to the vpn anymore. While another computer 
which is still running on stretch connects to the same vpn without any 
problems with exactly the same config parameters. Also openfortivpn and 
ppp are the same version on both systems.

As it seems it doesn't manage to configure the ppp interface correctly.
Maybe in buster something changed the way interfaces are configured? No 
idea.


Here is the openfortivpn logfile (i've deleted the repetition of certain 
messages and removed privacy related information) further down is the 
ppp log:


DEBUG:  openfortivpn 1.8.1
DEBUG:  Loaded config file "/etc/openfortivpn/config". 



DEBUG:  Resolving gateway host ip 



DEBUG:  Establishing ssl connection 



DEBUG:  server_addr: 



DEBUG:  server_port: 10443 



DEBUG:  gateway_addr:
DEBUG:  gateway_port: 10443 



DEBUG:  Gateway certificate validation failed. 



DEBUG:  Gateway certificate digest found in white list. 



INFO:   Connected to gateway.
DEBUG:  Cookie: SVPNCOOKIE=...== 




INFO:   Authenticated.
DEBUG:  Cookie: SVPNCOOKIE=...== 




INFO:   Remote gateway has allocated a VPN.
DEBUG:  server_addr: ...
DEBUG:  server_port: 10443 



DEBUG:  gateway_addr: ...
DEBUG:  gateway_port: 10443 



DEBUG:  Gateway certificate validation failed. 



DEBUG:  Gateway certificate digest found in white list. 



DEBUG:  Retrieving configuration 



DEBUG:  Establishing the tunnel 



DEBUG:  ppp_path: /usr/sbin/pppd 



DEBUG:  Switch to tunneling mode 



DEBUG:  Starting IO through the tunnel 



DEBUG:  pppd_read thread 



DEBUG:  ssl_read thread 



DEBUG:  ssl_write thread 



DEBUG:  if_config thread 



DEBUG:  pppd_write thread 



DEBUG:  pppd ---> gateway (16 bytes) 



DEBUG:  gateway ---> pppd (12 bytes) 



DEBUG:  gateway ---> pppd (16 bytes) 



DEBUG:  pppd ---> gateway (12 bytes) 



DEBUG:  pppd ---> gateway (10 bytes) 



DEBUG:  pppd ---> gateway (17 bytes) 



DEBUG:  pppd ---> gateway (18 bytes) 



DEBUG:  gateway ---> pppd (12 bytes) 



DEBUG:  gateway ---> pppd (10 bytes) 



DEBUG:  gateway ---> pppd (25 bytes) 



DEBUG:  gateway ---> pppd (12 bytes) 



DEBUG:  pppd ---> gateway (12 bytes) 



DEBUG:  pppd ---> gateway (12 bytes) 



DEBUG:  gateway ---> pppd (12 bytes) 



DEBUG:  gateway ---> pppd (12 bytes) 



DEBUG:  pppd ---> gateway (12 bytes) 



DEBUG:  pppd ---> gateway (12 bytes) 



DEBUG:  gateway ---> pppd (12 bytes) 



DEBUG:  gateway ---> pppd (12 bytes) 



INFO:   Got addresses: [192.168.0.231], ns [0.0.0.0, 0.0.0.0]
INFO:   negotiation complete
DEBUG:  Got Address: 192.168.0.231
DEBUG:  if_config: not ready yet... 



DEBUG:  pppd ---> gateway (12 bytes) 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  pppd ---> gateway (12 bytes) 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  gateway ---> pppd (12 bytes) 



DEBUG:  gateway ---> pppd (12 bytes) 



INFO:   Got addresses: [192.168.0.231], ns [0.0.0.0, 0.0.0.0]
INFO:   negotiation complete
DEBUG:  pppd ---> gateway (12 bytes)
DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  pppd ---> gateway (12 bytes) 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: