Re: [squid-users] Access regulation with multiple outgoing IPs

2015-10-25 Thread Amos Jeffries
On 26/10/2015 4:28 a.m., rudi wrote:
> Hey Amos,
> 
> thank you very much for your very helpful information. Now i have an access
> control an SSL is fixed too but i had to add port 80 as SSL port to use the
> proxies as https proxy in proxifier.
> 
> One more question. Now i can use the proxies from
> 193.xxx.xxx.x1/255.255.255.xxx. But if i want to use the proxies from a
> virtual machine i can not get access to them. I tried different Ips. Do you
> know what IPs or information i have to add to the acl on top  to get the VMs
> working? Thank you so much!
> 

These do not seem right:

The clients are on network 193
> acl localnet src 193.xxx.xxx.x1/255.255.255.xxx

But Squid is listening and sending with network 178.

> http_port 178.xxx.xxx.x3:3129 name=3129
> acl vm3129 myportname 3129
> tcp_outgoing_address 178.xxx.xxx.x3 vm3129
> 

Hopefully that is enough to resolve your issue. I can't help any further
without the numbers which you are eliding and a lot more details about
the network topology configuration.


PS. Squid uses modern CIDR subnet masks, not the 1970's netmask format.
If the xxx mask bit does not exactly match a CIDR mask it will be mapped
by dropping/0-ing the rightmost mask bits until it does.

Amos

___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users


Re: [squid-users] Access regulation with multiple outgoing IPs

2015-10-25 Thread rudi
Hey Amos,

thank you very much for your very helpful information. Now i have an access
control an SSL is fixed too but i had to add port 80 as SSL port to use the
proxies as https proxy in proxifier.

One more question. Now i can use the proxies from
193.xxx.xxx.x1/255.255.255.xxx. But if i want to use the proxies from a
virtual machine i can not get access to them. I tried different Ips. Do you
know what IPs or information i have to add to the acl on top  to get the VMs
working? Thank you so much!


This is my file with working access regulation and SSL fix:

acl localnet src 10.0.0.0/8 # RFC1918 possible internal network
acl localnet src 172.16.0.0/12  # RFC1918 possible internal network
acl localnet src 192.168.0.0/16 # RFC1918 possible internal network
acl localnet src fc00::/7   # RFC 4193 local private network range
acl localnet src fe80::/10  # RFC 4291 link-local (directly plugged)
machines
acl localnet src 193.xxx.xxx.x1/255.255.255.xxx


acl SSL_ports port 443
acl SSL_ports port 80
acl Safe_ports port 80  # http
acl Safe_ports port 21  # ftp
acl Safe_ports port 443 # https
acl Safe_ports port 70  # gopher
acl Safe_ports port 210 # wais
acl Safe_ports port 1025-65535  # unregistered ports
acl Safe_ports port 280 # http-mgmt
acl Safe_ports port 488 # gss-http
acl Safe_ports port 591 # filemaker
acl Safe_ports port 777 # multiling http
acl CONNECT method CONNECT

#
# Recommended minimum Access Permission configuration:
#

# Only allow cachemgr access from localhost
http_access allow localhost manager
http_access deny manager

# Deny requests to certain unsafe ports
http_access deny !Safe_ports

# Deny CONNECT to other than secure SSL ports
http_access deny CONNECT !SSL_ports


# We strongly recommend the following be uncommented to protect innocent
# web applications running on the proxy server who think the only
# one who can access services on "localhost" is a local user
http_access deny to_localhost

#
# INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS
#

http_port 178.xxx.xxx.x3:3129 name=3129
acl vm3129 myportname 3129
tcp_outgoing_address 178.xxx.xxx.x3 vm3129



# Example rule allowing access from your local networks.
# Adapt localnet in the ACL section to list your (internal) IP networks
# from where browsing should be allowed
http_access allow localnet
http_access allow localhost

# And finally deny all other access to this proxy
http_access deny all

