Need IPv6 code in mroute_extract_addr_from_packet

shinjikenny

How do I suppress these from my log? I have "mute 10" on the server config but I still get a lot of this:

Thu Jan 26 00:23:11 2012 xxxxxxxxxxxxx Need IPv6 code in mroute_extract_addr_from_packet
Thu Jan 26 00:23:11 2012 xxxxxxxxxxxxx Need IPv6 code in mroute_extract_addr_from_packet
Thu Jan 26 00:23:14 2012 xxxxxxxxxxxxx Need IPv6 code in mroute_extract_addr_from_packet
Thu Jan 26 00:23:14 2012 xxxxxxxxxxxxx Need IPv6 code in mroute_extract_addr_from_packet
Thu Jan 26 00:23:17 2012 xxxxxxxxxxxxx Need IPv6 code in mroute_extract_addr_from_packet
Thu Jan 26 00:23:17 2012 xxxxxxxxxxxxx Need IPv6 code in mroute_extract_addr_from_packet
Thu Jan 26 00:23:19 2012 xxxxxxxxxxxxx Need IPv6 code in mroute_extract_addr_from_packet
Thu Jan 26 00:23:19 2012 xxxxxxxxxxxxx Need IPv6 code in mroute_extract_addr_from_packet
Thu Jan 26 00:23:21 2012 xxxxxxxxxxxxx Need IPv6 code in mroute_extract_addr_from_packet
Thu Jan 26 00:23:22 2012 xxxxxxxxxxxxx Need IPv6 code in mroute_extract_addr_from_packet
Thu Jan 26 00:23:24 2012 xxxxxxxxxxxxx Need IPv6 code in mroute_extract_addr_from_packet
Thu Jan 26 00:23:24 2012 xxxxxxxxxxxxx Need IPv6 code in mroute_extract_addr_from_packet
Thu Jan 26 00:23:27 2012 xxxxxxxxxxxxx Need IPv6 code in mroute_extract_addr_from_packet
Thu Jan 26 00:23:27 2012 xxxxxxxxxxxxx Need IPv6 code in mroute_extract_addr_from_packet
Thu Jan 26 00:23:29 2012 xxxxxxxxxxxxx Need IPv6 code in mroute_extract_addr_from_packet
Thu Jan 26 00:23:29 2012 xxxxxxxxxxxxx Need IPv6 code in mroute_extract_addr_from_packet
Thu Jan 26 00:23:32 2012 xxxxxxxxxxxxx Need IPv6 code in mroute_extract_addr_from_packet
Thu Jan 26 00:23:32 2012 xxxxxxxxxxxxx Need IPv6 code in mroute_extract_addr_from_packet
Thu Jan 26 00:23:35 2012 xxxxxxxxxxxxx Need IPv6 code in mroute_extract_addr_from_packet
Thu Jan 26 00:23:35 2012 xxxxxxxxxxxxx Need IPv6 code in mroute_extract_addr_from_packet

janjust

this happens when a client sends IPv6 traffic over the tunnel; unbind the TCP/IP v6 protocol on the clients. You can safely ignore this warning message. If you really want to suppress it, you can try adding

verb [0|1]

to the server config, but that will also stop a lot of other useful messages from coming through.

dazo

I'd recommend to upgrade to OpenVPN 2.2.2. We've added a fix where these messages are not duplicated for each IPv6 packet.

See this commit for more info:
http://openvpn.git.sourceforge.net/git/gitweb.cgi?p=openvpn/openvpn-testing.git;a=commitdiff;h=b7bbe47a7fcfa74297ff04a50982b70113f28f96

resto

janjust wroteunbind the TCP/IP v6 protocol on the clients.

While upgrading the server is not an option for me, I wonder if removing the IPv6 binding on the clients is a security risk. Would this not allow client IPv6 traffic to leave the client via another route, ie leak ?

janjust

do you have a local IPv6 router/gateway on your network?if not then there will be no leakage; if you do, then your IPv6 clients will forward traffic to it. If you cannot trust your local network then I'd strongly advise you to unbind IPv6.