Topics

On my OPNsense-Appliance are several Interfaces and my "problem" is, that die Interfaces are not sortet. The WAN-Interface is on the bottom, the LAN-Interface is on the top and my Management-LAN-Interface is under the LAN-Interface.

It would be very nice, if we can sort the Interfaces. I don't know about the possibility to code the Interface-Widget, but it would be awesome.

Hello Guys,

i want to deactivate the root-user (for security purposes) in Web-GUI und add a new user with admin privileges. Thats no problem, but via SSH-connection i can't access the default shell-login und can't get su-privileges.

Is it possible, to add the new user to wheel/su-users?

Hello,

with Firefox I have the problem that the traffic monitor remains empty. On the other hand, everything is fine with Chrome, but I want to switch to Firefox.

Are there any tips for this?

With the update to OPNsense version 23.1.10, neither the firewall rules can be changed nor new ones created.

The following error message appears above:

1. The Source Bitness field is required
2. A valid source bitness must be specified

I noticed something strange with my OPNsense. If I take several MAC addresses as an alias, use this alias as a source and limit the destination ports for WLAN devices accordingly, it can happen with my Android smartphone that some apps cannot load the content.

In general, I have selected all Android ports and summarized the other, important ports in an alias and stored them as destination ports.

Now comes the strange thing: if I take the WiFi network as the source, everything works fine. So it looks to me that the OPNsense or my Android smartphone (Samsung Galaxy S21 Ultra 5G with static and real MAC-address) has some problem with the MAC address.

Maybe someone can help me on this topic.

Hi,

the .zip domains are a pretty big risk. With the unbound DNS, blocking this top-level domain should not be so easy.

I don't want to use PiHole or AdGuard. Is it somehow possible with Unbound DNS? Alternatively, can the feature be added accordingly by the development team?

Best regards

Hello,

i have updated my OPNsense to version 23.1.4 und now the clients cannot assign an IPv6-address anymore. The OPNsense interfaces itselfs have an IPv6 address, but the clients don't get an IPv6 address. I guess there es a problem with DHCPv6.

I also receive a 503 Service Unavailable Error Message when i connect to my opnsense. A revert to version 23.1.3 fix my problems successfully.

Hello!

Today I dealt with the topic of DNS over TLS and got it to work with Cloudflare DNS. With the Google DNS servers, however, not. At least according to this test: https://1.1.1.1/help

Can anyone tell me and/or show me how to get DNS over TLS working with the Google DNS servers with OPNsense?


Best regards

Hello,

this is my second try to solve the problem. In german section i doesn't got any replys.

I switched from IPFire to OPNsense about any weeks ago and have not yet repented it. I had to reinstall the box a few times before I got everything going as it is now. But when I was in a good position, I pulled a backup of the config.

When reinstalling OPNsense (after another setting error and no longer accessible WebGUI) and reloading the backup, the OPNsense was no longer accessible after the backup and the internet connection was also not available. After reinstalling OPNsense, by chance I only restored the fixed DHCP entries from the backup. After rebooting the same game, the web interface was no longer accessible and the internet connection was also not available.

Then I reinstalled OPNsense and only restored the firewall rules, aliases, etc. Restart-> everything was fine. Accordingly, there must be an error when restoring the fixed DHCP entries. The error occurred with OPNsense version 21.7.6. I use the following interfaces:

OPNsense with a WAN, LAN and WLAN interface. DHCP is active on the LAN and WLAN interface, but had partially assigned fixed IP addresses by the DHCP server. If further information is required, please let me know, but I no longer have any logs. But maybe someone can confirm this issue or maybe even explain what went wrong in this case. So far I have kept my hands off the fixed DHCP entries, but would like to use the feature, save with the backup and restore it without problems if necessary.

Best regards

Hallo,

ich bin nun vor etwa zwei Wochen von IPFire zu OPNsense gewechselt und habe es bisher nicht bereut. Bis ich alles so laufen hatte, wie es nun ist, musste ich die Kiste einige Male neu installieren. Als ich dann jedoch einen guten Stand hatte, habe ich von der Config ein Backup gezogen.

Bei erneuter Neuinstallation von OPNsense (nach einem weiteren Einstellungsfehler und nicht mehr erreichbarer WebGUI) und dem Wiedereinspielen des Backups, war die OPNsense nach dem Backup nicht mehr erreichbar und auch die Internetverbindung war nicht vorhanden. Nach erneuter Installation von OPNsense habe ich dann aus Zufall einzig die festen DHCP-Einträge aus dem Backup wiederhergestellt. Nach dem Reboot dasselbe Spiel, die Web-Oberfläche war nicht mehr erreichbar und auch die Internetverbindung war nicht verfügbar.

Dann habe ich OPNsense noch einmal neu installiert habe einzig die Firewall-Regeln, Aliase usw. wiederhergestellt. Neustart- > alles war bestens. Demnach muss ein Fehler beim Wiederherstellen der festen DHCP-Einträge vorliegen. Der Fehler trat mit OPNsense Version 21.7.6 auf. Folgende Schnittstellen verwende ich:

OPNsense mit einer WAN-, LAN- und WLAN-Schnittstellem DHCP war beim LAN- und WLAN-Interface aktiv, hatte jedoch teilweise feste IP-Adressen durch den DHCP-Server vergeben. Falls weitere Informationen benötigt werden, bitte Bescheid geben, Logs habe ich jedoch keine mehr. Aber eventuell kann dies jemand nachstellen oder vielleicht sogar erklären, was in diesem Fall schief gelaufen ist. Bisher habe ich von den festen DHCP-Einträgen die Finger gelassen, würde das Feature jedoch gerne nutzen, mit dem Backup sichern und es bei Bedarf ohne Probleme wiederherstellen können.