<div dir="auto"><span style="font-family:sans-serif;font-size:13.696px">Eliezer</span><div dir="auto"><font face="sans-serif"><span style="font-size:13.696px">Thanks for your good advice..<br></span></font><br><div data-smartmail="gmail_signature" dir="auto">Regards<br>Alex<br><a href="http://tech.jahtoe.com">tech.jahtoe.com</a><br><a href="http://bafila.jahtoe.com">bafila.jahtoe.com</a></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 6 Mar 2017 17:30, "Eliezer Croitoru" <<a href="mailto:eliezer@ngtech.co.il">eliezer@ngtech.co.il</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hey Alex,<br>
<br>
First goes first: If you spin any version of CentOS these days I recommend to use CentOS 7 and not 6.<br>
This is also based on many use cases which proved(to me and many others) that the kernel and many other components improved performance.<br>
If you already spinoff a server to mask your IP I believe that the more "perfected" way to do so is using a VPN.<br>
Specifically OpenVPN and a CentOS 7 with pritunl on it as the management web interface for OpenVPN.<br>
The instructions on how to install it are at:<br>
<a href="https://docs.pritunl.com/docs/installation" rel="noreferrer" target="_blank">https://docs.pritunl.com/docs/<wbr>installation</a><br>
<br>
The client can be found at:<br>
<a href="https://openvpn.net/index.php/open-source/downloads.html" rel="noreferrer" target="_blank">https://openvpn.net/index.php/<wbr>open-source/downloads.html</a><br>
<br>
And it would mask your IP address for all of your connections from the machine you are working on.<br>
Notice that some that the reason your IP is not masked is since there are scripts which can run on html5 and can bypass the proxy settings.<br>
<br>
Let me know if you need more help.<br>
<br>
Eliezer<br>
<br>
----<br>
<a href="http://ngtech.co.il/lmgtfy/" rel="noreferrer" target="_blank">http://ngtech.co.il/lmgtfy/</a><br>
Linux System Administrator<br>
Mobile: <a href="tel:%2B972-5-28704261" value="+972528704261">+972-5-28704261</a><br>
Email: <a href="mailto:eliezer@ngtech.co.il">eliezer@ngtech.co.il</a><br>
<br>
<br>
From: squid-users [mailto:<a href="mailto:squid-users-bounces@lists.squid-cache.org">squid-users-bounces@<wbr>lists.squid-cache.org</a>] On Behalf Of Alex Muir<br>
Sent: Monday, March 6, 2017 1:31 PM<br>
To: <a href="mailto:squid-users@lists.squid-cache.org">squid-users@lists.squid-cache.<wbr>org</a><br>
Subject: [squid-users] anonymous squid setup on digital ocean centos 6 but my IP still detected<br>
<br>
<br>
<br>
Greetings,<br>
<br>
I have implemented the following <a href="https://www.digitalocean.com/community/tutorials/how-to-install-squid-proxy-on-centos-6" rel="noreferrer" target="_blank">https://www.digitalocean.com/<wbr>community/tutorials/how-to-<wbr>install-squid-proxy-on-centos-<wbr>6</a> from digital ocean which sets up squid with settings to not have my IP address forwarded.<br>
I'm finding however that my local IP is still detected when I google what my local ip address is. I've configured firefox browser to use the proxy and have confirmed that it is using the proxy. Additionally https goes through the proxy however http is blocked. I'd like to ensure that http is not blocked.<br>
What changes do I need to make to get this working as desired?<br>
Here is the squid config setup:<br>
[root@CENTOSMASTER ~]# cat /etc/squid/squid.conf<br>
#<br>
# Recommended minimum configuration:<br>
#<br>
acl manager proto cache_object<br>
acl localhost src <a href="http://127.0.0.1/32" rel="noreferrer" target="_blank">http://127.0.0.1/32</a> ::1<br>
acl to_localhost dst <a href="http://127.0.0.0/8" rel="noreferrer" target="_blank">http://127.0.0.0/8</a> <a href="http://0.0.0.0/32" rel="noreferrer" target="_blank">http://0.0.0.0/32</a> ::1<br>
<br>
# Example rule allowing access from your local networks.<br>
# Adapt to list your (internal) IP networks from where browsing<br>
# should be allowed<br>
acl localnet src <a href="http://10.0.0.0/8" rel="noreferrer" target="_blank">http://10.0.0.0/8</a> # RFC1918 possible internal network<br>
acl localnet src <a href="http://172.16.0.0/12" rel="noreferrer" target="_blank">http://172.16.0.0/12</a> # RFC1918 possible internal network<br>
acl localnet src <a href="http://192.168.0.0/16" rel="noreferrer" target="_blank">http://192.168.0.0/16</a> # RFC1918 possible internal network<br>
acl localnet src fc00::/7 # RFC 4193 local private network range<br>
acl localnet src fe80::/10 # RFC 4291 link-local (directly plugged) machines<br>
<br>
acl SSL_ports port 443<br>
acl Safe_ports port 80 # http<br>
acl Safe_ports port 21 # ftp<br>
acl Safe_ports port 443 # https<br>
acl Safe_ports port 70 # gopher<br>
acl Safe_ports port 210 # wais<br>
acl Safe_ports port 1025-65535 # unregistered ports<br>
acl Safe_ports port 280 # http-mgmt<br>
acl Safe_ports port 488 # gss-http<br>
acl Safe_ports port 591 # filemaker<br>
acl Safe_ports port 777 # multiling http<br>
acl CONNECT method CONNECT<br>
<br>
#<br>
# Recommended minimum Access Permission configuration:<br>
#<br>
# Only allow cachemgr access from localhost<br>
http_access allow manager localhost<br>
http_access deny manager<br>
<br>
# Deny requests to certain unsafe ports<br>
http_access deny !Safe_ports<br>
<br>
# Deny CONNECT to other than secure SSL ports<br>
#http_access deny CONNECT !SSL_ports<br>
<br>
# We strongly recommend the following be uncommented to protect innocent<br>
# web applications running on the proxy server who think the only<br>
# one who can access services on "localhost" is a local user<br>
#http_access deny to_localhost<br>
<br>
#<br>
# INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS<br>
#<br>
<br>
# Example rule allowing access from your local networks.<br>
# Adapt localnet in the ACL section to list your (internal) IP networks<br>
# from where browsing should be allowed<br>
http_access allow localnet<br>
http_access allow localhost<br>
<br>
# And finally deny all other access to this proxy<br>
http_access deny all<br>
<br>
# Squid normally listens to port 3128<br>
http_port 3128<br>
<br>
# Uncomment and adjust the following to add a disk cache directory.<br>
#cache_dir ufs /var/spool/squid 100 16 256<br>
<br>
# Leave coredumps in the first cache dir<br>
coredump_dir /var/spool/squid<br>
<br>
# Add any of your own refresh_pattern entries above these.<br>
refresh_pattern ^ftp: 1440 20% 10080<br>
refresh_pattern ^gopher: 1440 0% 1440<br>
refresh_pattern -i (/cgi-bin/|\?) 0 0% 0<br>
refresh_pattern . 0 20%<br>
<br>
via off<br>
forwarded_for off<br>
<br>
request_header_access Allow allow all<br>
request_header_access Authorization allow all<br>
request_header_access WWW-Authenticate allow all<br>
request_header_access Proxy-Authorization allow all<br>
request_header_access Proxy-Authenticate allow all<br>
request_header_access Cache-Control allow all<br>
request_header_access Content-Encoding allow all<br>
request_header_access Content-Length allow all<br>
request_header_access Content-Type allow all<br>
request_header_access Date allow all<br>
request_header_access Expires allow all<br>
request_header_access Host allow all<br>
request_header_access If-Modified-Since allow all<br>
request_header_access Last-Modified allow all<br>
request_header_access Location allow all<br>
request_header_access Pragma allow all<br>
request_header_access Accept allow all<br>
request_header_access Accept-Charset allow all<br>
request_header_access Accept-Encoding allow all<br>
request_header_access Accept-Language allow all<br>
request_header_access Content-Language allow all<br>
request_header_access Mime-Version allow all<br>
request_header_access Retry-After allow all<br>
request_header_access Title allow all<br>
request_header_access Connection allow all<br>
request_header_access Proxy-Connection allow all<br>
request_header_access User-Agent allow all<br>
request_header_access Cookie allow all<br>
request_header_access All deny all<br>
<br>
I've posted the question on stackoverflow<br>
<br>
<a href="http://serverfault.com/questions/836385/anonymous-squid-setup-on-digital-ocean-centos-6-but-my-ip-still-detected" rel="noreferrer" target="_blank">http://serverfault.com/<wbr>questions/836385/anonymous-<wbr>squid-setup-on-digital-ocean-<wbr>centos-6-but-my-ip-still-<wbr>detected</a><br>
<br>
Regards<br>
Alex Muir<br>
Chief Data Engineer/Architect<br>
Jahtoe Technology<br>
<a href="http://tech.jahtoe.com" rel="noreferrer" target="_blank">http://tech.jahtoe.com</a><br>
<br>
</blockquote></div></div>