Yes, my usw case just considers one Valve leading outwards that I need to shut and bleed. Don’t need multiple freezing points for hight presure/isolated pipes. One fits all for me. The loop could be modified for those things. Now it is set to “2”. Not even considering °C or °F (°C in my case). Home Assistenten takes care of that
Thinking about it: i guess i should document my Automation a little more. It is checking the next 6 Days for freezing Temperatur not the current
Yeah, half my research ended in system hang reports
Update: ditched the second OpnSense and figured out that MTU discovery with PVE and stuff needs some hard tweeking. Got it to work now. Hit me up for guidance 😅
Should the nginx Proxy receive that package? If i trace between the LAN Host and GW, there are no Public IP’s
I think I let it rest for a day, I’m confused
Hm, could be a little bit much but Public IP -> WG0 -> Proxy -> Router -> Server and back should not be ok?
What? That’s totally confusing. Took my Laptop (192.168.35.242), tethered to my Mobile (192.168.35.116) and wiresharked. 192.168.35.0/24 should never ever be a part of my Network.
Never got the time to learn to read Captures :'(
At a time I tried to use two proxies but I changed it back to one. The host I try to reach is a Docker Host with Immich running. So the only real proxy should be “192.168.1.1”.
There is one DNAT rule at the public OPNsense routing the HTTP/s traffic to my proxy. Inside my DMZ an LAN is no NAT, only routing. Back out again there is a Masq/SNAT rule for my local IPs
green boxes are IP, red are FQDN
Curl capture (made first so DNS is captured aswell)
Firefox capture
I tested with my Mobile with LTE and got the same results
Ah sry, bad choise but i masked my real LAN IPs
That is a sexy loop. I need the heads up 6 days in advance so I am gonna leave it without the index. Gonna update the Post with my current solution.