Messages

1

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

« on: February 27, 2024, 04:16:58 pm »

While I appreciate your Sarcasm.. I also thank you for the fix... I was in the middle of searching the forums after posting this.  Thank you for the help.

2

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

3

22.1 Legacy Series / Re: GeoIP Error - with Update_tables

« on: April 18, 2022, 06:19:16 pm »

it's working fine now mine updated

4

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)

5

21.1 Legacy Series / Re: Traffic graph widget not working anymore after 21.1.2 update

« on: March 09, 2021, 01:38:54 pm »

@Fright that worked for me I just tested it and now my FFox is fine.

Doesn't work for me Firefox 86.0 @ Linux Debia

can you try
# opnsense-patch 4053952
?

6

21.1 Legacy Series / Re: New traffic widget broken in Firefox

« on: February 24, 2021, 06:55:07 pm »

Mine are blank in Ffox as well.

7

20.7 Legacy Series / Re: Default deny rule dispite having Rule to allow

« on: December 11, 2020, 09:10:30 pm »

Did you turn off the Block Private network on the LAN side if it's using a private network of 172.19.0.0   Interfaces/Lan/ there is a block bogon and block private network option.  Not sure if this helps.

Not sure if it's relevant as well but it could be that you need to setup the 172 network in the Virtual IP's so that it knows it's a relevant LAN network.

8

20.7 Legacy Series / Re: Firewall Live View filtering

« on: July 28, 2020, 07:19:33 pm »

change to SRC and Contains whatever ip should get what you want

9

20.1 Legacy Series / Re: WAN Port slow

« on: April 14, 2020, 10:08:29 pm »

I run a https://www.dell.com/us/en/business/servers/poweredge-r210/pd.aspx?refid=poweredge-r210&cs=04&s=bsd that I found on Ebay they are older servers but they run great, I'm on 1gb and I normally have about 940mb throughput

10

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

« on: March 10, 2020, 06:13:12 pm »

So apparently I thought it was my Velops causing it, but it's started up again, so not sure what's causing those?

11

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

« on: March 10, 2020, 01:44:18 pm »

Apparently this was my Linksys Velop System causing this, as it was stuck in an online/offline state.   Once I rebooted the Velop system (they are in bridge mode and only serve as WAPs) the errors cleared up.  Odd but I guess I'm not shocked lol

12

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

13

20.1 Legacy Series / Re: Strange DNS lookups from firewall

« on: February 13, 2020, 03:41:08 pm »

Looks like per - https://github.com/opnsense/docs/blob/master/source/manual/how-tos/dnscrypt-proxy.rst

You have to add your LAN ip to the listening port as well at the bottom of the page -----
Now change to Services->DNSCrypt-Proxy->Configuration and add your Local LAN IP address to the Listen Address field, e.g. 192.168.2.1:53.

Optionally you can set :53 to listen on all addresses like the default behaviour in Unbound.

14

20.1 Legacy Series / Re: Strange DNS lookups from firewall

« on: February 13, 2020, 03:34:50 pm »

ArminF did you tick the box that says Enable DNSCYRPT-Proxy at the very top?

Also did you fill out the Server list section at the bottom... IE I have Cloudflare and quad9-doh-ip4-filter-pri

15

20.1 Legacy Series / Re: Strange DNS lookups from firewall

« on: February 13, 2020, 03:30:21 pm »

ArminF did you tick the box that says Enable DNSCYRPT-Proxy at the very top?