Amos,
Probably it's enough.
Let's consider this option:
---
ipv6 nd managed-config-flag
---
This option sets "Managed address configuration" flag in RA messages:
http://www.juniper.net/techpubs/en_US/junose10.3/information-products/topic-collections/command-reference-a-m/ipv6-nd-managed-config-flag.html#id-42696
For what purpose there is a "Managed" flag ?
The answer is in RFC 2462:
A "managed address configuration" flag indicates whether hosts should
use stateful autoconfiguration to obtain addresses.
However, 2462 is obsoleted by 4862 and one of changes is:
"Removed the text regarding the M and O flags, considering the maturity
of implementations and operational experiences. ManagedFlag and
OtherConfigFlag were removed accordingly.". But also there is a Note in
4862: "(Note that this change does not mean the use of these flags is
deprecated)"
So, if there is a "managed" flag in RA, then hosts should use DHCPv6
IA_NA for address assignment.
If I understand clear, you "tried another option which is to send RA
from the Juniper". So, IMHO, you should remove "managed" flag from RA
messages. In my scenario I removed "managed" flag and Win7 host has
succesfully assigned Global Unicast address with a common /64 prefix.
Hope it helps.
03.01.2011 00:15, Amos Rosenboim пишет:
Hello Egor,
Thanks for the reply.
Below is my profile configuration.
profile "L2TP-Users-Profile"
ip unnumbered loopback 0
ip sa-validate
ip tcp adjust-mss 1360
ipv6 virtual-router default
ipv6 unnumbered loopback 0
ipv6 nd managed-config-flag
ipv6 nd other-config-flag
ipv6 nd ra-interval 3
ipv6 nd reachable-time 30000
ipv6 nd prefix-advertisement 2a02:ed0:1002:1::/64 3600 3000 autoconfig
ppp authentication pap
Please let me know if you need any other part of the configuration.
Regards
Amos
On Jan 2, 2011, at 8:44 PM, Egor Zimin wrote:
Hello, Amos.
I have some experience with Juniper IPv6oPPPoE on E-series.
Can you please show me "show configuration" of your BRAS ?
I have encountered a similar problem. In my case root cause was
validLifetime="0" in RA messages. Like this:
---
ipv6 nd prefix-advertisement 2001:db8::/64 0 0 autoconfig
---
2010/12/31 Amos Rosenboim<a...@oasis-tech.net>:
Hello Everybody and happy new year,
I'm managing the network of a small ISP and working on adding IPv6 to the
network.
Subscribers connect to the ISP services by either PPPoE or L2TP dialers.
On the ISP side the edge router (Juniper E310 BRAS) is configured with local
DHCP pool out of which a /48 is assigned to each subscriber.
This works great for client devices that uses IPv6DHCP with prefix delegation
option to request a prefix.
However when the client does not have a CPE and uses his windows box to connect
(by using Windows L2TP dialer) an IPv6 prefix is not assigned.
In packet captures we noticed that the windows client is sending DHCPv6 solicit
messages requesting for absolute non temporary addresses (IA_NA).
This makes sense as the device is a host however it's not supported by the
Juniper router.
We tried another option which is to send RA from the Juniper with a common /48
prefix for all subscribers.
In packet captures we are seeing the RA message with the prefix information,
however the windows client does not assign itself with any global scope address.
I'm not sure if we are doing something wrong on the Juniper ERX, or should
something be changed on the Win7 boxes.
Juniper JTAC helped me to determine the problem but are not willing to offer
any guidance as to the next steps.
Any real world configurations of IPv6 for PPP customers on ERX/E series routers
would be of great assistance.
Regards
Amos
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
--
Best regards,
Egor Zimin
--
Best regards,
Egor Zimin
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
