I was able to fix by adding the following code in /config/scripts/vyos-postconfig-bootup.script you can edit and save by running:

I can confirm that the issue is still here, something is wrong and usually when you assign ipv6 address to sub-interface like vlan or bridge etc.

How is your IPv6 config from the VyOS config?

Enabled inside VyOS kernel - please check with the next available rolling ISO

1. Vyos Router <-> Switch <-> Multiple Computers

A workaround in the meantime:

And in that case the attacker would just replace your router with their own since they already got physical access to the box.

There are use cases when it would be ideal to force a password at boot to protect the contents of the configuration. For example, a portable router with sensitive keys meant for temporary network connectivity.

The problem is how to make sure that the router can boot and reboot (for example "set system option reboot-on-panic" is handy) on itself without somebody having to connect to its console before it starts to function again. Really shitty situation for a remote site because then somebody needs to visit it aswell.

1. How is the physical topology (can you provide a drawing)?

I am having this exact problem and it evidently has been a problem for quite a few years.

Can this be accomplished with LUKS?

That CLI node ipv6 only implements a minor subset of the entire featureset of port forwarding.

Adding comments : maybe discontinue show ip bgp gives some issues / problems with automation tools (ansible o some custom script)While thinking out loud, it can be useful for new users create to alias.

Its not possible to "symlink" it?

Unfortunately this is "not that easy" as out CLI commands are passed down to FRR raw.

But at the same time it would help others who migrate to VyOS from Cisco, Arista etc.

show ip bgp is an old command, it comes from quagga ...So in my point of view , adding more command to do the same , could generate more confusion . show bgp address-family should be used.

PR created: https://github.com/vyos/vyatta-op/pull/66

Its good for traceability to get a snmp trap sent when the firewall config has been altered/changed/(re-)applied.

Yeah, no worries.

Im biased but here are my testresults using modified VyOS 1.4-rolling-202308060317:

@Apachez thank you for your response 🙏
Sorry, I really have attached screenshots but didn't grant access to them. Fixed.

Some internal test where done, using integration between:

• Traffic shaper. Currently supported in vyos cli
• Bridge firewall. Currently not supported in vyos cli.

According to https://www.kernel.org/doc/html/v6.1/admin-guide/serial-console.html

There were no screenshots included with this task?

PR created: https://github.com/vyos/vyatta-op/pull/65

It seems to exist for current Debian 12.1 (bookworm) so I think it should be a relativily simple task to add that if not already existing:

Sounds almost related to this longrunning shitshow between FRR and the Linux kernel:

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

I admit my setup isn't really the most common for production, but for the home lab crowd it might be ok. Realtek makes many network chip models I assume and their implementation might also vary from board manufacturer to another.
About not using VMware - that's a tougher ask :)

As stated, building libvyosconfig outside of the Docker image may not be desirable. However, as a compromise solution, we can consider moving the vyos1x-config pin/build into the libvyosconfig build script. Suggested PR to follow, and update to task description.