Messages

1

Zenarmor (Sensei) / Re: Upgrading to 22.1

« on: January 19, 2022, 05:21:42 pm »

This is correct. You can switch to "community" type now. The linker.hints file issue is with the FreeBSD build and a workaround has been added to the kernel build tools for 22.1.r2.


Cheers,
Franco

That's great thanks so much for your help Franco!! Okay so I'm back on the "community" type now and just to confirm 22.1.r1 is the latest community build?
Thanks again,Andy

2

Zenarmor (Sensei) / Re: Upgrading to 22.1

« on: January 19, 2022, 05:09:43 pm »

Good news! It appears removing os-sunnyvalley allowed my OPNsense instance to 'fully' upgrade to 22.1.r3.
However now it's doing something strange and appears to be in a loop (see attached screenshot).
I have applied the 22.1.r1 'update' as seen in the screenshot twice already but once the instance comes back online after applying it and I check for updates again, the same 22.1.r1 'update' shows despite being on .r3
Also this is the result of a Health Check Audit:

Code: [Select]

***GOT REQUEST TO AUDIT HEALTH***
Currently running OPNsense 22.1.r_3 (amd64/OpenSSL) at Thu Jan 20 00:04:47 AWST 2022
>>> Check installed kernel version
Version 22.1.r1 is correct.
>>> Check for missing or altered kernel files
Error 2 ocurred.
boot/kernel/linker.hints:
    size (374752, 375104)
    sha256digest (0x906322a5e39d85471ecbb57b94034c3703d6594ea034074c7219512a3d862604, 0xbc72238d15ac7afba505851dd89b7c301ba39bb39e463c48f4469074e4c0f957)
>>> Check installed base version
Version 22.1.r1 is correct.
>>> Check for missing or altered base files
No problems detected.
>>> Check for missing package dependencies
Checking all packages: .......... done
>>> Check for missing or altered package files
Checking all packages: .......... done
>>> Check for core packages consistency
Core package "opnsense-devel" has 65 dependencies to check.
Checking packages: ................................................................... done
***DONE***

3

Zenarmor (Sensei) / Re: Upgrading to 22.1

« on: January 19, 2022, 04:16:52 pm »

Did you move via beta to 22.1? Try reinstalling os-sunnyvalley, I think it couldn't be reapplied(yet). Your main mirror URL looks fine (22.1).

Oops sorry for the thread hopping, I shall stay here  .
No beta, I went from 21.7.7 -> 22.1.r1 (or so I thought lol  ).
No joy with reinstalling os-sunnyvalley, looks like my OPNsense instance has really screwed the pooch lol:

Code: [Select]

***GOT REQUEST TO REINSTALL***
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
Updating SunnyValley repository catalogue...
pkg-static: https://updates.sunnyvalley.io/opnsense/FreeBSD:13:amd64/21.7/OpenSSL/latest/meta.txz: Not Found
repository SunnyValley has no meta file, using default settings
pkg-static: https://updates.sunnyvalley.io/opnsense/FreeBSD:13:amd64/21.7/OpenSSL/latest/packagesite.txz: Not Found
Unable to update repository SunnyValley
Error updating repositories!
Checking integrity... done (0 conflicting)
Nothing to do.
***DONE***Shall I just reinstall a fresh 22.1 instance and restore from a 21.7.7 backup? Or have you anymore tricks up your sleeve to try. I'm also happy to provide any relevant logs as a means of understanding why this may have happened and to avoid it happening again to other users.

4

Zenarmor (Sensei) / Re: Upgrading to 22.1

« on: January 19, 2022, 03:41:18 pm »

It shouldn't point you to "21.7" so that means your upgrade was only partial. Check /var/cache/opnsense-update/.upgrade.log


Cheers,
Franco

Thanks Franco. I'm not sure how it got in this state, perhaps I didn't switch from community to development image properly?? Am I correct in just simply changing 'type' to development, hitting save, rebooting and then searching for updates? If so that process seemed to complete successfully.

5

Zenarmor (Sensei) / Re: Zenarmor 1.10.1 is out

« on: January 19, 2022, 12:04:13 pm »

