From owner-freebsd-net@FreeBSD.ORG Mon Feb 27 07:06:50 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 374F61065670; Mon, 27 Feb 2012 07:06:50 +0000 (UTC) (envelope-from agaviola@infoweapons.com) Received: from infoweapons.com (ironmail.v6home.org [184.105.238.50]) by mx1.freebsd.org (Postfix) with ESMTP id 1AD318FC08; Mon, 27 Feb 2012 07:06:49 +0000 (UTC) Received: from ([120.89.47.15]) by mail0.infoweapons.com with ESMTP with TLS id 4321444.9242324; Sun, 26 Feb 2012 23:06:21 -0800 Received: from [IPv6:2001:470:3d:2400:148b:9fc2:a186:ec38] (2001:470:3d:2400:148b:9fc2:a186:ec38) by webmail.infoweapons.com (2001:470:3d:2400::10:11) with Microsoft SMTP Server (TLS) id 8.2.255.0; Mon, 27 Feb 2012 15:06:21 +0800 Message-ID: <4F4B2B6C.7040601@infoweapons.com> Date: Mon, 27 Feb 2012 15:06:20 +0800 From: Archimedes Gaviola User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: Hiroki Sato References: <4F4AEDBF.3000903@infoweapons.com> <20120227.131108.899978360503655703.hrs@allbsd.org> <4F4B0930.5040302@infoweapons.com> In-Reply-To: <4F4B0930.5040302@infoweapons.com> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="ISO-8859-1"; format="flowed" Cc: "freebsd-net@FreeBSD.org" Subject: Re: Issue with multiple configured IPv6 prefixes in rtadvd.conf X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2012 07:06:50 -0000 On 2/27/2012 12:40 PM, Archimedes Gaviola wrote: > On 2/27/2012 12:11 PM, Hiroki Sato wrote: >> Archimedes Gaviola wrote >> in<4F4AEDBF.3000903@infoweapons.com>: >> >> ag> Now, my observation is that there seems to be a problem with >> ag> advertising two or perhaps more prefixes in the RA message. This has >> ag> been tested in 7.x and the issues were the same. FreeBSD 4.11 behave >> ag> the same as well. >> ag> >> ag> Is this a bug or limitation of the rtadvd design implementation? >> >> I am wondering where you got the notation ":addrs#1:" from. Please >> try the following: >> >> em2:\ >> :mtu#1400:\ >> :addr0="3ffe:501:ffff:100::":prefixlen0#64:vltime0#12345:pltime0#12345:\ >> :addr1="3ffe:501:ffff:101::":prefixlen1#64:vltime1#12345:pltime1#12345: >> >> -- Hiroki > Hi Hiroki, > > I got that notation from here > http://www.freebsd.org/doc/handbook/network-ipv6.html. Okay, let me try > you're recommendation. > > Thanks, > Hi Hiroki, I confirmed verifying on 8.2, 7.2 and 4.11, the notation you've suggested is working. In fact, I've tried at least 5 prefixes and it works perfectly. Therefore, this is not a bug or design limitation in the rtadvd but rather a configuration issue. vulcan2# cat /etc/rtadvd.conf em2:\ :mtu#1400:\ :addr0="3ffe:501:ffff:100::":prefixlen0#64:vltime0#12345:pltime0#12345:\ :addr1="3ffe:501:ffff:101::":prefixlen1#64:vltime1#12345:pltime1#12345:\ :addr2="3ffe:501:ffff:102::":prefixlen2#64:vltime2#12345:pltime2#12345:\ :addr3="3ffe:501:ffff:103::":prefixlen3#64:vltime3#12345:pltime3#12345:\ :addr4="3ffe:501:ffff:104::":prefixlen4#64:vltime4#12345:pltime4#12345: Here's the RA message log: Frame 2 (246 bytes on wire, 246 bytes captured) Ethernet II, Src: SuperMic_02:68:21 (00:25:90:02:68:21), Dst: IPv6mcast_00:00:00:01 (33:33:00:00:00:01) Internet Protocol Version 6 Internet Control Message Protocol v6 Type: 134 (Router advertisement) Code: 0 Checksum: 0x87c8 [correct] Cur hop limit: 56 Flags: 0xc8 Router lifetime: 1800 Reachable time: 0 Retrans timer: 0 ICMPv6 Option (Source link-layer address) Type: Source link-layer address (1) Length: 8 Link-layer address: 00:25:90:02:68:21 ICMPv6 Option (MTU) Type: MTU (5) Length: 8 MTU: 1500 ICMPv6 Option (Prefix information) Type: Prefix information (3) Length: 32 Prefix length: 64 Flags: 0xc0 Valid lifetime: 2592000 Preferred lifetime: 604800 Prefix: 3ffe:501:ffff:104:: ICMPv6 Option (Prefix information) Type: Prefix information (3) Length: 32 Prefix length: 64 Flags: 0xc0 Valid lifetime: 2592000 Preferred lifetime: 604800 Prefix: 3ffe:501:ffff:103:: ICMPv6 Option (Prefix information) Type: Prefix information (3) Length: 32 Prefix length: 64 Flags: 0xc0 Valid lifetime: 2592000 Preferred lifetime: 604800 Prefix: 3ffe:501:ffff:102:: ICMPv6 Option (Prefix information) Type: Prefix information (3) Length: 32 Prefix length: 64 Flags: 0xc0 Valid lifetime: 2592000 Preferred lifetime: 604800 Prefix: 3ffe:501:ffff:101:: ICMPv6 Option (Prefix information) Type: Prefix information (3) Length: 32 Prefix length: 64 Flags: 0xc0 Valid lifetime: 2592000 Preferred lifetime: 604800 Prefix: 3ffe:501:ffff:100:: So, thank you very much on the solution! Regards, Archimedes