Messages

@ffsb42 new link should be https://docs.opnsense.org/development/examples/helloworld.html , I've changed it accordingly, thanks for the ping.

I must say it looks beautiful, compliments the new GUI for OPNsense. As well that logo for D and O, indeed a pair made in heaven.

Thanks, new style is finished, but it will take quite some time before being implemented at other places as well.

Just curious, same dev for the new Web as for the GUI? ;)

nope, first project for new firm.

Also I am curious about the rack classed devices, in those you use air tunnels, do you have somewhere results or do you know what is the temp with and without them?

I know we measure them, in some cases even simulate upfront, but the exact difference I don't know (not my department ;))

Best regards,

Ad

We just redesigned our webshop with a clearer focus on the endproduct and our engineering efforts (https://www.deciso.com/showcase/).

Nothing changes, we still design our own hardware (and software 🙃), a clearer message helps people normally acquiring one of the larger vendors to compare our offering with theirs.
This includes explaining people what it can do rather than what's exactly being used inside.


Best regards,

Ad

Hi Mark,

By default traffic is (only) filtered on enc0, but when only using VTI tunnels, it's also possible to filter on these interfaces as described in the notes here https://docs.opnsense.org/manual/vpnet.html#route-based-vti

Best regards,

Ad

Hi,

You're probably looking for this https://docs.opnsense.org/manual/how-tos/ipsec-s2s-conn-binat.html , should be the same example as the legacy one, but for the new connections.

Just make sure to choose a unique reqid, certainly when legacy tunnels on the same machine exists (to prevent overlaps)

Best regards,

Ad

Would be nice to get the 5 failure points fixed/implemened and maybe also the addition 3 points sometime in future when possible.

Secure defaults you mean, see also the notes in passing and reusing headers in https://httpd.apache.org/docs/2.4/mod/mod_proxy.html

I don't mind if you would like to add some advanced toggles to deviate from these defaults, just open a ticket in https://github.com/opnsense/plugins (although these plugins don't live there, in terms of workload planning I rather have some ticket).

When opening a ticket, make sure to use our template and be exact in which options you would like to see and for which reason.

Best regards,

Ad

Maybe an email got lost somewhere, can you send a mail to support at opnsense dot com so I can check internally. Sending a payment link after you placed an order can't be an issue.

Best regards,

Ad

If you requested additional information and didn't hear back yet, best drop another mail. Ordering licenses can't be very slow, the shopping/delivery process is fully automated on our end (https://shop.opnsense.com/product/opnsense-business-edition/)

Best regards,

Ad

We're still on track,  the release should be available on the 30th of April.

Best regards,

Ad

I'm not aware of a way to identify the files that aren't needed, from python's perspective there is no register.

The most logical check would be a diff between this directory and the files registered in `pkg list`. Files not registered via pkg usually don't belong as we only use the package manager to install software.

I am still a bit lost on why this operates differently from within unbound, but glad this worked for you.

At least we know where to look next time, a structural fix is likely more difficult as we don't know when this got stuck, pkg should have removed the old one with the upgrade (likely some time ago).

Thanks for reporting back,

Best regards,

Ad

ok, very weird, it looks like this only happens inside the chroot environment for unbound in that case.
Can you run the following for me and report back the output?

Code Select Expand


find /var/unbound/usr/local/lib/python3.9 -name "*idna*"


If its something on the dashboard polling, the backend log (in debug) combined with this system log might be useful to track calls and times.

Most commands are detached using configd, which logs the actions performed. 

None of these messages have anything todo with the dashboard, dhclient not being able to obtain an address is one, the other ones relate to unbound (many from rc.bootup, which indicates either a reboot loop or something weird).

Maybe unbound couldn't start and tries to unmount the /var/unbound/lib directory anyway? But hard to tell with the data offered.

Best regards,

Ad

but on these machines (after reinstalling the package), is unbound still crashing if you stop/start it from gui?