"
Hello OPNsense Community,
I'm experiencing a peculiar issue with my OPNsense setup and would greatly appreciate any insights or advice you can offer.
Background:
Recently, my ISP had a downtime of about 4 hours. Once the service was restored, I noticed that I could no longer access my locally hosted services from the outside. These services are hosted on my home network and I use Cloudflare with a dynamic DNS setup to keep my WAN IP updated.
Current Status:
Cloudflare's configuration seems to be in order, and my WAN IP is correctly updated there.
I can successfully ping my services from within my network.
No changes were made to my local OPNsense configuration during this period.
Configuration Details:
My services are hosted on an internal server with the IP address 192.168.3.19.
The relevant ports (HTTP 80 and HTTPS 443) are forwarded in OPNsense to this IP.
Firewall rules are in place to allow incoming traffic on these ports.
Relevant Log Entries:
Here are some log entries from OPNsense that seem to indicate correct NAT and firewall configurations:
```
rdr log on vtnet1 inet proto tcp from any to (vtnet1) port = https -> 192.168.3.19 port 443
rdr log on vtnet1 inet proto tcp from any to (vtnet1) port = http -> 192.168.3.19 port 80
```
And the firewall rules:
```
pass in log quick on vtnet1 reply-to (vtnet1 109.89.65.1) inet proto tcp from any to 192.168.3.19 port = https
pass in log quick on vtnet1 reply-to (vtnet1 109.89.65.1) inet proto tcp from any to 192.168.3.19 port = http
```
Question:
Could the change in WAN IP due to the ISP downtime have influenced OPNsense in a way that disrupted the NAT/Firewall settings? Is there a known issue or a potential configuration oversight that could cause this kind of access problem post-ISP downtime?
Any help or guidance on what might have gone wrong or what I should check next would be immensely appreciated.
Thank you in advance for your time and assistance!
I'm experiencing a peculiar issue with my OPNsense setup and would greatly appreciate any insights or advice you can offer.
Background:
Recently, my ISP had a downtime of about 4 hours. Once the service was restored, I noticed that I could no longer access my locally hosted services from the outside. These services are hosted on my home network and I use Cloudflare with a dynamic DNS setup to keep my WAN IP updated.
Current Status:
Cloudflare's configuration seems to be in order, and my WAN IP is correctly updated there.
I can successfully ping my services from within my network.
No changes were made to my local OPNsense configuration during this period.
Configuration Details:
My services are hosted on an internal server with the IP address 192.168.3.19.
The relevant ports (HTTP 80 and HTTPS 443) are forwarded in OPNsense to this IP.
Firewall rules are in place to allow incoming traffic on these ports.
Relevant Log Entries:
Here are some log entries from OPNsense that seem to indicate correct NAT and firewall configurations:
```
rdr log on vtnet1 inet proto tcp from any to (vtnet1) port = https -> 192.168.3.19 port 443
rdr log on vtnet1 inet proto tcp from any to (vtnet1) port = http -> 192.168.3.19 port 80
```
And the firewall rules:
```
pass in log quick on vtnet1 reply-to (vtnet1 109.89.65.1) inet proto tcp from any to 192.168.3.19 port = https
pass in log quick on vtnet1 reply-to (vtnet1 109.89.65.1) inet proto tcp from any to 192.168.3.19 port = http
```
Question:
Could the change in WAN IP due to the ISP downtime have influenced OPNsense in a way that disrupted the NAT/Firewall settings? Is there a known issue or a potential configuration oversight that could cause this kind of access problem post-ISP downtime?
Any help or guidance on what might have gone wrong or what I should check next would be immensely appreciated.
Thank you in advance for your time and assistance!
