Topics

1

24.1 Legacy Series / (Solved) Upgrading Firmware to 24.1 from 23.7.12.5

« on: February 27, 2024, 03:50:02 pm »

I'm getting the below error -
***GOT REQUEST TO UPGRADE***
Currently running OPNsense 23.7.12_5 at Tue Feb 27 09:45:01 EST 2024
Fetching packages-24.1-amd64.tar: ................................................... done
Fetching base-24.1-amd64.txz: ............ done
Fetching kernel-24.1-amd64.txz: ...... done
Extracting packages-24.1-amd64.tar... done
Extracting base-24.1-amd64.txz... done
Extracting kernel-24.1-amd64.txz... done
Please reboot.
>>> Invoking upgrade script 'squid-plugin.php'
Squid web proxy is not active. Not installing replacement plugin.
>>> Invoking upgrade script 'unbound-duckdb.py'
Traceback (most recent call last):
  File "/usr/local/opnsense/site-python/duckdb_helper.py", line 65, in __enter__
    self.connection = duckdb.connect(database=self._path, read_only=self._read_only)
duckdb.IOException: IO Error: Trying to read a database file with version number 39, but we can only read version 51.
The database file was created with DuckDB version v0.6.0 or v0.6.1.

The storage of DuckDB is not yet stable; newer versions of DuckDB cannot read old database files and vice versa.
The storage will be stabilized when version 1.0 releases.

For now, we recommend that you load the database file in a supported version of DuckDB, and use the EXPORT DATABASE command followed by IMPORT DATABASE on the current version of DuckDB.

See the storage page for more information: https://duckdb.org/internals/storage

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/etc/rc.syshook.d/upgrade/20-unbound-duckdb.py", line 41, in <module>
    if export_database('/var/unbound/data/unbound.duckdb', '/var/cache/unbound.duckdb', 'unbound', 'unbound'):
  File "/usr/local/opnsense/site-python/duckdb_helper.py", line 147, in export_database
    with DbConnection(source, read_only=True) as db:
  File "/usr/local/opnsense/site-python/duckdb_helper.py", line 75, in __enter__
    raise StorageVersionException(str(e))
duckdb_helper.StorageVersionException: IO Error: Trying to read a database file with version number 39, but we can only read version 51.
The database file was created with DuckDB version v0.6.0 or v0.6.1.

The storage of DuckDB is not yet stable; newer versions of DuckDB cannot read old database files and vice versa.
The storage will be stabilized when version 1.0 releases.

For now, we recommend that you load the database file in a supported version of DuckDB, and use the EXPORT DATABASE command followed by IMPORT DATABASE on the current version of DuckDB.

See the storage page for more information: https://duckdb.org/internals/storage
>>> Error in upgrade script '20-unbound-duckdb.py'
***DONE***

2

22.1 Legacy Series / Resolved - GeoIP Error - with Update_tables

« on: April 07, 2022, 01:29:11 pm »

I'm running  OPNsense 22.1.2_1 and noticed my GeoIP hasn't updated since 3/29/2022 so it hasn't updated in over a week.   I created a new license and set it up to verify it's not an issue with the settings, and verified by using the URL that I added to config worked. Just wanted to verify if it was just me or if maybe GeoIP hasn't made any updates as of late?  I also noticed the following in my log files but seems that has been going on for some time.

2022-04-06T11:19:02-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 639076)   
2022-04-05T11:18:02-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 639076)   
2022-04-04T11:17:02-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 639076)   
2022-04-03T11:16:02-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 639076)   
2022-04-02T11:15:02-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 639076)   
2022-04-01T11:14:02-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 639076)   
2022-03-31T11:13:02-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 639076)   
2022-03-30T11:12:02-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 639076)   
2022-03-29T11:11:02-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 639076)   
2022-03-28T11:10:02-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 906989)   
2022-03-27T11:09:03-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 906989)   
2022-03-26T11:08:02-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 906989)   
2022-03-25T11:07:02-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 906989)   
2022-03-24T11:06:02-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 906989)   
2022-03-23T11:05:03-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 906989)   
2022-03-22T11:04:02-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 906526)   
2022-03-21T11:03:02-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 906526)   
2022-03-20T11:02:02-04:00   Error   /update_tables.py   geoip updated (files: 500 lines: 906526)

3

20.1 Legacy Series / Error's in FW log since Update to 20.1.2

« on: March 09, 2020, 08:55:54 pm »

I'm seeing ALOT of this in my FW all of the sudden since the upgrade to 20.1.2 from 20.1.1

WAN      Mar 9 15:54:05   192.168.254.254:1900   239.255.255.250:1900   udp   Block private networks from WAN   
   WAN      Mar 9 15:54:04   192.168.254.254:1900   239.255.255.250:1900   udp   Block private networks from WAN

4

20.1 Legacy Series / (Resolved) If I enable Forwarding Mode in Unbound DNS - DNS lookup Fails

« on: February 12, 2020, 04:27:13 pm »

OK so I'm running 20.1, and Unbound DNS, if I goto Services/Unbound/General and tick "Enable Forwarding Mode" my DNS lookup fails on my Windows boxes behind opnsense, if I do a lookup from Opnsense itself it works fine.  Anything on the LAN side fails, saying it's not getting a response from the DNS server.  I have DNS setup to 1.1.1.1 and 1.0.0.1 under System/Settings/General.   As soon as I uncheck Enable Forwarding Mode everything starts working again.   Any thoughts as to why this would be happening?  I have a single DNS setup on the Windows boxes and that's the opnsene box itself.

5

19.7 Legacy Series / Odd Plex port Denials?

« on: October 22, 2019, 10:11:58 pm »

I happened to be looking at my Logs today and noticed this -  It's working fine working fine.. then I see these Default Deny's in here?  Not sure why I would be getting those?  Everything still seems to be working Just found this odd?
   
   LAN      Oct 22 16:08:14   96.28.139.179:57415   192.168.29.10:32400   tcp   let out anything from firewall host itself   
   LAN      Oct 22 16:08:14   96.28.139.179:57414   192.168.29.10:32400   tcp   let out anything from firewall host itself   
   LAN      Oct 22 16:08:14   192.168.29.10:32400   96.28.139.179:57395   tcp   Default deny rule   
   LAN      Oct 22 16:08:14   192.168.29.10:32400   96.28.139.179:57394   tcp   Default deny rule   

6

19.7 Legacy Series / [SOLVED] /tmp/rules.debug: cannot define table bogonsv6: Cannot allocate memory

« on: October 11, 2019, 08:28:05 pm »

When trying to apply my Alias changes I'm getting the following error - Cannot Allocate Memory

7

19.7 Legacy Series / NAT Port Forward Rule Failure - Solved

« on: October 11, 2019, 07:59:43 pm »

I created a new rule on my FW for Port Forward of a port to an internal server.  I have SEVERAL rules that have all been setup for some time that work just fine.  They've been in place since 18.7, and I'm currently running 19.7.4_1. When I add the port forward.. IDENTICAL to other rules it's failing and saying it's hitting the default deny rule.  I've deleted it, and recreated it a couple of times and nothing seems to work.  I've attached a screenshot of my NAT Port FW rule.   I've also attached a rule of my Wan Rules.   I'm a little baffled by this, I've created many rules and never ran into this problem before.

8

General Discussion / Trying to get Grafana to work with Opnsense

« on: July 22, 2019, 02:24:56 pm »

I'm running 19.7 and trying to get Grafana setup to work.  I've setup Telegraf on my box, with InfluxDB setup.  When I test the Datasource on Grafana it shows up as working, but when I add a Dashboard that is supposed to pull in influxdb from telegraf it doesn't load anything it just shows up blank.
Datasource.  I'm new to this, and have never setup it up before so at a loss.. I did notice an IP from 35.226.211.0 that was being blocked by the firewall I've created a firewall rule to allow that IP, but still no luck?  Any help would be appreciated.

9

19.7 Legacy Series / High CPU Usage since upgrade from 19.1.10 to 19.7

« on: July 17, 2019, 07:46:24 pm »

Has anyone else noticed almost double high cpu usage compared from 19.1 to 19.7?  As a general rule, my CPU would max about 50% most of the time.. I RARELY saw it peek above that mark, I upgraded to 19.7 this morning and I'm peaking 70-80% frequently.   I've even spiked as high as 91%. 

10

19.1 Legacy Series / 19.1.2 Update? - Resolved

« on: February 28, 2019, 08:55:02 pm »

