Hi,

On Sun, Mar 19, 2017 at 3:10 PM, Gert Doering <g...@greenie.muc.de> wrote:

> The "prepare IPv6 route message to interactive service" was properly
> handing the correct interface index (r->adapter_index) for this case,
> but then always overwrote the gateway address with our magic tun/tap
> fe80::8 value.  Only do this for "on tap adapter" routes.
>
> Pinpointed by Selva Nair.
>
> Trac #850
>
> Signed-off-by: Gert Doering <g...@greenie.muc.de>
> ---
>  src/openvpn/route.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/src/openvpn/route.c b/src/openvpn/route.c
> index 7e536ef..08998d5 100644
> --- a/src/openvpn/route.c
> +++ b/src/openvpn/route.c
> @@ -3061,8 +3061,10 @@ do_route_ipv6_service(const bool add, const struct
> route_ipv6 *r, const struct t
>
>      /* In TUN mode we use a special link-local address as the next hop.
>       * The tapdrvr knows about it and will answer neighbor discovery
> packets.
> +     * (only do this for routes actually using the tun/tap device)
>       */
> -    if (tt->type == DEV_TYPE_TUN)
> +    if (tt->type == DEV_TYPE_TUN
> +        && msg.iface.index == tt->adapter_index )
>
     {
>          inet_pton(AF_INET6, "fe80::8", &msg.gateway.ipv6);
>      }
>

This should fix it. ACK.

Selva
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Reply via email to