ipv6 next-hop link-local
Gert Doering
gert at space.net
Sat Feb 19 16:37:10 CET 2011
Hi,
On Sat, Feb 19, 2011 at 03:00:41PM +0100, Francis Dupont wrote:
> In your previous mail you wrote:
>
> Is *anyone* running eBGP on link-locals?
>
> => note this is explicitely forbidden by RFC 2545 which
> is about eBGP on globals with in a particular case an
> added link-locals (because there is no standardized or
> reliable way to deduce a link-local from a global).
[..]
> PS: I read 'link-locals' as 'link-locals only' but
> IMHO it is the intended meaning.
I was thinking of actually having the TCP endpoints on link-local
addresses, as in
router bgp 1234
neighbour fe80::43:21 remote-as 4321 outgoing-interface gige 3/5"
or something like that (however it might be configured).
In that case, indeed, you wouldn't have a global next-hop to send
in the update message.
Gert Doering
-- NetMaster
--
did you enable IPv6 on something today...?
SpaceNet AG Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444 USt-IdNr.: DE813185279
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 306 bytes
Desc: not available
URL: <https://lists.cluenet.de/pipermail/ipv6-ops/attachments/20110219/09cbae17/attachment.sig>
More information about the ipv6-ops
mailing list