Ad Schellevis
Ad Schellevis
`ipfw` is used on our end as well (for the traffic shaper), so that's a scenario we currently can't support without spending valuable resources better used elsewhere.
sounds logical, yes. we're trying to enforce consistency.
I can point you where to find the ipfw commands, but our situation is not going to change as it has impact on others and this simply isn't a supported...
I don't mind taking a look at https://github.com/opnsense/core/pull/7981/commits/de690719fb1314b55d2ca74adb3a91f417de7aea, but the other commit looks to convoluted to me. can you open a PR for the reverse dns part only?
Not likely before the login sequence is rewritten to MVC, one of the concerns with this approach is possible unintended information leakage, it's not a great idea to educate an...
We will likely implement the proper workflow in some future release, assigning this to myself in the meantime to make it clear that it is on the list, but without...
nothing to fix here, see also https://docs.opnsense.org/manual/firewall.html#processing-order for defined ordering.
If there's an issue with the context, we should fix that at the caller, this will be quite confusing and prone to future mistakes. (assuming we don't want to remove...
I agree the most logical place to handle the translations would indeed be the controller layer as we have all relevant context available there, in which case this would be...
@tobiasdegen we're a bit busy with the upcoming release and need time to discuss this internally. In the meantime we'll keep the PR open.