On 31/01/11 19:25, Stefan Hellermann wrote:
Am 28.01.2011 13:09, schrieb Davide Brini:
On Friday 28 Jan 2011 11:57:30 Stefan Hellermann wrote:
Are you using the "multihome" option in the server configuration? As far
as I can tell, using "multihome" uses the PKTINFO information to source
UDP replies from the correct IP address; however, while it does work for
IPv4, I don't know if that functionality has been ported to IPv6
already. I'm CC-ing the devel list as well.
No I haven't tried multihome, and I don't know why I haven't seen this
option before... Why isn't this the default?
But, it seems it doesn't work for IPv6 yet, I get this:
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)
Not 100% sure but this may mean that multihome has not been ported to IPv6
yet. Perhaps you can open a ticket at
https://community.openvpn.net/openvpn
(you have to register and login first).
With tcp6-server this works.
Yes, because with TCP the source address selection is performed directly by
the OS internally. Using TCP was indeed the suggested workaround before UDP
multihoming was introduced in OpenVPN.
https://community.openvpn.net/openvpn/ticket/84
Thank you very much for your report! I've sent a notification to the
developer of the IPv6 transport patch, and I hope he chimes in soon.
kind regards,
David Sommerseth
