Ondrej Zajicek writes:
>> I was facing the same issue before, and unfortunately, RFC 5838
>> explicitly forbids IPv4 over IPv6 for OSPF.
>
> Well, we could add 'extended next hop' option to override it, even if it
> would be non-standard. It is rather small deviation.
That would be amazing.
On Tue, Jan 30, 2024 at 12:20:41PM +0100, Sebastian Hahn wrote:
> Hi Nico,
>
> > On 30. Jan 2024, at 10:32, Nico Schottelius via Bird-users
> > wrote:
> > OSPFv3 works fine on IPv6 and when creating two instances, one for IPv6
> > one for IPv4, things look correct. But how does OSFPv3
> As an alternative suggestion, I have since evaluated babel which mostly
> suits my purposes (except for some features not yet implemented in bird,
> like strict bind)
Could you please explain what's the feature you're missing?
Thanks,
-- Juliusz
> On 30. Jan 2024, at 14:09, Juliusz Chroboczek wrote:
>
>> As an alternative suggestion, I have since evaluated babel which mostly
>> suits my purposes (except for some features not yet implemented in bird,
>> like strict bind)
>
> Could you please explain what's the feature you're missing?
Good morning,
if we are talking about BGP, IPv4 routing over IPv6 works
beautifully. We just add another IPv4 channel and get BGP MP.
OSPFv3 works fine on IPv6 and when creating two instances, one for IPv6
one for IPv4, things look correct. But how does OSFPv3 conceptually work
if the
Hi Nico,
> On 30. Jan 2024, at 10:32, Nico Schottelius via Bird-users
> wrote:
> OSPFv3 works fine on IPv6 and when creating two instances, one for IPv6
> one for IPv4, things look correct. But how does OSFPv3 conceptually work
> if the interface of the ospf area do not have IPv4 addresses
On 30.01.24 10:32, Nico Schottelius via Bird-users wrote:
>
> Good morning,
>
> if we are talking about BGP, IPv4 routing over IPv6 works
> beautifully. We just add another IPv4 channel and get BGP MP.
>
> OSPFv3 works fine on IPv6 and when creating two instances, one for IPv6
> one for IPv4,
