Skip to content

Can vpn_gateway still be used over a tap interface for default routing? #936

@kabassanov

Description

@kabassanov

Hi,

I set up a testbed with 2 clients (Ubuntu and Windows 11) and a Debian openvpn server using tap interfaces. Addresses on the vpn network are assigned by an external dhcp server belonging to the same network (inside the vpn lan). I'm trying to redirect traffic through the tunnel and the remote vpn_gateway. Linux does not set up routes. Linux client openvpn is started from the shell in order to avoid at beginning some Network Manager potential issues. I've looked a little bit, and it seems that even if the dhcp gateway option from the tunneled dhcp replies is catched, rl->spec.flags are not set to RTSA_REMOTE_ENDPOINT in redirect_default_route_to_vpn. So the first function's warning is triggered (redirect-gateway def1 and route-gateway dhcp are pushed from the server, thus the message "VPN gateway parameter (--route-gateway or --ifconfig) is missing" is strange). I've just temporarily disabled this test in the function and I got at least a route for the remote vpn server. 0.0.0.0 and 128.0.0.0 still fail, because the vpn_gateway value does not seem to be queried as possible gateway (once it has been instanciated).

It seems to work on Windows.

Do you have any suggestion? (Ubuntu distribution packet 2.6.14 and manully recompiled 2.6.17 have similar behavior).

Thanks.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions