Opened 10 years ago

Closed 10 years ago

#147 closed Bug / Defect (fixed)

IPv6 errors on server side

Reported by: psilo Owned by: David Sommerseth
Priority: minor Milestone: release 2.2.2
Component: IPv6 Version: OpenVPN 2.2.0 (Community Ed)
Severity: Not set (select this one, unless your'e a OpenVPN developer) Keywords:
Cc:

Description

Linux x64 OpenVPN 2.2.0 server IPv4 mode
Windows 7 x64 OpenVPN 2.2.0 client

Many many errors in the server logs:

Wed Jun 29 22:12:51 2011 username/1.2.3.4:56990 Need IPv6 code in mroute_extract_addr_from_packet

The problem does not occur with client version 2.1.4.

Change History (7)

comment:1 Changed 10 years ago by Samuli Seppänen

Milestone: release 2.2.1release 2.2.2

Moving to milestone 2.2.2

comment:2 Changed 10 years ago by David Sommerseth

This will not be completely fixed before the 2.3 release. We can consider to reduce the amount of logging.

This is simply caused by the TUN/TAP adapter processing IPv6 packets and pushing them to OpenVPN. OpenVPN will not support IPv6 packets properly before v2.3.

comment:3 Changed 10 years ago by Gert Döring

specifically, the client side is just forwarding DHCPv6 and RS packets from the windows side, and the server has no IPv6 support in point-to-multipoint tun mode - so it's warning for every single packet that it doesn't know what to do with it, and doesn't even know how to print out what it is.

comment:4 Changed 10 years ago by David Sommerseth

Owner: set to Gert Döring
Status: newassigned

comment:5 Changed 10 years ago by Samuli Seppänen

In IRC meeting on 8th Dec 2011 it was agreed that a more sensible, one-time warning message should suffice as a fix.

comment:6 Changed 10 years ago by David Sommerseth

Owner: changed from Gert Döring to David Sommerseth
Status: assignedaccepted

I've proposed a fix for this issue here:
http://thread.gmane.org/gmane.network.openvpn.devel/5231

comment:7 Changed 10 years ago by David Sommerseth

Resolution: fixed
Status: acceptedclosed

Applied to release/2.2 branch

commit b7bbe47a7fcfa74297ff04a50982b70113f28f96
Author: David Sommerseth <davids@redhat.com>
Date:   Tue Dec 13 18:08:24 2011 +0100

    Only warn about non-tackled IPv6 packets once
    
    When using OpenVPN 2.2 on clients and server with Windows based
    clients, it will try to push IPv6 packets through the tunnel.  This
    causes the server log to be filled up with log entries like this:
    
     Wed Jun 29 22:12:51 2011 username/1.2.3.4:56990 Need IPv6 code in mroute_extract_addr_from_packet
    
    This patch modifies this message to state that IPv6 packets are not
    tackled in tun mode, and prints it only once.
    
    Trac: 147
    Signed-off-by: David Sommerseth <davids@redhat.com>
    Acked-by: Gert Doering <gert@greenie.muc.de>
Note: See TracTickets for help on using tickets.