Correction to the steps required to support ALL kea options programatically- it may need to be more like this:

As a note for myself and any other users not familiar with the project who need to perform a task like this in the feature, a few notes on changes needed based on a quick survey:

In T7723#232731, @Viacheslav wrote:

You need to add changes only in the vyos-1x repo

You need to add changes only in the vyos-1x repo

I would like to send a PR for this if I have time as it seems like a relatively good first issue to work on.

Pardon my typo in the notes, the correct option number is 26 as in the title of the issue

To clarify, I’m only asking that this option can be set to an integer. It would be neat to be able to instruct it to set the option to a value dynamically, deriving it from a specified interface, but that’s a lot more effort and probably rarely worth it

Let's check if nftables improved that. Either we can do it easily now, or we'll close this as wontfix, if Linux just doesn't implement feasible RPF as per the RFC.

the ticket is closed, and

ssh vyos@vyos -- /opt/vyatta/bin/vyatta-op-cmd-wrapper show interfaces

Also I realized, that the insert_failed and drop counters of conntrack are increasing:

I forgot to mention, that deleting the vrf_zones table "fixes" the issue.

Hi! I think I am hitting a similar/the same bug with a very minimal configuration.

https://github.com/vyos/vyos-vpp/pull/54

Tried to fix here: https://github.com/vyos/vyos-1x/pull/4616

Fixed in FRR master: https://github.com/FRRouting/frr/pull/17544

this is already supported by FRR and already used by VyOS, but not in this behavior. If you create an 2nd VRF and use dynamic routing protocols, you create in frr multiple processes of that routing protocol you use. OSPF and BGP in frr support multiple processes out of the box.

https://github.com/vyos/efi-boot-shim

Does it supported by FRR?

Sorry, wasn't on regular computer when I filed. Just wanted to get it put in.

@giga1699, Can you add steps or a set/seq of commands to reproduce?

@SrividyaA 1.5 and 1.4 use completely different DHCP server implementations so this task cannot possibly be relevant for both (even if they have a similar-looking issue, it will need completely different fixes).

We need a precise spec for it, what's required to support it. We also need a testing environment. I do think it would be nice to support it, but I wonder if it would bring many new customers.

@Viacheslav https://github.com/VyOS-Networks/vyos-1x/pull/891

In T6909#228780, @Viacheslav wrote:

@natali-rs1985 Can you create a backport to circinus?

@natali-rs1985 Can you create a backport to circinus?

PR https://github.com/vyos/vyos-build/pull/948