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

Topics - jezza007

#1
Hi,

I have setup and got working as per instructions.
I can reach the local LAN and remote sub-nets, and access resources.
Confirming forwarding and NAT are working.
The exit nodes work fine with all Tail-scale clients.

What I would like to do, is add a policy to route the local sub-net 192.168.20.0/24 to the far Tail-net exit node,
This works fine when using wire-guard gateways.

So on the LAN interface I add a rule
Action Pass, any, use remote Gateway 100.90.90.1

I see traffic leaving opnsense tails interface from the subnet device IP, using the opnsense tails Address confirming its nat'ted.
But as soon as I enable the rule to use the remote gateway it cant reach the internet, no return traffic

Anyone got this to work, or am I making an error?
#2
Zenarmor (Sensei) / [SOLVED] 24.7.8 update failing
November 09, 2024, 04:54:13 PM
Keep getting this issue when trying to update to 24.7.8
Currently running OPNsense 24.7.7

Tried all mirrors, anyone able to advise why it wont update?
Tried pkg clean -a and pkg update -f

Error here:
85 MiB to be downloaded.
[1/14] Fetching os-sensei-1.18.2.pkg: .......... done
pkg-static: cached package os-sensei-1.18.2: missing or size mismatch, fetching from remote
[2/14] Fetching os-sensei-1.18.2.pkg: ......... done
pkg-static: cached package os-sensei-1.18.2: missing or size mismatch, cannot continue
Consider running 'pkg update -f'
#3
Hi, if someone could help please, I have read the tutorial and successfully setup nginx with letsencrypt and the domain fqdn and base upstream server works perfectly on https://mydomain.com

I am trying to configure a second location which points to a second internal web service with a subfolder of the primary domain
https://mydomain.com/filemanger to point to another upstream server on https://192.168.1.5/

I have configured the second upstream location with (see screenshot)
URL pattern /filemanager/
path prefix /

so that when get https://mydomain.com/filemanager/ it directs to https://192.168.1.5/
It seems to start to load the page but then gets a 500 gateway timeout

Is this the correct way to configure for subfolders?
Thank you


#4
Hi,

I am stuck, I have to do an interim upgrade to 22.1.10_4 before it will allow upgrade to 22.7

I have a QEMU/KVM using virtio interface adapter with no vlans, there are no parent interfaces to add as I am not using vlans (per the solutions I have read).
I have also checked Hardware CRC, TSO, LRO is disabled, and VLAN hardware filtering is set to default as per forum articles I have read.

I have reverted to previous version on failure to reattempt. On one such attempt it successfully upgraded to 22.1.10_4 and I was able to logon to the web-gui, and internet worked for a few minutes then it stopped working.

Any help appreciated on which log files I need to check or how to determine what is happening?