Opened 17 months ago

Last modified 5 weeks ago

#1083 new Bug / Defect

iOS -- Log does not show route addition errors

Reported by: tincantech Owned by:
Priority: major Milestone:
Component: Generic / unclassified Version: OpenVPN Connect for iOS v1.2.9
Severity: Not set (select this one, unless your'e a OpenVPN developer) Keywords:



When pushing a route to iOS setting the gateway parameter is an error (Do not set the gateway because iOS does not allow this).

However, iOS currently silently ignores the error so the user cannot verify what has happened.

iOS log example:

2018-08-06 14:50:37 Sending PUSH_REQUEST to server...
2018-08-06 14:50:37 OPTIONS:
0 [route] [] [] [] 
1 [route-gateway] [] 
2 [topology] [subnet] 
3 [ping] [1800] 
4 [ping-restart] [3600] 
5 [ifconfig] [] [] 
6 [peer-id] [0] 
7 [cipher] [AES-256-GCM] 

2018-08-06 14:50:37 PROTOCOL OPTIONS:
  cipher: AES-256-GCM
  digest: SHA256
  compress: LZ4
  peer ID: 0
2018-08-06 14:50:37 EVENT: ASSIGN_IP
2018-08-06 14:50:37 NIP: preparing TUN network settings
2018-08-06 14:50:37 NIP: init TUN network settings with endpoint: OPENVPN-IP
2018-08-06 14:50:37 NIP: adding IPv4 address to network settings
2018-08-06 14:50:37 NIP: adding (included) IPv4 route
2018-08-06 14:50:37 Connected via NetworkExtensionTUN
2018-08-06 14:50:37 LZ4 init asym=0
2018-08-06 14:50:37 EVENT: CONNECTED @OPENVPN-IP:1194 (OPENVPN-IP) via /UDPv4 on NetworkExtensionTUN/ gw=[/]

This is the error:

0 [route] [] [] [] 

But the log does not acknowledge this.

Change History (1)

comment:1 Changed 5 weeks ago by Gert Döring

not sure I understand this ticket - the gateway has no effect on iOS, but the line is syntactically correct so the route should end up pointing to the VPN?

If you error out on this, very many configs will break that have a gateway which is basically just pointing into the tunnel.

Note: See TracTickets for help on using tickets.