Quote:
Originally Posted by dellthinker
Code:
http_port 127.0.0.1:3128
httpd_accel_host virtual
httpd_accel_port 80
httpd_accel_with_proxy on
httpd_accel_uses_host_header on
cache_effective_user squid
cache_effective_group squid
These are the changes that i read in the tutorial at the site i provided in my earlier post. The machine im running squid on is apart of a LAN that has 14 other computers connected to it via Eth/Wifi. Other than that its pretty straight forward. If anyone needs me to provide any other info to help me solve this problem just ask.
P.S. Should i use the machines DHCP assigned IP Address or the default 127.0.0.1 IP?
Thanx in advance! |
If you want people to read it, include a link. Otherwise, it doesn't exist (for me). And even then, I might not read it.
Code:
http_port 127.0.0.1:3128
# TAG: http_port
# Usage: port [options]
# hostname:port [options]
# 1.2.3.4:port [options]
#
# The socket addresses where Squid will listen for HTTP client
# requests. You may specify multiple socket addresses.
# There are three forms: port alone, hostname with port, and
# IP address with port. If you specify a hostname or IP
# address, Squid binds the socket to that specific
# address. This replaces the old 'tcp_incoming_address'
# option. Most likely, you do not need to bind to a specific
# address, so you can use the port number alone.
#
# If you are running Squid in accelerator mode, you
# probably want to listen on port 80 also, or instead.
#
# The -I command line option will override the *first* port
# specified here.
#
# You may specify multiple socket addresses on multiple lines.
...etc
I've always used the 'real' address of the machine (rather than the loopback address of 127.0.0.1, assuming that using the loopback address might end up with the packets traversing firewalls twice and that this might have an efficiency impact, but, I have ot admit, I'm not really that sure.
Code:
cache_effective_user squid
cache_effective_group squid
# TAG: cache_effective_user
# If you start Squid as root, it will change its effective/real
# UID/GID to the user specified below. The default is to change
# to UID to nobody. If you define cache_effective_user, but not
# cache_effective_group, Squid sets the GID to the effective
# user's default group ID (taken from the password file) and
# supplementary group list from the from groups membership of
# cache_effective_user.
#
#Default:
# cache_effective_user squid
seems reasonable, given that running services as root is a security problem waiting to happen (its still a potential security problem on a home network, just not one that you necessarily have to take seriously)...you might want to set up the squid account manually so that you know the password so that, if you need to debug, you can run squid manually
# TAG: cache_effective_group
# If you want Squid to run with a specific GID regardless of
# the group memberships of the effective user then set this
# to the group (or GID) you want Squid to run as. When set
# all other group privileges of the effective user is ignored
# and only this GID is effective. If Squid is not started as
# root the user starting Squid must be member of the specified
# group.
#
#Default:
# none
also seems reasonable
The others I can't currently comment on as this box only has 2.7 available to it and the config directives have changed between the 2.x series and the 3.x series. (So, you should say what your squid version is, because some of those directives clearly won't work on versions that don't recognise them.)
