Messages

1

24.7 Production Series / Re: Health data no longer updating after 24.7.7

« on: October 26, 2024, 10:57:51 am »

Same here.

2

24.7 Production Series / Re: No CPU temperature report since 24.7.7 update

« on: October 26, 2024, 10:42:23 am »

Same here (coming from 24.7.5_3).

3

23.7 Legacy Series / Re: Unknown gateway in Reporting -> Health -> Quality

« on: November 02, 2023, 12:47:15 pm »

I flushed the data under Reports->Settings and the entry is gone now.

Many Thanks!
Hans

4

23.7 Legacy Series / [Solved] Unknown gateway in Reporting -> Health -> Quality

« on: November 02, 2023, 09:45:36 am »

Hello all,

I have a rather cosmetic problem. I am currently using version 23.7.7_3. However, it may well be that the problem has been present for some time.

Under Reporting->Health->Quality there is a gateway (VLAN_51-Freifunk_LAN_GWv4, see first picture in the attachment) that does not appear under System->Gateways->Single (see second picture in the attachment; Gateways->Group is empty).

I don't remember putting this gateway on once. In any case, I would like to get rid of the entry now.

Does anyone know the problem and possibly even the solution?

Many thanks
Hans

5

23.1 Legacy Series / Re: NUT plugin does not work after upgrade to 23.1

« on: February 27, 2023, 03:54:11 pm »

I have NUT runnung on 23.1.1_2 with a APS Smart UPS 750. I also had problems to get NUT stated because of permission problems.

This is what helped in my case:

https://www.reddit.com/r/OPNsenseFirewall/comments/uos0ee/comment/i8kpa1l/

Screenshots of configurations attached.

Hans

6

23.1 Legacy Series / Re: Problem with ipv6 on VLANs only; LAN is ok

« on: February 19, 2023, 07:11:31 pm »

Sure! But logging is enabled for all rules and I don't see anything in live view.

I attach the rules for my "home"-vlan.

7

23.1 Legacy Series / Problem with ipv6 on VLANs only; LAN is ok

« on: February 19, 2023, 06:13:52 pm »

Hallo!

I have problems getting ipv6 to work on vlan interfaces. In principle, the configuration should be OK, because it works on LAN, i.e. the clients get an address and can also communicate with the outside via ipv6.

The physical interfaces belonging to the vlans are enabled, but otherwise unconfigured. Can this be a cause of the problem? In any case, I don't see any difference between the LAN configuration and the configurations of the VLANS.

LAN is on a physical interface. Various VLANS run on other interfaces.

Principle configuration:
- WAN: dhcp with send prefix hint -> /56 prefix
- LAN/VLAN: track interface WAN, Allow manual adjustment is checked
- Router advertisements: unmanaged

I am happy about any hints!

Thank you, Hans

8

23.1 Legacy Series / Re: After update: Starting web GUI...failed. | 503 - service unavailable

« on: February 17, 2023, 06:45:26 pm »

Ok, I regained access to webgui.

killing lighttpd and restarting the webgui worked. I still wonder why that happened...

9

23.1 Legacy Series / After update: Starting web GUI...failed. | 503 - service unavailable

« on: February 17, 2023, 06:15:48 pm »

Hallo,

I just updated from latest 22.7 to 23.1.1_2. Service seems to be running fine except lighttpd. So I have no access to the webgui (503 - service unavailable).

In the logs I found:

Code: [Select]

/var/log/system/latest.log:

<11>1 2023-02-17T17:56:57+01:00 fw.xxx opnsense 79616 - [meta sequenceId="1"] /usr/local/etc/rc.restart_webgui: The command '/usr/local/sbin/lighttpd -f /var/etc/lighty-webConfigurator.conf' returned exit code '255', the output was '2023-02-17 17:56:57: (network.c.537) can't bind to socket: 127.0.0.1:443: Address already in use'

This is what sockstat -4 -l gives:

Code: [Select]

