Messages

Well, the right way would be to add a user with limited privileges. Admin + exclusions are not possible. I know that's a churn for "almost everything", but that's also not a typical use case.

You can also remove pages from the menu for everyone via adding menu override files, but the URLs are still accessible manually so only do this if you're not trying to improve security.


Cheers,
Franco

> I think its irresponsible for OPNsense to expect us to not provide a direct iso link

I think it irresponsible to ask for direct bandwidth for uncompressed ISOs that are going to be abused by every cloud provider out there offering a "show me an iso and I'll boot your VM".

You'd think someone would be smart enough to allow decompression in their infinite wisdom. But I'm sure they know how not to support mirror maintainers at all. So a compressed iso is the best we've all got and can offer.  :D


Cheers,
Franco

Hi,

It could be related to .10 but not the ticket.  Unsure how to debug this, but you can use

# opnsense-revert -r 25.7.9 opnsense

and a reboot to confirm that is the actual issue or not.


Cheers,
Franco

This was fixed in https://github.com/opnsense/core/commit/7192016ac9

Thanks for the report!


Cheers,
Franco

> Just following up that I still see a memory leak in dnsmasq even after a reboot and an update to 25.7.10.

I don't think it's surprising given the fact that the binary did not change.


Cheers,
Franco

> Nonetheless... that person is a troll. Floodding the forum with bullshit bingo, which potentially harm others.

Yeah, trolling back is not a great plan.

Just report the thread(s) and we'll deal with it.


Cheers,
Franco

@fastboot you posted this 3 times. If I see another one you get a temp ban because this is will be considered spam.


Cheers,
Franco

This is a known issue on LTE connections.


Cheers,
Franco

You'll need to be a lot more specific please.


Cheers,
Franco

On ixl cards? Intel probably just broke it again after I had to advocate for a revert when the first commit came in.

https://github.com/opnsense/src/commit/aa1fce8528200

Good luck with that.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283820


Cheers,
Franco

Yes, years ago.


Cheers,
Franco

"force down" isn't about fbsd at all, it's a sense thing that came to be with the gateway monitoring and is effectively labelled incorrectly. It's more of a "do not use for automation" flag with the twist that it blanks the status for the gateway. Won't be easy to clean this up.  ;)


Cheers,
Franco

> I have the same problem

I don't?  :)

If you're not using static ARP and the neighbor is found via ARP it's not going anywhere.


Cheers,
Franco

If you have a concept for it you can open a ticket and see.

For now I noted your wish, but would like to hear from others in unrelated topics, too. So far this is the only one I've heard.


Cheers,
Franco