Related bug with migration https://vyos.dev/T5721
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Dec 11 2023
Change has been merged in
Dec 10 2023
Implement FRR features for SRv6
@Viacheslav I updated to the latest rolling version (VyOS 1.5-rolling-202312080024) in thr issue still persists but the error message ist different:
Dec 9 2023
@giga1699 could you re-check?
Can we close it?
I have tried to migrate to one of the last nightlies and now the situation is much better: vyos reboots, does not hang and I can ssh.
There is still an error in the migration script:
PR for 1.4 https://github.com/vyos/vyos-1x/pull/2599
@I-n-d-y Could you re-check?
Opened issue https://github.com/FRRouting/frr/issues/14924
There is no section address now
VyOS 1.5-rolling-202312070905
vyos@r4# set service dns dynamic Possible completions: interval Interval in seconds to wait between Dynamic DNS updates (default: 300) +> name Dynamic DNS configuration vrf VRF instance name
Duplicate
I have create a PR for backporting this to 1.4 : https://github.com/vyos/vyos-1x/pull/2597
Just so I understand you correctly, you mean:
Dec 8 2023
Details in the PR https://github.com/vyos/vyos-1x/pull/1516
@n.fort I have a branch with a backport of this for 1.4 (needs manual changes).
Or you can use PBR for destination/source address /port/protocol
PR https://github.com/vyos/vyos-1x/pull/2590
set load-balancing reverse-proxy service web mode http set load-balancing reverse-proxy service web port 443 set load-balancing reverse-proxy service web ssl certificate cert set load-balancing reverse-proxy service web ssl certificate client1 set load-balancing reverse-proxy backend bk01 server srv01 address 192.0.2.1 set load-balancing reverse-proxy backend bk01 server srv01 port 9898
I've just tested the "protocols failover" function in the 1.4-rolling-202311021324 - it works well!
Dec 7 2023
Could you create a PR?
Now we receive this error in 1.5-rolling-202312060024 when the command is executed:
Dec 6 2023
Per discussion on forums (https://forum.vyos.io/t/how-to-use-flowtables-in-vyos-1-4-with-zone-based-firewall/13004/4), custom chains do not currently have the ability to set offload as an action. The action is only able to be applied directly within the forward filter.
In the past any interface was supported, and it has been removed.
If you want to match any interface, you can complete remove interface matcher from the rule, since it's not mandatory (as it was in the past):
delete nat source rule 110 outbound-interface