To me, the better part is to imagine that IPv6 only Link-Layer(on IXPs and
Transit providers) will make PMTUD better working.
Em ter., 23 de abr. de 2024 11:57, Ondrej Zajicek via Bird-users <
bird-users@network.cz> escreveu:
> On Fri, Apr 19, 2024 at 02:29:44PM -0500, Jay Hanke via Bird-users wr
On Fri, Apr 19, 2024 at 02:29:44PM -0500, Jay Hanke via Bird-users wrote:
> Has anyone implemented lab or production IPv4 next hops over an IPv6
> only IX vlan with BIRD as the route server?
>
> I'm interested to hear your experiences. Specifically router vendor interop.
Note that there is an Eur
Thank you!
> On Apr 23, 2024, at 10:28 AM, Tore Anderson wrote:
>
> * Chris Malayter
>> Probably better question. Is RFC5549 supported by BIRD?
>
> Yes, RFC 8950 is on the list of supported standards, and can be configured
> with the «[require] extended next hop» configuration option.
>
> h
* Chris Malayter
Probably better question. Is RFC5549 supported by BIRD?
Yes, RFC 8950 is on the list of supported standards, and can be
configured with the «[require] extended next hop» configuration option.
https://bird.network.cz/?get_doc&v=20&f=bird-6.html#ss6.4
No reason whatsoever th
Probably better question. Is RFC5549 supported by BIRD?
-Chris
> On Apr 23, 2024, at 9:59 AM, Jay Hanke via Bird-users
> wrote:
>
> On Tue, Apr 23, 2024 at 8:45 AM Darren O'Connor
> wrote:
>>
>> I have used rfc5549 extensively in production, but not with bird. Is that
>> the same setup yo
I mistyped. Should be IPv6 hops for IPv4 routes.
On Tue, Apr 23, 2024 at 9:10 AM Tore Anderson wrote:
>
> * Jay Hanke
>
> > I haven't, but I cannot begin to fathom how that could possibly work.
> >
> >
> > https://www.ietf.org/archive/id/draft-chroboczek-int-v4-via-v6-01.html
> >
> >
> >
* Jay Hanke
I haven't, but I cannot begin to fathom how that could possibly work.
https://www.ietf.org/archive/id/draft-chroboczek-int-v4-via-v6-01.html
How can the receiving router possibly resolve an IPv4 next-hop
address
to an destination Ethernet MAC address, if the inter
On Tue, Apr 23, 2024 at 8:45 AM Darren O'Connor
wrote:
>
> I have used rfc5549 extensively in production, but not with bird. Is that the
> same setup you're talking about here?
>
Yes. Are there any IXPs doing this right now with bird2?
Ciao Tore,
if I am not mistaken this is rather easy and "standard":
- Router knows a.b.c.d/x is supposed to be routed via 2001:db::1
- Router can lookup the mac address of 2001:db::1 (usual icmp6)
- Router sends packet for a.b.c.d/x towards mac address of 2001:db::1
That's it.
Cheers,
Nico
p
I have used rfc5549 extensively in production, but not with bird. Is that
the same setup you're talking about here?
On Tue, Apr 23, 2024, 09:31 Jay Hanke via Bird-users
wrote:
>
>
>> I haven't, but I cannot begin to fathom how that could possibly work.
>>
>
> https://www.ietf.org/archive/id/draf
>
> I haven't, but I cannot begin to fathom how that could possibly work.
>
https://www.ietf.org/archive/id/draft-chroboczek-int-v4-via-v6-01.html
> How can the receiving router possibly resolve an IPv4 next-hop address
> to an destination Ethernet MAC address, if the interface facing the IX
> d
* Jay Hanke
Has anyone implemented lab or production IPv4 next hops over an IPv6
only IX vlan with BIRD as the route server?
I'm interested to hear your experiences. Specifically router vendor interop.
I haven't, but I cannot begin to fathom how that could possibly work.
How can the receiving
Has anyone implemented lab or production IPv4 next hops over an IPv6
only IX vlan with BIRD as the route server?
I'm interested to hear your experiences. Specifically router vendor interop.
Jay
13 matches
Mail list logo
