Ticket #3449 (closed defect: fixed)
Isn't the HTTP Proxy Port# field supposed to set the proxy port clients are supposed to use?
|Reported by:||bzflaglegomaniac@…||Owned by:||jamor@…|
|Severity:||normal||Keywords:||squid proxy port denied|
I wanted to set the port to 6000, so I set it as such and saved. Looking at the GUI later, it says it's 6000, but no client can access the Proxy server on that port. The firewall log says it's dropping them.
Looking at Rules Added By Zentyal Services (Advanced), I see: Input HTTP Proxy -m state --state NEW -i eth0 -p tcp --dport 3129 ACCEPT
Input HTTP Proxy -m state --state NEW -p tcp --dport 6000 DROP Input HTTP Proxy -m state --state NEW -i wlan0 -p tcp --dport 3129 ACCEPT NAT prerouting HTTP Proxy -i eth0 ! -d 192.168.0.200 -p tcp --dport 80 REDIRECT --to-ports 3129
192.168.0.200 is the Zentyal server.
Correct me if I'm wrong, but doesn't the second line explicitly DROP anything on port 6000?
On a hunch, I changed the proxy port on the clients to 3129 and it works, but I'd still like it to be 6000 so I'll remember it more easily.
I went to the Module Status page and removed HTTP Proxy and saved. I then went to the Rules Added By Zentyal Services (Advanced) page and confirmed that the above rules were removed. I then checked the HTTP Proxy/General? page and confirmed that still lists the port at 6000. Going back to Module Status, I re-added HTTP Proxy and checked the Rules Added By Zentyal Services (Advanced) page and confirmed that the rules listed above were re-added and the clients still cannot connect on 6000 but can on 3129.
Am I wrong in expecting that the HTTP Proxy/General? Port field is supposed to specify the port on which client proxy connections are accepted and not denied?
This is on Core version 2.2.3, updated 2 days ago with no pending updates.