Yes, thank you.

@jestabro , I don't have access to that file anymore, I have already reconfigured the router,

@pieteras.meyer , while I investigate a related issue, could you share the version before and after you attempted the failed upgrade, and the version string at the bottom of the config file in the before version ? Thanks.

Given that your current version is 1.4 20210504, this will be the next nightly, though it may be critical enough to build a rolling release now, in which case a few hours.

Okay thanks, which rolling release can I used that does not contain this bug?

Yes, this is an identified bug, thanks to your report:

Config in FRR is missing config from VyOS like route-maps

Below is config commands from before the upgrade

My understanding of the requirement would be, say, T3758 in the case of op-mode. I consider this to require the refinement of op-mode firstly, as one wants per-command authorization.

op-mode endpoints for 'show', 'generate', 'image' have been a part of the REST API for a while, as I'm sure you are aware (just to be clear):

In T1610#110278, @jestabro wrote:

@adestis there were discussions on this in the past week --- I will be helping @dmbaturin with the task

After some testing in regex101, it seems like a good replacement regex would be ^(http:\/\/|https:\/\/)?[a-z0-9]+(?:[\-\.]{1}[a-z0-9]+)*(\/.*)?$ but I'm not well versed enough to build an image off of my own branch to test that, and I can't figure out how to modify the installed version to use the new regex to test.

I very much like this idea.

Ok, thanks for the clarification.
I'm closing this task and marking it as resolved.

I've been testing , now we are able to configure BMP with load configuration .in latest version 8.2.2(they solved these issues)

Yes it is, although PR https://github.com/vyos/vyos-vm-images/pull/25 then caused some new issues but I just now reported those in T4278

@higebu it looks like PR https://github.com/vyos/vyos-vm-images/pull/25 caused some new issues (I use the qemu.yaml build). First:

fatal: [localhost]: FAILED! => {"changed": false, "msg": "AnsibleUndefinedVariable: 'enable_dhcp' is undefined"}

I propose to use this in the template (same for enable_ssh):

{% if enable_dhcp | default(True) %}

Or alternatively define those variables in all playbooks.

Sure, but its not being applied in the pdns recursor so I cant use static host mapping for ipv6 in my network, only locally on the vyos host. (It works fine with ipv4).

@hakwerk . Is this solved in PR https://github.com/vyos/vyos-vm-images/pull/24 ??

Splitting ipv4 files, and just adding what needed. In my case, I extracted content from geoip-ipv4.nft and create and include file geoip-CA-ipv4.nft (Canada IPs)

Perhaps only in-use sets can be determined and loaded?

After some custom build and POC, here's what I got:

• Filtering works, as shown in this table:

@SrividyaA Thanks !!!!