Opened 11 years ago

Closed 10 years ago

#84 closed Bug / Defect (fixed)

multihome with udp6 doesn't work

Reported by: the2masters Owned by: jjo
Priority: major Milestone: beta 2.3
Component: IPv6 Version: OpenVPN git master branch (Community Ed)
Severity: Not set (select this one, unless your'e a OpenVPN developer) Keywords:
Cc:

Description

I have multiple IPv6 tunnels and Openvpn answers always on the primary route.
With --multihome I get:
Jan 28 11:37:22 openvpn(server)[17978]: read UDPv6 [NO-INFO]: Connection
refused (code=146)
Jan 28 11:37:24 openvpn(server)[17978]: read UDPv6 [NO-INFO]: Connection
refused (code=146)
Jan 28 11:37:26 openvpn(server)[17978]: read UDPv6 [NO-INFO]: Connection
refused (code=146)
Jan 28 11:37:29 openvpn(server)[17978]: read UDPv6 [NO-INFO]: Connection
refused (code=146)

I don't know what code=146 means but I think multihome is not properly implemented for IPv6. tcp6-server is ok.

Why is multihome not enabled by default? (If it would work) I think everyone could use it (on Linux).

My Openvpn-version: openvpn-201102.tar.gz from here: ftp://ftp.secure-computing.net/pub/FreeBSD/ports/openvpn-devel/
compiled for mips.

See also: http://comments.gmane.org/gmane.network.openvpn.user/31788

Attachments (1)

0001-fix-multihome-for-IPv6-do-check-for-setsockopt-failu.patch (2.8 KB) - added by jjo 10 years ago.

Download all attachments as: .zip

Change History (7)

comment:1 Changed 11 years ago by David Sommerseth

Owner: set to jjo
Status: newassigned

comment:2 Changed 11 years ago by David Sommerseth

Commit f3ecd33c7c09 seems to be HEAD of the 201102 snapshot.

comment:3 Changed 10 years ago by jjo

Basically the fix is a 1-liner:
sed -i /setsockopt/s/IPV6_PKTINFO/IPV6_RECVPKTINFO/
, preparing a patch with additional defensive code around setsockopt() failures.

comment:4 Changed 10 years ago by the2masters

sorry, testing lasts longer than expected, my primary testing device broke down with other problems. I tested this on a router with two tunnelbroker ipv6-gateways and addresses from 3 different routed subnets. Everything is working as expected.

Tested-by: Stefan Hellermann <stefan@…>

comment:5 Changed 10 years ago by David Sommerseth

Milestone: beta 2.3

comment:6 Changed 10 years ago by David Sommerseth

Resolution: fixed
Status: assignedclosed

Based on the comment from 'the2masters', moving this one to fixed.

Note: See TracTickets for help on using tickets.