[j-nsp] IPv6 link-local addresses

[Harry Reynolds]

Just reassign a new LL of your choosing:

<<< auto-generated:

[edit interfaces t1-0/0/2]
lab at Bock# run show interfaces t1-0/0/2 | match fe80 
        Destination: fe80::/64, Local: fe80::212:1eff:fe7c:9b80

[edit interfaces t1-0/0/2]
lab at Bock# set unit 0 family inet6 address fe80::1111:1111:1111:1111/64 

[edit interfaces t1-0/0/2]
lab at Bock# commit 
commit complete

[edit interfaces t1-0/0/2]
lab at Bock# run show interfaces t1-0/0/2 | match fe80

        Destination: fe80::/64, Local: fe80::1111:1111:1111:1111

 HTHs


> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net 
> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Eric Van Tol
> Sent: Tuesday, September 18, 2007 2:47 PM
> To: juniper-nsp at puck.nether.net
> Subject: [j-nsp] IPv6 link-local addresses
> 
> Hi,
> Is there a way to manually set the link local address of an 
> interface in 8.x?  I am running into a problem where I have 
> T1 interfaces connected through a CT3 and they both have the 
> same link local address.  This is a back-to-back CT3 using 
> logical-routers:
> 
> admin at m20-re0# run show interfaces t1-0/1/0:0 | match fe80     
>         Destination: fe80::/64, Local: fe80::2a0:a5ff:fe28:f
> 
> [edit]
> admin at m20-re0# run show interfaces t1-0/1/1:0 | match fe80    
>         Destination: fe80::/64, Local: fe80::2a0:a5ff:fe28:f
> 
> The intended result is to have different addresses so my 
> OSPF3 adjacencies can come up:
> 
> Sep 18 21:34:49.963624 OSPF packet ignored: Our interface 
> address is source address fe80::2a0:a5ff:fe28:f
> 
> I've attempted to use the 'preferred' keyword on the v6 
> address, but that didn't work.
> 
> Any insight would be appreciated.
> 
> Thanks,
> eric
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net 
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>