- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
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
Apr 26 2025
@dmbaturin is this what you had in mind?
Apr 25 2025
@a.apostoliuk @sarthurdev I saw this a while back and was thinking about it today. I think it'd be useful to be able to disable conntrack per chain. It could be useful for people using VyOS in an ISP environment, where the firewall is more a mechanism to secure VyOS itself, rather than filter through traffic. It'd be pretty easy to implement.