Ad Schellevis
Ad Schellevis
The new interface uses a larger queue underneath, which removes the need for very large tables (which will be extremely slow to render). I don't think we should do this,...
it shows 100 out of maximum 30k, filters can be used to limit the active set.
we'll keep it under consideration, when offering choices beyond the specification of the used components, it usually leads to complains from others at a later point in time. A bit...
The MSS clamping setting in the interface is a remnant from legacy choices I'm afraid, last time we touched that code we already made a note that it should be...
> However, in this particular case there are two separate problems, and one of them is on OPNsense itself: Well that depends on the rest of the configuration, mtu sizes...
bigger fish to fry, not a priority right now. In the long run we should likely replace the tokenizer, but I think I already explained that in your other ticket.
this is the tokenizer we use https://dragonofmercy.github.io/Tokenize2/
maybe some browser plugin? on my box it looks like
I don't see pull requests attached, only tickets, but no-pool is likely all you need to prevent a pool overlap, which is implemented in https://github.com/opnsense/core/pull/9025
to avoid complexity, we don't plan in offering mixed situations at the moment.