Query: All Stories

	Include stories about projects I am a member of.

This is causing smoketests on the nightly builds to fail

DEBUG - Traceback (most recent call last):
DEBUG -   File "/usr/libexec/vyos/conf_mode/nat66.py", line 127, in <module>
DEBUG -     generate(c)
DEBUG -   File "/usr/libexec/vyos/conf_mode/nat66.py", line 101, in generate
DEBUG -     render(nftables_nat66_config, 'firewall/nftables-nat66.j2', nat, permission=0o755)
DEBUG -   File "/usr/lib/python3/dist-packages/vyos/template.py", line 142, in render
DEBUG -     rendered = render_to_string(template, content, formater, location)
DEBUG -                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
DEBUG -   File "/usr/lib/python3/dist-packages/vyos/template.py", line 111, in render_to_string
DEBUG -     rendered = template.render(content)
DEBUG -                ^^^^^^^^^^^^^^^^^^^^^^^^
DEBUG -   File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 1301, in render
DEBUG -     self.environment.handle_exception()
DEBUG -   File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 936, in handle_exception
DEBUG -     raise rewrite_traceback_stack(source=source)
DEBUG -   File "/usr/share/vyos/templates/firewall/nftables-nat66.j2", line 28, in top-level template code
DEBUG -     {{ config | nat_rule(rule, 'source', ipv6=True) }}
DEBUG -     ^^^^^^^^^^^^^^^^^^^^^^^^^
DEBUG -   File "/usr/lib/python3/dist-packages/vyos/template.py", line 660, in nat_rule
DEBUG -     return parse_nat_rule(rule_conf, rule_id, nat_type, ipv6)
DEBUG -            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
DEBUG -   File "/usr/lib/python3/dist-packages/vyos/nat.py", line 58, in parse_nat_rule
DEBUG -     oiface = rule_conf['outbound_interface']['interface_group']
DEBUG -              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^
DEBUG - TypeError: string indices must be integers, not 'str'

Plenty of nat66 related errors from last nightly build:

exactly , i'll give an example of what is the improving (or new cli) , we have a policy where we can mach different DSCPs associate with REAL TIME or VIOCE . Current in our cli , it would be something like this :

Using VyOS 1.5-rolling-202310220123.

I think the commit made by yzguy is referencing the wrong task-id.

Checked in VyOS 1.4-rolling-202310030309

LEFT router configuration

So, do you want to add a new syntax to archive the same behavior that we have for qos policy ?

The global state-policy was dropped from CLI.
Close it for now.

this case was resolved lasted configuration done .

this task is a re-definition from a traffic class , I think it could be more clear if we separate tc-filter in a class-map , so we can define different profiles in our cli based on services :

1.5 should not have such issues.
1.4: op-mode should be working as expected. Backport for https://github.com/vyos/vyos-1x/pull/2344 failed. I'll submit PR for 1.4 for such feature.

Hi all, looks like that thanks to: https://github.com/acassen/keepalived/issues/2296, keepalived upstream repository fixed this issue with commit: https://github.com/acassen/keepalived/commit/81eb41fb12afe6ef56a6fd79cd4cb3cb5362c34b

I think we can do something similar to it : https://alestic.com/2018/12/aws-ssm-parameter-store-git-key/

various tracking (interface etc)

Hi all, sorry for joining an old conversation, but I think it is a bit confused here and looks like you are trying to work-around the VRRP protocol specification with the argument rfc3768_compatibility - but I'm note sure to understand such behavior and if it is the best way.

In T5673#162681, @Apachez wrote:

Should debug code really be part of production releases?

Wouldnt it be sufficient that you can enable this on your own if you want a debug build being made?

Should debug code really be part of production releases?

@rayzilt Could you re-check and close it if solved?

Could you try it locally and see what happens?

@Apachez I suppose it is.

biosdevname is called by scripts in the initrd, so we can't remove it just yet.
it's not completely abandoned and had quite a few releases since the point when Vyatta forked it.
I sent a PR to allow biosdevname to run in VMs (that's the only thing that vyatta-biosdevname has and that's used in scripts): https://github.com/dell/biosdevname/pull/12

All Stories
Use Results
Edit Query
Hide Query

Oct 25 2023

Oct 24 2023

Oct 23 2023

Oct 22 2023

Oct 21 2023