[j-nsp] Using Framed-IPv6-Pool attribute to obtain ipv6 prefix-pool name for ICMPv6 RA

Egor Zimin lesnix at gmail.com
Mon Nov 1 10:46:35 EDT 2010


Hi folks,
I have simple testbed for "IPv6 over PPPoE" scenario:
BRAS: Juniper E120 10.1.0 release-0.0 [BuildId 10854]   (April 22, 2009  02:27)
PPPoE-client 1: Windows 7
PPPoE-client 2: Juniper SRX210B JUNOS 10.3R1.9

With regard to this I have a question for community:
Is it true, that JunOSe 10.1 doesn't support using Framed-IPv6-Pool to
obtain ipv6 prefix-pool name for IPv6 ND Router advertisments ?
What does it mean:
I'm trying to configure scenario with per-user /64 prefix, assigned
via ICMPv6 SLAAC.
1) I've modified dynamic profile:
 to initiate IPCP6, to specify ipv6 virtual-router, ipv6 unnumbered
lo0, ipv6 sa-validate and ipv6 nd ra-interval. This dynamic profile
works normally for another "IPv6 over PPPoE" scenarios (shared /64).

2) I configured IPv6 local pool:
--
ipv6 address-pool local
!
ipv6 local pool "IPV6-POOL"
 prefix 2001:db8:1::/48 64 preferred infinite valid infinite
 exclude-prefix 2001:db8:1::/64 2001:db8:1:1::/64
!
--
3) ... and included Framed-IPv6-Pool in Access-Accept messages.

Despite of this, there is no Prefix Information option in RA messages,
received by PPPoE clients:
--
>monitor traffic interface pp0.0 detail no-resolve
Address resolution is OFF.
Listening on pp0.0, capture size 1514 bytes

22:25:04.415369  In IP6 (hlim 255, next-header: ICMPv6 (58), length:
24) fe80::90:1a00:41a2:e4be > ff02::1: [icmp6 sum ok] ICMP6, router
advertisement, length 24
        hop limit 0, Flags [other stateful], pref medium, router
lifetime 1800s, reachable time 30000s, retrans time 0s
          mtu option (5), length 8 (1):  1492
--

In this(http://www.nanog.org/meetings/nanog46/presentations/Wednesday/Douitsis_ipv6_deploy_N46.pdf)
NANOG presentation I noticed:
"Framed-IPv6-Prefix required for NDRA over PPP link (cannot use Framed-IPv6-Pool
yet)"
Can anybody confirm this ? Does anybody know, are there any junose
versions, which support this feature?

-- 
Best regards,
Egor Zimin



More information about the juniper-nsp mailing list