On 5/4/21 11:34 AM, Saku Ytti wrote:
On Tue, 4 May 2021 at 18:28, Adam Thompson wrote:
When I look at my IPv6 routing table, the next-hops are all... well...
gibberish, at least to me. My experience is that LLAs are not durable, so
memorizing them is not IMHO a useful task. Figuring out
On 5/4/21 21:07, Adam Thompson wrote:
LOLOLOL.
“%VXLAN-4-IPV6_UNDERLAY_UNSUPPORTED: VXLAN encapsulation using IPv6
VTEP addresses is not supported on this platform”
Guess it’s going to be a non-issue for me, at this time, since VxLAN
was the main reason for this entire setup…
Thanks
On Behalf Of Adam
Thompson
Sent: Tuesday, May 4, 2021 10:29 AM
To: Saku Ytti
Cc: nanog
Subject: Re: IS-IS and IPv6 LLA next-hop - just Arista, or everyone?
I don't believe APIPA and Link-Local are precisely equivalent, but I agree it's
the closest thing IPv4 has. IS-IS/IPv4 would presumably u
hey,
I did an L3VPN over SRv6 test recently using IS-IS as the IGP. I
thought it was quite cool that I didn't configure any IPv6 addressing
at all in the core... simply enabled v6 on interfaces and allowed
FE80 LL's to run... IS-IS neighbored up... then added a mp-ibgp v6
loopback (rfc 4193)
I did an L3VPN over SRv6 test recently using IS-IS as the IGP. I thought it
was quite cool that I didn't configure any IPv6 addressing at all in the
core... simply enabled v6 on interfaces and allowed FE80 LL's to run... IS-IS
neighbored up... then added a mp-ibgp v6 loopback (rfc 4193) to the
On 5/4/21 17:34, Saku Ytti wrote:
I don't think you are, I read like an opinion piece so it's inherently
not right or wrong. I don't have the same experience and I consider
forcing LLA a blessing in limiting attack vectors and I personally
don't see downsides as all addresses are gibbering
On Tue, 4 May 2021 at 18:28, Adam Thompson wrote:
> I don't believe APIPA and Link-Local are precisely equivalent, but I agree
> it's the closest thing IPv4 has. IS-IS/IPv4 would
Agreed, APIPA is using link-local, but they're not the same. APIPA is
an application or process which needs the
:athomp...@merlin.mb.ca>
www.merlin.mb.ca<http://www.merlin.mb.ca/>
From: Saku Ytti
Sent: May 4, 2021 10:20
To: Adam Thompson
Cc: Mark Tinka ; nanog
Subject: Re: IS-IS and IPv6 LLA next-hop - just Arista, or everyone?
On Tue, 4 May 2021 at 18:15, Adam Thompson
On Tue, 4 May 2021 at 18:15, Adam Thompson wrote:
Hey Adam,
> I don't see any rationale in RFC 5308 for why the HELLO packet may only
> contain the LLA - does anyone know/remember why? (I'm hoping that
> understanding the rationale will make this an easier pill to swallow.)
> Obviously
...@merlin.mb.ca<mailto:athomp...@merlin.mb.ca>
www.merlin.mb.ca<http://www.merlin.mb.ca/>
From: NANOG on behalf of Saku
Ytti
Sent: May 4, 2021 01:44
To: Mark Tinka
Cc: nanog list
Subject: Re: IS-IS and IPv6 LLA next-hop - just Arista, or everyone?
O
On Tue, 4 May 2021 at 07:24, Mark Tinka wrote:
> Junos:
>> 2c0f:feb0::1/128 *[IS-IS/18] 02:43:49, metric 5870
>to fe80::1205:caff:fe86:4ac3 via et-4/0/2.0
>to fe80::5287:89ff:fef3:25c3 via et-4/0/2.0
>to
On 5/4/21 03:28, Adam Thompson wrote:
Hey, just checking as I don’t have any Cisco or Extreme or Juniper
gear running IS-IS to verify myself…
On current Arista (7280SR2K) and older Brocade (MLXe) routers, the
IPv6 next-hop address in IS-IS seems to always be the link-local
address of the
Hey, just checking as I don’t have any Cisco or Extreme or Juniper gear running
IS-IS to verify myself…
On current Arista (7280SR2K) and older Brocade (MLXe) routers, the IPv6
next-hop address in IS-IS seems to always be the link-local address of the
neighbour, instead of any manually-assigned
13 matches
Mail list logo
