Someone else got me pointed in the right direction and I finally found that setting. It's all working now as I expected it to.
----- Original Message ----- From: Steve Yates [mailto:[email protected]] To: [email protected],[email protected] Sent: Tue, 14 Feb 2017 20:38:53 +0000 Subject: RE: [pfSense] small problem with squid If I'm following, you're using a public IP:port. Did you set up NAT Reflection? (System/Advanced/Firewall & NAT) -- Steve Yates ITS, Inc. -----Original Message----- From: List [mailto:[email protected]] On Behalf Of Steve Berg Sent: Monday, February 13, 2017 3:45 PM To: [email protected] Subject: [pfSense] small problem with squid Just set up a new pfsense box, my own hardware running the latest release, 2.3.2-RELEASE-p1. So far it's been pretty smooth but I just ran into one glitch I can't quite figure out. I've got two NAT rules that redirect incoming ports 80xx and 80xy to two different web servers internal to my network. My external IP is resolved using DynDNS and everything works nicely from my iPad when I'm off the local network. But using the same hostname:port when I'm connected to the WiFi I get no response and the squid Real Time page shows a "TCP_DENIED/403" entry for one of the systems, and "TCP_MISS_ABORTED/000" for the other. Using the local IP when on the WiFi works as expected and I see 13.02.2017 15:43:00 10.x.x.x TCP_MISS/200 http://10.x.x.x/path/to/webpage - 10.x.x.x I'm fairly new to pfsense and squid so I've probably missed something simple but I'd appreciate a tip or pointer to where to go to fix this issue. _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
