Hi Team,

i used fedora 6 in the year 2007. in that i configured squid for internet access, bandwidth management etc. there was thousand of lines in squid.conf like delay pools, etc etc.

today i want to configure the squid once again for my other client.
i installed fc14 as i like it a lot.
but the squid.conf have very limited lines in that...

can any one help me in this regard.. why the lines are less....or the path is different... any help will be highly appreciable...

in fc6 everything is clear as it was in squid.conf itself...
what should i do...

reg,
jaten.

Both Squid and Fedora have changed a lot since 2007. Probably the easiest way to configure Squid now is to use the Squid configuration FAQ as a guide

That's not an adequate reason. FC14 (laughlin) was released in late 2010. While, for anything, there is the question whether it has current support, for Fedora this is worse because it is deliberately a fast-moving distro that doesn't have the testing (and therefore lack of bugs) that an enterprise distro gets. Some people say that this makes it particularly good for a desktop, but what is clear is that it does nothing to help ion the scenario which you are presenting because it doesn't have the extended support period, so you are going to have to keep updating in order to get support.

Wouldn't something like Centos, which does have extended support periods and does get more thorough testing be more appropriate?

I don't know what this '...my other client...' is; it seems that, if this is relevant, you should have explained something about your network architecture, but maybe it is just not relevant.

This is the first time that I've heard anyone complain that squid.conf doesn't have enough lines in it! The only thing that I can think is that Fedora have chosen to build a cut down version, which only has the major functionality and which does away with some of the fripperies (optional items). This would, therefore, need less configuring and fewer lines in squid.conf.

If it is true that your squid doesn't have the optional functionality, there is nothing that you can do with squid.conf to put that functionality back.

Are you saying that the path to squid is different, or the path to squid.conf is different, or something else entirely. If you could list the old path and the new path maybe someone could have a go at guessing why the change has (or hasn't) occurred, but really the more significant question seems to be 'Can you work with what you've got?' which, I would have thought, would have been the case, if you actually know the paths that you've got.

hi,

if you are looking for sample squid.conf file to use and modify. I guess it's available in /usr/share/doc/squid.XXXX.conf. i use CentOS. i never used fedora much. try

I don't know if it works or not but give a trail.

Post your default fedora squid.conf that you are not satisfied with, so we can see what is missing there.

#
# Recommended minimum configuration:
#
acl manager proto cache_object
acl localhost src 127.0.0.1/32 ::1
acl to_localhost dst 127.0.0.0/8 0.0.0.0/32 ::1

# Example rule allowing access from your local networks.
# Adapt to list your (internal) IP networks from where browsing
# should be allowed
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 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 manager localhost
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
"squid.conf.default" 74L, 2425C

Ok now , what do you want to achieve? What do you want to work and what not?