Hi there, please can I have some assistance changing over to the new repo that is compatible with 22.1? Whenever I check for firmware & package updates I'm always met with "Could not find the repository on the selected mirror."
Thanks.

Code: [Select]

***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 22.1.b_141 (amd64/OpenSSL) at Wed Jan 19 19:01:04 AWST 2022
Fetching changelog information, please wait... done
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.txz: .......... done
Processing entries: .......... done
OPNsense repository update completed. 777 packages processed.
Updating SunnyValley repository catalogue...
pkg: https://updates.sunnyvalley.io/opnsense/FreeBSD:13:amd64/21.7/OpenSSL/latest/meta.txz: Not Found
repository SunnyValley has no meta file, using default settings
pkg: https://updates.sunnyvalley.io/opnsense/FreeBSD:13:amd64/21.7/OpenSSL/latest/packagesite.txz: Not Found
Unable to update repository SunnyValley
Error updating repositories!
Checking integrity... done (0 conflicting)
Your packages are up to date.
***DONE***

6

Zenarmor (Sensei) / Re: Upgrading to 22.1

« on: January 19, 2022, 12:01:31 pm »

Hi,

22.1 repo for Zenarmor is published. Maybe you can try it.

Hi there, please can I have some assistance changing over to the new repo that is compatible with 22.1? Whenever I check for firmware & package updates I'm always met with "Could not find the repository on the selected mirror."
Thanks.

Code: [Select]

***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 22.1.b_141 (amd64/OpenSSL) at Wed Jan 19 19:01:04 AWST 2022
Fetching changelog information, please wait... done
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.txz: .......... done
Processing entries: .......... done
OPNsense repository update completed. 777 packages processed.
Updating SunnyValley repository catalogue...
pkg: https://updates.sunnyvalley.io/opnsense/FreeBSD:13:amd64/21.7/OpenSSL/latest/meta.txz: Not Found
repository SunnyValley has no meta file, using default settings
pkg: https://updates.sunnyvalley.io/opnsense/FreeBSD:13:amd64/21.7/OpenSSL/latest/packagesite.txz: Not Found
Unable to update repository SunnyValley
Error updating repositories!
Checking integrity... done (0 conflicting)
Your packages are up to date.
***DONE***

7

General Discussion / Re: Strict NAT Gaming - Enable UPNP plugin the way to go?

« on: June 28, 2021, 04:20:53 pm »

upnp should work for you. If both your sons play the same game at the same time this may pose a problem with with keeping an open NAT.

Can I please have some assistance, as this is precisely the problem I am facing with Call of Duty Cold War on both my PS5 & PC. I have just posted a thread about it here https://forum.opnsense.org/index.php?topic=23709.0 in more detail.

8

General Discussion / UPnP Gaming - NAT Reflection Issues?

« on: June 28, 2021, 03:02:40 pm »

Hi there, I've been pulling my hair out these last few days trying to get multiple devices that share the same forwarded ports to function simultaneously. After doing some research, this is certainly an issue many others have experienced, however their solutions either just don't work, or the thread dies...

To clarify, one device (say PC for example) is able to connect to the Call of Duty servers with an Open NAT, however a second device (PS5 for example) cannot connect at all.

Some examples of others experiencing this same problem:
https://forum.opnsense.org/index.php?topic=17855.0
https://www.reddit.com/r/OPNsenseFirewall/comments/av1t3w/upnp_problems_gaming/

My Setup:
PC - 192.168.1.12
PS5 - 192.168.100.16
Online Game - Call of Duty: Black Ops Cold War
Port required - 3074

I've setup the UPnP plugin within OPNsense with the following settings https://imgur.com/a/pLpN7Fh (I will refine/secure the ports when everything is working).

• The PC operates on LANBridge interface
  
• The PS5 operates on the Switch interface
  

As per others' recommendations, I have setup NAT > Outbound settings as follows: https://imgur.com/a/1lFKm12 AND ensured that NAT Reflection is enabled as seen here: https://imgur.com/a/7uHkBWw

Can someone with more knowledge than myself please assist. I feel like it shouldn't be this difficult, but I can't think what else to try...

Thank you  .