Topics

1

18.7 Legacy Series / 18.7.6 - Edited Alias Port Range seems not to be applied to the firewall

« on: November 04, 2018, 11:20:14 am »

OPNsense 18.7.6
I changed an already defined Port Range in aliases, saved and applied it. But pfInfo shows me still the old range in the firewall rule. So it seems the firewall rule was not updated. In 18.7.5 this works without problems.

Helmut

2

German - Deutsch / pftop Fenster - horizontales Scrollen

« on: January 17, 2018, 05:58:40 pm »

Hallo,

wenn ich im Fenster von pftop (unter Firewall:Diagnostics:pftop) nach rechts scrolle, wird mir bei jeder Aktualisierung des Fensterinhalts der horizontale Scrollbalken wieder ganz nach links verschoben. Da die Aktualisierung im Sekundentakt stattfindet ist es ziemlich schwierig die Werte abzulesen. In anderen Fenstern, z.B. pfinfo:Rules passiert das nicht. Gibt es da Möglichkeiten das zu verhindern?

Gruß
Helmut

3

17.1 Legacy Series / [SOLVED] cron doesn't reload new time settings with -HUP signal

« on: May 08, 2017, 06:17:22 pm »

During my tests with the rc.update_bogons script i realized that cron does not reload new time settings with kill -s HUP (cron pid). As descriped in the cron manpage changing the modification time of the spool directory /var/cron/tabs does the trick. No HUP Signal needed.

As far as i can see, the cron entries are generated with php from the system.inc file followed be a HUP signal for cron. This might be a problem. The modification time of the cron spool directory should be changed.

Cheers,
Helmut

4

17.1 Legacy Series / [SOLVED] Problem with rc.update_bogons script

« on: May 02, 2017, 05:13:06 pm »

I have an OPNSense Box (17.1.4) filtering Traffic between an Office Network and an Automation Network. The OPNSense Box has no Internet Connection, so updating Bogon Networks will not work and is not necessary in my case. There is no option for disabling the update, so I set the frequency to monthly.

On the 1st of the month I got a big CPU Load, over 30000 states for udp from 127.0.0.1 to 127.0.0.1:53 and the log file is filling up with following messages:
root: rc.update_bogons is starting up
root: rc.update_bogons is beginning the update cycle
root: Could not download https://pkg.opnsense.org/FreeBSD:11:amd64/17.1/sets/bogons.txz

I think the rc.update_bogons script generates an endless loop when there is no connection to the pkg.opnsense.org server. The sleep command isn't executed when the script is relaunched from an PROC_ERROR. Some parts of the script:

if [ "${COMMAND}" = "cron" ]; then
    VALUE=$(jot -r 1 1 900)
    echo "rc.update_bogons is sleeping for ${VALUE} seconds" | logger
    sleep ${VALUE}
fi

if [ ! -f ${WORKDIR}/bogons.txz ]; then
    echo "Could not download ${URL}" | logger
    PROC_ERROR=1

if [ -n "${PROC_ERROR}" ]; then
    # Relaunch and sleep
    sh /usr/local/etc/rc.update_bogons &
    exit
fi

A nice feature would be a setting for update frequency: Daily, Weekly, Monthly and never

5

17.1 Legacy Series / UEFI installation freezes after changing the keymap

« on: April 18, 2017, 08:38:46 pm »

I tried to install OPNsense-17.1.4-OpenSSL-vga-amd64.img in UEFI Modus. When I change the keymap from default to another language (german in my case) the system freezes after accepting the changes. Only Ctrl+Alt+Del for reboot is working. With the default keymap everything is fine.

6

German - Deutsch / Reporting Health letzter Zoom Level

« on: April 08, 2017, 12:16:04 pm »

Weiß jemand ab welchem Zeitpunkt beim Reporting Health im letzten Zoom Level Daten angezeigt werden. Nach 45 Tagen stand bei mir immer noch "No Data Available".

Im vorletzten Zoom Level wechselt die Zeitachse in ein ziemlich ungewöhnliches Format, z.B. "17 d089". Ich interpretiere das als Jahr 2017 und laufender Tag 89. Gewollt oder nicht, ist auf jeden Fall ungewohnt.

7

16.7 Legacy Series / [SOLVED] 16.7.r1 - wizard shows wrong headlines

« on: July 07, 2016, 08:09:48 am »

Wizard from 16.7.r1 shows wrong headlines. For example: on the page for the WAN Interface the headline is Time Server Information. Of course, this is not a critical bug.