From owner-freebsd-net@FreeBSD.ORG Fri May 29 13:40:38 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 625373A9 for ; Fri, 29 May 2015 13:40:38 +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 270BC1163 for ; Fri, 29 May 2015 13:40:38 +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 9CAB1200C0100 for ; Fri, 29 May 2015 15:40:35 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) Subject: Re: No RTM_NEWADDR message generated when adding IPv6 addresses to a tun interface From: Michael Tuexen In-Reply-To: <0590FE39-614E-49D9-AD67-477DFA12630B@lurchi.franken.de> Date: Fri, 29 May 2015 15:40:33 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <145CC3C4-41BB-4CB3-89ED-3631761BE0B6@lurchi.franken.de> References: <0590FE39-614E-49D9-AD67-477DFA12630B@lurchi.franken.de> To: FreeBSD Net 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: Fri, 29 May 2015 13:40:38 -0000 > On 29 May 2015, at 01:12, Michael Tuexen = wrote: >=20 > Dear all, >=20 > 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. >=20 > 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. >=20 > Does anyone know why I'm not receiving the RTM_NEWADDR when adding > an IPv6 address to a tun interface? >=20 > If it matters, the above is tested on head... Just for the records: The issue was fixed in https://svnweb.freebsd.org/changeset/base/283696 Best regards Michael >=20 > Best regards > Michael > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >=20