Messages

i have tryied the documentation but it talks about gateways and all sorts or stuff that i dont really understand. i tried following the instructions but i couldnt get it to work.

Hi

So im trying to set up "remote Tunneled accees" as defined here: https://forums.unraid.net/topic/84226-wireguard-quickstart/.

But i need to create a static route for this:  "Remark: configure your router with a static route of 10.253.0.0/24 to 192.168.2.193"

i have looked the the forum/documentation but i cant really find an answer for what i need. can any tell me what i need to do to get this fixed.

Hi

So i run Adguard through a docker and since installation of Opensence it has never worked right I'm having frequent outages.  I have no idea what's causing the issues but this is Opnsense and most likely me being a moron and missing an option... can someone help...
All my DNS options are right from what I can see, there is nothing being blocked in the firewall just a "timeout" message from Adguard. The weird thing is Adgaurd is "working" for the most part but keep getting this issue. I have also noticed intermittent slow speeds on my phone since the move not sure if this is somehow related....
I will also mention If i change an option in adguard it works for the fors 30 seconds then goes back to timeout. 


So my setup is

FTTP Modem> opensence Vm 10g nic > Wax203 netgear wifi/Switch > unraid 2.5g Switch > Adguard Docker

All cables are fine, so I really cant think of an issue


Opnsense is running in a VM on Unraid


https://imgur.com/a/xzL3LOW

It was likely returning IPv6 addresses from the DNS lookup and trying to use them.

If you don't have IPv6 on your WAN, then it will likely not work.

Glad to hear you got it sorted.

This worked for me, I was playing with IPV6 on lan and wan and it was causing outages and speed issues. Turned them off and BOOM! back up to 1gbp

Hi

Can somone help me, i have a binhex-quibittorrent running though openVPN but im unable to access the gui of my torrent on my lan. I have tried setting up a lan rules so allow traffic to and from port 8080 but nothing seems to be working.
I have tried changing the ports but it isnt working either.

https://imgur.com/a/S7ekdsT

i will say also i was using the "official" NPM I moved to the unofficial one which uses 1801 and 1443 instead of the normal ports.

Im not sure if this or the Wi-Fi rule helped but it this point I don't care as its finally working as intended.

So After everything i needed a separate Wan rule to open the ports as the automatic one just want cutting it!

ok  i think im onto something, i have set all my Subsomains up as Conical names on DYNU. It is the subdomains having issues getting through the wall. Its also saying timeout so I'm not sure if there is a latency issue ?

My physical domain is not having an issue

TBH im giving up, whilst its a nice bit of kit. spending 4 days just trying to get port forwarding to work properly is a joke.
Whatever it is it is 100% opnsense as I've just dialed up openwrt and it works without a hitch.

i did find this but it a lot didn't help me https://www.reddit.com/r/OPNsenseFirewall/comments/mcwqce/port_forwarding_to_nginx_proxy_on_other_server/

I might give myself a go with Swag and see if its just NGPM being awkward but if that doesn't work I will have to close it and move on.

if it helps im getting error 408 now

I turned off the floating Rules and the Nats still nothing, again the only thing that works is resetting the docker but then it dies

doesnt make a diffrence

it wont connect the page jsut tells me it cant complete the request.

but this comes up

all      tcp   192.168.1.193:39402   213.120.42.217:443   192.168.1.100:443   TIME_WAIT:TIME_WAIT   Reflection NAT Rule Webserver 443

maybe the nat reflection is interfering somehow?

There are timeout rules, it's called "states". If a state times out, the connection is closed. That's probably what makes it "look" like ports are closed, even if they are not. You can change the behavior of the OPNsense regarding states. Firewall: Settings: Advanced: Firewall Optimization or Schedule States. But be careful with those.



When you restart NGINX, the states are probably initiated again.

Check "Firewall: Diagnostics: States" and find the "Rule" that allows your port forward. Also look in Firewall: Diagnostics: Sessions" to see if the TCP Sessions Age and Expires is working correctly.

that's all I can find for my https://imgur.com/a/lCLEdV1 "rule" oddly I cant find anything for my specific plan Rule called NGINX

its gone back and ports closing again now:(

Disclosure: I don't do docker nor containers.
That out of the way, what tells you ports are closed, where are the listeners?

Im checking Via DYNU the company that host my domains, they are saying 80 & 443 are closed. Again the "fix" is to restart NGINX . Im not sure why it just decided to close them.. is there a timeout rule I'm missing?