More info: Maybe VyOS being affected by https://github.com/FRRouting/frr/issues/18537 ?
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Apr 30 2025
The simplest—and perhaps most crude—way to accomplish this may be to restart the vyos-domain-resolver service. This will automatically update the FQDN cache, remote groups, and restart the timer for regular pull intervals.
Same stuff see screenshoot:
Deploy a new VM with 1.4.2 copy configuration to the /config/config.boot (remove HW-id's), and reboot the router or execute load
In T5493#222634, @adestis wrote:You are right, when a correct "base" address for the prefix is used.
If not the prefix is silently discarded (192.0.0.0/24 vs. 192.0.0.8/24).
I am ok with it. Just important for documentation.
Generated rules:
vyos@r14# cat /run/nftables-ct.conf #!/usr/sbin/nft -f
In short, setting listen-address requires an explicit 'systemctl restart nginx' instead of the existing 'systemctl reload-or-restart nginx'; a workaround before merge of the PR is to call the restart.
Apr 29 2025
I've issued a PR for this at https://github.com/vyos/vyos-1x/pull/4482, attempting to address a few things T5816 missed.
PR
https://github.com/vyos/vyos-http-api-tools/pull/22
Opt to upgrade h11 package version only; cf. comments there.
Apr 28 2025
I'm close to having a PR ready for this. I'm finishing up all the smoketests and then will be ready to PR.
Adding a simple condition seems to do the work:
@AlexFT Could you recheck the latest rolling to confirm that all works as expected?
You are right, when a correct "base" address for the prefix is used.
If not the prefix is silently discarded (192.0.0.0/24 vs. 192.0.0.8/24).
I am ok with it. Just important for documentation.
In T5493#222631, @adestis wrote:@Embezzle you are only supporting IP addresses but no prefixes as 192.0.0.8/24 ?
Do you have plans to also support networks/prefixes?
A lot of the original proposed features would be left aside if the implementation would stop here.
Or maybe I am the only one complaining here.
@Embezzle you are only supporting IP addresses but no prefixes as 192.0.0.8/24 ?
Do you have plans to also support networks/prefixes?
We tested the solution implemented by @Embezzle and it seems to work.
Apr 27 2025
@canoziia Yes you can close, I marked as resolved this time, thanks!
Thanks :) I saw it in the commit notes, they must not be working correctly still :(
Should I close this task?
In T7394#222617, @curtdept wrote:Still happening somewhere
{F14387702}
Still happening somewhere