Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Chiny

#1
24.7, 24.10 Series / Re: vnstat date format
September 13, 2024, 10:26:25 AM
Yes, that works, thanks.   The dd/mm/yyyy survived a minor point update and reboot, which is what I wanted to achieve.

Curiously though, despite the...

# locale (LC_ALL) ("-" = use system locale)
Locale "-"


...in the templates file, OPNsense still resolutely ignores locale, giving the same problem as my first post.   It does require the Day/Month/Top format changes to get dd/mm/yyyy, which feels a bit of a kludge.

But it does work, so my problem is solved.   Thanks again for the tip re templates.
#2
24.7, 24.10 Series / vnstat date format
September 04, 2024, 04:48:36 PM
I'd like the OPNsense GUI of vnstat to show dates in dd/mm/yy format, Locale "en_GB.UTF-8" would suit me nicely.   Unfortunately, my setup provides mm/dd/yy.

/usr/local/etc/vnstat.conf says:

Quote# locale (LC_ALL) ("-" = use system locale)
Locale "-"

The terminal output of    % locale   is:
QuoteLANG=en_GB.UTF-8
LC_CTYPE="en_GB.UTF-8"
LC_COLLATE="en_GB.UTF-8"
LC_TIME="en_GB.UTF-8"
LC_NUMERIC="en_GB.UTF-8"
LC_MONETARY="en_GB.UTF-8"
LC_MESSAGES="en_GB.UTF-8"
LC_ALL=

The terminal output of: vnstat -d
does provide dates in dd/mm/yy format, as expected.

So... it appears that OPNsense GUI has its own opinion of Locale but where is this stored ?

For good measure, I edit'd /usr/local/etc/vnstat.conf such that:

Quote# locale (LC_ALL) ("-" = use system locale)
Locale "en_GB.UTF-8"

... and the GUI output of vnstat changes to dd/mm/yy format.   Of course, that doesn't work for long, getting re-written with reboots, updates and so on.

What am I missing ?   How can I get the GUI display of vnstat to use dd/mm/yy ?
#3
OK, a challenge for when I have a moment; rsync my VmStats or somesuch.   Thanks for your help.
#4
OK, well not good news.   I did a re-install from a USB stick after finding I could import my configuration from the PC SSD, whew.   It now boots fine and I've not yet found anything not working.   Audits appear happy.   Shame to have lost my VnStat numbers but maybe they are there, somewhere, on the USB stick.   
#5
I also have this error, rebooting after upgrading from 23.1.11-1 (I think it was) to 23.7    Can I recover from this error somehow ?   I hope not a re-install  :(
#6
23.1 Legacy Series / timezone for cron
April 17, 2023, 07:42:34 PM
Currently running OPNsense 23.1.5_4-amd64 with plugin os-speedtest-community 0.9_3

cron is scheduled to run speedtest once per day, at 20:05 in the OPNsense GUI.   Now that summertime has arrived and the timezone has moved from +0000 to +0100, cron runs an hour earlier at 19:05 according to the speedtest output.

OPNsense GUI Dashboard displays +0100 time correctly.   I've double checked tzsetup to check my timezone.   (Shell) date shows the +0100 time correctly.    Presumably cron allows for TZ ?   Or have I missed a config  :-[
#7
I'm too new to OPNsense to be sure but from ntpd experience, this does have a whiff of a firewall problem.   How about trying:
ntpdate -d 127.0.0.1
and making sure you get both transmit and receive back ?   That should answer the firewall question.
#8
I've been looking for a few hours at this issue and couldn't see how to make the last step.   Whilst not directly solving my problem (coudn't see how to enter a single IPv4 source address), it did confirm I was on the right lines - now sorted - many thanks.

My excuse is that I am a newbie, had OPNsense running for just under 2 days, with a new mini-PC (first PC in decades) and FreeBSD is new to me (unless you count macOS).   Working well, complete with a few plugins installed.