Retested with VyOS Stream 1.5-2025-Q2:
Ignoring invalid states for certain protocols was necessary to get most of the traffic working working again on bridges:
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Aug 8 2025
For the latest rolling seems fixed in T6371
vyos@r14# run show nat source rules
Rule Source Destination Proto Out-Int Translation
------ -------------- ----------------- ------- --------- -------------
230 192.168.0.0/16 192.168.0.5 UDP eth1 masquerade
sport any dport 60000-60010
[edit]
vyos@r14#Aug 7 2025
Additional details from Slack:
it is not only 1st run. He runs his playbook for 3 routers. Only one works without problems. He says that the configs are the same and the version is - 1.4.3.
Ansible verbose info
@a.apostoliuk hi!
Can we have:
Aug 6 2025
@josha I agree with you. Perhaps it should be like this?
In T7646#231844, @ryanzuwala wrote:Based on a recent Slack conversation we had about this, it seems like the most reasonable solution is to have configuration options like this:
- ipv6 address autoconf - accept RAs and do whatever M and O flags tell it to do
- ipv6 address dhcpv6 - DHCPv6 without RAs, must configure default route separately if needed
- ipv6 address dhcpv6 nd-defgtw - DCHPv6 without RAs, determine default route from neighbor discovery (possibly using the functionality in @josha script above)
- ipv6 address xx:xx:xx.... - Static IP
Based on a recent Slack conversation we had about this, it seems like the most reasonable solution is to have configuration options like this:
There are more fundamental problems here with the implementation that are incomplete.
This task can be closed. Initial implementation completed.
@ServerForge, let us know if you want to claim some tasks regarding bugs.
Thanks.
I have created 2 bug reports https://vyos.dev/T7690 and https://vyos.dev/T7691