How to choose IPv6 addresses for customer links?

Dan White dwhite at
Mon Feb 2 04:51:11 CET 2009

Steve Bertrand wrote:
> ...and, if you assign a /64 global between eBGP peers (as opposed to
> anything longer), BGP will automagically configure the next-hop to the
> link-local:
> B>* 2001:478:235::/48 [20/0] via fe80::d8ea:2f09, gif1, 06:07:43
> opposed to this route, where a /128 global PtP is in place:
> B>* 2001:478:178::/48 [20/0] via 2001:4978:1:600::1, gif0, 06:08:14
> What I haven't tested, but plan on doing so, is whether my theory that
> moving the IPv6 peering address from one source interface to another
> will not disrupt this link-local next-hop.
> You (Dan) are going to like BGP. I have had much fortune finding people
> to help me out with it, particularly in the v6 context. If you ever need
> any help testing a setup in the global context, email me off-list. So
> long as it's low-bandwidth, I'll do anything I can to pass along
> knowledge I've gained from others (including sessions (non-transit),
> VMs, test routers etc). When I help others learn, I'm either reinforcing
> knowledge, or having to research the unknown.

Thanks Steve, I appreciate all the pointers in the right direction.

What is the benefit of using BGP in a scenario like this (ethernet link 
to customer)? Would OSPF6 or RIPNG make more sense since shouldn't need 
to know their address?

- Dan

More information about the ipv6-ops mailing list