# Squid normally listens to port 3128
#http_port 3128


Best regards
Manuel



--
View this message in context: 
http://squid-web-proxy-cache.1019090.n4.nabble.com/Access-regulation-with-multiple-outgoing-IPs-tp4673900p4673906.html
Sent from the Squid - Users mailing list archive at Nabble.com.
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users


[squid-users] Access regulation with multiple outgoing IPs

2015-10-24 Thread rudi
Hey guys, 

im trying to setup squid for windows. I have different IPs on my server and
i want to assign them to VMs:
VM1 --> Outgoing IP1
VM2 --> Outgoing IP2
...

So far this is working! But now i want to deny all other IPs to avoid false
access. So all VMs have the same incoming IP (i think) but the outgoing IP
changes by port. 

Can you help me to set up the access regulation and deny all unwanted
adresses?


acl localnet src 10.0.0.0/8 # RFC1918 possible internal network
acl localnet src 172.16.0.0/12  # RFC1918 possible internal network
acl localnet src 192.168.0.0/16 # RFC1918 possible internal network
acl localnet src fc00::/7   # RFC 4193 local private network range
acl localnet src fe80::/10  # RFC 4291 link-local (directly plugged)
machines


http_port 5.189.xxx.xx1:3129 name=3129
http_port 5.189.xxx.xx2:3130 name=3130

#VM1
acl vm3129 myportname 3129 src 213.xxx.xxx.83/24 
tcp_outgoing_address 5.189.xxx.xx1 vm3129
http_access allow vm3129

#VM2
acl vm3130 myportname 3130 src 213.xxx.xxx.83/24
tcp_outgoing_address 5.189.xxx.xx2 bot3130
http_access allow vm3130


acl SSL_ports port 443
acl Safe_ports port 80  # http
acl Safe_ports port 21  # ftp
acl Safe_ports port 443 # https
acl Safe_ports port 70  # gopher
acl Safe_ports port 210 # wais
acl Safe_ports port 1025-65535  # unregistered ports
acl Safe_ports port 280 # http-mgmt
acl Safe_ports port 488 # gss-http
acl Safe_ports port 591 # filemaker
acl Safe_ports port 777 # multiling http
acl CONNECT method CONNECT

#
# Recommended minimum Access Permission configuration:
#

# Only allow cachemgr access from localhost
http_access allow localhost manager
http_access deny manager

# Deny requests to certain unsafe ports
http_access deny !Safe_ports

# Deny CONNECT to other than secure SSL ports
#http_access deny CONNECT !SSL_ports


# We strongly recommend the following be uncommented to protect innocent
# web applications running on the proxy server who think the only
# one who can access services on "localhost" is a local user
#http_access deny to_localhost

#
# INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS
#

# Example rule allowing access from your local networks.
# Adapt localnet in the ACL section to list your (internal) IP networks
# from where browsing should be allowed
http_access allow localnet
http_access allow localhost
#http_access allow all


# And finally deny all other access to this proxy
http_access deny all

# Squid normally listens to port 3128
#http_port 3128


# Uncomment the line below to enable disk caching - path format is
/cygdrive/, i.e.
#cache_mem 64 MB
#cache_dir aufs /cygdrive/d/squid/cache 4000 16 256


# Leave coredumps in the first cache dir
#coredump_dir /var/cache/squid

# Add any of your own refresh_pattern entries above these.
refresh_pattern ^ftp:   144020% 10080
refresh_pattern ^gopher:14400%  1440
refresh_pattern -i (/cgi-bin/|\?) 0 0%  0
refresh_pattern .   0   20% 4320

dns_nameservers xxx xxx

max_filedescriptors 3200



Thank you for your help!



--
View this message in context: 
http://squid-web-proxy-cache.1019090.n4.nabble.com/Access-regulation-with-multiple-outgoing-IPs-tp4673900.html
Sent from the Squid - Users mailing list archive at Nabble.com.
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users