Recent posts

#1

26.1, 26,4 Series / Re: Use Hostnames Instead of I...

Last post by WiteWulf - Today at 01:44:03 PM

I understand that it's nothing to do with proxmox, thanks, but I like to give plenty of detail about the opnsense instance I'm requesting assistance with, as it's traditional to criticise people for not doing so.

As stated, I'm already forwarding requests for osx.ninja to dnsmasq. I'll do the same for 1.168.192.in-addr.arpa

Time passes...

Thanks that worked perfectly! Reverse resolution works, and reporting is now using hostnames👍

#2

26.7 Release Candidate Series / Re: Upgrades into RC1 via 26.1...

Last post by Wrigleys - Today at 01:17:53 PM

Labels are off due to a kernel error but we found the problem already, see https://github.com/opnsense/src/issues/295

Great, thanks for that!

#3

26.7 Release Candidate Series / Re: OPNsense 26.7.r2_3 Disk Wi...

Last post by franco - Today at 12:55:32 PM

I've seen this too and I have the suspicion this started after https://github.com/opnsense/core/commit/beff82708582

# opnsense-patch https://github.com/opnsense/core/commit/beff82708582

Does that help?


Cheers,
Franco

#4

26.1, 26,4 Series / Re: Use Hostnames Instead of I...

Last post by meyergru - Today at 12:53:56 PM

This has nothing to do with Proxmox.

If you want Unbound to resolve local hostnames, you will most likely have the domain osx.ninja forwarded to Dnsmasq on port 53053.
You must do the same for "1.168.192.in-addr.arpa" to enable reverse lookups.

#5

26.7 Release Candidate Series / Re: Upgrades into RC1 via 26.1...

Last post by franco - Today at 12:51:27 PM

Labels are off due to a kernel error but we found the problem already, see https://github.com/opnsense/src/issues/295

#6

26.1, 26,4 Series / Use Hostnames Instead of IP Ad...

Last post by WiteWulf - Today at 12:43:13 PM

I'm running 26.1.11 as VM on proxmox. I've searched the forums and only found people asking specifically about this with respect to Zenarmour reports, and those threads didn't address my issue.

Is it possible to have OPNsense use local hostnames in reports such as Traffic and Unbound DNS?

I have static entries in dnsmasq for all the hosts I care about on my LAN, but the above reports only ever use their IP addresses (v4 and v6).

As I'm using RA to assign v6 addresses I don't expect to see those resolved, but the v4 addresses would be useful.

I'm using the standard Unbound on port 53, forwarding queries for my local domain (osx.ninja) to dnsmasq on 53053. Local name resolution works (i.e. I can ping pdu.osx.ninja and get 192.168.1.6), but I can't get reverse resolution (ie. dig -x 192.168.1.6 returns NXDOMAIN), except for the device itself (dig -x 192.168.1.1 correctly returns opnsense.osx.ninja).

#7

26.7 Release Candidate Series / Re: Services widget

Last post by Wrigleys - Today at 12:19:34 PM

In addition to I've noticed a scroll bar in single column mode even if I dragged the table down completely.

[repository SunnyValley has no meta file, using default settings]

#8

German - Deutsch / Partial update failure detecte...

Last post by PrinceLG - Today at 12:00:59 PM

***GOT REQUEST TO UPDATE***
Currently running OPNsense 26.1.11_6 (amd64) at Sun Jul 12 09:49:32 CEST 2026
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
Updating SunnyValley repository catalogue...
Waiting for another process to update repository SunnyValley
Updating mimugmail repository catalogue...
Fetching meta.conf: . done
mimugmail repository is up to date.
All repositories are up to date.
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
Updating SunnyValley repository catalogue...
pkg-static: An error occurred while fetching package: Unknown error
pkg-static: An error occurred while fetching package: Unknown error
repository SunnyValley has no meta file, using default settings
pkg-static: An error occurred while fetching package: Unknown error
pkg-static: An error occurred while fetching package: Unknown error
pkg-static: An error occurred while fetching package: Unknown error
pkg-static: An error occurred while fetching package: Unknown error
Unable to update repository SunnyValley
Updating mimugmail repository catalogue...
Fetching meta.conf: . done
mimugmail repository is up to date.
Error updating repositories!
Checking for upgrades (6 candidates): ...... done
Processing candidates (6 candidates): ... done
The following 2 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
   os-sensei: 2.6 -> 2.6.1 [SunnyValley]
   os-sensei-agent: 2.6 -> 2.6.1 [SunnyValley]

Number of packages to be upgraded: 2

The process will require 2 MiB more space.
173 MiB to be downloaded.
pkg-static: An error occurred while fetching package: Unknown error
pkg-static: An error occurred while fetching package: Unknown error
Flushing temporary package files... done
Starting web GUI...done.
Partial update failure detected: report this error log to OPNsense.
No further actions will be taken. Please restart the update now.
***DONE***

#9

26.1, 26,4 Series / Re: First time OPNsense setup ...

Last post by daveMar - Today at 11:55:16 AM

Any help is very much appreciated, let me know what information I can provide.

Read this : https://forum.opnsense.org/index.php?topic=52253.0

It basically comes down to having to do this : https://forum.opnsense.org/index.php?topic=48695.0

!!! READ FIRST !!! as much as possible about it and only proceed once you are 100% sure you know what you are going to do step by step ;)

Thank you very much. I did go through the referenced topics and ended up upgrading the 2.17 NVM to 2.32 on both of my Intel I226-V interfaces. So far so no issues, I hope it stays this way!

#10

26.7 Release Candidate Series / Re: OPNsense 26.7.r2_3 Disk Wi...

Last post by MoonbeamFrame - Today at 10:31:55 AM

This may be a red herring as I've just see this behavior on my local live firewall running 26.1.11_6.

My initial suspicion was the browser, Firefox 152.0.5 on Linux, But I see a similar behavior in Brave.

The difference is that in Brave I can see the box drawn oversized before collapsing back to the expected size. I subsequently saw the same with Firefox but after a few minutes.