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 - cryogenic666

#1
20.1 Legacy Series / Re: 20.1.4 - ntopng
April 09, 2020, 02:11:29 AM
I'm also getting permission denied in the log files for ntopng for basically everything under /var/db/ntopng/#/rrd (substitute # with numbers 0-5). They're owned by ntopng/wheel, so I'm not sure what's going on, but it can't seem to update rrd files
#2
20.1 Legacy Series / Re: 20.1.4 - ntopng
April 09, 2020, 01:50:19 AM
It's the new 4.0 version of NtopNG, actually, and I'm seeing the same thing myself. It also doesn't use the same GeoIP databases and doesn't include the GeoIP update stuff to do all of that for you.
#3
Can you ping those DNS servers? What happens if you try to do a nslookup using those DNS servers? I have a Pihole running on my network and did have to set it to allow clients not on the same subnet to query it in order for it to work, so depending on what you're doing for DNS, look into that as well. (if you can ping it but not nslookup, that's likely your issue)
#4
I'd guess they mean that the silver in the paste is 99.9% pure and not that the paste is 99.9% silver. But I can totally see how you'd read it that way.
#5
I'm currently running OPNsense on an AMD A4-5000 with 4GB RAM and a dual port PCI-E x4 Intel NIC (identifies as 82571EB) and can't get gigabit speeds on my symmetrical AT&T fiber connection. The best I see via the firewall is around 750-800, with upload being higher than down. I've watched CPU usage via Top and it never exceeds 35% so I'm not sure what could be the issue, as I can hit 920-950 with the same PC connected straight to the modem. I'm not running Suricata or any other services outside the norm other than VnStat (and disabling that made no difference). I've also unchecked the boxes to disable Hardware CRC/TSO/LRO in the settings. Anything else that could be the cause of it? I also see astronomical upload bufferbloat (350ms) compared to when connected to the modem directly (15ms).