root@fw:/var/log/system # sockstat -4 -l
USER     COMMAND    PID   FD PROTO  LOCAL ADDRESS         FOREIGN ADDRESS     
unbound  unbound    65003 7  udp4   *:53530               *:*
unbound  unbound    65003 8  tcp4   *:53530               *:*
unbound  unbound    65003 11 udp4   *:53530               *:*
unbound  unbound    65003 12 tcp4   *:53530               *:*
unbound  unbound    65003 15 udp4   *:53530               *:*
unbound  unbound    65003 16 tcp4   *:53530               *:*
unbound  unbound    65003 19 udp4   *:53530               *:*
unbound  unbound    65003 20 tcp4   *:53530               *:*
unbound  unbound    65003 21 tcp4   127.0.0.1:953         *:*
root     ntpd       43914 21 udp4   *:123                 *:*
root     ntpd       43914 22 udp4   192.168.178.1:123     *:*
root     ntpd       43914 27 udp4   127.0.0.1:123         *:*
root     ntpd       43914 28 udp4   10.10.40.1:123        *:*
root     ntpd       43914 29 udp4   192.168.60.1:123      *:*
root     ntpd       43914 30 udp4   192.168.61.1:123      *:*
root     ntpd       43914 31 udp4   192.168.62.1:123      *:*
root     ntpd       43914 32 udp4   10.10.10.1:123        *:*
root     ntpd       43914 35 udp4   10.10.20.1:123        *:*
root     ntpd       43914 36 udp4   10.10.30.1:123        *:*
root     ntpd       43914 41 udp4   79.254.24.138:123     *:*
root     ntpd       43914 44 udp4   10.0.3.1:123          *:*
root     sshd       48126 4  tcp4   127.0.0.1:22          *:*
root     sshd       48126 6  tcp4   10.0.3.1:22           *:*
root     sshd       48126 7  tcp4   10.10.99.1:22         *:*
root     sshd       48126 9  tcp4   10.10.10.1:22         *:*
root     sshd       48126 11 tcp4   192.168.178.1:22      *:*
root     lighttpd   16655 6  tcp4   127.0.0.1:443         *:*
root     lighttpd   16655 8  tcp4   192.168.178.1:443     *:*
root     lighttpd   16655 10 tcp4   10.10.10.1:443        *:*
root     lighttpd   16655 12 tcp4   10.10.99.1:443        *:*
root     lighttpd   16655 13 tcp4   10.0.3.1:443          *:*
root     lighttpd   16655 15 tcp4   127.0.0.1:80          *:*
root     lighttpd   16655 17 tcp4   192.168.178.1:80      *:*
root     lighttpd   16655 19 tcp4   10.10.10.1:80         *:*
root     lighttpd   16655 21 tcp4   10.10.99.1:80         *:*
root     lighttpd   16655 22 tcp4   10.0.3.1:80           *:*
nut      upsd       18521 4  tcp4   127.0.0.1:3493        *:*
root     radiusd    97016 9  udp4   127.0.0.1:18120       *:*
root     radiusd    97016 10 udp4   *:1812                *:*
root     radiusd    97016 11 udp4   *:1813                *:*
root     radiusd    97016 14 udp4   *:31044               *:*
root     udpbroadca 72489 3  udp4   *:5354                *:*
_flowd   flowd      26815 3  udp4   127.0.0.1:2056        *:*
root     AdGuardHom 20823 12 tcp4   192.168.178.1:8080    *:*
root     AdGuardHom 20823 18 udp46  *:53                  *:*
root     AdGuardHom 20823 22 tcp46  *:53                  *:*
root     lighttpd   17579 4  tcp4   127.0.0.1:43580       *:*
zabbix   zabbix_age 7898  4  tcp4   *:10050               *:*
zabbix   zabbix_age 7896  4  tcp4   *:10050               *:*
zabbix   zabbix_age 7446  4  tcp4   *:10050               *:*
zabbix   zabbix_age 6885  4  tcp4   *:10050               *:*
zabbix   zabbix_age 6512  4  tcp4   *:10050               *:*
zabbix   zabbix_age 2174  4  tcp4   *:10050               *:*
root     mdns-repea 27576 3  udp4   *:5353                *:*
root     mdns-repea 27576 4  udp4   192.168.178.1:5353    *:*
root     mdns-repea 27576 6  udp4   10.10.10.1:5353       *:*
root     mdns-repea 27576 7  udp4   10.10.20.1:5353       *:*
root     mdns-repea 27576 8  udp4   10.10.30.1:5353       *:*
root     mdns-repea 27576 9  udp4   10.10.40.1:5353       *:*
nobody   samplicate 23026 3  udp4   127.0.0.1:2055        *:*
nobody   samplicate 23026 4  udp4   *:2844                *:*
dhcpd    dhcpd      22517 18 udp4   *:67                  *:*
?        ?          ?     ?  udp4   *:51820               *:*

