Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
There is less than 2 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
okay, well first i suggest that you look in your squid configuration file 'squid.conf' and check out where your log files go, if they are commented out then remove the '#' and make the log /var/log/squid, then restart squid and see what the log puts out.
i've got a fairly debugging command for squid ... but it's at work and i can't remember it, i think it's something like this ' squid -XNDz' try this, and if that dosn't tell you whats wrong, post the output here and i'll post the command when i get to work tomorrow.
Warning: failed to resolve 127.0.0.1 to a fully qualified in hostname
GetMyHostname: 'Fedserver'resolved into 'Fedserver'
FATA: Could not determine fully qualified hostname. Please set 'visible_hostname'
Squid Cache (Version 2.5.STABLE9): Terminated abnormally.
CPU Usage: 0.046 seconds = 0.019 user + 0.027 sys
Maximum Resident Size: 0 KB
Page Faults with Physical i/o: 0
okay well, not too sure, but go into your /etc/squid/squid.conf file and set your visible hostname setting, then start it failing that, post your squid.conf file on this forum. if you don't know what your FQDN is look in /etc/hosts file
Also you might want to try installing webmin and using the squid module to setup your squid server, webmin is an easy to follow web interface into a lot of servers including squid.
well once again, you've caught me out of the office, i have most of my information in there, i've just hit a weekend so i wont be back in for a couple of days, but i have found a website that might help.
I know i've suggest it before, but try and install webmin! it makes squid management and setup so much easier!
Using the Provided Block Lists
Content blocking is quite simple to use. Using the Webmin tool, you select Servers and then Squid Proxy Server and, finally, Access Control. On this screen you will see three boxes of options. Two are relevant to content blocking, Access Control Lists and Proxy Restrictions.
Access Control Lists are lists of patterns to be matched. It is possible to make matches based on every facet of a web request, but the ones we are interested in for content blocking are URL Regexp and Web Server Regexp. As you can see, several lists are already provided for you. In our example, we will turn on blocking of pornography and pirated software sites. Further, we will "unblock" several sites that would be unjustly blocked by our pattern because they are found at similar URLs but do not contain the questionable content being blocked.
To turn on blocking, you click on Add Proxy Restriction in the Proxy Restrictions options box. This will bring you to a new screen where you can select which list to use for matching. Here you click Deny and choose the porn.block and games.block ACLs. After clicking Save you will be returned to the Access Control page. Also be aware that the order in which ACLs appear in the Proxy Restrictions box is important. The ACL code only reads through the entries until it reaches one that matches. So if an allow rule is in place before the deny rule the allow rule will take precedence. Use the movement arrows on the right side of the Proxy Restriction box to reorder your rules.
Don't forget to add the unblock list for whatever Block Lists you are using to prevent unfair blocking of harmless or educational sites. The unblock list must come before the block list in the Proxy Restrictions list. Use the arrows to reorder again.
The Squid server will need to be restarted by clicking Apply Changes in the upper right hand corner of the page. At this point, blocking should be in place. Test it with your browser by going to a known site that should be blocked, such as http://www.playboy.com, if blocking is working you will receive an Access Denied page from the proxy. This, and all other message pages from the proxy, can be customized for your environment.