Query: All Stories

	Include stories about projects I am a member of.

Initial draft; suggested changes and testing to follow:

In T3900#133375, @Viacheslav wrote:

Regarding interface groups it will be possible later, after firewall re-design

In case anyone comes across this bug report, I submitted a couple PRs to fix this earlier this year: https://phabricator.vyos.net/T4245

I've submitted a PR to reintroduce the patch: https://github.com/vyos/vyos-build/pull/259

@daryll-swer For your use case, you can use your tables/chains (not standard names like RAW/MANGLE INPUT/OUTPUT etc.), that won't be cleared by the VyOS firewall CLI

nft add table MYRAW
nft -- add chain ip MYRAW  my_chain '{ type filter hook prerouting priority raw; policy accept; }'
nft add rule ip MYRAW my_chain ip saddr 192.0.2.5 counter drop

In case of filtering on a VRF, would it be an idea to use the MAC address instead of the interface name in the rule?

Has there been any updates on this? @Viacheslav, it would be great to have this functionality on VyOS.

An example of dict that we can use

{
    "images": {
        "rolling": {
            "latest": {
                "arch": "amd64",
                "flavors": ["azure"],
                "image": "vyos-rolling-latest.iso",
                "latest": True,
                "lts": False,
                "release_date": "2022-09-02",
                "release_train": "sagitta",
                "version": "1.4-rolling-202209020217"
            },
            "1.4-rolling-202209020217": {
                "arch": "amd64",
                "flavors": ["generic"],
                "image": "vyos-1.4-rolling-202209020217-amd64.iso",
                "latest": True,
                "lts": False,
                "release_date": "2022-09-02",
                "release_train": "sagitta",
                "version": "1.4-rolling-202209020217"
            },
            "1.4-rolling-202208291850": {
                "arch": "amd64",
                "flavors": ["openstack"],
                "image": "vyos-1.4-rolling-202208291850-amd64.iso",
                "latest": False,
                "lts": False,
                "release_date": "2022-08-29",
                "release_train": "sagitta",
                "version": "1.4-rolling-20220829850"
            }
        },
        "lts": {
            "latest": {
                "arch": "amd64",
                "flavors": ["generic"],
                "image": "vyos-1.3-x.iso",
                "latest": True,
                "lts": True,
                "release_date": "2022-xx-xx",
                "release_train": "equuleus",
                "version": "1.3-stable-202208230511"
            }
        }
    }
}

I will modify the docs.

Could be a part of T4118

1.3 is not affected by this bug

This will be resolved by the PR in T4664.

I do see I need to update the docs. Will do if this change is going to be merged.

Need an advice guys, how we can reproduce the problem. I tried to peer with bird and announced 100k prefixes to the vyos box, but this simple config did not cause memory leak with bgpd. Still trying

I also notice looking at the backup after another reboot:

I hate to drag up an old ticket, but I've just encountered this issue.
A freshly built VyOS 1.3-rolling-202209010158

A similar task T3541 I'll leave a link here

Maybe I'm wrong, I see it as some small API (on some hosts) without links to the images but with information about images (in JSON).
We compare our local VyOS version and the version that we get from API, if diff => true send a message to the "wall"

Smoketest can't pass policy route
Fix https://github.com/vyos/vyos-1x/pull/1512

All Stories
Use Results
Edit Query
Hide Query

Sep 3 2022

Sep 2 2022

Sep 1 2022

Aug 31 2022

Aug 30 2022