Topics

1

20.1 Legacy Series / Per host statistics in Reporting: Traffic does not work anymore

« on: April 16, 2020, 06:31:42 pm »

Hello,

I've been having stability problems with my APU2C2-based router (it crashes and reboots randomly) and after one of these occasions the Reporting: Traffic screen stopped working properly. The moving graph is fine at the top, but no matter what I select at the bottom lines (Interface, Sort by, Filter, Display, Top) nothing is displayed below the "Host IP   Bandwidth In   Bandwidth Out   Total In" line. I tried to clear RRD Netflow and Insight data, but it did not help - though I'm not sure where it gets the information from.

Is there any known trick I can do to reset it to a default state? It's not a problem if I lose historical data.

2

20.1 Legacy Series / Is remote logging faulty?

« on: April 11, 2020, 12:51:51 pm »

Hello all,

I'm still chasing why my APU2C2 resets randomly (see https://forum.opnsense.org/index.php?topic=16351.0), hence at some point I set up remote logging. Very simple: one rule which forwards EVERYTHING to the loghost.

The problem is: NOTHING gets logged until syslog-ng starts, e.g. boot dmesg.

Here's a log snippet, today morning I restarted my router manually (tune something in the BIOS):

2020-04-11T10:14:29+00:00 auth.info sshd[31201]: Received signal 15; terminating.
2020-04-11T10:18:45+00:00 syslog.notice syslog-ng[91955]: syslog-ng starting up; version='3.25.1'

I don't think that's the right way to do remote logging.

Did I set up something incorrectly or is this feature simply missing form OPNsense?

3

20.1 Legacy Series / Recurring random crashes with 20.1.x on a PC Engines APU2

« on: March 22, 2020, 11:42:04 am »

Hello all,

I have an annoying problem with my router: it randomly crashes from time to time. Sometimes it can go for almost a month without problems, sometimes it reboots after a couple of days. All 20.1.x versions showed this behaviour.

There are no infos at all in the local log files. I set up remote logging to another APU2 running Linux but to no avail, as there were no usable infos, either. Interestingly, the bootup kernel messages were not logged on the loghost, either, but I might need to tune something for that.

I don't think it's caused by overheating, as the CPU temp graphs show constant temperatures between 60-62°C. Of course it could still be a another hardware problem. There's a 16GB mSATA card installed, the internet uplink is provided by a USB LTE stick in PPP mode and all the 3 igbX interfaces are in use. The BIOS is fairly receny, 4.11.0.2.

Another somewhat disturbing thing is that these crashes are not visible in lastlog. Perhaps it's a BSD thingie (I'm mostly used to Linux and Solaris form my jobs and am fairly new to BSDs). The last crash happened today morning at around 8:10 CET - between the 2 topmost lines in last's output.

root       pts/0    A.B.C.D           Sun Mar 22 10:20   still logged in
root       pts/0    A.B.C.D           Sat Mar 21 22:22 - 22:24  (00:01)
root       pts/0    A.B.C.D           Sat Mar 21 06:45 - 06:51  (00:06)

I know it's pretty much trying to catch a black cat in a dark room at this point, but perhaps others also experienced this. Does anyone perhaps have any ideas where I can start to look for more clues?

I also thought about setting up logging for the serial console, as I have a FreeNAS box close to the router which I use for console access with a USB-serial converter.

Unfortunately I cannot trigger this behaviour and I couldn't correlate it to other events, either. This morning it happened while my family was still sleeping , so there was basically no traffic and load on the router.

Any help is much appreciated.

Gabor

4

20.1 Legacy Series / Reproducible DNS resolution problems with Unbound

« on: February 02, 2020, 11:56:36 pm »

Hello all,

This is my first post here, so a short introduction: I'm a seasoned *nix sysadmin (Solaris and Linux at $DAYJOB, and whatever I can get my hands dirty with at home), but quite new to OPNsense. I tried to look for an answer to my problem, but could not find one - apologies if I just missed something.

I have recently migrated my home network from a Turris Omnia to OPNsense/APU2C2, but DNS resolution with the default Unbound is still flaky. I set it up in standalone mode without upstream resolvers. After restarting Unbound (to clear the cache) the first resolution of any DNS record with the host command is always completely or partially ends in not found/SERVFAIL. The 2nd try works, I assume meanwhile Unbound gets and caches the results.

The clients I tried it with: Macs on WiFi, a wired FreeNAS box (11.2U7) and locally, on the router. Same results.

I used "host" only for testing, but the bug manifests itself with "real" clients, too. And it's pretty annoying when the browser comes back with a "$YOURFAVOURITESEARCHENGINE does not exist".

I did not test caching intentionally, but I remember that retrying a DNS record after sufficient time repeated these results: first answer failed, as if Unbound had been restarted.

Alternatively I stopped Unbound and quickly set up DNSmasq with 1.1.1.1 as upstream - it works flawlessly. But I prefer to use my own DNS resolver and not relying on any provider.


Has anyone else experienced the same problem or am I doing something wrong?


(I have been using Unbound on a small and old Debian box for years, but haven't yet seen anything like this.)