Can anybody help me to get the weggui running again?

Thanks, Hans

10

German - Deutsch / Re: Radius-Problem seit Update

« on: November 26, 2022, 10:16:51 am »

Keine Ahnung ob es hilft: ich hatte nach dem Übergang von 22.7.6 auf 22.7.7 Anmeldeprobleme im WLAN mit WPA-EAP und freeradius-server auf der OPNsense. Aufgetreten ist das bei mir nur mit iOS und iPadOS (jeweils aktuelle Version). MacOS devices hatten keine Probleme. Geholfen hat bei mir "Netzwerk ignorieren" und dann neu anmelden. Seeehr merkwürdig....

Mit Update auf 22.7.8 warte ich noch...

Ein Test wäre aber schön, revert zurück geht ja immer

OK. Habe gerade auf 22.7.8 geupdated. Reboot wurde nicht durchgeführt (nicht automatisch und auch nicht von mir). Verbindung geht bislang. Auch keine weiteren Auffälligkeiten bisher...

11

German - Deutsch / Re: Radius-Problem seit Update

« on: November 25, 2022, 07:06:09 pm »

Keine Ahnung ob es hilft: ich hatte nach dem Übergang von 22.7.6 auf 22.7.7 Anmeldeprobleme im WLAN mit WPA-EAP und freeradius-server auf der OPNsense. Aufgetreten ist das bei mir nur mit iOS und iPadOS (jeweils aktuelle Version). MacOS devices hatten keine Probleme. Geholfen hat bei mir "Netzwerk ignorieren" und dann neu anmelden. Seeehr merkwürdig....

Mit Update auf 22.7.8 warte ich noch...

12

22.1 Legacy Series / Re: NUT package brocken?

« on: June 14, 2022, 02:16:52 pm »

When I add this tunable via the GUI its end up in loader.conf (not loader.conf.local) and "Type" is shown as "unsupported".

13

German - Deutsch / Re: WireGuard + AdGuard

« on: May 21, 2022, 11:11:16 am »

Versuch bitte mal als DNS Server bei Deinen WireGuard Clients die OPNsense Adresse im Wireguard Netz (10.0.3.1/32?) einzustellen. So läuft es bei mir (ebenfalls mit AdGuard und unbound).

14

German - Deutsch / Re: Wie mache ich ein Gerät in einem zweiten Subnetz bekannt?

« on: May 03, 2022, 08:59:29 am »

Na ja, Zigbee hat mit Ethernet ja zunächst gar nichts zu tun. Hier hängt wahrscheinlich ein Zigbee Dongle (über USB?) an einem Rechner in den einem Subnet. Und der Smartphone Client befindet sich in dem anderen Subnet. So gesehen ist es wohl ein "normales" Problem "Zugriff von Client in Subnet A auf Server in Subnet B". Aber ohne weitere Details könnte ich jetzt auch nicht mehr sagen.

15

21.7 Legacy Series / NUT plugin on 21.7.8: Diagnostic GUI page is empty but plugin is working fine

« on: February 27, 2022, 07:08:28 pm »

Hey all.

I have a strange problem with the nut plugin on my opnsense running 21.7.8:

My UPS ist connected to my opnsense via USB. NUT plugin configured as "standalone". I get UPS info on cli using the upsc command. Shutdown is working also. Secondary servers can also connect to the NUT-server on the opnsense (MODE=netclient). So erverything seems to work perfectly fine.

Surprinsingly, the Diagnostic page of the plugin is completely empty (yes, I already reset opnsense). Even more surprisingly: if I connect the UPS to another server an configure opnsense in netclient mode the Diagnostic page shows correct content.

Any idea what's going on here? Any commands to run to get more insight?

Thanks!
Hans