Date: Mon, 27 Feb 2012 15:16:47 +0800 From: Archimedes Gaviola <agaviola@infoweapons.com> To: Hiroki Sato <hrs@FreeBSD.org> Cc: "freebsd-net@FreeBSD.org" <freebsd-net@FreeBSD.org> Subject: Re: Issue with multiple configured IPv6 prefixes in rtadvd.conf Message-ID: <4F4B2DDF.6000602@infoweapons.com> In-Reply-To: <4F4B2B6C.7040601@infoweapons.com> References: <4F4AEDBF.3000903@infoweapons.com> <20120227.131108.899978360503655703.hrs@allbsd.org> <4F4B0930.5040302@infoweapons.com> <4F4B2B6C.7040601@infoweapons.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2/27/2012 3:06 PM, Archimedes Gaviola wrote: > On 2/27/2012 12:40 PM, Archimedes Gaviola wrote: >> On 2/27/2012 12:11 PM, Hiroki Sato wrote: >>> Archimedes Gaviola<agaviola@infoweapons.com> 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 Ooops, sorry. reject the previous log (that was taken from a dynamic RA message, not using the rtadvd.conf), this is the correct one. Frame 3 (214 bytes on wire, 214 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: 0x6ebe [correct] Cur hop limit: 64 Flags: 0x00 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: 1400 ICMPv6 Option (Prefix information) Type: Prefix information (3) Length: 32 Prefix length: 64 Flags: 0xc0 Valid lifetime: 12345 Preferred lifetime: 12345 Prefix: 3ffe:501:ffff:104:: ICMPv6 Option (Prefix information) Type: Prefix information (3) Length: 32 Prefix length: 64 Flags: 0xc0 Valid lifetime: 12345 Preferred lifetime: 12345 Prefix: 3ffe:501:ffff:103:: ICMPv6 Option (Prefix information) Type: Prefix information (3) Length: 32 Prefix length: 64 Flags: 0xc0 Valid lifetime: 12345 Preferred lifetime: 12345 Prefix: 3ffe:501:ffff:102:: ICMPv6 Option (Prefix information) Type: Prefix information (3) Length: 32 Prefix length: 64 Flags: 0xc0 Valid lifetime: 12345 Preferred lifetime: 12345 Prefix: 3ffe:501:ffff:101:: ICMPv6 Option (Prefix information) Type: Prefix information (3) Length: 32 Prefix length: 64 Flags: 0xc0 Valid lifetime: 12345 Preferred lifetime: 12345 Prefix: 3ffe:501:ffff:100::
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F4B2DDF.6000602>