Yes, I agree with that, readability will be better if everything is in order.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Jan 9 2024
I suggest changing order just as a cosmetic fix: feels more reasonable/readable to parse first "incoming", and then "outgoing"
@n.fort
Looks like 1) and 2) is correct, as well as 'Action=accept in vyos command shall remain as accept in nftables'.
However, the 3) is not obvious to me. As long as all rules with Action=Accept in both IN and OUT chains will migrate to Action=return, looks like there should be no difference in order, other than probably for performance reason.
I stopped using conntrack-sync before I moved to 1.3 (which I am currently running) so I can't confirm either way.
I expect it's no longer an issue though and this task can be closed.
Should be a non-issue with the new firewall implementation.
Changes that seems to be needed only in migration script https://github.com/vyos/vyos-1x/blob/current/src/migration-scripts/firewall/10-to-11:
- Use accept action for base-chains (it's done, no change needed here).
- Migrate action=accept to action=return on every rule.
- fix order and ensure all "in" rules are applied first.
vyos-vm-images will soon be phased out completely.
This issue is on and off, but mostly solved now.
This needs to be properly worded as a feature request, if it's still relevant with the new firewall implementation.
No longer reproducible in 1.5
The CLI prevents that now.
Someone needs to test it on a system with a real wireless NIC.
The script was rewritten and adds all servers now.
I presume it's no longer an issue, but I'd like to confirm.
No longer reproducible, the underscore is displayed as expected.
If any new information turns up, feel free to reopen.
The PR was rejected.
I suppose we need a clearer idea of what we do with sysctl values.
Crux is unsupported now.
The original syntax is now allowed anymore.
Should be easy to do now that ipaddrcheck supports range validation.