IPoE server was rewritten to get_config_dict
The original bug was solved

@FileGo Could you re-check it with 1.4-rc3 or the latest rolling?
Not sure that we can fix anything in this specific case.

Close it as invalid; there are no responses from the author.
Feel free to reopen it if you still have this issue. We need more details, dumps, and probably the whole configuration for debugging.

No responses from the author
I closed the task because we do not have other issues like this.
Feel free to reopen if it is required.

@dberlin Can you recheck?

@JonD Have you figured out what the problem is?

@pjeevarathinam Could you re-check wiht 1.4-rc3 or the latest rolling?
You can play with descriptions

vyos@r4# set system frr descriptors 
Possible completions:
   <1024-8192>          Number of file descriptors

I believe it was an issue with my DNS server. Nevertheless, the issue cannot be reproduced so the bug report can be closed.

@c-po in task T4797 (https://github.com/vyos/vyos-1x/pull/1648) you mentioned that the author should use the system task-scheduler feature.
I would understand this the same way as the author did:
The implementation of scheduling should be a module which could be reused by other features/extensions but the "cron" data should be stored separate from
what the user can schedule via the config.
But maybe you see it differently?

Honestly? Rather not. Even though i have been testing this extensively, there needs to be some discussion re: old-config-impact (+some testing); Similarly, _ideally_ this would not just go for standard python regex, but instead try to figure out what frr _acutally_ uses. So, while a poc, i think this needs a bit more work.

@tfiebig Could you add a PR?

@Apachez I would need this feature in another feature (https://vyos.dev/T6040) to avoid a double implementation.

PR https://github.com/vyos/vyos-1x/pull/3000

@greywolfe Any update?

@svd135 Can you recheck?

@twan Could you try with the 1.4-rc3 image?

@dcplaya provide the whole configuration to reproduce or close the task if the reason is firewall incorrect configuration.

PR https://github.com/vyos/vyos-1x/pull/2999

PR: https://github.com/vyos/vyos-1x/pull/2998

Not an issue on 1.5 with Kea.

PR: https://github.com/vyos/vyos-1x/pull/2997

This turns out to be non-trivial, due to the interaction between legacy and modern behavior; nonetheless, a simple preliminary fix is in testing, and the task will be updated with the details when the PR is complete.

https://github.com/vyos/vyos-1x/pull/2987

This does seem to be new behaviour introduced with Kea. ISC dhcpd did previously assume local distribution of a subnet based on the interface having an address within the subnet, Kea has changed to require this being explicitly defined.

PR: https://github.com/vyos/vyos-1x/pull/2993

I'm thinking end of the day an integrated learn address script that can update vyos's forwarder or any of the upstream DNS its using, and then calling learn-address on each client learned in the openvpn is the ideal way to do it since learn-address is built into openvpn

Here is a redacted version