Hi, On Mon, Feb 17, 2014 at 08:28:59PM +0100, Tore Anderson wrote: > Now that has been fixed upstream (Linux 3.14), I tried again. Here I am > connecting from 84.209.94.36 to 87.238.35.254, which is a secondary > address on the server (87.238.35.145 is the primary). The OpenVPN > server logs: > > ::ffff:84.209.94.36 TLS: Initial packet from > [AF_INET6]::ffff:84.209.94.36:39970 (via ::ffff:87.238.35.254%eth0), > sid=a79ae4ef 7abb8215
Cool :-) > So the Linux 3.14 fix seems to work, as OpenVPN now does see which IPv4 > address the server was contacted on. Progress! However the VPN doesn't > come up, and tcpdump reveals why - OpenVPN is responding from the > primary address of the server rater than the one it was contacted on: > > 20:21:02.555667 IP 84.209.94.36.39970 > 87.238.35.254.1194: UDP, length 14 > 20:21:02.556719 IP 87.238.35.145.1194 > 84.209.94.36.39970: UDP, length 26 > > So we're closer, but not quite there yet unfortunately... Could you run my test program to see whether that gets it right? http://www.greenie.net/ipv6/mhome.c For some platforms I also had to change the sending part (data structures, alignment, whatnot) and that has not yet been integrated into OpenVPN proper, and I think Linux was among them, at least for 64bit. > This happens both with today's git master and with 2.3.2. BTW Arne's > patch to socket.c that fixes the assert crash we originally discussed > still isn't included in git master, has it been forgotten about? ISTR that Arne wrote something about "this is a quick fix, will send a proper patch later". Then we lost a bit of momentum :-( gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany g...@greenie.muc.de fax: +49-89-35655025 g...@net.informatik.tu-muenchen.de
pgp3fyEv1Fx5A.pgp
Description: PGP signature
