Relevant PR:
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Nov 11 2022
Nov 10 2022
Hmm, I can't seem to reproduce that name with "pdns-recursor/now 4.8.0~beta1-1pdns.bullseye amd64" or "pdns-recursor/now 4.8.0~beta2-1pdns.bullseye amd64" both in a live bare-metal system or in a VM. Both versions return pdns_recursor for me when printed from p.name(). The worker thread names (as listed from ps or htop) also don't match: "rec/web+stat" and "rec/taskThread", not that either of these are returned by p.name().
We use p.name from process_iter and it returns pdns-r/worker. That‘s why I have reverted the commits as in the latest 1.4 VyOS iso with PDNS 4.8 beta it‘s how they names the worker thread
Nov 9 2022
list/lists in config and op-mode now moved to external-list
task-scheduler logic was moved into vyos.task_scheduler so it can be imported properly and used by other modules
@c-po I noticed you've reverted the commit, may I ask how you're able to reproduce the process name of 'pdns-r/worker'? Just doing the testing again with the latest build as of writing (vyos-1.4-rolling-202211060813-amd64.iso), I get:
Nov 8 2022
In the PR it was requested to change the group category from lists to external-list which I'm fine with, but before I do the work to rename files and fields, does everyone agree with this change?
I've added PR https://github.com/vyos/vyos-1x/pull/1649 for review. Not tested yet, I want to know if I'm on the right path.
PR was added, I'm just trying to learn the documentation system now. Though to be frank documentation has never been my strong suit.
To be a PR, after discussion with @sdev :
https://github.com/vyos/vyos-1x/compare/current...jestabro:trace-migration
@v.huti Thanks for investigating and testing! How about you create a PR with the patch against 1.3 / equuleus ?
TLDR; confirmed fixed for 1.3, please backport.
FRRouting Release 8.4 Available for Download
November 7, 2022
One miracle at a time :)
Nov 7 2022
Hi @zsdc! This seems to be related to T4028. The relevant commits are:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓ commit 92980561382fc04380414a6e2f6ca6746c2fe5e9 ┃ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┻━━━━━━━━━━━━━━━━━━━━━━━━━ Author: Donald Sharp <[email protected]> Date: Mon Apr 19 19:23:45 2021 -0400
i see it like that
Nov 6 2022
re-signed crux repo
I'm not sure if wildcard-address fits. The address and the mask together combine to create the wildcard.
Nov 5 2022
Note: this requires https://phabricator.vyos.net/T4800 to be completed.
Well, after a better code reading, the var should be named chroot_includes_dir instead of includes_chroot_dir.
Thanks for catching this
Relevant PRs:
Nov 4 2022
Nov 3 2022
After a few hours of digging I do think this request would be very similar to geoip, only ipv4, and ipv6 groups would be required per list.
PR adds groups to NAT: https://github.com/vyos/vyos-1x/pull/1633
Reopened, as this was never backported to 1.3; set for 1.3.3.
I didn't look deep into the nft groups, so I wasn't sure if we could mix ipv4/6 and addresses and networks, if we can then I agree one group would be best, though I'm sure ipv4/6 would still need to separate but checking each line for : makes that task super easy and fast.
From my point of fiew, looks interesting.
The proposed structure and behaviour doesn't look that different than what is currently in geoip filtering: external URLs with data, and sync from time to time.