I would still recommend you to try to test to put a L2-switch between your 5G-router and the VyOS box and see if that resolves the situation.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Oct 27 2023
One way however to make the variable more robust in case there are for whatever reason more than one squashfs mounted object available is to select the one who is "loop0".
Looking through https://vyos.dev/T5457 I now get what you meant by "re-broke it".
Nope, it works fine, now; your revision to the change re-broke it.
https://github.com/vyos/vyos-build/pull/441 PR has been created
Does your 5G-modem do any NAT on its own or does it just forward the DHCP to the ISP?
So in short https://vyos.dev/T5440 will be broken again?
Does your 5G-modem do any NAT on its own or does it just forward the DHCP to the ISP?
Oct 26 2023
Could also be if legacy spanning-tree is being used that it will take approx 25 seconds before packets are being forwarded after a linkdown - workaround here is to enable "spanning-tree portfast" or disable spanning-tree.
Yes, it does. thank you
@SrividyaA Can you confirm this is working as you expect?
This error was already fixed in https://github.com/vyos/vyos-1x/pull/2406
@jvoss thanks to confirm !
PR for op-mode command that fits new cli: https://github.com/vyos/vyos-1x/pull/2408
Oct 25 2023
To verify that it isnt something in your 5G modem that triggers this behaviour try to put a L2-switch in between and then simulate a link failure between VyOS and this L2-switch and see how things behaves?
PR for 1.3 https://github.com/vyos/vyos-1x/pull/2402
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:
Oct 24 2023
Using VyOS 1.5-rolling-202310220123.
I think the commit made by yzguy is referencing the wrong task-id.
Oct 23 2023
For RQ for Sagitta: https://github.com/vyos/vyos-1x/pull/2399
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.
Oct 22 2023
I think we can do something similar to it : https://alestic.com/2018/12/aws-ssm-parameter-store-git-key/
various tracking (interface etc)
Oct 21 2023
Could you try it locally and see what happens?
- 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
vni100 should be the bridge slave here.
So those options could be in the same level of "allowed-vlan" and "native-vlan"