From owner-freebsd-net@FreeBSD.ORG Thu May 28 23:12:25 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 063F59D4 for ; Thu, 28 May 2015 23:12:25 +0000 (UTC) (envelope-from Michael.Tuexen@lurchi.franken.de) Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mail-n.franken.de", Issuer "Thawte DV SSL CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BEFE9828 for ; Thu, 28 May 2015 23:12:24 +0000 (UTC) (envelope-from Michael.Tuexen@lurchi.franken.de) Received: from [192.168.1.200] (p508F01E5.dip0.t-ipconnect.de [80.143.1.229]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id B8EAA1C02FF09 for ; Fri, 29 May 2015 01:12:20 +0200 (CEST) From: Michael Tuexen Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: No RTM_NEWADDR message generated when adding IPv6 addresses to a tun interface Message-Id: <0590FE39-614E-49D9-AD67-477DFA12630B@lurchi.franken.de> Date: Fri, 29 May 2015 01:12:19 +0200 To: FreeBSD Net Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) X-Mailer: Apple Mail (2.2098) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2015 23:12:25 -0000 Dear all, I'm using a tun interface with the IFF_BROADCAST | IFF_MULTICAST mode. I can use ifconfig to add an IPv4 or IPv6 address. So far so good. I'm running a program which gets all messages from a routing socket. When I'm adding an IPv4 address to the tun interfaces, I receive a RTM_NEWADDR routing message with the added address. However, I do NOT receive one, when I'm adding an IPv6 address. When deleting an IPv4 or IPv6 address, I do receive the corresponding RTM_DELADDR message. Does anyone know why I'm not receiving the RTM_NEWADDR when adding an IPv6 address to a tun interface? If it matters, the above is tested on head... Best regards Michael