I updated to 19.1.2 and now I'm seeing ALOT of LAN activity being blocked?

   LAN      Feb 28 14:53:47   [fe80::5e96:56ff:febf:70e7]:546   [ff02::1:2]:547   UDP   allow access to DHCPv6 server on LAN   
   LAN      Feb 28 14:53:45   192.168.29.100:40318   54.175.224.52:2350   tcp   Default deny rule   
   LAN      Feb 28 14:53:45   40.134.81.116:19856   192.168.29.10:32400   tcp   let out anything from firewall host itself   
   LAN      Feb 28 14:53:44   40.134.81.116:19836   192.168.29.10:32400   tcp   let out anything from firewall host itself   
   LAN      Feb 28 14:53:42   192.168.29.101:34350   52.87.251.209:2350   tcp   Default deny rule   
   LAN      Feb 28 14:53:37   40.134.81.116:19735   192.168.29.10:32400   tcp   let out anything from firewall host itself   
   LAN      Feb 28 14:53:36   192.168.29.102:40790   54.175.224.52:2350   tcp   Default deny rule   
   LAN      Feb 28 14:53:36   34.245.172.51:41078   192.168.29.10:32400   tcp   let out anything from firewall host itself   
   LAN      Feb 28 14:53:24   192.168.29.10:59736   35.241.26.53:443   tcp   Default deny rule   
   LAN      Feb 28 14:53:20   192.168.29.10:54240   173.194.197.188:5228   tcp   Default deny rule   
   LAN      Feb 28 14:53:17   192.168.29.100:47928   172.217.7.130:443   tcp   Default deny rule   
   LAN      Feb 28 14:53:17   192.168.29.100:39756   216.58.192.129:443   tcp   Default deny rule

11

19.1 Legacy Series / Building a new box and getting this error when trying to upgrade to production r

« on: January 26, 2019, 04:11:47 pm »

***GOT REQUEST TO UPGRADE: maj***
Fetching packages-19.1.r1-OpenSSL-amd64.tar: .......................................... done
Fetching base-19.1.r1-amd64.obsolete: .. failed
***DONE***

12

18.7 Legacy Series / CPU Hitting 100% during speedtest? - Bottleneck?

« on: January 17, 2019, 03:58:05 pm »

I'm curious if this would be a bottleneck.  I have Spectrums Internet 400/20mb Package.   I happened to be monitoring the stats on my Opnsense box when I ran a speed test from another windows box.   I noticed that when my speedtest came pretty close to hitting 400mb the cpu spiked to 100% in Opnsense.   I'm running n 1u Atom box with an Atom D252, it has a 4core 1.8ghz cpu and 4gb of RAM with dual 1gb nicks built in. I'm running on version 10.7.10,  my question is there any tweaking I should do?   I would think that this box should have NO issues managing this?

13

19.1 Legacy Series / [SOLVED] Aliases not accepting Changes

« on: November 20, 2018, 12:52:56 pm »

When I add a new IP to my Whitelist Alias it's not keeping it. I can type it in, hit apply and close and go back in and it's gone.

14

19.1 Legacy Series / [SOLVED] Rules keep wiping themselves out

« on: November 16, 2018, 02:53:34 pm »

If I try to make any Deletes to my Firewall Rules on
Versions    OPNsense 19.1.b_167-amd64
FreeBSD 11.1-RELEASE-p15
OpenSSL 1.0.2p 14 Aug 2018

I was running 18.7.7 and switched up to the Beta.  If I delete an Old rule out it wipes ALL rules out and I have to do a restore configuration to get them back.  I can make changes to the existing rules and it's fine.  It seems to just happen when I delete an existing rule it wipes out all rules.

15

18.7 Legacy Series / IPV6 being blocked?

« on: October 25, 2018, 08:24:06 pm »

I'm getting the following in my Firewall Logs...
   lan      Oct 25 14:18:44   [fe80::6c3a:297e:xxxx:xxxx]:51968   [2001:470:1:18::125]:80   TCP   Default deny rule   

My Lan rules are all Defaulted to normal for IPV6
IPv6 *    LAN net    *    *    *    *       Default allow LAN IPv6 to any rule


I'm confused as to why it is blocking IPV6 on the Lan?

I'm running 18.7.6 so freshly upgraded.  I had IPV6 turned off on the Lan before because it would stop working after a few days and would have to always wind up rebooting everything to get it to clear up, I figured I would try it after the upgrade and I'm seeing this, I've rebooted the firewall as well as the box I'm trying to connect to.