ERROR: read: Input/output error about openfortivpn

[ssurba]

In my case exactly the same error as in the original post was caused by ppp package missing from the system.

[Zenithar]

Ok fixed with a reboot, current kernel has been updated and not matching the "new" one.

[GitteHuber]

Up until 1.3.0 I had the exact same problem and debug output as cgogolin. Just wanted to confirm that version 1.3.1 fixed it. ( On my Ubuntu 16.4.2 machine, at least)

[Zenithar]

Same problem for me with 1.2.0 from AUR on a ArchLinux.

[twiebe]

In my case, a route has been pushed by the vpn server, that matches the remote address of the vpn endpoint itself. Therefor, all following vpn packets will not reach the vpn server, which causes the input output error.

A static route to the endpoint address via the local gateway helps.

I've seen other vpn clients add these routes automatically, to avoid such issues. I'd suggest to do this in openfortivpn as well.

[aggregat4]

@twiebe can you post the command you used to set the route? I'm not sure what addresses you mean exactly. I have a similar problem.

[twiebe]

@aggregat4:
The public address of your vpn server.

F.e.:
If your vpn server's public address would be 8.8.8.8 and your vpn server would push the route 8.8.0.0/16, then your host would try to send all further packets, after the route has been pushed, to your vpn server through pppX instead of ethX.

As a workaround, you could set a static route to your vpn server through your regular gateway before starting openfortivpn:
# ip route add VPN_SERVER_PUBLIC_ADDR via DEFAULT_GATEWAY_ADDR

[mrbaseman]

the routing problems discussed above should be fixed in 1.3.1. Now openfortivpn adds such a route to the gateway host before setting up the pushed routes.

[mvernimmen-CG]

That route does not appear to get set with 1.4.0, I had to apply the workaround before starting openfortivpn to get it to work. Also the routes that the vpn hands out are not set by openfortivpn, I had to add them myself. This is on Raspbian GNU/Linux 8 (jessie).

[DimitriPapadopoulos]

@mvernimmen-CG It would have been better to open a new ticket. Since this has been fixed in version 1.3.1, causes are probably different although symptoms are similar.

My suggestions:

• Please provide error messages using option -v - see first post in this ticket.
• Since this looks like an embedded system, is command /usr/sbin/netstat available?

[mvernimmen-CG]

Sure, I'll do that. I posted in here because the ticket was open, I see you closed it now :)

[henkRW]

Up until 1.3.0 I had the exact same problem and debug output as cgogolin. Just wanted to confirm that version 1.3.1 fixed it. ( On my Ubuntu 16.4.2 machine, at least)

I can confirm it. I had similar problem with 1.3.0 version after update to 1.6.0 Forti VPN started work.

[mrbaseman]

@henkRW thanks for this feedback.