tag:blogger.com,1999:blog-49384437206029241372014-10-04T22:45:18.615-07:00Linux SpecialistSupport The Linux, Linux Server, Squid, Webserver, dhcp server, smba, print, MrtgMuhammad Imranhttp://www.blogger.com/profile/12158641287038478088noreply@blogger.comBlogger137125tag:blogger.com,1999:blog-4938443720602924137.post-28241998247556808922010-05-07T01:31:00.000-07:002010-05-07T01:32:24.628-07:00Threat Modeling and Risk Management Linux<div style="text-align: justify; font-family: courier new;"><span style="font-weight: bold;"></span><br />Since this book is about building secure Linux Internet servers from the ground up, you’re probably expecting system-hardening procedures, guidelines for configuring applications securely, and other very specific and low-level information. And indeed, subsequent chapters contain a great deal of this.<br />But what, really, are we hardening against? The answer to that question is different from system to system and network to network, and in all cases, it changes over time. It’s also more complicated than most people realize. In short, threat analysis is a moving target.<br />Far from a reason to avoid the question altogether, this means that threat modeling is an absolutely essential first step (a recurring step, actually) in securing a system or a network. Most people acknowledge that a sufficiently skilled and determined attacker[1] can compromise almost any system, even if you’ve carefully considered and planned against likely attack-vectors. It therefore follows that if you don’t plan against even the most plausible and likely threats to a given system’s security, that system will be particularly vulnerable.<br />[1] As an abstraction, the "sufficiently determined attacker" (someone theoretically able to<br />compromise any system on any network, outrun bullets, etc.) has a special place in the<br />imaginations and nightmares of security professionals. On the one hand, in practice such people<br />are rare: just like "physical world" criminals, many if not most people who risk the legal and social<br />consequences of committing electronic crimes are stupid and predictable. The most likely<br />attackers therefore tend to be relatively easy to keep out. On the other hand, if you are targeted<br />by a skilled and highly motivated attacker, especially one with "insider" knowledge or access,<br />your only hope is to have considered the worst and not just the most likely threats.<br />This chapter offers some simple methods for threat modeling and risk management, with real-life examples of many common threats and their consequences. The techniques covered should give enough detail about evaluating security risks to lend context, focus, and the proper air of urgency to the tools and techniques the rest of the book covers. At the very least, I hope it will help you to think about network security threats in a logical and organized way.</div>Muhammad Imranhttp://www.blogger.com/profile/12158641287038478088noreply@blogger.comtag:blogger.com,1999:blog-4938443720602924137.post-12595967924379410292010-05-07T01:28:00.000-07:002010-05-07T01:29:11.131-07:00Change Text on XP Start Button XP TrickStep 1 - Modify Explorer.exe File<br /><br />In order to make the changes, the file explorer.exe located at C:\Windows needs to be edited. Since explorer.exe is a binary file it requires a special editor. For purposes of this article I have used Resource Hacker. Resource HackerTM is a freeware utility to view, modify, rename, add, delete and extract resources in 32bit Windows executables and resource files (*.res). It incorporates an internal resource script compiler and decompiler and works on Microsoft Windows 95/98/ME, Windows NT, Windows 2000 and Windows XP operating systems.<br /><br />get this from h**p://delphi.icm.edu.pl/ftp/tools/ResHack.zip<br /><br />The first step is to make a backup copy of the file explorer.exe located at C:\Windows\explorer. Place it in a folder somewhere on your hard drive where it will be safe. Start Resource Hacker and open explorer.exe located at C:\Windows\explorer.exe.<br /><br />The category we are going to be using is "String Table". Expand it by clicking the plus sign then navigate down to and expand string 37 followed by highlighting 1033. If you are using the Classic Layout rather than the XP Layout, use number 38. The right hand pane will display the stringtable. We’re going to modify item 578, currently showing the word “start” just as it displays on the current Start button.<br /><br />There is no magic here. Just double click on the word “start” so that it’s highlighted, making sure the quotation marks are not part of the highlight. They need to remain in place, surrounding the new text that you’ll type. Go ahead and type your new entry. In my case I used Click Me!<br /><br />You’ll notice that after the new text string has been entered the Compile Script button that was grayed out is now active. I won’t get into what’s involved in compiling a script, but suffice it to say it’s going to make this exercise worthwhile. Click Compile Script and then save the altered file using the Save As command on the File Menu. Do not use the Save command – Make sure to use the Save As command and choose a name for the file. Save the newly named file to C:\Windows.<br /><br /><br />Step 2 – Modify the Registry<br /><br />!!!make a backup of your registry before making changes!!!<br /><br />Now that the modified explorer.exe has been created it’s necessary to modify the registry so the file will be recognized when the user logs on to the system. If you don’t know how to access the registry I’m not sure this article is for you, but just in case it’s a temporary memory lapse, go to Start (soon to be something else) Run and type regedit in the Open field. Navigate to:<br /><br />HKEY_LOCAL_MACHINE\ SOFTWARE\ Microsoft\ Windows NT\ CurrentVersion\ Winlogon<br /><br />In the right pane, double click the "Shell" entry to open the Edit String dialog box. In Value data: line, enter the name that was used to save the modified explorer.exe file. Click OK.<br /><br />Close Registry Editor and either log off the system and log back in, or reboot the entire system if that’s your preference. If all went as planned you should see your new Start button with the revised text.[/b]Muhammad Imranhttp://www.blogger.com/profile/12158641287038478088noreply@blogger.comtag:blogger.com,1999:blog-4938443720602924137.post-55404780838207492572010-04-17T10:06:00.001-07:002010-04-17T10:07:13.366-07:00Single Users vs. Multiusers vs. Network Users<span style="font-weight: bold; font-family: trebuchet ms;">Single Users vs. Multiusers vs. Network Users</span><br /><span style="font-family: trebuchet ms;">Windows was designed according to the “one computer, one desk, one user” vision ofMicrosoft’s</span><br /><span style="font-family: trebuchet ms;">cofounder Bill Gates. For the sake of discussion, I’ll call this philosophy single-user. In this</span><br /><span style="font-family: trebuchet ms;">arrangement, two people cannot work in parallel running (for example) Microsoft Word on the</span><br /><span style="font-family: trebuchet ms;">same machine at the same time. Using Terminal Services in Windows 2000 or Windows XP</span><br /><span style="font-family: trebuchet ms;">allows remote use of one computer from another but is still bound by the single-user paradigm.</span><br /><span style="font-family: trebuchet ms;">The Windows .NET Server products, which are unfinished as of this writing, continue to add</span><br /><span style="font-family: trebuchet ms;">terminal features to enable more than one user to access the server simultaneously.</span><br /><span style="font-family: trebuchet ms;">Linux borrows its philosophy from UNIX. When UNIX was originally developed at Bell</span><br /><span style="font-family: trebuchet ms;">Labs in the early 1970s, it ran on a PDP-7 computer that needed to be shared by an entire</span><br /><span style="font-family: trebuchet ms;">department. It required a design that allowed multiple users to log in to the central machine at</span><br /><span style="font-family: trebuchet ms;">the same time. Various people could edit documents, compile programs, and do other work</span><br /><span style="font-family: trebuchet ms;">at the exact same time. The operating system on the central machine took care of the “sharing”</span><br /><span style="font-family: trebuchet ms;">details, so that each user seemed to have an individual system. This multiuser tradition</span><br /><span style="font-family: trebuchet ms;">continues through today, on other UNIXs as well. And since Linux’s birth in the early 1990s,</span><br /><span style="font-family: trebuchet ms;">it has supported the multiuser arrangement.</span><br /><br /><span style="font-family: trebuchet ms;">Today, the most common implementation of a multiuser setup is to support servers—</span><br /><span style="font-family: trebuchet ms;">systems dedicated to running large programs for use by many clients. Each member of a</span><br /><span style="font-family: trebuchet ms;">department can have a smaller workstation on the desktop, with enough power for day-to-day</span><br /><span style="font-family: trebuchet ms;">work. When they need to do something requiring significantly more CPU power or memory,</span><br /><span style="font-family: trebuchet ms;">they can run the operation on the server.</span><br /><span style="font-family: trebuchet ms;">Linux, Windows 2000, and Windows .NET Server are all capable of providing services</span><br /><span style="font-family: trebuchet ms;">such as databases over the network. Users of this arrangement can be called network users,</span><br /><span style="font-family: trebuchet ms;">since they are never actually logged in to the server but rather send requests to the server. The</span><span style="font-family: trebuchet ms;"> server does the work and then sends the results back to the user via the network. The catch in</span><span style="font-family: trebuchet ms;"> this case is that an application must be specifically written to perform such server/client duties.</span><span style="font-family: trebuchet ms;"> Under Linux, a user can run any program allowed by the system administrator on the server</span><span style="font-family: trebuchet ms;"> without having to redesign that program. Most users find the ability to run arbitrary programs</span><span style="font-family: trebuchet ms;"> on other machines to be of significant benefit.</span>Muhammad Imranhttp://www.blogger.com/profile/12158641287038478088noreply@blogger.comtag:blogger.com,1999:blog-4938443720602924137.post-61932478962045853672010-04-17T10:01:00.000-07:002010-04-17T10:06:03.646-07:00What Is the GNU Public License?<div style="text-align: justify; font-family: trebuchet ms;"><span style="font-weight: bold;">What Is the GNU Public License?</span><br />The most important thing to emerge from the GNU project has been the GNU General Public<br />License (GPL). This license explicitly states that the software being released is free, and that<br />no one can ever take away these freedoms. It is acceptable to take the software and resell it,<br />even for a profit; however, in this resale, the seller must release the full source code, including<span style="font-family: trebuchet ms;"> any changes. Because the resold package remains under the GPL, the package can be distributed</span> free and resold yet again by anyone else for a profit. Of primary importance is the liability clause: The programmers are not liable for any damages caused by their software. More about GNU and the GPL can be found at http://www.gnu.org.<br /><br />It should be noted that the GPL is not the only license used by free software developers<br />(although it is arguably the most popular). Other licenses, such as BSD and Apache, have<br />similar liability clauses but differ in terms of their redistribution. For instance, the BSD license<br />allows people to make changes to the code and ship those changes without having to disclose<br />the added code. (The GPL would require that the added code be shipped.) For more information about other open-source licenses, check out http://www.opensource.org.<br /></div>Muhammad Imranhttp://www.blogger.com/profile/12158641287038478088noreply@blogger.comtag:blogger.com,1999:blog-4938443720602924137.post-90893246534410507852010-04-12T13:55:00.000-07:002010-04-12T14:01:03.112-07:00ISP’s Primary DNS Server Setup Architecture<meta equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 11"><meta name="Originator" content="Microsoft Word 11"><link style="font-family: courier new;" rel="File-List" href="file:///C:%5CDOCUME%7E1%5CIMRAN%5CLOCALS%7E1%5CTemp%5Cmsohtml1%5C03%5Cclip_filelist.xml"><span style="font-size:100%;"><o:smarttagtype style="font-family: courier new;" namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="country-region"></o:smarttagtype><o:smarttagtype style="font-family: courier new;" namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"></o:smarttagtype><o:smarttagtype style="font-family: courier new;" namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"></o:smarttagtype></span><!--[if gte mso 9]><xml> <w:worddocument> <w:view>Normal</w:View> <w:zoom>0</w:Zoom> <w:punctuationkerning/> <w:validateagainstschemas/> <w:saveifxmlinvalid>false</w:SaveIfXMLInvalid> <w:ignoremixedcontent>false</w:IgnoreMixedContent> <w:alwaysshowplaceholdertext>false</w:AlwaysShowPlaceholderText> <w:compatibility> <w:breakwrappedtables/> <w:snaptogridincell/> <w:wraptextwithpunct/> <w:useasianbreakrules/> <w:dontgrowautofit/> </w:Compatibility> <w:browserlevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:latentstyles deflockedstate="false" latentstylecount="156"> </w:LatentStyles> </xml><![endif]--><!--[if !mso]><object classid="clsid:38481807-CA0E-42D2-BF39-B33AF135CC4D" id="ieooui"></object> <style> st1\:*{behavior:url(#ieooui) } </style> <![endif]--><style> <!-- /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} --> </style><!--[if gte mso 10]> <style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;} table.MsoTableGrid {mso-style-name:"Table Grid"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; border:solid windowtext 1.0pt; mso-border-alt:solid windowtext .5pt; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-border-insideh:.5pt solid windowtext; mso-border-insidev:.5pt solid windowtext; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;} </style> <![endif]--> <p class="MsoNormal" style="text-align: center;font-family:courier new;" align="center"><span style="font-size:100%;"><b style="">ISP’s Server Architecture<o:p></o:p></b></span></p> <p class="MsoNormal" style="font-family:courier new;"><span style="font-size:100%;"><b style=""><o:p> </o:p></b></span></p> <p class="MsoNormal" style="font-family:courier new;"><span style="font-size:100%;"><b style="">Primary DNS Server:<o:p></o:p></b></span></p> <table class="MsoTableGrid" style="border: medium none ; border-collapse: collapse;font-family:courier new;" border="1" cellpadding="0" cellspacing="0"> <tbody><tr style=""> <td style="border: 1pt solid windowtext; padding: 0in 5.4pt; width: 6.15in;" valign="top" width="590"> <p class="MsoNormal"><span style="font-size:100%;"><b style="">Partition Table Informtion<o:p></o:p></b></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; padding: 0in 5.4pt; width: 6.15in;color:-moz-use-text-color windowtext windowtext;" valign="top" width="590"> <p class="MsoNormal"><span style="font-size:100%;">Filesystem</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">Size</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">Used Avail Use% Mounted on</span></p> <p class="MsoNormal"><span style="font-size:100%;">/dev/sda1</span><span style=";font-size:100%;" > </span><span style=";font-size:100%;" > </span><span style="font-size:100%;">3.0G</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">667M</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">2.2G</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">24% /</span></p> <p class="MsoNormal"><span style="font-size:100%;">tmpfs</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">252M</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">0</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">252M</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">0% /dev/shm</span></p> <p class="MsoNormal"><span style="font-size:100%;">/dev/sda5</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">102M</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">36M</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">67M</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">36% /boot</span></p> <p class="MsoNormal"><span style="font-size:100%;">/dev/sda7</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">2.4G</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">33M</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">2.2G</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">2% /tmp</span></p> <p class="MsoNormal"><span style="font-size:100%;">/dev/sda2</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">2.0G</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">96M</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">1.8G</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">5% /var<b style=""><o:p></o:p></b></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; padding: 0in 5.4pt; width: 6.15in;color:-moz-use-text-color windowtext windowtext;" valign="top" width="590"> <p class="MsoNormal"><span style="font-size:100%;"><b style="">Packages used for DNS:</b> bind-utils-9.3.1-3, bind-chrootenv-9.3.1-3, bind-9.3.1-3, bind-libs-9.3.1-3.2</span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; padding: 0in 5.4pt; width: 6.15in;color:-moz-use-text-color windowtext windowtext;" valign="top" width="590"> <p class="MsoNormal"><span style="font-size:100%;"><b style="">Configuration file: </b>/etc/named.conf<b style=""><o:p></o:p></b></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; padding: 0in 5.4pt; width: 6.15in;color:-moz-use-text-color windowtext windowtext;" valign="top" width="590"> <p class="MsoNormal"><span style="font-size:100%;"># Copyright (c) 2001-2004 SuSE Linux AG, <st1:place st="on"><st1:city st="on">Nuernberg</st1:city>, <st1:country-region st="on">Germany</st1:country-region></st1:place>.</span></p> <p class="MsoNormal"><span style="font-size:100%;"># All rights reserved.</span></p> <p class="MsoNormal"><span style="font-size:100%;">#</span></p> <p class="MsoNormal"><span style="font-size:100%;"># Author: Frank Bodammer, Lars Mueller <lmuelle@suse.de></lmuelle@suse.de></span></p> <p class="MsoNormal"><span style="font-size:100%;">#</span></p> <p class="MsoNormal"><span style="font-size:100%;"># /etc/named.conf</span></p> <p class="MsoNormal"><span style="font-size:100%;">#</span></p> <p class="MsoNormal"><span style="font-size:100%;"># This is a sample configuration file for the name server BIND 9.</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">It works as</span></p> <p class="MsoNormal"><span style="font-size:100%;"># a caching only name server without modification.</span></p> <p class="MsoNormal"><span style="font-size:100%;">#</span></p> <p class="MsoNormal"><span style="font-size:100%;"># A sample configuration for setting up your own domain can be found in</span></p> <p class="MsoNormal"><span style="font-size:100%;"># /usr/share/doc/packages/bind/sample-config.</span></p> <p class="MsoNormal"><span style="font-size:100%;">#</span></p> <p class="MsoNormal"><span style="font-size:100%;"># A description of all available options can be found in</span></p> <p class="MsoNormal"><span style="font-size:100%;"># /usr/share/doc/packages/bind/misc/options.</span></p> <p class="MsoNormal"><span style="font-size:100%;"><o:p> </o:p></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">options {<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><o:p> </o:p></span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;"># The directory statement defines the name server's working directory</span></p> <p class="MsoNormal"><span style="font-size:100%;"><o:p> </o:p></span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;"><b style="">directory "/var/lib/named";<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><o:p> </o:p></span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;"># Write dump and statistics file to the log subdirectory.</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">The</span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;"># pathenames are relative to the chroot jail.</span></p> <p class="MsoNormal"><span style="font-size:100%;"><o:p> </o:p></span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;"><b style="">dump-file "/var/log/named_dump.db";<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>statistics-file "/var/log/named.stats";<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><o:p> </o:p></span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;"># The forwarders record contains a list of servers to which queries</span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;"># should be forwarded.</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">Enable this line and modify the IP address to</span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;"># your provider's name server.</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">Up to three servers may be listed.</span></p> <p class="MsoNormal"><span style="font-size:100%;"><o:p> </o:p></span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;">#forwarders { 192.0.2.1; 192.0.2.2; };</span></p> <p class="MsoNormal"><span style="font-size:100%;"><o:p> </o:p></span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;"># Enable the next entry to prefer usage of the name server declared in</span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;"># the forwarders section.</span></p> <p class="MsoNormal"><span style="font-size:100%;"><o:p> </o:p></span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;">#forward first;</span></p> <p class="MsoNormal"><span style="font-size:100%;"><o:p> </o:p></span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;"># The listen-on record contains a list of local network interfaces to</span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;"># listen on.</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">Optionally the port can be specified.</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">Default is to</span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;"># listen on all interfaces found on your system.</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">The default port is</span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;"># 53.</span></p> <p class="MsoNormal"><span style="font-size:100%;"><o:p> </o:p></span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;">#listen-on port 53 { 127.0.0.1; };</span></p> <p class="MsoNormal"><span style="font-size:100%;"><o:p> </o:p></span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;"># The listen-on-v6 record enables or disables listening on IPv6</span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;"># interfaces.</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">Allowed values are 'any' and 'none' or a list of</span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;"># addresses.</span></p> <p class="MsoNormal"><span style="font-size:100%;"><o:p> </o:p></span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;"><b style="">listen-on-v6 { any; };<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><o:p> </o:p></span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;"># The next three statements may be needed if a firewall stands between</span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;"># the local server and the internet.</span></p> <p class="MsoNormal"><span style="font-size:100%;"><o:p> </o:p></span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;">#query-source address * port 53;</span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;">#transfer-source * port 53;</span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;">#notify-source * port 53;</span></p> <p class="MsoNormal"><span style="font-size:100%;"><o:p> </o:p></span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;"># The allow-query record contains a list of networks or IP addresses</span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;"># to accept and deny queries from. The default is to allow queries</span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;"># from all hosts.</span></p> <p class="MsoNormal"><span style="font-size:100%;"><o:p> </o:p></span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;">#allow-query { 127.0.0.1; };</span></p> <p class="MsoNormal"><span style="font-size:100%;"><o:p> </o:p></span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;"># If notify is set to yes (default), notify messages are sent to other</span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;"># name servers when the the zone data is changed.</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">Instead of setting</span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;"># a global 'notify' statement in the 'options' section, a separate</span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;"># 'notify' can be added to each zone definition.</span></p> <p class="MsoNormal"><span style="font-size:100%;"><o:p> </o:p></span></p> <p class="MsoNormal"><span style=";font-size:100%;" > </span><span style="font-size:100%;"><b style="">notify no;<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">};<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><o:p> </o:p></span></p> <p class="MsoNormal"><span style="font-size:100%;"># To configure named's logging remove the leading '#' characters of the</span></p> <p class="MsoNormal"><span style="font-size:100%;"># following examples.</span></p> <p class="MsoNormal"><span style="font-size:100%;">#logging {</span></p> <p class="MsoNormal"><span style="font-size:100%;">#</span><span style=";font-size:100%;" > </span><span style="font-size:100%;"># Log queries to a file limited to a size of 100 MB.</span></p> <p class="MsoNormal"><span style="font-size:100%;">#</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">channel query_logging {</span></p> <p class="MsoNormal"><span style="font-size:100%;">#</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">file "/var/log/named_querylog"</span></p> <p class="MsoNormal"><span style="font-size:100%;">#</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">versions 3 size 100M;</span></p> <p class="MsoNormal"><span style="font-size:100%;">#</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">print-time yes;</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">// timestamp log entries</span></p> <p class="MsoNormal"><span style="font-size:100%;">#</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">};</span></p> <p class="MsoNormal"><span style="font-size:100%;">#</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">category queries {</span></p> <p class="MsoNormal"><span style="font-size:100%;">#</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">query_logging;</span></p> <p class="MsoNormal"><span style="font-size:100%;">#</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">};</span></p> <p class="MsoNormal"><span style="font-size:100%;">#</span></p> <p class="MsoNormal"><span style="font-size:100%;">#</span><span style=";font-size:100%;" > </span><span style="font-size:100%;"># Or log this kind alternatively to syslog.</span></p> <p class="MsoNormal"><span style="font-size:100%;">#</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">channel syslog_queries {</span></p> <p class="MsoNormal"><span style="font-size:100%;">#</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">syslog user;</span></p> <p class="MsoNormal"><span style="font-size:100%;">#</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">severity info;</span></p> <p class="MsoNormal"><span style="font-size:100%;">#</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">};</span></p> <p class="MsoNormal"><span style="font-size:100%;">#</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">category queries { syslog_queries; };</span></p> <p class="MsoNormal"><span style="font-size:100%;">#</span></p> <p class="MsoNormal"><span style="font-size:100%;">#</span><span style=";font-size:100%;" > </span><span style="font-size:100%;"># Log general name server errors to syslog.</span></p> <p class="MsoNormal"><span style="font-size:100%;">#</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">channel syslog_errors {</span></p> <p class="MsoNormal"><span style="font-size:100%;">#</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">syslog user;</span></p> <p class="MsoNormal"><span style="font-size:100%;">#</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">severity error;</span></p> <p class="MsoNormal"><span style="font-size:100%;">#</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">};</span></p> <p class="MsoNormal"><span style="font-size:100%;">#</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">category default { syslog_errors;</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">};</span></p> <p class="MsoNormal"><span style="font-size:100%;">#</span></p> <p class="MsoNormal"><span style="font-size:100%;">#</span><span style=";font-size:100%;" > </span><span style="font-size:100%;"># Don't log lame server messages.</span></p> <p class="MsoNormal"><span style="font-size:100%;">#</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">category lame-servers { null; };</span></p> <p class="MsoNormal"><span style="font-size:100%;">#};</span></p> <p class="MsoNormal"><span style="font-size:100%;"><o:p> </o:p></span></p> <p class="MsoNormal"><span style="font-size:100%;"># The following zone definitions don't need any modification.</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">The first one</span></p> <p class="MsoNormal"><span style="font-size:100%;"># is the definition of the root name servers.</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">The second one defines</span></p> <p class="MsoNormal"><span style="font-size:100%;"># localhost while the third defines the reverse lookup for localhost.</span></p> <p class="MsoNormal"><span style="font-size:100%;"><o:p> </o:p></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">zone "." in {<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>type hint;<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>file "root.hint";<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">};<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><o:p> </o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">zone "localhost" in {<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>type master;<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>file "localhost.zone";<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">};<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><o:p> </o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">zone "0.0.127.in-addr.arpa" in {<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>type master;<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>file "127.0.0.zone";<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">};<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><o:p> </o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">zone "ns1" IN {<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>type master;<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>file "master/ns1.zone";<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>allow-transfer {202.125.142.117;};<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">};<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><o:p> </o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">zone "142.125.202.in-addr.arpa" IN {<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>type master;<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>file "master/rns1.zone";<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">};<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span><o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">zone "pucit.edu.pk" IN {<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>type master;<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>file "master/pucitedu.zone";<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">allow-transfer {202.125.142.117;};<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">};<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><o:p> </o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">zone "pucitonline.net" IN {<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>type master;<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>file "master/pucitnet.zone";<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">allow-transfer {202.125.142.117;};<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">};<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><o:p> </o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">zone "mapasha.com" IN {<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>type master;<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>file "master/mapasha.zone";<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">allow-transfer {202.125.142.117;};<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">};<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><o:p> </o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">zone "mtexperts.co.uk" IN {<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>type master;<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>file "master/mtexpert.zone";<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">allow-transfer {202.125.142.117;};<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">};<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><o:p> </o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">zone "agiletechnologies.org" IN {<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>type master;<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>file "master/agile.zone";<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">allow-transfer {202.125.142.117;};<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">};<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><o:p> </o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">zone "ktexperts.com" IN {<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>type master;<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>file "master/ktexperts.zone";<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">allow-transfer {202.125.142.117;};<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">};<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><o:p> </o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">zone "completeislam.com" IN {<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>type master;<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>file "master/cislam.zone";<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">allow-transfer {202.125.142.117;};<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">};<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><o:p> </o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">zone "peace.com.pk" IN {<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>type master;<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>file "master/peace.zone";<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><o:p> </o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">allow-transfer {202.125.142.117;};<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">};<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><o:p> </o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">zone "ghazisolutions.com" IN {<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>type master;<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>file "master/ghazi.zone";<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">allow-transfer {202.125.142.117;};<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">};<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><o:p> </o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">zone "puran.info" IN {<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>type master;<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>file "master/puran.zone";<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">allow-transfer {202.125.142.117;};<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">};<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><o:p> </o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">zone "nms.pucit" IN {<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>type master;<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>file "master/nms.zone";<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">allow-transfer {202.125.142.117;};<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">};<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><o:p> </o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">zone "pucitonline.com" IN {<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>type master;<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>file "master/pucitonline.zone";<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">Allow-transfer {202.125.142.117;};<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">};<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">zone "ngnexporters.com" IN {<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>type master;<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><span style=""> </span>file "master/ngnexporters.zone";<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">Allow-transfer {202.125.142.117;};<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">};<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><o:p> </o:p></span></p> <p class="MsoNormal"><span style="font-size:100%;"># Include the meta include file generated by createNamedConfInclude.</span><span style=";font-size:100%;" > </span><span style="font-size:100%;">This</span></p> <p class="MsoNormal"><span style="font-size:100%;"># includes all files as configured in NAMED_CONF_INCLUDE_FILES from</span></p> <p class="MsoNormal"><span style="font-size:100%;"># /etc/sysconfig/named</span></p> <p class="MsoNormal"><span style="font-size:100%;"><o:p> </o:p></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style="">include "/etc/named.conf.include";<o:p></o:p></b></span></p> <p class="MsoNormal"><span style="font-size:100%;"><o:p> </o:p></span></p> <p class="MsoNormal"><span style="font-size:100%;"># You can insert further zone records for your own domains below or create</span></p> <p class="MsoNormal"><span style="font-size:100%;"># single files in /etc/named.d/ and add the file names to</span></p> <p class="MsoNormal"><span style="font-size:100%;"># NAMED_CONF_INCLUDE_FILES.</span></p> <p class="MsoNormal"><span style="font-size:100%;"># See /usr/share/doc/packages/bind/README.SUSE for more details.<b style=""><o:p></o:p></b></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 6.15in;" valign="top" width="590"> <p class="MsoNormal"><span style="font-size:100%;"><b style="">/var/lib/named/pucitnet<o:p></o:p></b></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 6.15in;" valign="top" width="590"> <p class="MsoNormal" style=""><span style="font-size:100%;">$TTL 2D<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;">@ <span style=""> </span>IN<span style=""> </span>SOA<span style=""> </span>ns1.pucitonline.net.<span style=""> </span>root.pucitonline.net. (<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;"><span style=""> </span><span style=""> </span>200312121;<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;"><span style=""> </span>3600;<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;"><span style=""> </span>3600;<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;"><span style=""> </span>3600;<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;"><span style=""> </span><span style=""> </span>1h );<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;"><span style=""> </span>IN<span style=""> </span>NS<span style=""> </span>ns1<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;"><span style=""> </span>IN<span style=""> </span>NS<span style=""> </span>ns2<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;">ns1<span style=""> </span><span style=""> </span>IN<span style=""> </span>A<span style=""> </span>202.125.142.107<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;">ns2<span style=""> </span>IN <span style=""> </span>A<span style=""> </span>202.125.142.117<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;">www<span style=""> </span>IN<span style=""> </span>A<span style=""> </span>202.125.142.121<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;">pucitonline.net.<span style=""> </span><span style=""> </span>IN<span style=""> </span>MX 10<span style=""> </span>mail<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;">mail<span style=""> </span>IN<span style=""> </span>A<span style=""> </span>202.125.142.115<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;">ftp<span style=""> </span>IN<span style=""> </span>A<span style=""> </span>202.125.142.121<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;">radius<span style=""> </span>IN<span style=""> </span>A<span style=""> </span>202.125.142.108<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;">nms<span style=""> </span>IN <span style=""> </span>A<span style=""> </span>202.125.142.108<o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:100%;"><b style=""><o:p> </o:p></b></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 6.15in;" valign="top" width="590"> <p class="MsoNormal" style=""><span style="font-size:100%;"><b style=""><span style="">/var/lib/named/pucitedu</span></b><b style=""><o:p></o:p></b></span></p> </td> </tr> <tr style=""> <td style="border-style: none solid solid; border-color: -moz-use-text-color windowtext windowtext; border-width: medium 1pt 1pt; padding: 0in 5.4pt; width: 6.15in;" valign="top" width="590"> <p class="MsoNormal" style=""><span style="font-size:100%;">$TTL 2D<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;">@ <span style=""> </span>IN<span style=""> </span>SOA<span style=""> </span>ns1.pucitonline.net.<span style=""> </span>root.pucitonline.net. (<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;"><span style=""> </span>200312121;<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;"><span style=""> </span>360;<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;"><span style=""> </span><span style=""> </span>3600;<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;"><span style=""> </span>3600;<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;"><span style=""> </span>1h );<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;"><span style=""> </span>IN<span style=""> </span>NS<span style=""> </span>ns1.pucitonline.net.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;"><span style=""> </span>IN<span style=""> </span>NS<span style=""> </span>ns2.pucitonline.net.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;">ns1<span style=""> </span><span style=""> </span>IN<span style=""> </span>A<span style=""> </span>202.125.142.107<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;">ns2<span style=""> </span>IN <span style=""> </span>A<span style=""> </span>202.125.142.117<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;">www<span style=""> </span>IN<span style=""> </span>A<span style=""> </span>202.125.142.121<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;">pucit.edu.pk.<span style=""> </span>IN<span style=""> </span>MX 10<span style=""> </span>mail<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;">mail<span style=""> </span>IN<span style=""> </span>A<span style=""> </span>202.125.142.122<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;">ftp<span style=""> </span>IN<span style=""> </span>A<span style=""> </span>202.125.146.174<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;">flypucit<span style=""> </span>IN<span style=""> </span>A<span style=""> </span>202.125.142.109<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;">moon<span style=""> </span>IN<span style=""> </span>A<span style=""> </span>202.125.142.97<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;">library<span style=""> </span>IN<span style=""> </span>A<span style=""> </span>202.125.142.112<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;">alumni<span style=""> </span>IN<span style=""> </span>A<span style=""> </span>202.125.142.112<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;">lectures<span style=""> </span>IN<span style=""> </span>A<span style=""> </span>202.125.142.112<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size:100%;"><b style=""><o:p> </o:p></b></span></p> </td> </tr> </tbody></table> <p class="MsoNormal" style="font-family:courier new;"><span style="font-size:100%;"><b style=""><o:p> </o:p></b></span></p> Muhammad Imranhttp://www.blogger.com/profile/12158641287038478088noreply@blogger.comtag:blogger.com,1999:blog-4938443720602924137.post-72563972105224310082010-03-13T00:56:00.000-08:002010-03-13T00:56:25.168-08:00Shamil Bank of Bahrain Job A Brighter Future<a href="http://today-online-jobs.blogspot.com/2010/03/shamil-bank-of-bahrain-job-brighter.html">Shamil Bank of Bahrain Job A Brighter Future</a>Muhammad Imranhttp://www.blogger.com/profile/12158641287038478088noreply@blogger.comtag:blogger.com,1999:blog-4938443720602924137.post-75457432098315574792010-02-17T01:36:00.000-08:002010-02-17T01:46:33.910-08:00Linux Dual Booting Issues troubleshooting<span style="font-weight: bold;">Dual-Booting Issues</span><br />If you are new to Linux, you may not be ready to commit to a complete system when you just<br />want a test drive. All distributions of Linux can be installed on only certain partitions of your<br />hard disk while leaving others alone. Typically, this means allowing Microsoft Windows to<br />coexist with Linux.<br /><br />Because you are focusing on server installations, the text will not cover the details of<br />building a dual-booting system; however, anyone with a little experience in creating partitions<br />on a disk should be able to figure this out. If you are having difficulty, you may want to refer<br />to the installation guide that comes with your distribution or another one of the many available<br />beginner’s guides to Linux.<br /><br />Some quick hints: If a Windows 95 or Windows 98 partition currently consumes an entire<br />hard disk as drive C:, you can use the fips tool to repartition the disk. Simply defragment and<br />then run fips.exe. If you are using Windows NT/2000 with NTFS and have already allocated<br />all the disk with data on each partition, you may have to move data around a bit by hand to<br />free up a partition. Don’t bother trying to shrink an NTFS partition, though; because of its<br />complexity, it doesn’t like being resized, and doing so will lead to corruption.<br /><br />You may find using a commercial tool such as Partition Magic to be especially helpful,<br />because it offers support for NTFS, FAT32, and regular FAT, as well as a large number of<br />other file system types. Its user interface is also significantly nicer than fips.<br />If you’re going to be installing a dual-boot system, install Linux last. If you install<br />Windows last, it will clobber the boot information for your Linux system. If you install Linux<br />last, it will recognize that you have Windows installed and let you choose which one you want<br />to boot by default. Linux gets an “A” for citizenship.<br /><br /><span style="font-weight: bold;">Methods of Installation</span><br />With the improved connectivity and speed of both local area networks and Internet connections,<br />it is becoming an increasingly popular option to perform installations over the network rather<br />than using a local CD-ROM.<br />In general, you’ll find that network installations become important once you’ve decided to<br />deploy Linux over many machines and therefore require a fast installation procedure in which<br />many systems can install at the same time.<br /><br />Typically, server installations aren’t well suited to automation, because each server usually<br />has a unique task; thus, each server will have a slightly different configuration. For example, a<br />server dedicated to handling logging information sent to it over the network is going to have<br />especially large partitions set up for the appropriate logging directories, compared with a file<br />server that performs no logging of its own. (The obvious exception is for server farms where<br />you have large numbers of replicated servers. But even those installations have their nuances<br />that require attention to detail specific to the installation.)<br /><br />Because of this, you will focus exclusively on the technique for installing a system from a<br />CD-ROM. Of course, once you have gone through the process from a CD-ROM, you will find<br />performing the network-based installations to be very straightforward.Muhammad Imranhttp://www.blogger.com/profile/12158641287038478088noreply@blogger.comtag:blogger.com,1999:blog-4938443720602924137.post-50747471723133939302010-02-17T01:32:00.000-08:002010-02-17T01:36:42.977-08:00Using Dump Backup and Restore Linux OS<span style="font-weight: bold;">dump and restore</span><br />The dump tool works by making a copy of an entire file system. The restore tool can then<br />take this copy and pull any and all files from it.<br /><div style="text-align: justify;">To support incremental backups, dump uses the concept of dump levels. A dump level of 0 means a full backup. Any dump level above 0 is an incremental relative to the last time a dump with a lower dump level occurred. For example, a dump level of 1 covers all the changes to the file system since the last level 0 dump, a dump level of 2 covers all of the changes to the file system since the last level 1 dump, and so on—all the way through dump level 9. Consider a case in which you have three dumps: the first is a level 0, the second is a level 1, and the third is also a level 1. The first dump is, of course, a full backup. The second dump (level 1) contains all the changes made since the first dump. The third dump (also a level 1) also has all the changes.<br /><br /></div>The dump utility stores all the information about its dumps in the /etc/dumpdates file.<br />This file lists each backed-up file system, when it was backed up, and at what dump level.<br />Given this information, you can determine which tape to use for a restore. For example, if you<br />perform level 0 dumps on Monday, level 1 incrementals on Tuesday and Wednesday, and then<br />level 2 incrementals on Thursday and Friday, a file that was last modified on Tuesday but got<br />accidentally erased on Friday can be restored from Tuesday night’s incremental backup.<br />A file that was last modified during the preceding week will be on Monday’s level 0 tape.<br /><br /><br /><span style="font-weight: bold;">Using dump</span><br />The dump tool is a command-line utility. It takes many parameters, but the most relevant are<br />as shown in Table 21-2.<br />For example, here is the command to perform a level 0 dump to /dev/st0 of the /dev/hda1<br />file system:<br /><br />[root@scribe /root]# dump -0 -f /dev/st0 /dev/hda1<br /><br /><br /><span style="font-weight: bold;">dump Parameter Description</span><br />– n Specifies the dump level, where n is a number between 0 and 9. For<br />example, –0 would perform a full backup.<br /><br />–b blocksize Sets the dump block size to blocksize, which is measured in kilobytes. If you<br />are backing up many large files, using a larger block size will increase<br />performance. You may need to carefully adjust this to match the capabilities<br />of your tape system.<br /><br />–B count Specifies a number ( count) of records per tape to be dumped. If there is<br />more data to dump than there is tape space, dump will prompt you to insert<br />a new tape.<br /><br />–f filename Specifies a location ( filename) for the resulting dump file. You can make the<br />dump file a normal file that resides on another file system, or you can write<br />the dump file to the tape device. The SCSI tape device is /dev/st0.<br /><br />–u Updates the /etc/dumpdates file after a successful dump.<br /><br />–d density Specifies the density of the tape in bits per inch.<br /><br />–s size Specifies the size of the tape in feet.<br /><br />–a Bypasses all tape-length calculations and writes until an end-of-media signal<br />is returned. This works best for most modern tape drives and is particularly<br />useful for appending data to existing tapes. This is the default mode.<br /><br />–z or –j Compresses each data block. The –z parameter uses zlib compression, while<br /><br />–j uses bzlib. Either option can be immediately followed with a number, if<br />you want to specify the compression level, or white space, if you want to<br />accept the default compression level of 2. Your tape drive must be able to<br />support variable-length blocks to be able to use this feature. If your tape<br />system has hardware compression built in, don’t use both the hardware<br />compression and this option together, or your files will likely increase in size.<br /><br /><span style="font-weight: bold;">Using dump to Back Up an Entire System </span><br />The dump utility works by making an<br />archive of one file system. If your entire system comprises multiple file systems, you need to<br />run dump for every file system. Since dump creates its output as a single, large file, you can<br />store multiple dumps to a single tape by using a nonrewinding tape device.<br />Assuming we’re backing up to a SCSI tape device, /dev/nst0, we must first decide which<br />file systems we’re backing up. This information is in the /etc/fstab file. Obviously, we don’t<br />want to back up files such as /dev/cdrom, so we skip those. Depending on our data, we may or<br />may not want to back up certain partitions (such as swap and /tmp).<br /><br /><br />Let’s assume this leaves us with /dev/hda1, /dev/hda3, /dev/hda5, and /dev/hda6. To<br />back up these to /dev/nst0, compressing them along the way, we would issue the following<br />series of commands:<br />[root@scribe /root]# mt -f /dev/nst0 rewind<br />[root@scribe /root]# dump -0uz -f /dev/nst0 /dev/hda1<br />[root@scribe /root]# dump -0uz -f /dev/nst0 /dev/hda3<br />[root@scribe /root]# dump -0uz -f /dev/nst0 /dev/hda5<br />[root@scribe /root]# dump -0uz -f /dev/nst0 /dev/hda6<br />[root@scribe /root]# mt -f /dev/nst0 rewind<br />[root@scribe /root]# mt -f /dev/nst0 ejectMuhammad Imranhttp://www.blogger.com/profile/12158641287038478088noreply@blogger.comtag:blogger.com,1999:blog-4938443720602924137.post-6498826897537155282010-02-08T11:10:00.000-08:002010-02-08T11:12:29.675-08:00Assembly Language Programming with Linux H33T<b style="color: rgb(0, 51, 0);">Title........</b><span style="color: rgb(0, 51, 0);">: Assembly Language Step-by-Step - Programming with Linux, 3rd Edition</span><br /> <br /> <b style="color: rgb(0, 51, 0);">Author.......</b><span style="color: rgb(0, 51, 0);">: Jeff Duntemann</span><br /> <br /> <b style="color: rgb(0, 51, 0);">Pages........</b><span style="color: rgb(0, 51, 0);">: 648</span><br /> <br /> <b style="color: rgb(0, 51, 0);">Publisher....</b><span style="color: rgb(0, 51, 0);">: Wiley; 3 edition (October 5, 2009)</span><br /> <br /> <b style="color: rgb(0, 51, 0);">Language.....</b><span style="color: rgb(0, 51, 0);">: English</span><br /> <br /> <b style="color: rgb(0, 51, 0);">Format.......</b><span style="color: rgb(0, 51, 0);">: PDF</span><br /><br /><a href="http://www.h33t.com/download.php?id=cf98d0769d7e99ad1afb22abada56fda5a8df1bc&amp;f=Assembly%20Language%20Step-by-Step%20-%20Programming%20with%20Linux%5BIamthebest%5D%5BH33T%5D.torrent"><span style="color: rgb(0, 0, 0); font-weight: bold;">DOWNLOAD TORRENT</span></a><br /><br /><br /> <span style="color: rgb(0, 51, 0);" >The eagerly anticipated new edition of the bestselling introduction to x86 assembly language<br /><br />The long-awaited third edition of this bestselling introduction to assembly language has been completely rewritten to focus on 32-bit protected-mode Linux and the free NASM assembler. Assembly is the fundamental language bridging human ideas and the pure silicon hearts of computers, and popular author Jeff Dunteman retains his distinctive lighthearted style as he presents a step-by-step approach to this difficult technical discipline.<br /><br />He starts at the very beginning, explaining the basic ideas of programmable computing, the binary and hexadecimal number systems, the Intel x86 computer architecture, and the process of software development under Linux. From that foundation he systematically treats the x86 instruction set, memory addressing, procedures, macros, and interface to the C-language code libraries upon which Linux itself is built.<br /><br />Serves as an ideal introduction to x86 computing concepts, as demonstrated by the only language directly understood by the CPU itself<br /><br />Uses an approachable, conversational style that assumes no prior experience in programming of any kind<br /><br />Presents x86 architecture and assembly concepts through a cumulative tutorial approach that is ideal for self-paced instruction<br /><br />Focuses entirely on free, open-source software, including Ubuntu Linux, the NASM assembler, the Kate editor, and the Gdb/Insight debugger.<br /><br />Includes an x86 instruction set reference for the most common machine instructions, specifically tailored for use by programming beginners</span>Muhammad Imranhttp://www.blogger.com/profile/12158641287038478088noreply@blogger.comtag:blogger.com,1999:blog-4938443720602924137.post-20204717637137555152010-01-27T14:24:00.000-08:002010-01-27T14:25:45.379-08:00Fville hack tool for FREE - 2010 window-linux<object height="344" width="425"><param name="movie" value="http://www.youtube.com/v/xsYWJSSjbz8&amp;hl=en_US&amp;fs=1&amp;"><param name="allowFullScreen" value="true"><param name="allowscriptaccess" value="always"><embed src="http://www.youtube.com/v/xsYWJSSjbz8&amp;hl=en_US&amp;fs=1&amp;" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" height="344" width="425"></embed></object>Muhammad Imranhttp://www.blogger.com/profile/12158641287038478088noreply@blogger.comtag:blogger.com,1999:blog-4938443720602924137.post-80958474225740111282010-01-12T03:19:00.000-08:002010-01-12T03:20:43.467-08:00Configuring Disk Quota in Linux<span style="font-weight: bold;">Configuring Quota Settings</span><br />Creating, modifying, and removing quotas on either a per-user or per-group basis is done via<br />the edquota command. In this section, you’ll look at the usage of this command and run through<br />some examples as well. First, some terminology:<br /><br />● Soft Limit This requested limit is placed on a user or group. If the user’s account exceeds<br />the soft limit, a grace period can be imposed as to how long the account can exist over the<br />soft limit. During this time phase, users can be warned that their accounts are over the limit.<br /><br />● Hard Limit This limit is imposed by the operating system and cannot be overrun.<br />Any attempts to write data beyond the hard limit are denied.<br /><br />● Grace Period (Time Limit) When a user’s account exceeds the soft limit, a clock starts<br />tracking. After the grace period expires, the user cannot access the account. The length of<br />this grace period should depend on the environment. A common value is one week. To<br />keep the account from being disabled, the user needs to remove or compress files until his<br />or her disk consumption falls below the soft limitMuhammad Imranhttp://www.blogger.com/profile/12158641287038478088noreply@blogger.comtag:blogger.com,1999:blog-4938443720602924137.post-46576440260662297072010-01-10T06:56:00.000-08:002010-01-10T07:00:35.745-08:00Bind 9 Fedore Setup DNS Server for Squid CashingThis is Sample Configuration for file DNS Server Configuration for<br />Fedora and other linux flavors which use Bind9.<br /><br />1. Configure listen port (as in File)<br />2. Configure Allow Query (as in File)<br />2. Configure Forwarders (as in file)<br /><br />you can also just copy and past this script in your Named.conf file<br />and change as per your requirement<br /><br />//<br />// named.caching-nameserver.conf<br />//<br />// Provided by Red Hat caching-nameserver package to configure the<br />// ISC BIND named(8) DNS server as a caching only nameserver<br />// (as a localhost DNS resolver only).<br />//<br />// See /usr/share/doc/bind*/sample/ for example named configuration files.<br />//<br />// DO NOT EDIT THIS FILE - use system-config-bind or an editor<br />// to create named.conf - edits to this file will be lost on<br />// caching-nameserver package upgrade.<br />//<br />options {<br /> listen-on port 53 { 127.0.0.1; 192.168.0.254; };<br /> listen-on-v6 port 53 { ::1; };<br /> directory "/var/named";<br /> dump-file "/var/named/data/cache_dump.db";<br /> statistics-file "/var/named/data/named_stats.txt";<br /> memstatistics-file "/var/named/data/named_mem_stats.txt";<br /> allow-query { localhost; 192.168.0.0/22; };<br /> recursion yes;<br /> forwarders { 210.2.181.6; 210.2.181.7; 4.2.2.4; };<br />};<br /><br />logging {<br /> channel default_debug {<br /> file "data/named.run";<br /> severity dynamic;<br /> };<br />};<br /><br />zone "." IN {<br /> type hint;<br /> file "named.ca";<br />};<br /><br />include "/etc/named.rfc1912.zones";Muhammad Imranhttp://www.blogger.com/profile/12158641287038478088noreply@blogger.comtag:blogger.com,1999:blog-4938443720602924137.post-86109921263429365252010-01-08T03:14:00.000-08:002010-01-08T03:19:35.122-08:00Transperent Proxy in Squid 2.6 and Squid 3This is very Simple Configuration for configure Squid 2.6 or Squid 3.0<br />act as a Transparent. if you are old user of Squid and linux then this is very simple<br />configuration all the squid configuration same.<br />when you configure just type transparent after port as under:-<br /><br />http_port 3128 transparent<br /><br />Further Setting and tracks of squid i will write in my next blog<br />Thanks.<br /><br />Further Help contact with us<br />LinuxMall Team<br />Pakistan<br />092-321-8466323Muhammad Imranhttp://www.blogger.com/profile/12158641287038478088noreply@blogger.comtag:blogger.com,1999:blog-4938443720602924137.post-51907572934806034772010-01-04T03:21:00.000-08:002010-01-04T03:31:36.130-08:00squid.conf sample file of fedora# WELCOME TO SQUID 2<br /># ------------------<br />#<br /># This is the default Squid configuration file. You may wish<br /># to look at the Squid home page (http://www.squid-cache.org/)<br /># for the FAQ and other documentation.<br />#<br /># The default Squid config file shows what the defaults for<br /># various options happen to be. If you don't need to change the<br /># default, you shouldn't uncomment the line. Doing so may cause<br /># run-time problems. In some cases "none" refers to no default<br /># setting at all, while in other cases it refers to a valid<br /># option - the comments for that keyword indicate if this is the<br /># case.<br />#<br /># NETWORK OPTIONS<br /># -----------------------------------------------------------------------------<br /><br /># TAG: http_port<br /># Usage: port<br /># hostname:port<br /># 1.2.3.4:port<br />#<br /># The socket addresses where Squid will listen for HTTP client<br /># requests. You may specify multiple socket addresses.<br /># There are three forms: port alone, hostname with port, and<br /># IP address with port. If you specify a hostname or IP<br /># address, Squid binds the socket to that specific<br /># address. This replaces the old 'tcp_incoming_address'<br /># option. Most likely, you do not need to bind to a specific<br /># address, so you can use the port number alone.<br />#<br /># The default port number is 3128.<br />#<br /># If you are running Squid in accelerator mode, you<br /># probably want to listen on port 80 also, or instead.<br />#<br /># The -a command line option will override the *first* port<br /># number listed here. That option will NOT override an IP<br /># address, however.<br />#<br /># You may specify multiple socket addresses on multiple lines.<br />#<br /># If you run Squid on a dual-homed machine with an internal<br /># and an external interface we recommend you to specify the<br /># internal address:port in http_port. This way Squid will only be<br /># visible on the internal address.<br />#<br />#Default:<br />http_port 8080<br /><br /># TAG: https_port<br /># Usage: [ip:]port cert=certificate.pem [key=key.pem] [options...]<br />#<br /># The socket address where Squid will listen for HTTPS client<br /># requests.<br />#<br /># This is really only useful for situations where you are running<br /># squid in accelerator mode and you want to do the SSL work at the<br /># accelerator level.<br />#<br /># You may specify multiple socket addresses on multiple lines,<br /># each with their own SSL certificate and/or options.<br />#<br /># Options:<br />#<br /># cert= Path to SSL certificate (PEM format)<br />#<br /># key= Path to SSL private key file (PEM format)<br /># if not specified, the certificate file is<br /># assumed to be a combined certificate and<br /># key file<br />#<br /># version= The version of SSL/TLS supported<br /># 1 automatic (default)<br /># 2 SSLv2 only<br /># 3 SSLv3 only<br /># 4 TLSv1 only<br />#<br /># cipher= Colon separated list of supported ciphers<br />#<br /># options= Various SSL engine options. The most important<br /># being:<br /># NO_SSLv2 Disallow the use of SSLv2<br /># NO_SSLv3 Disallow the use of SSLv3<br /># NO_TLSv1 Disallow the use of TLSv1<br /># See src/ssl_support.c or OpenSSL documentation<br /># for a more complete list.<br />#<br />#Default:<br /># none<br /><br /># TAG: ssl_unclean_shutdown<br /># Some browsers (especially MSIE) bugs out on SSL shutdown<br /># messages.<br />#<br />#Default:<br /># ssl_unclean_shutdown off<br /><br /># TAG: icp_port<br /># The port number where Squid sends and receives ICP queries to<br /># and from neighbor caches. Default is 3130. To disable use<br /># "0". May be overridden with -u on the command line.<br />#<br />#Default:<br /># icp_port 3130<br /><br /># TAG: htcp_port<br /># Note: This option is only available if Squid is rebuilt with the<br /># --enable-htcp option<br />#<br /># The port number where Squid sends and receives HTCP queries to<br /># and from neighbor caches. Default is 4827. To disable use<br /># "0".<br />#<br />#Default:<br /># htcp_port 4827<br /><br /># TAG: mcast_groups<br /># This tag specifies a list of multicast groups which your server<br /># should join to receive multicasted ICP queries.<br />#<br /># NOTE! Be very careful what you put here! Be sure you<br /># understand the difference between an ICP _query_ and an ICP<br /># _reply_. This option is to be set only if you want to RECEIVE<br /># multicast queries. Do NOT set this option to SEND multicast<br /># ICP (use cache_peer for that). ICP replies are always sent via<br /># unicast, so this option does not affect whether or not you will<br /># receive replies from multicast group members.<br />#<br /># You must be very careful to NOT use a multicast address which<br /># is already in use by another group of caches.<br />#<br /># If you are unsure about multicast, please read the Multicast<br /># chapter in the Squid FAQ (http://www.squid-cache.org/FAQ/).<br />#<br /># Usage: mcast_groups 239.128.16.128 224.0.1.20<br />#<br /># By default, Squid doesn't listen on any multicast groups.<br />#<br />#Default:<br /># none<br /><br /># TAG: udp_incoming_address<br /># TAG: udp_outgoing_address<br /># udp_incoming_address is used for the ICP socket receiving packets<br /># from other caches.<br /># udp_outgoing_address is used for ICP packets sent out to other<br /># caches.<br />#<br /># The default behavior is to not bind to any specific address.<br />#<br /># A udp_incoming_address value of 0.0.0.0 indicates Squid<br /># should listen for UDP messages on all available interfaces.<br />#<br /># If udp_outgoing_address is set to 255.255.255.255 (the default)<br /># it will use the same socket as udp_incoming_address. Only<br /># change this if you want to have ICP queries sent using another<br /># address than where this Squid listens for ICP queries from other<br /># caches.<br />#<br /># NOTE, udp_incoming_address and udp_outgoing_address can not<br /># have the same value since they both use port 3130.<br />#<br />#Default:<br /># udp_incoming_address 0.0.0.0<br /># udp_outgoing_address 255.255.255.255<br /><br /><br /># OPTIONS WHICH AFFECT THE NEIGHBOR SELECTION ALGORITHM<br /># -----------------------------------------------------------------------------<br /><br /># TAG: cache_peer<br /># To specify other caches in a hierarchy, use the format:<br />#<br /># cache_peer hostname type http_port icp_port<br />#<br /># For example,<br />#<br /># # proxy icp<br /># # hostname type port port options<br /># # -------------------- -------- ----- ----- -----------<br /> cache_peer 192.168.0.253 parent 3128 3130 round-robin<br /> cache_peer 192.168.0.10 parent 8080 0 round-robin<br /># cache_peer sib1.foo.net sibling 3128 3130 [proxy-only]<br /># cache_peer sib2.foo.net sibling 3128 3130 [proxy-only]<br />#<br /># type: either 'parent', 'sibling', or 'multicast'.<br />#<br /># proxy_port: The port number where the cache listens for proxy<br /># requests.<br />#<br /># icp_port: Used for querying neighbor caches about<br /># objects. To have a non-ICP neighbor<br /># specify '7' for the ICP port and make sure the<br /># neighbor machine has the UDP echo port<br /># enabled in its /etc/inetd.conf file.<br />#<br /># options: proxy-only<br /># weight=n<br /># ttl=n<br /># no-query<br /># default<br /># round-robin<br /># multicast-responder<br /># closest-only<br /># no-digest<br /># no-netdb-exchange<br /># no-delay<br /># login=user:password | PASS | *:password<br /># connect-timeout=nn<br /># digest-url=url<br /># allow-miss<br /># max-conn<br /># htcp<br /># carp-load-factor<br />#<br /># use 'proxy-only' to specify objects fetched<br /># from this cache should not be saved locally.<br />#<br /># use 'weight=n' to specify a weighted parent.<br /># The weight must be an integer. The default weight<br /># is 1, larger weights are favored more.<br />#<br /># use 'ttl=n' to specify a IP multicast TTL to use<br /># when sending an ICP queries to this address.<br /># Only useful when sending to a multicast group.<br /># Because we don't accept ICP replies from random<br /># hosts, you must configure other group members as<br /># peers with the 'multicast-responder' option below.<br />#<br /># use 'no-query' to NOT send ICP queries to this<br /># neighbor.<br />#<br /># use 'default' if this is a parent cache which can<br /># be used as a "last-resort." You should probably<br /># only use 'default' in situations where you cannot<br /># use ICP with your parent cache(s).<br />#<br /># use 'round-robin' to define a set of parents which<br /># should be used in a round-robin fashion in the<br /># absence of any ICP queries.<br />#<br /># 'multicast-responder' indicates the named peer<br /># is a member of a multicast group. ICP queries will<br /># not be sent directly to the peer, but ICP replies<br /># will be accepted from it.<br />#<br /># 'closest-only' indicates that, for ICP_OP_MISS<br /># replies, we'll only forward CLOSEST_PARENT_MISSes<br /># and never FIRST_PARENT_MISSes.<br />#<br /># use 'no-digest' to NOT request cache digests from<br /># this neighbor.<br />#<br /># 'no-netdb-exchange' disables requesting ICMP<br /># RTT database (NetDB) from the neighbor.<br />#<br /># use 'no-delay' to prevent access to this neighbor<br /># from influencing the delay pools.<br />#<br /># use 'login=user:password' if this is a personal/workgroup<br /># proxy and your parent requires proxy authentication.<br /># Note: The string can include URL escapes (i.e. %20 for<br /># spaces). This also means % must be written as %%.<br />#<br /># use 'login=PASS' if users must authenticate against<br /># the upstream proxy. This will pass the users credentials<br /># as they are to the peer proxy. This only works for the<br /># Basic HTTP authentication scheme. Note: To combine this<br /># with proxy_auth both proxies must share the same user<br /># database as HTTP only allows for one proxy login.<br /># Also be warned this will expose your users proxy<br /># password to the peer. USE WITH CAUTION<br />#<br /># use 'login=*:password' to pass the username to the<br /># upstream cache, but with a fixed password. This is meant<br /># to be used when the peer is in another administrative<br /># domain, but it is still needed to identify each user.<br /># The star can optionally be followed by some extra<br /># information which is added to the username. This can<br /># be used to identify this proxy to the peer, similar to<br /># the login=username:password option above.<br />#<br /># use 'connect-timeout=nn' to specify a peer<br /># specific connect timeout (also see the<br /># peer_connect_timeout directive)<br />#<br /># use 'digest-url=url' to tell Squid to fetch the cache<br /># digest (if digests are enabled) for this host from<br /># the specified URL rather than the Squid default<br /># location.<br />#<br /># use 'allow-miss' to disable Squid's use of only-if-cached<br /># when forwarding requests to siblings. This is primarily<br /># useful when icp_hit_stale is used by the sibling. To<br /># extensive use of this option may result in forwarding<br /># loops, and you should avoid having two-way peerings<br /># with this option. (for example to deny peer usage on<br /># requests from peer by denying cache_peer_access if the<br /># source is a peer)<br />#<br /># use 'max-conn' to limit the amount of connections Squid<br /># may open to this peer.<br />#<br /># use 'htcp' to send HTCP, instead of ICP, queries<br /># to the neighbor. You probably also want to<br /># set the "icp port" to 4827 instead of 3130.<br />#<br /># use 'carp-load-factor=f' to define a parent<br /># cache as one participating in a CARP array.<br /># The 'f' values for all CARP parents must add<br /># up to 1.0.<br />#<br />#<br /># NOTE: non-ICP/HTCP neighbors must be specified as 'parent'.<br />#<br />#Default:<br /># none<br /><br /># TAG: cache_peer_domain<br /># Use to limit the domains for which a neighbor cache will be<br /># queried. Usage:<br />#<br /># cache_peer_domain cache-host domain [domain ...]<br /># cache_peer_domain cache-host !domain<br />#<br /># For example, specifying<br />#<br /># cache_peer_domain parent.foo.net .edu<br />#<br /># has the effect such that UDP query packets are sent to<br /># 'bigserver' only when the requested object exists on a<br /># server in the .edu domain. Prefixing the domainname<br /># with '!' means the cache will be queried for objects<br /># NOT in that domain.<br />#<br /># NOTE: * Any number of domains may be given for a cache-host,<br /># either on the same or separate lines.<br /># * When multiple domains are given for a particular<br /># cache-host, the first matched domain is applied.<br /># * Cache hosts with no domain restrictions are queried<br /># for all requests.<br /># * There are no defaults.<br /># * There is also a 'cache_peer_access' tag in the ACL<br /># section.<br />#<br />#Default:<br /># none<br /><br /># TAG: neighbor_type_domain<br /># usage: neighbor_type_domain neighbor parent|sibling domain domain ...<br />#<br /># Modifying the neighbor type for specific domains is now<br /># possible. You can treat some domains differently than the the<br /># default neighbor type specified on the 'cache_peer' line.<br /># Normally it should only be necessary to list domains which<br /># should be treated differently because the default neighbor type<br /># applies for hostnames which do not match domains listed here.<br />#<br />#EXAMPLE:<br /># cache_peer parent cache.foo.org 3128 3130<br /># neighbor_type_domain cache.foo.org sibling .com .net<br /># neighbor_type_domain cache.foo.org sibling .au .de<br />#<br />#Default:<br /># none<br /><br /># TAG: icp_query_timeout (msec)<br /># Normally Squid will automatically determine an optimal ICP<br /># query timeout value based on the round-trip-time of recent ICP<br /># queries. If you want to override the value determined by<br /># Squid, set this 'icp_query_timeout' to a non-zero value. This<br /># value is specified in MILLISECONDS, so, to use a 2-second<br /># timeout (the old default), you would write:<br />#<br /># icp_query_timeout 2000<br />#<br />#Default:<br /># icp_query_timeout 0<br /><br /># TAG: maximum_icp_query_timeout (msec)<br /># Normally the ICP query timeout is determined dynamically. But<br /># sometimes it can lead to very large values (say 5 seconds).<br /># Use this option to put an upper limit on the dynamic timeout<br /># value. Do NOT use this option to always use a fixed (instead<br /># of a dynamic) timeout value. To set a fixed timeout see the<br /># 'icp_query_timeout' directive.<br />#<br />#Default:<br /># maximum_icp_query_timeout 2000<br /><br /># TAG: mcast_icp_query_timeout (msec)<br /># For Multicast peers, Squid regularly sends out ICP "probes" to<br /># count how many other peers are listening on the given multicast<br /># address. This value specifies how long Squid should wait to<br /># count all the replies. The default is 2000 msec, or 2<br /># seconds.<br />#<br />#Default:<br /># mcast_icp_query_timeout 2000<br /><br /># TAG: dead_peer_timeout (seconds)<br /># This controls how long Squid waits to declare a peer cache<br /># as "dead." If there are no ICP replies received in this<br /># amount of time, Squid will declare the peer dead and not<br /># expect to receive any further ICP replies. However, it<br /># continues to send ICP queries, and will mark the peer as<br /># alive upon receipt of the first subsequent ICP reply.<br />#<br /># This timeout also affects when Squid expects to receive ICP<br /># replies from peers. If more than 'dead_peer' seconds have<br /># passed since the last ICP reply was received, Squid will not<br /># expect to receive an ICP reply on the next query. Thus, if<br /># your time between requests is greater than this timeout, you<br /># will see a lot of requests sent DIRECT to origin servers<br /># instead of to your parents.<br />#<br />#Default:<br /># dead_peer_timeout 10 seconds<br /><br /># TAG: hierarchy_stoplist<br /># A list of words which, if found in a URL, cause the object to<br /># be handled directly by this cache. In other words, use this<br /># to not query neighbor caches for certain objects. You may<br /># list this option multiple times. Note: never_direct overrides<br /># this option.<br />#We recommend you to use at least the following line.<br />hierarchy_stoplist cgi-bin ?<br /><br /># TAG: no_cache<br /># A list of ACL elements which, if matched, cause the request to<br /># not be satisfied from the cache and the reply to not be cached.<br /># In other words, use this to force certain objects to never be cached.<br />#<br /># You must use the word 'DENY' to indicate the ACL names which should<br /># NOT be cached.<br />#<br />#We recommend you to use the following two lines.<br />acl QUERY urlpath_regex cgi-bin \?<br />no_cache deny QUERY<br /><br /><br /># OPTIONS WHICH AFFECT THE CACHE SIZE<br /># -----------------------------------------------------------------------------<br /><br /># TAG: cache_mem (bytes)<br /># NOTE: THIS PARAMETER DOES NOT SPECIFY THE MAXIMUM PROCESS SIZE.<br /># IT ONLY PLACES A LIMIT ON HOW MUCH ADDITIONAL MEMORY SQUID WILL<br /># USE AS A MEMORY CACHE OF OBJECTS. SQUID USES MEMORY FOR OTHER<br /># THINGS AS WELL. SEE THE SQUID FAQ SECTION 8 FOR DETAILS.<br />#<br /># 'cache_mem' specifies the ideal amount of memory to be used<br /># for:<br /># * In-Transit objects<br /># * Hot Objects<br /># * Negative-Cached objects<br />#<br /># Data for these objects are stored in 4 KB blocks. This<br /># parameter specifies the ideal upper limit on the total size of<br /># 4 KB blocks allocated. In-Transit objects take the highest<br /># priority.<br />#<br /># In-transit objects have priority over the others. When<br /># additional space is needed for incoming data, negative-cached<br /># and hot objects will be released. In other words, the<br /># negative-cached and hot objects will fill up any unused space<br /># not needed for in-transit objects.<br />#<br /># If circumstances require, this limit will be exceeded.<br /># Specifically, if your incoming request rate requires more than<br /># 'cache_mem' of memory to hold in-transit objects, Squid will<br /># exceed this limit to satisfy the new requests. When the load<br /># decreases, blocks will be freed until the high-water mark is<br /># reached. Thereafter, blocks will be used to store hot<br /># objects.<br />#<br />#Default:<br /># cache_mem 128 MB<br /><br /># TAG: cache_swap_low (percent, 0-100)<br /># TAG: cache_swap_high (percent, 0-100)<br />#<br /># The low- and high-water marks for cache object replacement.<br /># Replacement begins when the swap (disk) usage is above the<br /># low-water mark and attempts to maintain utilization near the<br /># low-water mark. As swap utilization gets close to high-water<br /># mark object eviction becomes more aggressive. If utilization is<br /># close to the low-water mark less replacement is done each time.<br />#<br /># Defaults are 90% and 95%. If you have a large cache, 5% could be<br /># hundreds of MB. If this is the case you may wish to set these<br /># numbers closer together.<br />#<br />#Default:<br /># cache_swap_low 90<br /># cache_swap_high 95<br /><br /># TAG: maximum_object_size (bytes)<br /># Objects larger than this size will NOT be saved on disk. The<br /># value is specified in kilobytes, and the default is 4MB. If<br /># you wish to get a high BYTES hit ratio, you should probably<br /># increase this (one 32 MB object hit counts for 3200 10KB<br /># hits). If you wish to increase speed more than your want to<br /># save bandwidth you should leave this low.<br />#<br /># NOTE: if using the LFUDA replacement policy you should increase<br /># this value to maximize the byte hit rate improvement of LFUDA!<br /># See replacement_policy below for a discussion of this policy.<br />#<br />#Default:<br /># maximum_object_size 300 MB<br /><br /># TAG: minimum_object_size (bytes)<br /># Objects smaller than this size will NOT be saved on disk. The<br /># value is specified in kilobytes, and the default is 0 KB, which<br /># means there is no minimum.<br />#<br />#Default:<br /># minimum_object_size 0 KB<br /><br /># TAG: maximum_object_size_in_memory (bytes)<br /># Objects greater than this size will not be attempted to kept in<br /># the memory cache. This should be set high enough to keep objects<br /># accessed frequently in memory to improve performance whilst low<br /># enough to keep larger objects from hoarding cache_mem .<br />#<br />#Default:<br /># maximum_object_size_in_memory 8 KB<br /><br /># TAG: ipcache_size (number of entries)<br /># TAG: ipcache_low (percent)<br /># TAG: ipcache_high (percent)<br /># The size, low-, and high-water marks for the IP cache.<br />#<br />#Default:<br /># ipcache_size 1024<br /># ipcache_low 90<br /># ipcache_high 95<br /><br /># TAG: fqdncache_size (number of entries)<br /># Maximum number of FQDN cache entries.<br />#<br />#Default:<br /># fqdncache_size 1024<br /><br /># TAG: cache_replacement_policy<br /># The cache replacement policy parameter determines which<br /># objects are evicted (replaced) when disk space is needed.<br />#<br /># lru : Squid's original list based LRU policy<br /># heap GDSF : Greedy-Dual Size Frequency<br /># heap LFUDA: Least Frequently Used with Dynamic Aging<br /># heap LRU : LRU policy implemented using a heap<br />#<br /># Applies to any cache_dir lines listed below this.<br />#<br /># The LRU policies keeps recently referenced objects.<br />#<br /># The heap GDSF policy optimizes object hit rate by keeping smaller<br /># popular objects in cache so it has a better chance of getting a<br /># hit. It achieves a lower byte hit rate than LFUDA though since<br /># it evicts larger (possibly popular) objects.<br />#<br /># The heap LFUDA policy keeps popular objects in cache regardless of<br /># their size and thus optimizes byte hit rate at the expense of<br /># hit rate since one large, popular object will prevent many<br /># smaller, slightly less popular objects from being cached.<br />#<br /># Both policies utilize a dynamic aging mechanism that prevents<br /># cache pollution that can otherwise occur with frequency-based<br /># replacement policies.<br />#<br /># NOTE: if using the LFUDA replacement policy you should increase<br /># the value of maximum_object_size above its default of 4096 KB to<br /># to maximize the potential byte hit rate improvement of LFUDA.<br />#<br /># For more information about the GDSF and LFUDA cache replacement<br /># policies see http://www.hpl.hp.com/techreports/1999/HPL-1999-69.html<br /># and http://fog.hpl.external.hp.com/techreports/98/HPL-98-173.html.<br />#<br />#Default:<br /># cache_replacement_policy lru<br /><br /># TAG: memory_replacement_policy<br /># The memory replacement policy parameter determines which<br /># objects are purged from memory when memory space is needed.<br />#<br /># See cache_replacement_policy for details.<br />#<br />#Default:<br /># memory_replacement_policy lru<br /><br /><br /># LOGFILE PATHNAMES AND CACHE DIRECTORIES<br /># -----------------------------------------------------------------------------<br /><br /># TAG: cache_dir<br /># Usage:<br />#<br /># cache_dir Type Directory-Name Fs-specific-data [options]<br />#<br /># You can specify multiple cache_dir lines to spread the<br /># cache among different disk partitions.<br />#<br /># Type specifies the kind of storage system to use. Only "ufs"<br /># is built by default. To enable any of the other storage systems<br /># see the --enable-storeio configure option.<br />#<br /># 'Directory' is a top-level directory where cache swap<br /># files will be stored. If you want to use an entire disk<br /># for caching, this can be the mount-point directory.<br /># The directory must exist and be writable by the Squid<br /># process. Squid will NOT create this directory for you.<br />#<br /># The ufs store type:<br />#<br /># "ufs" is the old well-known Squid storage format that has always<br /># been there.<br />#<br /># cache_dir ufs Directory-Name Mbytes L1 L2 [options]<br />#<br /># 'Mbytes' is the amount of disk space (MB) to use under this<br /># directory. The default is 100 MB. Change this to suit your<br /># configuration. Do NOT put the size of your disk drive here.<br /># Instead, if you want Squid to use the entire disk drive,<br /># subtract 20% and use that value.<br />#<br /># 'Level-1' is the number of first-level subdirectories which<br /># will be created under the 'Directory'. The default is 16.<br />#<br /># 'Level-2' is the number of second-level subdirectories which<br /># will be created under each first-level directory. The default<br /># is 256.<br />#<br /># The aufs store type:<br />#<br /># "aufs" uses the same storage format as "ufs", utilizing<br /># POSIX-threads to avoid blocking the main Squid process on<br /># disk-I/O. This was formerly known in Squid as async-io.<br />#<br /># cache_dir aufs Directory-Name Mbytes L1 L2 [options]<br />#<br /># see argument descriptions under ufs above<br />#<br /># The diskd store type:<br />#<br /># "diskd" uses the same storage format as "ufs", utilizing a<br /># separate process to avoid blocking the main Squid process on<br /># disk-I/O.<br />#<br /># cache_dir diskd Directory-Name Mbytes L1 L2 [options] [Q1=n] [Q2=n]<br />#<br /># see argument descriptions under ufs above<br />#<br /># Q1 specifies the number of unacknowledged I/O requests when Squid<br /># stops opening new files. If this many messages are in the queues,<br /># Squid won't open new files. Default is 64<br />#<br /># Q2 specifies the number of unacknowledged messages when Squid<br /># starts blocking. If this many messages are in the queues,<br /># Squid blocks until it receives some replies. Default is 72<br />#<br /># When Q1 < Q2 (the default), the cache directory is optimized<br /># for lower response time at the expense of a decrease in hit<br /># ratio. If Q1 > Q2, the cache directory is optimized for<br /># higher hit ratio at the expense of an increase in response<br /># time.<br />#<br /># The coss store type:<br />#<br /># block-size=n defines the "block size" for COSS cache_dir's.<br /># Squid uses file numbers as block numbers. Since file numbers<br /># are limited to 24 bits, the block size determines the maximum<br /># size of the COSS partition. The default is 512 bytes, which<br /># leads to a maximum cache_dir size of 512<<24, or 8 GB. Note<br /># you should not change the coss block size after Squid<br /># has written some objects to the cache_dir.<br />#<br /># Common options:<br />#<br /># read-only, this cache_dir is read only.<br />#<br /># max-size=n, refers to the max object size this storedir supports.<br /># It is used to initially choose the storedir to dump the object.<br /># Note: To make optimal use of the max-size limits you should order<br /># the cache_dir lines with the smallest max-size value first and the<br /># ones with no max-size specification last.<br />#<br /># Note that for coss, max-size must be less than COSS_MEMBUF_SZ<br /># (hard coded at 1 MB).<br />#<br />#Default:<br /> cache_dir ufs /var/spool/squid 42000 16 256<br /><br /># TAG: cache_access_log<br /># Logs the client request activity. Contains an entry for<br /># every HTTP and ICP queries received. To disable, enter "none".<br />#<br />#Default:<br /># cache_access_log /var/log/squid/access.log<br /><br /># TAG: cache_log<br /># Cache logging file. This is where general information about<br /># your cache's behavior goes. You can increase the amount of data<br /># logged to this file with the "debug_options" tag below.<br />#<br />#Default:<br /># cache_log /var/log/squid/cache.log<br /><br /># TAG: cache_store_log<br /># Logs the activities of the storage manager. Shows which<br /># objects are ejected from the cache, and which objects are<br /># saved and for how long. To disable, enter "none". There are<br /># not really utilities to analyze this data, so you can safely<br /># disable it.<br />#<br />#Default:<br /># cache_store_log /var/log/squid/store.log<br /><br /># TAG: cache_swap_log<br /># Location for the cache "swap.state" file. This log file holds<br /># the metadata of objects saved on disk. It is used to rebuild<br /># the cache during startup. Normally this file resides in each<br /># 'cache_dir' directory, but you may specify an alternate<br /># pathname here. Note you must give a full filename, not just<br /># a directory. Since this is the index for the whole object<br /># list you CANNOT periodically rotate it!<br />#<br /># If %s can be used in the file name it will be replaced with a<br /># a representation of the cache_dir name where each / is replaced<br /># with '.'. This is needed to allow adding/removing cache_dir<br /># lines when cache_swap_log is being used.<br />#<br /># If have more than one 'cache_dir', and %s is not used in the name<br /># these swap logs will have names such as:<br />#<br /># cache_swap_log.00<br /># cache_swap_log.01<br /># cache_swap_log.02<br />#<br /># The numbered extension (which is added automatically)<br /># corresponds to the order of the 'cache_dir' lines in this<br /># configuration file. If you change the order of the 'cache_dir'<br /># lines in this file, these log files will NOT correspond to<br /># the correct 'cache_dir' entry (unless you manually rename<br /># them). We recommend you do NOT use this option. It is<br /># better to keep these log files in each 'cache_dir' directory.<br />#<br />#Default:<br /># none<br /><br /># TAG: emulate_httpd_log on|off<br /># The Cache can emulate the log file format which many 'httpd'<br /># programs use. To disable/enable this emulation, set<br /># emulate_httpd_log to 'off' or 'on'. The default<br /># is to use the native log format since it includes useful<br /># information Squid-specific log analyzers use.<br />#<br />#Default:<br /># emulate_httpd_log off<br /><br /># TAG: log_ip_on_direct on|off<br /># Log the destination IP address in the hierarchy log tag when going<br /># direct. Earlier Squid versions logged the hostname here. If you<br /># prefer the old way set this to off.<br />#<br />#Default:<br /># log_ip_on_direct on<br /><br /># TAG: mime_table<br /># Pathname to Squid's MIME table. You shouldn't need to change<br /># this, but the default file contains examples and formatting<br /># information if you do.<br />#<br />#Default:<br /># mime_table /etc/squid/mime.conf<br /><br /># TAG: log_mime_hdrs on|off<br /># The Cache can record both the request and the response MIME<br /># headers for each HTTP transaction. The headers are encoded<br /># safely and will appear as two bracketed fields at the end of<br /># the access log (for either the native or httpd-emulated log<br /># formats). To enable this logging set log_mime_hdrs to 'on'.<br />#<br />#Default:<br /># log_mime_hdrs off<br /><br /># TAG: useragent_log<br /># Squid will write the User-Agent field from HTTP requests<br /># to the filename specified here. By default useragent_log<br /># is disabled.<br />#<br />#Default:<br /># none<br /><br /># TAG: referer_log<br /># Squid will write the Referer field from HTTP requests to the<br /># filename specified here. By default referer_log is disabled.<br />#<br />#Default:<br /># none<br /><br /># TAG: pid_filename<br /># A filename to write the process-id to. To disable, enter "none".<br />#<br />#Default:<br /># pid_filename /var/run/squid.pid<br /><br /># TAG: debug_options<br /># Logging options are set as section,level where each source file<br /># is assigned a unique section. Lower levels result in less<br /># output, Full debugging (level 9) can result in a very large<br /># log file, so be careful. The magic word "ALL" sets debugging<br /># levels for all sections. We recommend normally running with<br /># "ALL,1".<br />#<br />#Default:<br /># debug_options ALL,1<br /><br /># TAG: log_fqdn on|off<br /># Turn this on if you wish to log fully qualified domain names<br /># in the access.log. To do this Squid does a DNS lookup of all<br /># IP's connecting to it. This can (in some situations) increase<br /># latency, which makes your cache seem slower for interactive<br /># browsing.<br />#<br />#Default:<br /># log_fqdn off<br /><br /># TAG: client_netmask<br /># A netmask for client addresses in logfiles and cachemgr output.<br /># Change this to protect the privacy of your cache clients.<br /># A netmask of 255.255.255.0 will log all IP's in that range with<br /># the last digit set to '0'.<br />#<br />#Default:<br /># client_netmask 255.255.255.255<br /><br /><br /># OPTIONS FOR EXTERNAL SUPPORT PROGRAMS<br /># -----------------------------------------------------------------------------<br /><br /># TAG: ftp_user<br /># If you want the anonymous login password to be more informative<br /># (and enable the use of picky ftp servers), set this to something<br /># reasonable for your domain, like wwwuser@somewhere.net<br />#<br /># The reason why this is domainless by default is the<br /># request can be made on the behalf of a user in any domain,<br /># depending on how the cache is used.<br /># Some ftp server also validate the email address is valid<br /># (for example perl.com).<br />#<br />#Default:<br /># ftp_user Squid@<br /><br /># TAG: ftp_list_width<br /># Sets the width of ftp listings. This should be set to fit in<br /># the width of a standard browser. Setting this too small<br /># can cut off long filenames when browsing ftp sites.<br />#<br />#Default:<br /># ftp_list_width 32<br /><br /># TAG: ftp_passive<br /># If your firewall does not allow Squid to use passive<br /># connections, turn off this option.<br />#<br />#Default:<br /># ftp_passive on<br /><br /># TAG: ftp_sanitycheck<br /># For security and data integrity reasons Squid by default performs<br /># sanity checks of the addresses of FTP data connections ensure the<br /># data connection is to the requested server. If you need to allow<br /># FTP connections to servers using another IP address for the data<br /># connection turn this off.<br />#<br />#Default:<br /># ftp_sanitycheck on<br /><br /># TAG: ftp_telnet_protocol<br /># The FTP protocol is officially defined to use the telnet protocol<br /># as transport channel for the control connection. However, many<br /># implementations are broken and does not respect this aspect of<br /># the FTP protocol.<br />#<br /># If you have trouble accessing files with ASCII code 255 in the<br /># path or similar problems involving this ASCII code you can<br /># try setting this directive to off. If that helps, report to the<br /># operator of the FTP server in question that their FTP server<br /># is broken and does not follow the FTP standard.<br />#<br />#Default:<br /># ftp_telnet_protocol on<br /><br /># TAG: cache_dns_program<br /># Note: This option is only available if Squid is rebuilt with the<br /># --disable-internal-dns option<br />#<br /># Specify the location of the executable for dnslookup process.<br />#<br />#Default:<br /># cache_dns_program /usr/lib/squid/dnsserver<br /><br /># TAG: dns_children<br /># Note: This option is only available if Squid is rebuilt with the<br /># --disable-internal-dns option<br />#<br /># The number of processes spawn to service DNS name lookups.<br /># For heavily loaded caches on large servers, you should<br /># probably increase this value to at least 10. The maximum<br /># is 32. The default is 5.<br />#<br /># You must have at least one dnsserver process.<br />#<br />#Default:<br /># dns_children 5<br /><br /># TAG: dns_retransmit_interval<br /># Initial retransmit interval for DNS queries. The interval is<br /># doubled each time all configured DNS servers have been tried.<br />#<br />#<br />#Default:<br /># dns_retransmit_interval 5 seconds<br /><br /># TAG: dns_timeout<br /># DNS Query timeout. If no response is received to a DNS query<br /># within this time all DNS servers for the queried domain<br /># are assumed to be unavailable.<br />#<br />#Default:<br /># dns_timeout 2 minutes<br /><br /># TAG: dns_defnames on|off<br /># Note: This option is only available if Squid is rebuilt with the<br /># --disable-internal-dns option<br />#<br /># Normally the 'dnsserver' disables the RES_DEFNAMES resolver<br /># option (see res_init(3)). This prevents caches in a hierarchy<br /># from interpreting single-component hostnames locally. To allow<br /># dnsserver to handle single-component names, enable this<br /># option.<br />#<br />#Default:<br /># dns_defnames off<br /><br /># TAG: dns_nameservers<br /># Use this if you want to specify a list of DNS name servers<br /># (IP addresses) to use instead of those given in your<br /># /etc/resolv.conf file.<br /># On Windows platforms, if no value is specified here or in<br /># the /etc/resolv.conf file, the list of DNS name servers are<br /># taken from the Windows registry, both static and dynamic DHCP<br /># configurations are supported.<br />#<br /># Example: dns_nameservers 10.0.0.1 192.172.0.4<br />#<br />#Default:<br /># none<br /><br /># TAG: hosts_file<br /># Location of the host-local IP name-address associations<br /># database. Most Operating Systems have such a file: under<br /># Un*X it's by default in /etc/hosts. MS-Windows NT/2000 places<br /># it in %SystemRoot%(by default<br /># c:\winnt)\system32\drivers\etc\hosts, while Windows 9x/ME<br /># places it in %windir%(usually c:\windows)\hosts<br />#<br /># The file contains newline-separated definitions, in the<br /># form ip_address_in_dotted_form name [name ...] names are<br /># whitespace-separated. lines beginning with an hash (#)<br /># character are comments.<br />#<br /># The file is checked at startup and upon configuration. If<br /># set to 'none', it won't be checked. If append_domain is<br /># used, that domain will be added to domain-local (i.e. not<br /># containing any dot character) host definitions.<br />#<br />#Default:<br /># hosts_file /etc/hosts<br /><br /># TAG: diskd_program<br /># Specify the location of the diskd executable.<br /># Note that this is only useful if you have compiled in<br /># diskd as one of the store io modules.<br />#<br />#Default:<br /># diskd_program /usr/lib/squid/diskd<br /><br /># TAG: unlinkd_program<br /># Specify the location of the executable for file deletion process.<br />#<br />#Default:<br /># unlinkd_program /usr/lib/squid/unlinkd<br /><br /># TAG: pinger_program<br /># Note: This option is only available if Squid is rebuilt with the<br /># --enable-icmp option<br />#<br /># Specify the location of the executable for the pinger process.<br />#<br />#Default:<br /># pinger_program /usr/lib/squid/pinger<br /><br /># TAG: redirect_program<br /># Specify the location of the executable for the URL redirector.<br /># Since they can perform almost any function there isn't one included.<br /># See the FAQ (section 15) for information on how to write one.<br /># By default, a redirector is not used.<br />#<br />#Default:<br /># none<br /><br /># TAG: redirect_children<br /># The number of redirector processes to spawn. If you start<br /># too few Squid will have to wait for them to process a backlog of<br /># URLs, slowing it down. If you start too many they will use RAM<br /># and other system resources.<br />#<br />#Default:<br /># redirect_children 5<br /><br /># TAG: redirect_rewrites_host_header<br /># By default Squid rewrites any Host: header in redirected<br /># requests. If you are running an accelerator this may<br /># not be a wanted effect of a redirector.<br />#<br />#Default:<br /># redirect_rewrites_host_header on<br /><br /># TAG: redirector_access<br /># If defined, this access list specifies which requests are<br /># sent to the redirector processes. By default all requests<br /># are sent.<br />#<br />#Default:<br /># none<br /><br /># TAG: auth_param<br /># This is used to define parameters for the various authentication<br /># schemes supported by Squid.<br />#<br /># format: auth_param scheme parameter [setting]<br />#<br /># The order in which authentication schemes are presented to the client is<br /># dependent on the order the scheme first appears in config file. IE<br /># has a bug (it's not rfc 2617 compliant) in that it will use the basic<br /># scheme if basic is the first entry presented, even if more secure<br /># schemes are presented. For now use the order in the recommended<br /># settings section below. If other browsers have difficulties (don't<br /># recognize the schemes offered even if you are using basic) either<br /># put basic first, or disable the other schemes (by commenting out their<br /># program entry).<br />#<br /># Once an authentication scheme is fully configured, it can only be<br /># shutdown by shutting squid down and restarting. Changes can be made on<br /># the fly and activated with a reconfigure. I.E. You can change to a<br /># different helper, but not unconfigure the helper completely.<br />#<br /># Please note that while this directive defines how Squid processes<br /># authentication it does not automatically activate authentication.<br /># To use authentication you must in addition make use of ACLs based<br /># on login name in http_access (proxy_auth, proxy_auth_regex or<br /># external with %LOGIN used in the format tag). The browser will be<br /># challenged for authentication on the first such acl encountered<br /># in http_access processing and will also be re-challenged for new<br /># login credentials if the request is being denied by a proxy_auth<br /># type acl.<br />#<br /># WARNING: authentication can't be used in a transparently intercepting<br /># proxy as the client then thinks it is talking to an origin server and<br /># not the proxy. This is a limitation of bending the TCP/IP protocol to<br /># transparently intercepting port 80, not a limitation in Squid.<br />#<br /># === Parameters for the basic scheme follow. ===<br />#<br /># "program" cmdline<br /># Specify the command for the external authenticator. Such a program<br /># reads a line containing "username password" and replies "OK" or<br /># "ERR" in an endless loop. "ERR" responses may optionally be followed<br /># by a error description available as %m in the returned error page.<br />#<br /># By default, the basic authentication scheme is not used unless a<br /># program is specified.<br />#<br /># If you want to use the traditional proxy authentication, jump over to<br /># the helpers/basic_auth/NCSA directory and type:<br /># % make<br /># % make install<br />#<br /># Then, set this line to something like<br />#<br /># auth_param basic program /usr/libexec/ncsa_auth /usr/etc/passwd<br />#<br /># "children" numberofchildren<br /># The number of authenticator processes to spawn.<br /># If you start too few Squid will have to wait for them to process a<br /># backlog of usercode/password verifications, slowing it down. When<br /># password verifications are done via a (slow) network you are likely to<br /># need lots of authenticator processes.<br /># auth_param basic children 5<br />#<br /># "realm" realmstring<br /># Specifies the realm name which is to be reported to the client for<br /># the basic proxy authentication scheme (part of the text the user<br /># will see when prompted their username and password).<br /># auth_param basic realm Squid proxy-caching web server<br />#<br /># "credentialsttl" timetolive<br /># Specifies how long squid assumes an externally validated<br /># username:password pair is valid for - in other words how often the<br /># helper program is called for that user. Set this low to force<br /># revalidation with short lived passwords. Note that setting this high<br /># does not impact your susceptibility to replay attacks unless you are<br /># using an one-time password system (such as SecureID). If you are using<br /># such a system, you will be vulnerable to replay attacks unless you<br /># also use the max_user_ip ACL in an http_access rule.<br /># auth_param basic credentialsttl 2 hours<br />#<br /># "casesensitive" on|off<br /># Specifies if usernames are case sensitive. Most user databases are<br /># case insensitive allowing the same username to be spelled using both<br /># lower and upper case letters, but some are case sensitive. This<br /># makes a big difference for user_max_ip ACL processing and similar.<br /># auth_param basic casesensitive off<br />#<br /># === Parameters for the digest scheme follow ===<br />#<br /># "program" cmdline<br /># Specify the command for the external authenticator. Such a program<br /># reads a line containing "username":"realm" and replies with the<br /># appropriate H(A1) value base64 encoded or ERR if the user (or his H(A1)<br /># hash) does not exists. See rfc 2616 for the definition of H(A1).<br /># "ERR" responses may optionally be followed by a error description<br /># available as %m in the returned error page.<br />#<br /># By default, the digest authentication scheme is not used unless a<br /># program is specified.<br />#<br /># If you want to use a digest authenticator, jump over to the<br /># helpers/digest_auth/ directory and choose the authenticator to use.<br /># It it's directory type<br /># % make<br /># % make install<br />#<br /># Then, set this line to something like<br />#<br /># auth_param digest program /usr/libexec/digest_auth_pw /usr/etc/digpass<br />#<br />#<br /># "children" numberofchildren<br /># The number of authenticator processes to spawn (no default). If you<br /># start too few Squid will have to wait for them to process a backlog of<br /># H(A1) calculations, slowing it down. When the H(A1) calculations are<br /># done via a (slow) network you are likely to need lots of authenticator<br /># processes.<br /># auth_param digest children 5<br />#<br /># "realm" realmstring<br /># Specifies the realm name which is to be reported to the client for the<br /># digest proxy authentication scheme (part of the text the user will see<br /># when prompted their username and password).<br /># auth_param digest realm Squid proxy-caching web server<br />#<br /># "nonce_garbage_interval" timeinterval<br /># Specifies the interval that nonces that have been issued to clients are<br /># checked for validity.<br /># auth_param digest nonce_garbage_interval 5 minutes<br />#<br /># "nonce_max_duration" timeinterval<br /># Specifies the maximum length of time a given nonce will be valid for.<br /># auth_param digest nonce_max_duration 30 minutes<br />#<br /># "nonce_max_count" number<br /># Specifies the maximum number of times a given nonce can be used.<br /># auth_param digest nonce_max_count 50<br />#<br /># "nonce_strictness" on|off<br /># Determines if squid requires strict increment-by-1 behavior for nonce<br /># counts, or just incrementing (off - for use when useragents generate<br /># nonce counts that occasionally miss 1 (ie, 1,2,4,6)).<br /># auth_param digest nonce_strictness off<br />#<br /># "check_nonce_count" on|off<br /># This directive if set to off can disable the nonce count check<br /># completely to work around buggy digest qop implementations in certain<br /># mainstream browser versions. Default on to check the nonce count to<br /># protect from authentication replay attacks.<br /># auth_param digest check_nonce_count on<br />#<br /># "post_workaround" on|off<br /># This is a workaround to certain buggy browsers who sends an incorrect<br /># request digest in POST requests when reusing the same nonce as acquired<br /># earlier in response to a GET request.<br /># auth_param digest post_workaround off<br />#<br /># === NTLM scheme options follow ===<br />#<br /># "program" cmdline<br /># Specify the command for the external NTLM authenticator. Such a<br /># program participates in the NTLMSSP exchanges between Squid and the<br /># client and reads commands according to the Squid NTLMSSP helper<br /># protocol. See helpers/ntlm_auth/ for details. Recommended ntlm<br /># authenticator is ntlm_auth from Samba-3.X, but a number of other<br /># ntlm authenticators is available.<br />#<br /># By default, the ntlm authentication scheme is not used unless a<br /># program is specified.<br />#<br /># auth_param ntlm program /path/to/samba/bin/ntlm_auth --helper-protocol=squid-2.5-ntlmssp<br />#<br /># "children" numberofchildren<br /># The number of authenticator processes to spawn (no default). If you<br /># start too few Squid will have to wait for them to process a backlog<br /># of credential verifications, slowing it down. When credential<br /># verifications are done via a (slow) network you are likely to need<br /># lots of authenticator processes.<br /># auth_param ntlm children 5<br />#<br /># "max_challenge_reuses" number<br /># The maximum number of times a challenge given by a ntlm authentication<br /># helper can be reused. Increasing this number increases your exposure<br /># to replay attacks on your network. 0 (the default) means use the<br /># challenge is used only once. See also the max_ntlm_challenge_lifetime<br /># directive if enabling challenge reuses.<br /># auth_param ntlm max_challenge_reuses 0<br />#<br /># "max_challenge_lifetime" timespan<br /># The maximum time period a ntlm challenge is reused over. The<br /># actual period will be the minimum of this time AND the number of<br /># reused challenges.<br /># auth_param ntlm max_challenge_lifetime 2 minutes<br />#<br /># "use_ntlm_negotiate" on|off<br /># Enables support for NTLM NEGOTIATE packet exchanges with the helper.<br /># The configured ntlm authenticator must be able to handle NTLM<br /># NEGOTIATE packet. See the authenticator programs documentation if<br /># unsure. ntlm_auth from Samba-3.0.2 or later supports the use of this<br /># option.<br /># The NEGOTIATE packet is required to support NTLMv2 and a<br /># number of other negotiable NTLMSSP options, and also makes it<br /># more likely the negotiation is successful. Enabling this parameter<br /># will also solve problems encountered when NT domain policies<br /># restrict users to access only certain workstations. When this is off,<br /># all users must be allowed to log on the proxy servers too, or they'll<br /># get "invalid workstation" errors - and access denied - when trying to<br /># use Squid's services.<br /># Use of ntlm NEGOTIATE is incompatible with challenge reuse, so<br /># enabling this parameter will OVERRIDE the max_challenge_reuses and<br /># max_challenge_lifetime parameters and set them to 0.<br /># auth_param ntlm use_ntlm_negotiate off<br />#<br />#Recommended minimum configuration:<br />#auth_param digest program <uncomment and complete this line><br />#auth_param digest children 5<br />#auth_param digest realm Squid proxy-caching web server<br />#auth_param digest nonce_garbage_interval 5 minutes<br />#auth_param digest nonce_max_duration 30 minutes<br />#auth_param digest nonce_max_count 50<br />#auth_param ntlm program <uncomment and complete this line to activate><br />#auth_param ntlm children 5<br />#auth_param ntlm max_challenge_reuses 0<br />#auth_param ntlm max_challenge_lifetime 2 minutes<br />#auth_param ntlm use_ntlm_negotiate off<br />#auth_param basic program <uncomment and complete this line><br />auth_param basic children 5<br />auth_param basic realm Squid proxy-caching web server<br />auth_param basic credentialsttl 2 hours<br />auth_param basic casesensitive off<br /><br /># TAG: authenticate_cache_garbage_interval<br /># The time period between garbage collection across the username cache.<br /># This is a tradeoff between memory utilization (long intervals - say<br /># 2 days) and CPU (short intervals - say 1 minute). Only change if you<br /># have good reason to.<br />#<br />#Default:<br /># authenticate_cache_garbage_interval 1 hour<br /><br /># TAG: authenticate_ttl<br /># The time a user & their credentials stay in the logged in user cache<br /># since their last request. When the garbage interval passes, all user<br /># credentials that have passed their TTL are removed from memory.<br />#<br />#Default:<br /># authenticate_ttl 1 hour<br /><br /># TAG: authenticate_ip_ttl<br /># If you use proxy authentication and the 'max_user_ip' ACL, this<br /># directive controls how long Squid remembers the IP addresses<br /># associated with each user. Use a small value (e.g., 60 seconds) if<br /># your users might change addresses quickly, as is the case with<br /># dialups. You might be safe using a larger value (e.g., 2 hours) in a<br /># corporate LAN environment with relatively static address assignments.<br />#<br />#Default:<br /># authenticate_ip_ttl 0 seconds<br /><br /># TAG: external_acl_type<br /># This option defines external acl classes using a helper program to<br /># look up the status<br />#<br /># external_acl_type name [options] FORMAT.. /path/to/helper [helper arguments..]<br />#<br /># Options:<br />#<br /># ttl=n TTL in seconds for cached results (defaults to 3600<br /># for 1 hour)<br /># negative_ttl=n<br /># TTL for cached negative lookups (default same<br /># as ttl)<br /># children=n Concurrency level / number of processes spawn<br /># to service external acl lookups of this type.<br /># Note: see compatibility note below<br /># cache=n result cache size, 0 is unbounded (default)<br /># protocol=3.0 Use URL-escaped strings instead of quoting<br />#<br /># FORMAT specifications<br />#<br /># %LOGIN Authenticated user login name<br /># %IDENT Ident user name<br /># %SRC Client IP<br /># %DST Requested host<br /># %PROTO Requested protocol<br /># %PORT Requested port<br /># %METHOD Request method<br /># %{Header} HTTP request header<br /># %{Hdr:member} HTTP request header list member<br /># %{Hdr:;member}<br /># HTTP request header list member using ; as<br /># list separator. ; can be any non-alphanumeric<br /># character.<br />#<br /># In addition, any string specified in the referencing acl will<br /># also be included in the helper request line, after the specified<br /># formats (see the "acl external" directive)<br />#<br /># The helper receives lines per the above format specification,<br /># and returns lines starting with OK or ERR indicating the validity<br /># of the request and optionally followed by additional keywords with<br /># more details.<br />#<br /># General result syntax:<br />#<br /># OK/ERR keyword=value ...<br />#<br /># Defined keywords:<br />#<br /># user= The users name (login)<br /># error= Error description (only defined for ERR results)<br />#<br /># Keyword values need to be enclosed in quotes if they may contain<br /># whitespace, or the whitespace escaped using \. Any quotes or \<br /># characters within the keyword value must be \ escaped.<br />#<br /># If protocol=3.0 then URL escaping of the strings is used instead<br /># of the above described quoting format.<br />#<br /># Compatibility Note: The children= option was named concurrency= in<br /># Squid-2.5.STABLE3 and earlier and such syntax is still accepted to<br /># keep compatibility within the Squid-2.5 release. However, the meaning<br /># of concurrency= option has changed in Squid-3 and the old syntax of<br /># the directive is therefore deprecated from Squid-2.5.STABLE4 and later.<br /># If you want to be able to easily downgrade to earlier Squid-2.5<br /># releases you may want to continue using the old name, if not<br /># please use the new name.<br />#<br />#Default:<br /># none<br /><br /><br /># OPTIONS FOR TUNING THE CACHE<br /># -----------------------------------------------------------------------------<br /><br /># TAG: wais_relay_host<br /># TAG: wais_relay_port<br /># Relay WAIS request to host (1st arg) at port (2 arg).<br />#<br />#Default:<br /># wais_relay_port 0<br /><br /># TAG: request_header_max_size (KB)<br /># This specifies the maximum size for HTTP headers in a request.<br /># Request headers are usually relatively small (about 512 bytes).<br /># Placing a limit on the request header size will catch certain<br /># bugs (for example with persistent connections) and possibly<br /># buffer-overflow or denial-of-service attacks.<br />#<br />#Default:<br /># request_header_max_size 20 KB<br /><br /># TAG: request_body_max_size (KB)<br /># This specifies the maximum size for an HTTP request body.<br /># In other words, the maximum size of a PUT/POST request.<br /># A user who attempts to send a request with a body larger<br /># than this limit receives an "Invalid Request" error message.<br /># If you set this parameter to a zero (the default), there will<br /># be no limit imposed.<br />#<br />#Default:<br /># request_body_max_size 0 KB<br /><br /># TAG: refresh_pattern<br /># usage: refresh_pattern [-i] regex min percent max [options]<br />#<br /># By default, regular expressions are CASE-SENSITIVE. To make<br /># them case-insensitive, use the -i option.<br />#<br /># 'Min' is the time (in minutes) an object without an explicit<br /># expiry time should be considered fresh. The recommended<br /># value is 0, any higher values may cause dynamic applications<br /># to be erroneously cached unless the application designer<br /># has taken the appropriate actions.<br />#<br /># 'Percent' is a percentage of the objects age (time since last<br /># modification age) an object without explicit expiry time<br /># will be considered fresh.<br />#<br /># 'Max' is an upper limit on how long objects without an explicit<br /># expiry time will be considered fresh.<br />#<br /># options: override-expire<br /># override-lastmod<br /># reload-into-ims<br /># ignore-reload<br />#<br /># override-expire enforces min age even if the server<br /># sent a Expires: header. Doing this VIOLATES the HTTP<br /># standard. Enabling this feature could make you liable<br /># for problems which it causes.<br />#<br /># override-lastmod enforces min age even on objects<br /># that were modified recently.<br />#<br /># reload-into-ims changes client no-cache or ``reload''<br /># to If-Modified-Since requests. Doing this VIOLATES the<br /># HTTP standard. Enabling this feature could make you<br /># liable for problems which it causes.<br />#<br /># ignore-reload ignores a client no-cache or ``reload''<br /># header. Doing this VIOLATES the HTTP standard. Enabling<br /># this feature could make you liable for problems which<br /># it causes.<br />#<br /># Basically a cached object is:<br />#<br /># FRESH if expires < now, else STALE<br /># STALE if age > max<br /># FRESH if lm-factor < percent, else STALE<br /># FRESH if age < min<br /># else STALE<br />#<br /># The refresh_pattern lines are checked in the order listed here.<br /># The first entry which matches is used. If none of the entries<br /># match the default will be used.<br />#<br /># Note, you must uncomment all the default lines if you want<br /># to change one. The default setting is only active if none is<br /># used.<br />#<br />#Suggested default:<br />refresh_pattern ^ftp: 1440 20% 10080<br />refresh_pattern ^gopher: 1440 0% 1440<br />refresh_pattern . 0 20% 4320<br /><br /># TAG: quick_abort_min (KB)<br /># TAG: quick_abort_max (KB)<br /># TAG: quick_abort_pct (percent)<br /># The cache by default continues downloading aborted requests<br /># which are almost completed (less than 16 KB remaining). This<br /># may be undesirable on slow (e.g. SLIP) links and/or very busy<br /># caches. Impatient users may tie up file descriptors and<br /># bandwidth by repeatedly requesting and immediately aborting<br /># downloads.<br />#<br /># When the user aborts a request, Squid will check the<br /># quick_abort values to the amount of data transfered until<br /># then.<br />#<br /># If the transfer has less than 'quick_abort_min' KB remaining,<br /># it will finish the retrieval.<br />#<br /># If the transfer has more than 'quick_abort_max' KB remaining,<br /># it will abort the retrieval.<br />#<br /># If more than 'quick_abort_pct' of the transfer has completed,<br /># it will finish the retrieval.<br />#<br /># If you do not want any retrieval to continue after the client<br /># has aborted, set both 'quick_abort_min' and 'quick_abort_max'<br /># to '0 KB'.<br />#<br /># If you want retrievals to always continue if they are being<br /># cached set 'quick_abort_min' to '-1 KB'.<br />#<br />#Default:<br /># quick_abort_min 16 KB<br /># quick_abort_max 16 KB<br /># quick_abort_pct 95<br /><br /># TAG: negative_ttl time-units<br /># Time-to-Live (TTL) for failed requests. Certain types of<br /># failures (such as "connection refused" and "404 Not Found") are<br /># negatively-cached for a configurable amount of time. The<br /># default is 5 minutes. Note that this is different from<br /># negative caching of DNS lookups.<br />#<br />#Default:<br /># negative_ttl 5 minutes<br /><br /># TAG: positive_dns_ttl time-units<br /># Upper limit on how long Squid will cache positive DNS responses.<br /># Default is 6 hours (360 minutes). This directive must be set<br /># larger than negative_dns_ttl.<br />#<br />#Default:<br /># positive_dns_ttl 6 hours<br /><br /># TAG: negative_dns_ttl time-units<br /># Time-to-Live (TTL) for negative caching of failed DNS lookups.<br /># This also makes sets the lower cache limit on positive lookups.<br /># Minimum value is 1 second, and it is not recommendable to go<br /># much below 10 seconds.<br />#<br />#Default:<br /># negative_dns_ttl 1 minute<br /><br /># TAG: range_offset_limit (bytes)<br /># Sets a upper limit on how far into the the file a Range request<br /># may be to cause Squid to prefetch the whole file. If beyond this<br /># limit Squid forwards the Range request as it is and the result<br /># is NOT cached.<br />#<br /># This is to stop a far ahead range request (lets say start at 17MB)<br /># from making Squid fetch the whole object up to that point before<br /># sending anything to the client.<br />#<br /># A value of -1 causes Squid to always fetch the object from the<br /># beginning so it may cache the result. (2.0 style)<br />#<br /># A value of 0 causes Squid to never fetch more than the<br /># client requested. (default)<br />#<br />#Default:<br /># range_offset_limit 0 KB<br /><br /><br /># TIMEOUTS<br /># -----------------------------------------------------------------------------<br /><br /># TAG: forward_timeout time-units<br /># This parameter specifies how long Squid should at most attempt in<br /># finding a forwarding path for the request before giving up.<br />#<br />#Default:<br /># forward_timeout 4 minutes<br /><br /># TAG: connect_timeout time-units<br /># This parameter specifies how long to wait for the TCP connect to<br /># the requested server or peer to complete before Squid should<br /># attempt to find another path where to forward the request.<br />#<br />#Default:<br /># connect_timeout 1 minute<br /><br /># TAG: peer_connect_timeout time-units<br /># This parameter specifies how long to wait for a pending TCP<br /># connection to a peer cache. The default is 30 seconds. You<br /># may also set different timeout values for individual neighbors<br /># with the 'connect-timeout' option on a 'cache_peer' line.<br />#<br />#Default:<br /># peer_connect_timeout 30 seconds<br /><br /># TAG: read_timeout time-units<br /># The read_timeout is applied on server-side connections. After<br /># each successful read(), the timeout will be extended by this<br /># amount. If no data is read again after this amount of time,<br /># the request is aborted and logged with ERR_READ_TIMEOUT. The<br /># default is 15 minutes.<br />#<br />#Default:<br /># read_timeout 15 minutes<br /><br /># TAG: request_timeout<br /># How long to wait for an HTTP request after initial<br /># connection establishment.<br />#<br />#Default:<br /># request_timeout 5 minutes<br /><br /># TAG: persistent_request_timeout<br /># How long to wait for the next HTTP request on a persistent<br /># connection after the previous request completes.<br />#<br />#Default:<br /># persistent_request_timeout 1 minute<br /><br /># TAG: client_lifetime time-units<br /># The maximum amount of time a client (browser) is allowed to<br /># remain connected to the cache process. This protects the Cache<br /># from having a lot of sockets (and hence file descriptors) tied up<br /># in a CLOSE_WAIT state from remote clients that go away without<br /># properly shutting down (either because of a network failure or<br /># because of a poor client implementation). The default is one<br /># day, 1440 minutes.<br />#<br /># NOTE: The default value is intended to be much larger than any<br /># client would ever need to be connected to your cache. You<br /># should probably change client_lifetime only as a last resort.<br /># If you seem to have many client connections tying up<br /># filedescriptors, we recommend first tuning the read_timeout,<br /># request_timeout, persistent_request_timeout and quick_abort values.<br />#<br />#Default:<br /># client_lifetime 1 day<br /><br /># TAG: half_closed_clients<br /># Some clients may shutdown the sending side of their TCP<br /># connections, while leaving their receiving sides open. Sometimes,<br /># Squid can not tell the difference between a half-closed and a<br /># fully-closed TCP connection. By default, half-closed client<br /># connections are kept open until a read(2) or write(2) on the<br /># socket returns an error. Change this option to 'off' and Squid<br /># will immediately close client connections when read(2) returns<br /># "no more data to read."<br />#<br />#Default:<br /># half_closed_clients on<br /><br /># TAG: pconn_timeout<br /># Timeout for idle persistent connections to servers and other<br /># proxies.<br />#<br />#Default:<br /># pconn_timeout 120 seconds<br /><br /># TAG: ident_timeout<br /># Maximum time to wait for IDENT lookups to complete.<br />#<br /># If this is too high, and you enabled IDENT lookups from untrusted<br /># users, you might be susceptible to denial-of-service by having<br /># many ident requests going at once.<br />#<br />#Default:<br /># ident_timeout 10 seconds<br /><br /># TAG: shutdown_lifetime time-units<br /># When SIGTERM or SIGHUP is received, the cache is put into<br /># "shutdown pending" mode until all active sockets are closed.<br /># This value is the lifetime to set for all open descriptors<br /># during shutdown mode. Any active clients after this many<br /># seconds will receive a 'timeout' message.<br />#<br />#Default:<br /># shutdown_lifetime 30 seconds<br /><br /><br /># ACCESS CONTROLS<br /># -----------------------------------------------------------------------------<br /><br /># TAG: acl<br /># Defining an Access List<br />#<br /># acl aclname acltype string1 ...<br /># acl aclname acltype "file" ...<br />#<br /># when using "file", the file should contain one item per line<br />#<br /># acltype is one of the types described below<br />#<br /># By default, regular expressions are CASE-SENSITIVE. To make<br /># them case-insensitive, use the -i option.<br />#<br /># acl aclname src ip-address/netmask ... (clients IP address)<br /># acl aclname src addr1-addr2/netmask ... (range of addresses)<br /># acl aclname dst ip-address/netmask ... (URL host's IP address)<br /># acl aclname myip ip-address/netmask ... (local socket IP address)<br />#<br /># acl aclname arp mac-address ... (xx:xx:xx:xx:xx:xx notation)<br /># # The arp ACL requires the special configure option --enable-arp-acl.<br /># # Furthermore, the arp ACL code is not portable to all operating systems.<br /># # It works on Linux, Solaris, FreeBSD and some other *BSD variants.<br /># #<br /># # NOTE: Squid can only determine the MAC address for clients that are on<br /># # the same subnet. If the client is on a different subnet, then Squid cannot<br /># # find out its MAC address.<br />#<br /># acl aclname srcdomain .foo.com ... # reverse lookup, client IP<br /># acl aclname dstdomain .foo.com ... # Destination server from URL<br /># acl aclname srcdom_regex [-i] xxx ... # regex matching client name<br /># acl aclname dstdom_regex [-i] xxx ... # regex matching server<br /># # For dstdomain and dstdom_regex a reverse lookup is tried if a IP<br /># # based URL is used and no match is found. The name "none" is used<br /># # if the reverse lookup fails.<br />#<br /># acl aclname time [day-abbrevs] [h1:m1-h2:m2]<br /># day-abbrevs:<br /># S - Sunday<br /># M - Monday<br /># T - Tuesday<br /># W - Wednesday<br /># H - Thursday<br /># F - Friday<br /># A - Saturday<br /># h1:m1 must be less than h2:m2<br /># acl aclname url_regex [-i] ^http:// ... # regex matching on whole URL<br /># acl aclname urlpath_regex [-i] \.gif$ ... # regex matching on URL path<br /># acl aclname urllogin [-i] [^a-zA-Z0-9] ... # regex matching on URL login field<br /># acl aclname port 80 70 21 ...<br /># acl aclname port 0-1024 ... # ranges allowed<br /># acl aclname myport 3128 ... # (local socket TCP port)<br /># acl aclname proto HTTP FTP ...<br /># acl aclname method GET POST ...<br /># acl aclname browser [-i] regexp ...<br /># # pattern match on User-Agent header (see also req_header below)<br /># acl aclname referer_regex [-i] regexp ...<br /># # pattern match on Referer header<br /># # Referer is highly unreliable, so use with care<br /># acl aclname ident username ...<br /># acl aclname ident_regex [-i] pattern ...<br /># # string match on ident output.<br /># # use REQUIRED to accept any non-null ident.<br /># acl aclname src_as number ...<br /># acl aclname dst_as number ...<br /># # Except for access control, AS numbers can be used for<br /># # routing of requests to specific caches. Here's an<br /># # example for routing all requests for AS#1241 and only<br /># # those to mycache.mydomain.net:<br /># # acl asexample dst_as 1241<br /># # cache_peer_access mycache.mydomain.net allow asexample<br /># # cache_peer_access mycache_mydomain.net deny all<br />#<br /># acl aclname proxy_auth username ...<br /># acl aclname proxy_auth_regex [-i] pattern ...<br /># # list of valid usernames<br /># # use REQUIRED to accept any valid username.<br /># #<br /># # NOTE: when a Proxy-Authentication header is sent but it is not<br /># # needed during ACL checking the username is NOT logged<br /># # in access.log.<br /># #<br /># # NOTE: proxy_auth requires a EXTERNAL authentication program<br /># # to check username/password combinations (see<br /># # auth_param directive).<br /># #<br /># # WARNING: proxy_auth can't be used in a transparent proxy. It<br /># # collides with any authentication done by origin servers. It may<br /># # seem like it works at first, but it doesn't.<br />#<br /># acl aclname snmp_community string ...<br /># # A community string to limit access to your SNMP Agent<br /># # Example:<br /># #<br /># # acl snmppublic snmp_community public<br />#<br /># acl aclname maxconn number<br /># # This will be matched when the client's IP address has<br /># # more than <number> HTTP connections established.<br />#<br /># acl aclname max_user_ip [-s] number<br /># # This will be matched when the user attempts to log in from more<br /># # than <number> different ip addresses. The authenticate_ip_ttl<br /># # parameter controls the timeout on the ip entries.<br /># # If -s is specified the limit is strict, denying browsing<br /># # from any further IP addresses until the ttl has expired. Without<br /># # -s Squid will just annoy the user by "randomly" denying requests.<br /># # (the counter is reset each time the limit is reached and a<br /># # request is denied)<br /># # NOTE: in acceleration mode or where there is mesh of child proxies,<br /># # clients may appear to come from multiple addresses if they are<br /># # going through proxy farms, so a limit of 1 may cause user problems.<br />#<br /># acl aclname req_mime_type mime-type1 ...<br /># # regex match against the mime type of the request generated<br /># # by the client. Can be used to detect file upload or some<br /># # types HTTP tunneling requests.<br /># # NOTE: This does NOT match the reply. You cannot use this<br /># # to match the returned file type.<br />#<br /># acl aclname req_header header-name [-i] any\.regex\.here<br /># # regex match against any of the known request headers. May be<br /># # thought of as a superset of "browser", "referer" and "mime-type"<br /># # ACLs.<br />#<br /># acl aclname rep_mime_type mime-type1 ...<br /># # regex match against the mime type of the reply received by<br /># # squid. Can be used to detect file download or some<br /># # types HTTP tunneling requests.<br /># # NOTE: This has no effect in http_access rules. It only has<br /># # effect in rules that affect the reply data stream such as<br /># # http_reply_access.<br />#<br /># acl aclname rep_header header-name [-i] any\.regex\.here<br /># # regex match against any of the known response headers.<br /># # Example:<br /># #<br /># # acl many_spaces rep_header Content-Disposition -i [[:space:]]{3,}<br />#<br /># acl acl_name external class_name [arguments...]<br /># # external ACL lookup via a helper class defined by the<br /># # external_acl_type directive.<br />#<br />#Examples:<br />#acl macaddress arp 09:00:2b:23:45:67<br />#acl myexample dst_as 1241<br />#acl password proxy_auth REQUIRED<br />#acl fileupload req_mime_type -i ^multipart/form-data$<br />#acl javascript rep_mime_type -i ^application/x-javascript$<br />#<br />#Recommended minimum configuration:<br />acl all src 0.0.0.0/0.0.0.0<br /><br /><br />#################################################<br />acl net2 src 192.168.0.200/32<br />acl net2 src 192.168.0.10/32<br />acl net2 src 192.168.0.11/32<br />acl net3 src 192.168.0.101/32<br />acl net3 src 192.168.0.27/32<br />acl net3 src 192.168.0.41/32<br />acl net src 192.168.1.0/255.255.255.0<br />##################################################<br /><br /><br /><br /><br />acl manager proto cache_object<br />acl localhost src 127.0.0.1/255.255.255.255<br />acl to_localhost dst 127.0.0.0/8<br />acl SSL_ports port 443 563<br />acl Safe_ports port 80 # http<br />acl Safe_ports port 21 # ftp<br />acl Safe_ports port 443 563 # https, snews<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 />#acl dl1 url_regex -i "/etc/squid/ban"<br />#acl abc url_regex -i cgi-bin passport gateway google gmail<br /><br /><br />######################## Windows Update Block ###########<br />acl abc2 url_regex -i ^http://du.download.windowsupdate.com<br />acl abc2 url_regex -i ^http://download.windowsupdate.com<br />acl abc2 url_regex -i ^http://www.download.windowsupdate.com<br />#########################<br /><br />acl opendl time 11:00-23:59<br />acl opendl time 00:00-01:00<br /><br /># TAG: follow_x_forwarded_for<br /># Allowing or Denying the X-Forwarded-For header to be followed to<br /># find the original source of a request.<br />#<br /># Requests may pass through a chain of several other proxies<br /># before reaching us. The X-Forwarded-For header will contain a<br /># comma-separated list of the IP addresses in the chain, with the<br /># rightmost address being the most recent.<br />#<br /># If a request reaches us from a source that is allowed by this<br /># configuration item, then we consult the X-Forwarded-For header<br /># to see where that host received the request from. If the<br /># X-Forwarded-For header contains multiple addresses, and if<br /># acl_uses_indirect_client is on, then we continue backtracking<br /># until we reach an address for which we are not allowed to<br /># follow the X-Forwarded-For header, or until we reach the first<br /># address in the list. (If acl_uses_indirect_client is off, then<br /># it's impossible to backtrack through more than one level of<br /># X-Forwarded-For addresses.)<br />#<br /># The end result of this process is an IP address that we will<br /># refer to as the indirect client address. This address may<br /># be treated as the client address for access control, delay<br /># pools and logging, depending on the acl_uses_indirect_client,<br /># delay_pool_uses_indirect_client and log_uses_indirect_client<br /># options.<br />#<br /># SECURITY CONSIDERATIONS:<br />#<br /># Any host for which we follow the X-Forwarded-For header<br /># can place incorrect information in the header, and Squid<br /># will use the incorrect information as if it were the<br /># source address of the request. This may enable remote<br /># hosts to bypass any access control restrictions that are<br /># based on the client's source addresses.<br />#<br /># For example:<br />#<br /># acl localhost src 127.0.0.1<br /># acl my_other_proxy srcdomain .proxy.example.com<br /># follow_x_forwarded_for allow localhost<br /># follow_x_forwarded_for allow my_other_proxy<br />#<br />#Default:<br /># follow_x_forwarded_for deny all<br /><br /># TAG: acl_uses_indirect_client on|off<br /># Controls whether the indirect client address<br /># (see follow_x_forwarded_for) is used instead of the<br /># direct client address in acl matching.<br />#<br />#Default:<br /># acl_uses_indirect_client on<br /><br /># TAG: delay_pool_uses_indirect_client on|off<br /># Controls whether the indirect client address<br /># (see follow_x_forwarded_for) is used instead of the<br /># direct client address in delay pools.<br />#<br />#Default:<br /># delay_pool_uses_indirect_client on<br /><br /># TAG: log_uses_indirect_client on|off<br /># Controls whether the indirect client address<br /># (see follow_x_forwarded_for) is used instead of the<br /># direct client address in the access log.<br />#<br />#Default:<br /># log_uses_indirect_client on<br /><br /># TAG: http_access<br /># Allowing or Denying access based on defined access lists<br />#<br /># Access to the HTTP port:<br /># http_access allow|deny [!]aclname ...<br />#<br /># NOTE on default values:<br />#<br /># If there are no "access" lines present, the default is to deny<br /># the request.<br />#<br /># If none of the "access" lines cause a match, the default is the<br /># opposite of the last line in the list. If the last line was<br /># deny, the default is allow. Conversely, if the last line<br /># is allow, the default will be deny. For these reasons, it is a<br /># good idea to have an "deny all" or "allow all" entry at the end<br /># of your access lists to avoid potential confusion.<br />#<br />#Default:<br /># http_access deny all<br />#<br />#Recommended minimum configuration:<br />#<br /># Only allow cachemgr access from localhost<br />http_access allow manager localhost<br />http_access deny manager<br /># Deny requests to unknown ports<br />http_access deny !Safe_ports<br /># Deny CONNECT to other than 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 /># INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS<br /><br /># Example rule allowing access from your local networks. Adapt<br /># to list your (internal) IP networks from where browsing should<br /># be allowed<br />#acl our_networks src 192.168.1.0/24 192.168.2.0/24<br />#http_access allow our_networks<br /><br /># And finally deny all other access to this proxy<br />http_access allow localhost<br /><br />http_access deny abc2<br />http_access allow net<br />http_access allow net2<br /><br />http_access deny all<br /><br /># TAG: http_reply_access<br /># Allow replies to client requests. This is complementary to http_access.<br />#<br /># http_reply_access allow|deny [!] aclname ...<br />#<br /># NOTE: if there are no access lines present, the default is to allow<br /># all replies<br />#<br /># If none of the access lines cause a match the opposite of the<br /># last line will apply. Thus it is good practice to end the rules<br /># with an "allow all" or "deny all" entry.<br />#<br />#Default:<br /> http_reply_access allow all<br />#<br />#Recommended minimum configuration:<br />#<br /># Insert your own rules here.<br />#<br />#<br /># and finally allow by default<br />http_reply_access allow all<br /><br /># TAG: icp_access<br /># Allowing or Denying access to the ICP port based on defined<br /># access lists<br />#<br /># icp_access allow|deny [!]aclname ...<br />#<br /># See http_access for details<br />#<br />#Default:<br /># icp_access deny all<br />#<br />#Allow ICP queries from everyone<br />icp_access allow all<br /><br /># TAG: miss_access<br /># Use to force your neighbors to use you as a sibling instead of<br /># a parent. For example:<br />#<br /># acl localclients src 172.16.0.0/16<br /># miss_access allow localclients<br /># miss_access deny !localclients<br />#<br /># This means only your local clients are allowed to fetch<br /># MISSES and all other clients can only fetch HITS.<br />#<br /># By default, allow all clients who passed the http_access rules<br /># to fetch MISSES from us.<br />#<br />#Default setting:<br /># miss_access allow all<br /><br /># TAG: cache_peer_access<br /># Similar to 'cache_peer_domain' but provides more flexibility by<br /># using ACL elements.<br />#<br /># cache_peer_access cache-host allow|deny [!]aclname ...<br />#<br /># The syntax is identical to 'http_access' and the other lists of<br /># ACL elements. See the comments for 'http_access' below, or<br /># the Squid FAQ (http://www.squid-cache.org/FAQ/FAQ-10.html).<br />#<br />#Default:<br /># none<br /><br /># TAG: ident_lookup_access<br /># A list of ACL elements which, if matched, cause an ident<br /># (RFC931) lookup to be performed for this request. For<br /># example, you might choose to always perform ident lookups<br /># for your main multi-user Unix boxes, but not for your Macs<br /># and PCs. By default, ident lookups are not performed for<br /># any requests.<br />#<br /># To enable ident lookups for specific client addresses, you<br /># can follow this example:<br />#<br /># acl ident_aware_hosts src 198.168.1.0/255.255.255.0<br /># ident_lookup_access allow ident_aware_hosts<br /># ident_lookup_access deny all<br />#<br /># Only src type ACL checks are fully supported. A src_domain<br /># ACL might work at times, but it will not always provide<br /># the correct result.<br />#<br />#Default:<br /># ident_lookup_access deny all<br /><br /># TAG: tcp_outgoing_tos<br /># Allows you to select a TOS/Diffserv value to mark outgoing<br /># connections with, based on the username or source address<br /># making the request.<br />#<br /># tcp_outgoing_tos ds-field [!]aclname ...<br />#<br /># Example where normal_service_net uses the TOS value 0x00<br /># and normal_service_net uses 0x20<br />#<br /># acl normal_service_net src 10.0.0.0/255.255.255.0<br /># acl good_service_net src 10.0.1.0/255.255.255.0<br /># tcp_outgoing_tos 0x00 normal_service_net 0x00<br /># tcp_outgoing_tos 0x20 good_service_net<br />#<br /># TOS/DSCP values really only have local significance - so you should<br /># know what you're specifying. For more information, see RFC2474 and <br /># RFC3260.<br />#<br /># The TOS/DSCP byte must be exactly that - a octet value 0 - 255, or<br /># "default" to use whatever default your host has. Note that in<br /># practice often only values 0 - 63 is usable as the two highest bits<br /># have been redefined for use by ECN (RFC3168).<br />#<br /># Processing proceeds in the order specified, and stops at first fully<br /># matching line.<br />#<br /># Note: The use of this directive using client dependent ACLs is<br /># incompatible with the use of server side persistent connetions. To<br /># ensure correct results it is best to set server_persisten_connections<br /># to off when using this directive in such configurations.<br />#<br />#Default:<br /># none<br /><br /># TAG: tcp_outgoing_address<br /># Allows you to map requests to different outgoing IP addresses<br /># based on the username or sourceaddress of the user making<br /># the request.<br />#<br /># tcp_outgoing_address ipaddr [[!]aclname] ...<br />#<br /># Example where requests from 10.0.0.0/24 will be forwarded<br /># with source address 10.1.0.1, 10.0.2.0/24 forwarded with<br /># source address 10.1.0.2 and the rest will be forwarded with<br /># source address 10.1.0.3.<br />#<br /># acl normal_service_net src 10.0.0.0/255.255.255.0<br /># acl good_service_net src 10.0.1.0/255.255.255.0<br /># tcp_outgoing_address 10.0.0.1 normal_service_net<br /># tcp_outgoing_address 10.0.0.2 good_service_net<br /># tcp_outgoing_address 10.0.0.3<br />#<br /># Processing proceeds in the order specified, and stops at first fully<br /># matching line.<br />#<br /># Note: The use of this directive using client dependent ACLs is<br /># incompatible with the use of server side persistent connetions. To<br /># ensure correct results it is best to set server_persisten_connections<br /># to off when using this directive in such configurations.<br />#<br />#Default:<br /># none<br /><br /># TAG: reply_header_max_size (KB)<br /># This specifies the maximum size for HTTP headers in a reply.<br /># Reply headers are usually relatively small (about 512 bytes).<br /># Placing a limit on the reply header size will catch certain<br /># bugs (for example with persistent connections) and possibly<br /># buffer-overflow or denial-of-service attacks.<br />#<br />#Default:<br /># reply_header_max_size 20 KB<br /><br /># TAG: reply_body_max_size bytes allow|deny acl acl...<br /># This option specifies the maximum size of a reply body in bytes.<br /># It can be used to prevent users from downloading very large files,<br /># such as MP3's and movies. When the reply headers are received,<br /># the reply_body_max_size lines are processed, and the first line with<br /># a result of "allow" is used as the maximum body size for this reply.<br /># This size is checked twice. First when we get the reply headers,<br /># we check the content-length value. If the content length value exists<br /># and is larger than the allowed size, the request is denied and the<br /># user receives an error message that says "the request or reply<br /># is too large." If there is no content-length, and the reply<br /># size exceeds this limit, the client's connection is just closed<br /># and they will receive a partial reply.<br />#<br /># WARNING: downstream caches probably can not detect a partial reply<br /># if there is no content-length header, so they will cache<br /># partial responses and give them out as hits. You should NOT<br /># use this option if you have downstream caches.<br />#<br /># If you set this parameter to zero (the default), there will be<br /># no limit imposed.<br />#<br />#Default:<br /># reply_body_max_size 0 allow all<br /><br /><br /># ADMINISTRATIVE PARAMETERS<br /># -----------------------------------------------------------------------------<br /><br /># TAG: cache_mgr<br /># Email-address of local cache manager who will receive<br /># mail if the cache dies. The default is "root".<br />#<br /><br />cache_mgr imrance@hotmail.com<br />#Default:<br /># cache_mgr root<br /><br /># TAG: mail_from<br /># From: email-address for mail sent when the cache dies.<br /># The default is to use 'appname@unique_hostname'.<br /># Default appname value is "squid", can be changed into <br /># src/globals.h before building squid.<br />#<br />#Default:<br /># none<br /><br /># TAG: mail_program<br /># Email program used to send mail if the cache dies.<br /># The default is "mail". The specified program must complain<br /># with the standard Unix mail syntax:<br /># mail_program recipient < mailfile<br /># Optional command line options can be specified.<br />#<br />#Default:<br /># mail_program mail<br /><br /># TAG: cache_effective_user<br /># If you start Squid as root, it will change its effective/real<br /># UID/GID to the user specified below. The default is to change<br /># to UID to "squid". If you define cache_effective_user, but not<br /># cache_effective_group, Squid sets the GID to the effective<br /># user's default group ID (taken from the password file) and<br /># supplementary group list from the from groups membership of<br /># cache_effective_user.<br />cache_effective_user squid<br />#<br />#Default:<br /># cache_effective_user squid<br /><br /># TAG: cache_effective_group<br /># If you want Squid to run with a specific GID regardless of<br /># the group memberships of the effective user then set this<br /># to the group (or GID) you want Squid to run as. When set<br /># all other group privileges of the effective user is ignored<br /># and only this GID is effective. If Squid is not started as<br /># root the user starting Squid must be member of the specified<br /># group.<br />cache_effective_group squid<br />#<br />#Default:<br /># cache_effective_group squid <br /><br /><br />visible_hostname proxy.rays.net<br /># TAG: visible_hostname<br /># If you want to present a special hostname in error messages, etc,<br /># define this. Otherwise, the return value of gethostname()<br /># will be used. If you have multiple caches in a cluster and<br /># get errors about IP-forwarding you must set them to have individual<br /># names with this setting.<br />#<br />#Default:<br /># none<br /><br /># TAG: unique_hostname<br /># If you want to have multiple machines with the same<br /># 'visible_hostname' you must give each machine a different<br /># 'unique_hostname' so forwarding loops can be detected.<br />#<br />#Default:<br /># none<br /><br /># TAG: hostname_aliases<br /># A list of other DNS names your cache has.<br />#<br />#Default:<br /># none<br /><br /><br /># OPTIONS FOR THE CACHE REGISTRATION SERVICE<br /># -----------------------------------------------------------------------------<br />#<br /># This section contains parameters for the (optional) cache<br /># announcement service. This service is provided to help<br /># cache administrators locate one another in order to join or<br /># create cache hierarchies.<br />#<br /># An 'announcement' message is sent (via UDP) to the registration<br /># service by Squid. By default, the announcement message is NOT<br /># SENT unless you enable it with 'announce_period' below.<br />#<br /># The announcement message includes your hostname, plus the<br /># following information from this configuration file:<br />#<br /># http_port<br /># icp_port<br /># cache_mgr<br />#<br /># All current information is processed regularly and made<br /># available on the Web at http://www.ircache.net/Cache/Tracker/.<br /><br /># TAG: announce_period<br /># This is how frequently to send cache announcements. The<br /># default is `0' which disables sending the announcement<br /># messages.<br />#<br /># To enable announcing your cache, just uncomment the line<br /># below.<br />#<br />#Default:<br /># announce_period 0<br />#<br />#To enable announcing your cache, just uncomment the line below.<br />#announce_period 1 day<br /><br /># TAG: announce_host<br /># TAG: announce_file<br /># TAG: announce_port<br /># announce_host and announce_port set the hostname and port<br /># number where the registration message will be sent.<br />#<br /># Hostname will default to 'tracker.ircache.net' and port will<br /># default default to 3131. If the 'filename' argument is given,<br /># the contents of that file will be included in the announce<br /># message.<br />#<br />#Default:<br /># announce_host tracker.ircache.net<br /># announce_port 3131<br /><br /><br /># HTTPD-ACCELERATOR OPTIONS<br /># -----------------------------------------------------------------------------<br /><br /><br /> httpd_accel_host virtual<br /># TAG: httpd_accel_host<br /># TAG: httpd_accel_port<br /># If you want to run Squid as an httpd accelerator, define the<br /># host name and port number where the real HTTP server is.<br />#<br /># If you want IP based virtual host support specify the<br /># hostname as "virtual". This will make Squid use the IP address<br /># where it accepted the request as hostname in the URL.<br />#<br /># If you want virtual port support specify the port as "0".<br />#<br /># NOTE: enabling httpd_accel_host disables proxy-caching and<br /># ICP. If you want these features enabled also, set<br /># the 'httpd_accel_with_proxy' option.<br />#<br />#Default:<br /> httpd_accel_port 80<br /><br /># TAG: httpd_accel_single_host on|off<br /># If you are running Squid as an accelerator and have a single backend<br /># server set this to on. This causes Squid to forward the request<br /># to this server, regardless of what any redirectors or Host headers<br /># say.<br />#<br /># Leave this at off if you have multiple backend servers, and use a<br /># redirector (or host table or private DNS) to map the requests to the<br /># appropriate backend servers. Note that the mapping needs to be a<br /># 1-1 mapping between requested and backend (from redirector) domain<br /># names or caching will fail, as caching is performed using the<br /># URL returned from the redirector.<br />#<br /># See also redirect_rewrites_host_header.<br />#<br />#Default:<br /># httpd_accel_single_host off<br /><br /># TAG: httpd_accel_with_proxy on|off<br /># If you want to use Squid as both a local httpd accelerator<br /># and as a proxy, change this to 'on'. Note however your<br /># proxy users may have trouble to reach the accelerated domains<br /># unless their browsers are configured not to use this proxy for<br /># those domains (for example via the no_proxy browser configuration<br /># setting)<br />#<br />#Default:<br /> httpd_accel_with_proxy on<br /><br /># TAG: httpd_accel_uses_host_header on|off<br /># HTTP/1.1 requests include a Host: header which is basically the<br /># hostname from the URL. The Host: header is used for domain based<br /># virtual hosts. If your accelerator needs to provide domain based<br /># virtual hosts on the same IP address you will need to turn this<br /># on.<br />#<br /># Note Squid does NOT check the value of the Host header matches<br /># any of your accelerated server, so it may open a big security hole<br /># unless you take care to set up access controls proper. We recommend<br /># this option remain disabled unless you are sure of what you<br /># are doing.<br />#<br /># However, you will need to enable this option if you run Squid<br /># as a transparent proxy. Otherwise, virtual servers which<br /># require the Host: header will not be properly cached.<br />#<br />#Default:<br /> httpd_accel_uses_host_header on<br /><br /># TAG: httpd_accel_no_pmtu_disc on|off<br /># In many setups of transparently intercepting proxies Path-MTU<br /># discovery can not work on traffic towards the clients. This is<br /># the case when the intercepting device does not fully track<br /># connections and fails to forward ICMP must fragment messages<br /># to the cache server. <br /># <br /># If you have such setup and experience that certain clients<br /># sporadically hang or never complete requests set this to on.<br />#<br />#Default:<br /># httpd_accel_no_pmtu_disc off<br /><br /><br /># MISCELLANEOUS<br /># -----------------------------------------------------------------------------<br /><br /># TAG: dns_testnames<br /># The DNS tests exit as soon as the first site is successfully looked up<br />#<br /># This test can be disabled with the -D command line option.<br />#<br />#Default:<br /># dns_testnames netscape.com internic.net nlanr.net microsoft.com<br /><br /># TAG: logfile_rotate<br /># Specifies the number of logfile rotations to make when you<br /># type 'squid -k rotate'. The default is 10, which will rotate<br /># with extensions 0 through 9. Setting logfile_rotate to 0 will<br /># disable the rotation, but the logfiles are still closed and<br /># re-opened. This will enable you to rename the logfiles<br /># yourself just before sending the rotate signal.<br />#<br /># Note, the 'squid -k rotate' command normally sends a USR1<br /># signal to the running squid process. In certain situations<br /># (e.g. on Linux with Async I/O), USR1 is used for other<br /># purposes, so -k rotate uses another signal. It is best to get<br /># in the habit of using 'squid -k rotate' instead of 'kill -USR1<br /># <pid>'.<br /># <br />logfile_rotate 10<br />#<br />#Default:<br /># logfile_rotate 0<br /><br /># TAG: append_domain<br /># Appends local domain name to hostnames without any dots in<br /># them. append_domain must begin with a period.<br />#<br /># Be warned there are now Internet names with no dots in<br /># them using only top-domain names, so setting this may<br /># cause some Internet sites to become unavailable.<br />#<br />#Example:<br /># append_domain .yourdomain.com<br />#<br />#Default:<br /># none<br /><br /># TAG: tcp_recv_bufsize (bytes)<br /># Size of receive buffer to set for TCP sockets. Probably just<br /># as easy to change your kernel's default. Set to zero to use<br /># the default buffer size.<br />#<br />#Default:<br /># tcp_recv_bufsize 0 bytes<br /><br /># TAG: err_html_text<br /># HTML text to include in error messages. Make this a "mailto"<br /># URL to your admin address, or maybe just a link to your<br /># organizations Web page.<br />#<br /># To include this in your error messages, you must rewrite<br /># the error template files (found in the "errors" directory).<br /># Wherever you want the 'err_html_text' line to appear,<br /># insert a %L tag in the error template file.<br />#<br />#Default:<br /># none<br /><br /># TAG: deny_info<br /># Usage: deny_info err_page_name acl<br /># or deny_info http://... acl<br /># Example: deny_info ERR_CUSTOM_ACCESS_DENIED bad_guys<br />#<br /># This can be used to return a ERR_ page for requests which<br /># do not pass the 'http_access' rules. A single ACL will cause<br /># the http_access check to fail. If a 'deny_info' line exists<br /># for that ACL Squid returns a corresponding error page.<br />#<br /># You may use ERR_ pages that come with Squid or create your own pages<br /># and put them into the configured errors/ directory.<br />#<br /># Alternatively you can specify an error URL. The browsers will<br /># get redirected (302) to the specified URL. %s in the redirection<br /># URL will be replaced by the requested URL.<br />#<br /># Alternatively you can tell Squid to reset the TCP connection<br /># by specifying TCP_RESET.<br />#<br />#Default:<br /># none<br /><br /># TAG: memory_pools on|off<br /># If set, Squid will keep pools of allocated (but unused) memory<br /># available for future use. If memory is a premium on your<br /># system and you believe your malloc library outperforms Squid<br /># routines, disable this.<br />#<br />#Default:<br /> memory_pools on<br /><br /># TAG: memory_pools_limit (bytes)<br /># Used only with memory_pools on:<br /># memory_pools_limit 50 MB<br />#<br /># If set to a non-zero value, Squid will keep at most the specified<br /># limit of allocated (but unused) memory in memory pools. All free()<br /># requests that exceed this limit will be handled by your malloc<br /># library. Squid does not pre-allocate any memory, just safe-keeps<br /># objects that otherwise would be free()d. Thus, it is safe to set<br /># memory_pools_limit to a reasonably high value even if your<br /># configuration will use less memory.<br />#<br /># If set to zero, Squid will keep all memory it can. That is, there<br /># will be no limit on the total amount of memory used for safe-keeping.<br />#<br /># To disable memory allocation optimization, do not set<br /># memory_pools_limit to 0. Set memory_pools to "off" instead.<br />#<br /># An overhead for maintaining memory pools is not taken into account<br /># when the limit is checked. This overhead is close to four bytes per<br /># object kept. However, pools may actually _save_ memory because of<br /># reduced memory thrashing in your malloc library.<br />#<br />#Default:<br /># memory_pools_limit 5 MB<br /><br /># TAG: forwarded_for on|off<br /># If set, Squid will include your system's IP address or name<br /># in the HTTP requests it forwards. By default it looks like<br /># this:<br />#<br /># X-Forwarded-For: 192.1.2.3<br />#<br /># If you disable this, it will appear as<br />#<br /># X-Forwarded-For: unknown<br />#<br />#Default:<br /># forwarded_for on<br /><br /># TAG: log_icp_queries on|off<br /># If set, ICP queries are logged to access.log. You may wish<br /># do disable this if your ICP load is VERY high to speed things<br /># up or to simplify log analysis.<br />#<br />#Default:<br /># log_icp_queries on<br /><br /># TAG: icp_hit_stale on|off<br /># If you want to return ICP_HIT for stale cache objects, set this<br /># option to 'on'. If you have sibling relationships with caches<br /># in other administrative domains, this should be 'off'. If you only<br /># have sibling relationships with caches under your control,<br /># it is probably okay to set this to 'on'.<br /># If set to 'on', your siblings should use the option "allow-miss"<br /># on their cache_peer lines for connecting to you.<br />#<br />#Default:<br /># icp_hit_stale off<br /><br /># TAG: minimum_direct_hops<br /># If using the ICMP pinging stuff, do direct fetches for sites<br /># which are no more than this many hops away.<br />#<br />#Default:<br /># minimum_direct_hops 4<br /><br /># TAG: minimum_direct_rtt<br /># If using the ICMP pinging stuff, do direct fetches for sites<br /># which are no more than this many rtt milliseconds away.<br />#<br />#Default:<br /># minimum_direct_rtt 400<br /><br /># TAG: cachemgr_passwd<br /># Specify passwords for cachemgr operations.<br />#<br /># Usage: cachemgr_passwd password action action ...<br />#<br /># Some valid actions are (see cache manager menu for a full list):<br /># 5min<br /># 60min<br /># asndb<br /># authenticator<br /># cbdata<br /># client_list<br /># comm_incoming<br /># config *<br /># counters<br /># delay<br /># digest_stats<br /># dns<br /># events<br /># filedescriptors<br /># fqdncache<br /># histograms<br /># http_headers<br /># info<br /># io<br /># ipcache<br /># mem<br /># menu<br /># netdb<br /># non_peers<br /># objects<br /># offline_toggle *<br /># pconn<br /># peer_select<br /># redirector<br /># refresh<br /># server_list<br /># shutdown *<br /># store_digest<br /># storedir<br /># utilization<br /># via_headers<br /># vm_objects<br />#<br /># * Indicates actions which will not be performed without a<br /># valid password, others can be performed if not listed here.<br />#<br /># To disable an action, set the password to "disable".<br /># To allow performing an action without a password, set the<br /># password to "none".<br />#<br /># Use the keyword "all" to set the same password for all actions.<br />#<br />#Example:<br /># cachemgr_passwd secret shutdown<br /># cachemgr_passwd lesssssssecret info stats/objects<br /># cachemgr_passwd disable all<br />#<br />#Default:<br /># none<br /><br /># TAG: store_avg_object_size (kbytes)<br /># Average object size, used to estimate number of objects your<br /># cache can hold. See doc/Release-Notes-1.1.txt. The default is<br /># 13 KB.<br />#<br />#Default:<br /># store_avg_object_size 13 KB<br /><br /># TAG: store_objects_per_bucket<br /># Target number of objects per bucket in the store hash table.<br /># Lowering this value increases the total number of buckets and<br /># also the storage maintenance rate. The default is 50.<br />#<br />#Default:<br /># store_objects_per_bucket 20<br /><br /># TAG: client_db on|off<br /># If you want to disable collecting per-client statistics,<br /># turn off client_db here.<br />#<br />#Default:<br /># client_db on<br /><br /># TAG: netdb_low<br /># TAG: netdb_high<br /># The low and high water marks for the ICMP measurement<br /># database. These are counts, not percents. The defaults are<br /># 900 and 1000. When the high water mark is reached, database<br /># entries will be deleted until the low mark is reached.<br />#<br />#Default:<br /># netdb_low 900<br /># netdb_high 1000<br /><br /># TAG: netdb_ping_period<br /># The minimum period for measuring a site. There will be at<br /># least this much delay between successive pings to the same<br /># network. The default is five minutes.<br />#<br />#Default:<br /># netdb_ping_period 5 minutes<br /><br /># TAG: query_icmp on|off<br /># If you want to ask your peers to include ICMP data in their ICP<br /># replies, enable this option.<br />#<br /># If your peer has configured Squid (during compilation) with<br /># '--enable-icmp' that peer will send ICMP pings to origin server<br /># sites of the URLs it receives. If you enable this option the<br /># ICP replies from that peer will include the ICMP data (if available).<br /># Then, when choosing a parent cache, Squid will choose the parent with<br /># the minimal RTT to the origin server. When this happens, the<br /># hierarchy field of the access.log will be<br /># "CLOSEST_PARENT_MISS". This option is off by default.<br />#<br />#Default:<br /># query_icmp off<br /><br /># TAG: test_reachability on|off<br /># When this is 'on', ICP MISS replies will be ICP_MISS_NOFETCH<br /># instead of ICP_MISS if the target host is NOT in the ICMP<br /># database, or has a zero RTT.<br />#<br />#Default:<br /># test_reachability off<br /><br /># TAG: buffered_logs on|off<br /># cache.log log file is written with stdio functions, and as such<br /># it can be buffered or unbuffered. By default it will be unbuffered.<br /># Buffering it can speed up the writing slightly (though you are<br /># unlikely to need to worry unless you run with tons of debugging<br /># enabled in which case performance will suffer badly anyway..).<br />#<br />#Default:<br /># buffered_logs off<br /><br /># TAG: reload_into_ims on|off<br /># When you enable this option, client no-cache or ``reload''<br /># requests will be changed to If-Modified-Since requests.<br /># Doing this VIOLATES the HTTP standard. Enabling this<br /># feature could make you liable for problems which it<br /># causes.<br />#<br /># see also refresh_pattern for a more selective approach.<br />#<br />#Default:<br /># reload_into_ims off<br /><br /># TAG: always_direct<br /># Usage: always_direct allow|deny [!]aclname ...<br />#<br /># Here you can use ACL elements to specify requests which should<br /># ALWAYS be forwarded by Squid to the origin servers without using<br /># any peers. For example, to always directly forward requests for<br /># local servers ignoring any parents or siblings you may have use<br /># something like:<br />#<br /># acl local-servers dstdomain my.domain.net<br /># always_direct allow local-servers<br />#<br /># To always forward FTP requests directly, use<br />#<br /># acl FTP proto FTP<br /># always_direct allow FTP<br />#<br /># NOTE: There is a similar, but opposite option named<br /># 'never_direct'. You need to be aware that "always_direct deny<br /># foo" is NOT the same thing as "never_direct allow foo". You<br /># may need to use a deny rule to exclude a more-specific case of<br /># some other rule. Example:<br />#<br /># acl local-external dstdomain external.foo.net<br /># acl local-servers dstdomain .foo.net<br /># always_direct deny local-external<br /># always_direct allow local-servers<br />#<br /># NOTE: If your goal is to make the client forward the request<br /># directly to the origin server bypassing Squid then this needs<br /># to be done in the client configuration. Squid configuration<br /># can only tell Squid how Squid should fetch the object.<br />#<br /># NOTE: This directive is not related to caching. The replies<br /># is cached as usual even if you use always_direct. To not cache<br /># the replies see no_cache.<br />#<br /># This option replaces some v1.1 options such as local_domain<br /># and local_ip.<br />#<br />#Default:<br /># none<br /><br /># TAG: never_direct<br /># Usage: never_direct allow|deny [!]aclname ...<br />#<br /># never_direct is the opposite of always_direct. Please read<br /># the description for always_direct if you have not already.<br />#<br /># With 'never_direct' you can use ACL elements to specify<br /># requests which should NEVER be forwarded directly to origin<br /># servers. For example, to force the use of a proxy for all<br /># requests, except those in your local domain use something like:<br />#<br /># acl local-servers dstdomain .foo.net<br /># acl all src 0.0.0.0/0.0.0.0<br /># never_direct deny local-servers<br /># never_direct allow all<br />#<br /># or if Squid is inside a firewall and there are local intranet<br /># servers inside the firewall use something like:<br />#<br /># acl local-intranet dstdomain .foo.net<br /># acl local-external dstdomain external.foo.net<br /># always_direct deny local-external<br /># always_direct allow local-intranet<br /># never_direct allow all<br />#<br /># This option replaces some v1.1 options such as inside_firewall<br /># and firewall_ip.<br />#<br />#Default:<br /># none<br /><br /># TAG: header_access<br /># Usage: header_access header_name allow|deny [!]aclname ...<br />#<br /># WARNING: Doing this VIOLATES the HTTP standard. Enabling<br /># this feature could make you liable for problems which it<br /># causes.<br />#<br /># This option replaces the old 'anonymize_headers' and the<br /># older 'http_anonymizer' option with something that is much<br /># more configurable. This new method creates a list of ACLs<br /># for each header, allowing you very fine-tuned header<br /># mangling.<br />#<br /># You can only specify known headers for the header name.<br /># Other headers are reclassified as 'Other'. You can also<br /># refer to all the headers with 'All'.<br />#<br /># For example, to achieve the same behavior as the old<br /># 'http_anonymizer standard' option, you should use:<br />#<br /># header_access From deny all<br /># header_access Referer deny all<br /># header_access Server deny all<br /># header_access User-Agent deny all<br /># header_access WWW-Authenticate deny all<br /># header_access Link deny all<br />#<br /># Or, to reproduce the old 'http_anonymizer paranoid' feature<br /># you should use:<br />#<br /># header_access Allow allow all<br /># header_access Authorization allow all<br /># header_access WWW-Authenticate allow all<br /># header_access Cache-Control allow all<br /># header_access Content-Encoding allow all<br /># header_access Content-Length allow all<br /># header_access Content-Type allow all<br /># header_access Date allow all<br /># header_access Expires allow all<br /># header_access Host allow all<br /># header_access If-Modified-Since allow all<br /># header_access Last-Modified allow all<br /># header_access Location allow all<br /># header_access Pragma allow all<br /># header_access Accept allow all<br /># header_access Accept-Charset allow all<br /># header_access Accept-Encoding allow all<br /># header_access Accept-Language allow all<br /># header_access Content-Language allow all<br /># header_access Mime-Version allow all<br /># header_access Retry-After allow all<br /># header_access Title allow all<br /># header_access Connection allow all<br /># header_access Proxy-Connection allow all<br /># header_access All deny all<br />#<br /># By default, all headers are allowed (no anonymizing is<br /># performed).<br />#<br />#Default:<br /># none<br /><br /># TAG: header_replace<br /># Usage: header_replace header_name message<br /># Example: header_replace User-Agent Nutscrape/1.0 (CP/M; 8-bit)<br />#<br /># This option allows you to change the contents of headers<br /># denied with header_access above, by replacing them with<br /># some fixed string. This replaces the old fake_user_agent<br /># option.<br />#<br /># By default, headers are removed if denied.<br />#<br />#Default:<br /># none<br /><br /># TAG: icon_directory<br /># Where the icons are stored. These are normally kept in<br /># /usr/share/squid/icons<br />#<br />#Default:<br /># icon_directory /usr/share/squid/icons<br /><br /># TAG: global_internal_static<br /># This directive controls is Squid should intercept all requests for<br /># /squid-internal-static/ no matter which host the URL is requesting<br /># (default on setting), or if nothing special should be done for<br /># such URLs (off setting). The purpose of this directive is to make<br /># icons etc work better in complex cache hierarchies where it may<br /># not always be possible for all corners in the cache mesh to reach<br /># the server generating a directory listing.<br />#<br />#Default:<br /># global_internal_static on<br /><br /># TAG: short_icon_urls<br /># If this is enabled Squid will use short URLs for icons.<br />#<br /># If off the URLs for icons will always be absolute URLs<br /># including the proxy name and port.<br />#<br />#Default:<br /># short_icon_urls off<br /><br /># TAG: error_directory<br /># Directory where the error files are read from.<br /># /usr/lib/squid/errors contains sets of error files<br /># in different languages. The default error directory<br /># is /etc/squid/errors, which is a link to one of these<br /># error sets.<br />#<br /># If you wish to create your own versions of the error files,<br /># either to customize them to suit your language or company,<br /># copy the template English files to another<br /># directory and point this tag at them.<br /># <br />#error_directory /usr/share/squid/errors/English<br />#<br />#Default:<br /># error_directory /usr/share/squid/errors/English<br /><br /># TAG: maximum_single_addr_tries<br /># This sets the maximum number of connection attempts for a<br /># host that only has one address (for multiple-address hosts,<br /># each address is tried once).<br />#<br /># The default value is one attempt, the (not recommended)<br /># maximum is 255 tries. A warning message will be generated<br /># if it is set to a value greater than ten.<br />#<br /># Note: This is in addition to the request re-forwarding which<br /># takes place if Squid fails to get a satisfying response.<br />#<br />#Default:<br /># maximum_single_addr_tries 1<br /><br /># TAG: retry_on_error<br /># If set to on Squid will automatically retry requests when<br /># receiving an error response. This is mainly useful if you<br /># are in a complex cache hierarchy to work around access<br /># control errors.<br />#<br />#Default:<br /># retry_on_error off<br /><br /># TAG: snmp_port<br /># Squid can now serve statistics and status information via SNMP.<br /># A value of "0" disables SNMP support. If you wish to use SNMP,<br /># set this to "3401" to use the normal SNMP support.<br />#<br />#Default:<br /># snmp_port 0<br /><br /># TAG: snmp_access<br /># Allowing or denying access to the SNMP port.<br />#<br /># All access to the agent is denied by default.<br /># usage:<br />#<br /># snmp_access allow|deny [!]aclname ...<br />#<br />#Example:<br /># snmp_access allow snmppublic localhost<br /># snmp_access deny all<br />#<br />#Default:<br /># snmp_access deny all<br /><br /># TAG: snmp_incoming_address<br /># TAG: snmp_outgoing_address<br /># Just like 'udp_incoming_address' above, but for the SNMP port.<br />#<br /># snmp_incoming_address is used for the SNMP socket receiving<br /># messages from SNMP agents.<br /># snmp_outgoing_address is used for SNMP packets returned to SNMP<br /># agents.<br />#<br /># The default snmp_incoming_address (0.0.0.0) is to listen on all<br /># available network interfaces.<br />#<br /># If snmp_outgoing_address is set to 255.255.255.255 (the default)<br /># it will use the same socket as snmp_incoming_address. Only<br /># change this if you want to have SNMP replies sent using another<br /># address than where this Squid listens for SNMP queries.<br />#<br /># NOTE, snmp_incoming_address and snmp_outgoing_address can not have<br /># the same value since they both use port 3401.<br />#<br />#Default:<br /># snmp_incoming_address 0.0.0.0<br /># snmp_outgoing_address 255.255.255.255<br /><br /># TAG: as_whois_server<br /># WHOIS server to query for AS numbers. NOTE: AS numbers are<br /># queried only when Squid starts up, not for every request.<br />#<br />#Default:<br /># as_whois_server whois.ra.net<br /># as_whois_server whois.ra.net<br /><br /># TAG: wccp_router<br /># Use this option to define your WCCP ``home'' router for<br /># Squid. Setting the 'wccp_router' to 0.0.0.0 (the default)<br /># disables WCCP.<br />#<br />#Default:<br /># wccp_router 0.0.0.0<br /><br /># TAG: wccp_version<br /># According to some users, Cisco IOS 11.2 only supports WCCP<br /># version 3. If you're using that version of IOS, change<br /># this value to 3.<br />#<br />#Default:<br /># wccp_version 4<br /><br /># TAG: wccp_incoming_address<br /># TAG: wccp_outgoing_address<br /># wccp_incoming_address Use this option if you require WCCP<br /># messages to be received on only one<br /># interface. Do NOT use this option if<br /># you're unsure how many interfaces you<br /># have, or if you know you have only one<br /># interface.<br />#<br /># wccp_outgoing_address Use this option if you require WCCP<br /># messages to be sent out on only one<br /># interface. Do NOT use this option if<br /># you're unsure how many interfaces you<br /># have, or if you know you have only one<br /># interface.<br />#<br /># The default behavior is to not bind to any specific address.<br />#<br /># NOTE, wccp_incoming_address and wccp_outgoing_address can not have<br /># the same value since they both use port 2048.<br />#<br />#Default:<br /># wccp_incoming_address 0.0.0.0<br /># wccp_outgoing_address 255.255.255.255<br /><br /><br /># DELAY POOL PARAMETERS (all require DELAY_POOLS compilation option)<br /># -----------------------------------------------------------------------------<br /><br /># TAG: delay_pools<br /># This represents the number of delay pools to be used. For example,<br /># if you have one class 2 delay pool and one class 3 delays pool, you<br /># have a total of 2 delay pools.<br />#<br />#Default:<br /># delay_pools 0<br /><br /># TAG: delay_class<br /># This defines the class of each delay pool. There must be exactly one<br /># delay_class line for each delay pool. For example, to define two<br /># delay pools, one of class 2 and one of class 3, the settings above<br /># and here would be:<br />#<br />#Example:<br /># delay_pools 2 # 2 delay pools<br /># delay_class 1 2 # pool 1 is a class 2 pool<br /># delay_class 2 3 # pool 2 is a class 3 pool<br />#<br /># The delay pool classes are:<br />#<br /># class 1 Everything is limited by a single aggregate<br /># bucket.<br />#<br /># class 2 Everything is limited by a single aggregate<br /># bucket as well as an "individual" bucket chosen<br /># from bits 25 through 32 of the IP address.<br />#<br /># class 3 Everything is limited by a single aggregate<br /># bucket as well as a "network" bucket chosen<br /># from bits 17 through 24 of the IP address and a<br /># "individual" bucket chosen from bits 17 through<br /># 32 of the IP address.<br />#<br /># NOTE: If an IP address is a.b.c.d<br /># -> bits 25 through 32 are "d"<br /># -> bits 17 through 24 are "c"<br /># -> bits 17 through 32 are "c * 256 + d"<br />#<br />#Default:<br /># none<br /><br /># TAG: delay_access<br /># This is used to determine which delay pool a request falls into.<br />#<br /># delay_access is sorted per pool and the matching starts with pool 1,<br /># then pool 2, ..., and finally pool N. The first delay pool where the<br /># request is allowed is selected for the request. If it does not allow<br /># the request to any pool then the request is not delayed (default).<br />#<br /># For example, if you want some_big_clients in delay<br /># pool 1 and lotsa_little_clients in delay pool 2:<br />#<br />#Example:<br /># delay_access 1 allow some_big_clients<br /># delay_access 1 deny all<br /># delay_access 2 allow lotsa_little_clients<br /># delay_access 2 deny all<br />#<br />#Default:<br /># none<br /><br /># TAG: delay_parameters<br /># This defines the parameters for a delay pool. Each delay pool has<br /># a number of "buckets" associated with it, as explained in the<br /># description of delay_class. For a class 1 delay pool, the syntax is:<br />#<br />#delay_parameters pool aggregate<br />#<br /># For a class 2 delay pool:<br />#<br />#delay_parameters pool aggregate individual<br />#<br /># For a class 3 delay pool:<br />#<br />#delay_parameters pool aggregate network individual<br />#<br /># The variables here are:<br />#<br /># pool a pool number - ie, a number between 1 and the<br /># number specified in delay_pools as used in<br /># delay_class lines.<br />#<br /># aggregate the "delay parameters" for the aggregate bucket<br /># (class 1, 2, 3).<br />#<br /># individual the "delay parameters" for the individual<br /># buckets (class 2, 3).<br />#<br /># network the "delay parameters" for the network buckets<br /># (class 3).<br />#<br /># A pair of delay parameters is written restore/maximum, where restore is<br /># the number of bytes (not bits - modem and network speeds are usually<br /># quoted in bits) per second placed into the bucket, and maximum is the<br /># maximum number of bytes which can be in the bucket at any time.<br />#<br /># For example, if delay pool number 1 is a class 2 delay pool as in the<br /># above example, and is being used to strictly limit each host to 64kbps<br /># (plus overheads), with no overall limit, the line is:<br />#<br />#delay_parameters 1 -1/-1 8000/8000<br />#<br /># Note that the figure -1 is used to represent "unlimited".<br />#<br /># And, if delay pool number 2 is a class 3 delay pool as in the above<br /># example, and you want to limit it to a total of 256kbps (strict limit)<br /># with each 8-bit network permitted 64kbps (strict limit) and each<br /># individual host permitted 4800bps with a bucket maximum size of 64kb<br /># to permit a decent web page to be downloaded at a decent speed<br /># (if the network is not being limited due to overuse) but slow down<br /># large downloads more significantly:<br />#<br />#delay_parameters 2 32000/32000 8000/8000 600/8000<br />#<br /># There must be one delay_parameters line for each delay pool.<br />#<br />#Default:<br /># none<br /><br /># TAG: delay_initial_bucket_level (percent, 0-100)<br /># The initial bucket percentage is used to determine how much is put<br /># in each bucket when squid starts, is reconfigured, or first notices<br /># a host accessing it (in class 2 and class 3, individual hosts and<br /># networks only have buckets associated with them once they have been<br /># "seen" by squid).<br />#<br />#Default:<br /># delay_initial_bucket_level 50<br /><br /># TAG: incoming_icp_average<br /># TAG: incoming_http_average<br /># TAG: incoming_dns_average<br /># TAG: min_icp_poll_cnt<br /># TAG: min_dns_poll_cnt<br /># TAG: min_http_poll_cnt<br /># Heavy voodoo here. I can't even believe you are reading this.<br /># Are you crazy? Don't even think about adjusting these unless<br /># you understand the algorithms in comm_select.c first!<br />#<br />#Default:<br /># incoming_icp_average 6<br /># incoming_http_average 4<br /># incoming_dns_average 4<br /># min_icp_poll_cnt 8<br /># min_dns_poll_cnt 8<br /># min_http_poll_cnt 8<br /><br /># TAG: max_open_disk_fds<br /># To avoid having disk as the I/O bottleneck Squid can optionally<br /># bypass the on-disk cache if more than this amount of disk file<br /># descriptors are open.<br />#<br /># A value of 0 indicates no limit.<br />#<br />#Default:<br /># max_open_disk_fds 0<br /><br /># TAG: offline_mode<br /># Enable this option and Squid will never try to validate cached<br /># objects.<br />#<br />#Default:<br /># offline_mode off<br /><br /># TAG: uri_whitespace<br /># What to do with requests that have whitespace characters in the<br /># URI. Options:<br />#<br /># strip: The whitespace characters are stripped out of the URL.<br /># This is the behavior recommended by RFC2396.<br /># deny: The request is denied. The user receives an "Invalid<br /># Request" message.<br /># allow: The request is allowed and the URI is not changed. The<br /># whitespace characters remain in the URI. Note the<br /># whitespace is passed to redirector processes if they<br /># are in use.<br /># encode: The request is allowed and the whitespace characters are<br /># encoded according to RFC1738. This could be considered<br /># a violation of the HTTP/1.1<br /># RFC because proxies are not allowed to rewrite URI's.<br /># chop: The request is allowed and the URI is chopped at the<br /># first whitespace. This might also be considered a<br /># violation.<br />#<br />#Default:<br /># uri_whitespace strip<br /><br /># TAG: broken_posts<br /># A list of ACL elements which, if matched, causes Squid to send<br /># an extra CRLF pair after the body of a PUT/POST request.<br />#<br /># Some HTTP servers has broken implementations of PUT/POST,<br /># and rely on an extra CRLF pair sent by some WWW clients.<br />#<br /># Quote from RFC2068 section 4.1 on this matter:<br />#<br /># Note: certain buggy HTTP/1.0 client implementations generate an<br /># extra CRLF's after a POST request. To restate what is explicitly<br /># forbidden by the BNF, an HTTP/1.1 client must not preface or follow<br /># a request with an extra CRLF.<br />#<br />#Example:<br /># acl buggy_server url_regex ^http://....<br /># broken_posts allow buggy_server<br />#<br />#Default:<br /># none<br /><br /># TAG: mcast_miss_addr<br /># Note: This option is only available if Squid is rebuilt with the<br /># -DMULTICAST_MISS_STREAM option<br />#<br /># If you enable this option, every "cache miss" URL will<br /># be sent out on the specified multicast address.<br />#<br /># Do not enable this option unless you are are absolutely<br /># certain you understand what you are doing.<br />#<br />#Default:<br /># mcast_miss_addr 255.255.255.255<br /><br /># TAG: mcast_miss_ttl<br /># Note: This option is only available if Squid is rebuilt with the<br /># -DMULTICAST_MISS_TTL option<br />#<br /># This is the time-to-live value for packets multicasted<br /># when multicasting off cache miss URLs is enabled. By<br /># default this is set to 'site scope', i.e. 16.<br />#<br />#Default:<br /># mcast_miss_ttl 16<br /><br /># TAG: mcast_miss_port<br /># Note: This option is only available if Squid is rebuilt with the<br /># -DMULTICAST_MISS_STREAM option<br />#<br /># This is the port number to be used in conjunction with<br /># 'mcast_miss_addr'.<br />#<br />#Default:<br /># mcast_miss_port 3135<br /><br /># TAG: mcast_miss_encode_key<br /># Note: This option is only available if Squid is rebuilt with the<br /># -DMULTICAST_MISS_STREAM option<br />#<br /># The URLs that are sent in the multicast miss stream are<br /># encrypted. This is the encryption key.<br />#<br />#Default:<br /># mcast_miss_encode_key XXXXXXXXXXXXXXXX<br /><br /># TAG: nonhierarchical_direct<br /># By default, Squid will send any non-hierarchical requests<br /># (matching hierarchy_stoplist or not cachable request type) direct<br /># to origin servers.<br />#<br /># If you set this to off, Squid will prefer to send these<br /># requests to parents.<br />#<br /># Note that in most configurations, by turning this off you will only<br /># add latency to these request without any improvement in global hit<br /># ratio.<br />#<br /># If you are inside an firewall see never_direct instead of<br /># this directive.<br />#<br />#Default:<br /># nonhierarchical_direct on<br /><br /># TAG: prefer_direct<br /># Normally Squid tries to use parents for most requests. If you for some<br /># reason like it to first try going direct and only use a parent if<br /># going direct fails set this to on.<br />#<br /># By combining nonhierarchical_direct off and prefer_direct on you<br /># can set up Squid to use a parent as a backup path if going direct<br /># fails.<br />#<br /># Note: If you want Squid to use parents for all requests see<br /># the never_direct directive. prefer_direct only modifies how Squid<br /># acts on cachable requests.<br />#<br />#Default:<br /># prefer_direct off<br /><br /># TAG: strip_query_terms<br /># By default, Squid strips query terms from requested URLs before<br /># logging. This protects your user's privacy.<br />#<br />#Default:<br /># strip_query_terms on<br /><br /># TAG: coredump_dir<br /># By default Squid leaves core files in the directory from where<br /># it was started. If you set 'coredump_dir' to a directory<br /># that exists, Squid will chdir() to that directory at startup<br /># and coredump files will be left there.<br />#<br />#Default:<br /># coredump_dir none<br />#<br /># Leave coredumps in the first cache dir<br />coredump_dir /var/spool/squid<br /><br /># TAG: redirector_bypass<br /># When this is 'on', a request will not go through the<br /># redirector if all redirectors are busy. If this is 'off'<br /># and the redirector queue grows too large, Squid will exit<br /># with a FATAL error and ask you to increase the number of<br /># redirectors. You should only enable this if the redirectors<br /># are not critical to your caching system. If you use<br /># redirectors for access control, and you enable this option,<br /># users may have access to pages they should not<br /># be allowed to request.<br />#<br />#Default:<br /># redirector_bypass off<br /><br /># TAG: ignore_unknown_nameservers<br /># By default Squid checks that DNS responses are received<br /># from the same IP addresses they are sent to. If they<br /># don't match, Squid ignores the response and writes a warning<br /># message to cache.log. You can allow responses from unknown<br /># nameservers by setting this option to 'off'.<br />#<br />#Default:<br /># ignore_unknown_nameservers on<br /><br /># TAG: digest_generation<br /># This controls whether the server will generate a Cache Digest<br /># of its contents. By default, Cache Digest generation is<br /># enabled if Squid is compiled with USE_CACHE_DIGESTS defined.<br />#<br />#Default:<br /># digest_generation on<br /><br /># TAG: digest_bits_per_entry<br /># This is the number of bits of the server's Cache Digest which<br /># will be associated with the Digest entry for a given HTTP<br /># Method and URL (public key) combination. The default is 5.<br />#<br />#Default:<br /># digest_bits_per_entry 5<br /><br /># TAG: digest_rebuild_period (seconds)<br /># This is the number of seconds between Cache Digest rebuilds.<br />#<br />#Default:<br /># digest_rebuild_period 1 hour<br /><br /># TAG: digest_rewrite_period (seconds)<br /># This is the number of seconds between Cache Digest writes to<br /># disk.<br />#<br />#Default:<br /># digest_rewrite_period 1 hour<br /><br /># TAG: digest_swapout_chunk_size (bytes)<br /># This is the number of bytes of the Cache Digest to write to<br /># disk at a time. It defaults to 4096 bytes (4KB), the Squid<br /># default swap page.<br />#<br />#Default:<br /># digest_swapout_chunk_size 4096 bytes<br /><br /># TAG: digest_rebuild_chunk_percentage (percent, 0-100)<br /># This is the percentage of the Cache Digest to be scanned at a<br /># time. By default it is set to 10% of the Cache Digest.<br />#<br />#Default:<br /># digest_rebuild_chunk_percentage 10<br /><br /># TAG: chroot<br /># Use this to have Squid do a chroot() while initializing. This<br /># also causes Squid to fully drop root privileges after<br /># initializing. This means, for example, that if you use a HTTP<br /># port less than 1024 and try to reconfigure, you will get an<br /># error.<br />#<br />#Default:<br /># none<br /><br /># TAG: client_persistent_connections<br /># TAG: server_persistent_connections<br /># Persistent connection support for clients and servers. By<br /># default, Squid uses persistent connections (when allowed)<br /># with its clients and servers. You can use these options to<br /># disable persistent connections with clients and/or servers.<br />#<br />#Default:<br /># client_persistent_connections on<br /># server_persistent_connections on<br /><br /># TAG: detect_broken_pconn<br /># Some servers have been found to incorrectly signal the use<br /># of HTTP/1.0 persistent connections even on replies not<br /># compatible, causing significant delays. This server problem<br /># has mostly been seen on redirects.<br />#<br /># By enabling this directive Squid attempts to detect such<br /># broken replies and automatically assume the reply is finished<br /># after 10 seconds timeout.<br />#<br />#Default:<br /># detect_broken_pconn off<br /><br /># TAG: balance_on_multiple_ip<br /># Some load balancing servers based on round robin DNS have been <br /># found not to preserve user session state across requests<br /># to different IP addresses.<br />#<br /># By default Squid rotates IP's per request. By disabling<br /># this directive only connection failure triggers rotation.<br />#<br />#Default:<br /># balance_on_multiple_ip on<br /><br /># TAG: pipeline_prefetch<br /># To boost the performance of pipelined requests to closer<br /># match that of a non-proxied environment Squid can try to fetch<br /># up to two requests in parallel from a pipeline.<br />#<br /># Defaults to off for bandwidth management and access logging<br /># reasons.<br />#<br />#Default:<br /># pipeline_prefetch off<br /><br /># TAG: extension_methods<br /># Squid only knows about standardized HTTP request methods.<br /># You can add up to 20 additional "extension" methods here.<br />#<br />#Default:<br /># none<br /><br /># TAG: request_entities<br /># Squid defaults to deny GET and HEAD requests with request entities,<br /># as the meaning of such requests are undefined in the HTTP standard<br /># even if not explicitly forbidden.<br />#<br /># Set this directive to on if you have clients which insists<br /># on sending request entities in GET or HEAD requests. But be warned<br /># that there is server software (both proxies and web servers) which<br /># can fail to properly process this kind of request which may make you<br /># vulnerable to cache pollution attacks if enabled.<br />#<br />#Default:<br /># request_entities off<br /><br /># TAG: high_response_time_warning (msec)<br /># If the one-minute median response time exceeds this value,<br /># Squid prints a WARNING with debug level 0 to get the<br /># administrators attention. The value is in milliseconds.<br />#<br />#Default:<br /># high_response_time_warning 0<br /><br /># TAG: high_page_fault_warning<br /># If the one-minute average page fault rate exceeds this<br /># value, Squid prints a WARNING with debug level 0 to get<br /># the administrators attention. The value is in page faults<br /># per second.<br />#<br />#Default:<br /># high_page_fault_warning 0<br /><br /># TAG: high_memory_warning<br /># If the memory usage (as determined by mallinfo) exceeds<br /># value, Squid prints a WARNING with debug level 0 to get<br /># the administrators attention.<br />#<br />#Default:<br /># high_memory_warning 0<br /><br /># TAG: store_dir_select_algorithm<br /># Set this to 'round-robin' as an alternative.<br />#<br />#Default:<br /># store_dir_select_algorithm least-load<br /><br /># TAG: forward_log<br /># Note: This option is only available if Squid is rebuilt with the<br /># -DWIP_FWD_LOG option<br />#<br /># Logs the server-side requests.<br />#<br /># This is currently work in progress.<br />#<br />#Default:<br /># none<br /><br /># TAG: ie_refresh on|off<br /># Microsoft Internet Explorer up until version 5.5 Service<br /># Pack 1 has an issue with transparent proxies, wherein it<br /># is impossible to force a refresh. Turning this on provides<br /># a partial fix to the problem, by causing all IMS-REFRESH<br /># requests from older IE versions to check the origin server<br /># for fresh content. This reduces hit ratio by some amount<br /># (~10% in my experience), but allows users to actually get<br /># fresh content when they want it. Note that because Squid<br /># cannot tell if the user is using 5.5 or 5.5SP1, the behavior<br /># of 5.5 is unchanged from old versions of Squid (i.e. a<br /># forced refresh is impossible). Newer versions of IE will,<br /># hopefully, continue to have the new behavior and will be<br /># handled based on that assumption. This option defaults to<br /># the old Squid behavior, which is better for hit ratios but<br /># worse for clients using IE, if they need to be able to<br /># force fresh content.<br />#<br />#Default:<br /># ie_refresh off<br /><br /># TAG: vary_ignore_expire on|off<br /># Many HTTP servers supporting Vary gives such objects<br /># immediate expiry time with no cache-control header<br /># when requested by a HTTP/1.0 client. This option<br /># enables Squid to ignore such expiry times until<br /># HTTP/1.1 is fully implemented.<br /># WARNING: This may eventually cause some varying<br /># objects not intended for caching to get cached.<br />#<br />#Default:<br /># vary_ignore_expire off<br /><br /># TAG: sleep_after_fork (microseconds)<br /># When this is set to a non-zero value, the main Squid process<br /># sleeps the specified number of microseconds after a fork()<br /># system call. This sleep may help the situation where your<br /># system reports fork() failures due to lack of (virtual)<br /># memory. Note, however, that if you have a lot of child<br /># processes, these sleep delays will add up and your<br /># Squid will not service requests for some amount of time<br /># until all the child processes have been started.<br />#<br />#Default:<br /># sleep_after_fork 0<br /><br /># TAG: relaxed_header_parser on|off|warn<br /># In the default "on" setting Squid accepts certain forms<br /># of non-compliant HTTP messages where it is unambiguous<br /># what the sending application intended even if the message<br /># is not correctly formatted. The messages is then normalized<br /># to the correct form when forwarded by Squid.<br />#<br /># If set to "warn" then a warning will be emitted in cache.log<br /># each time such HTTP error is encountered.<br />#<br /># If set to "off" then such HTTP errors will cause the request<br /># or response to be rejected.<br />#<br />#Default:<br /># relaxed_header_parser on<br /><br /># TAG: max_filedesc<br /># The maximum number of open file descriptors.<br />#<br />#Default:<br /># max_filedesc 1024<br /><br />#sleep_after_fork 0<br />#always_direct allow abc<br />#always_direct allow dl2<br />#never_direct allow QUERY<br />#never_direct allow dl1<br />#cache_peer_access 192.168.0.253 deny dl1<br />#cache_peer_access 192.168.0.10 allow dl1<br /><br />delay_pools 3<br /><br />delay_class 1 2<br />delay_access 1 deny net2<br />delay_access 1 deny net3<br />delay_access 1 allow net opendl<br />delay_parameters 1 -1/-1 7000/7000<br /><br />delay_class 2 2<br />delay_access 2 deny net2<br />delay_access 2 allow net3<br />delay_access 2 allow net<br />delay_parameters 2 -1/-1 10000/10000<br /><br />delay_class 3 2<br />delay_access 3 allow net2<br />delay_parameters 3 -1/-1 -1/-1Muhammad Imranhttp://www.blogger.com/profile/12158641287038478088noreply@blogger.comtag:blogger.com,1999:blog-4938443720602924137.post-72328186288467190502009-12-01T16:42:00.000-08:002009-12-01T16:44:48.090-08:00Linux and other Free and Open Source SoftwareMany Open source software available on internet<br />i have found some very useful and working links.<br /><br /><br /><span style="font-weight: bold;">Linux and other Free and Open Source Software</span><br />http://www.redhat.com/software/rhel/purchase/index.html<br />http://www.redhat.com/software/rhel/desktop/<br />http://www.freesoftwarecdr.com/shop/product_info.php?products_id=135<br />http://www.freesoftwarecdr.com/shop/product_info.php?products_id=139<br />http://www.freesoftwarecdr.com/shop/product_info.php?products_id=91<br />http://store.mandrakesoft.com/index.php<br />http://www.novell.com/products/linuxprofessional/pricing.html<br />http://www.suse.com/us/business/products/server/sles/pricing.html<br />http://store.slackware.com/cgibin/<br />store<br />http://www.openbsd.com/orders.htmlMuhammad Imranhttp://www.blogger.com/profile/12158641287038478088noreply@blogger.comtag:blogger.com,1999:blog-4938443720602924137.post-27940249061075831112009-11-29T10:35:00.000-08:002009-11-29T10:43:18.343-08:00Customizing a GNOME Desktop of Redhat Linux<a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_OHVjG26-BJQ/SxLAtZ6kJZI/AAAAAAAAAUw/OIP8ecjCKYA/s1600/gnome-linux-wallpaper.jpg"><img style="margin: 0pt 0pt 10px 10px; float: right; cursor: pointer; width: 242px; height: 181px;" src="http://2.bp.blogspot.com/_OHVjG26-BJQ/SxLAtZ6kJZI/AAAAAAAAAUw/OIP8ecjCKYA/s320/gnome-linux-wallpaper.jpg" alt="" id="BLOGGER_PHOTO_ID_5409597988708558226" border="0" /></a><br /><br />Customizing a GNOME Desktop<br />Desktop configuration is a very personal issue, as each user seems to have a particular favored<br />way of doing things. Without trying some changes, however, it’s hard to know how one can do<br />things. You now know enough to tweak a GNOME desktop a bit; in this project, you’ll change<br />some commonly altered configuration settings.<br /><br />Step by Step<br />1. From the default GNOME desktop, right-click on a blank space on the panel.<br />2. Click the Properties menu item.<br />3. You can use this page to reposition the panel to any of the four edges of the desktop, but<br />leave the location alone for now. In the Size drop-down menu, select Small (36 pixels).<br />4. Check the Show/Hide Buttons box.<br /><br />5. Check the Arrows on the Hide Buttons box.<br />6. Click Close. The panel at the bottom of the screen should now be shorter, and its icons<br />smaller and more widely spaced.<br />7. Right-click on a blank spot on the panel and select Add To Panel.<br />8. Select Utility and then System Monitor. A system monitor area should appear on the panel;<br />it will graphically show CPU usage.<br />9. Right-click on a blank spot on the panel and select Launcher from the menu.<br />10. Select System Tools and then Terminal. A terminal icon will appear on the panel; clicking<br />this icon will open a terminal where you can use the command-line interface.<br />11. Right-click on a blank spot on the panel and select Launcher from the menu again.<br />12. Select the Office menu and then Project Management. A Mr. Project icon should appear on<br />the panel; this tool is still under development, but it is similar in concept to Microsoft Project.<br />13. Right-click on a blank spot on the panel and select New Panel.<br />14. Select the Menu Panel option, and a menu bar should appear at the top of the desktop.<br />Applications and actions can be invoked from this menu bar, and it can also hold additional<br />launchers, applets, and utilities.<br />15. Right-click on the new menu panel at the top of the screen.<br />16. Select Add To Panel, and then the Accessories menu, and the Stock Ticker option. A stock<br />ticker area should appear on the menu panel.<br />17. Right-click on the stock ticker area on the panel and select Preferences. A configuration<br />page should appear.<br />18. Type RHAT in the New Symbol field.<br />19. Click the Add button, and then click Close. In five minutes, the Red Hat stock price should<br />begin scrolling in the stock ticker area, along with the default index information.<br />20. Move the icons on the panels by left-clicking them and then dragging them to the desired<br />locations.Muhammad Imranhttp://www.blogger.com/profile/12158641287038478088noreply@blogger.comtag:blogger.com,1999:blog-4938443720602924137.post-85033944869604612742009-11-23T13:58:00.000-08:002009-11-23T13:59:23.032-08:00Exploring CUPS in Redhat Linux all linux flavors<div style="text-align: justify;"><span style="font-weight: bold;font-size:180%;" >CUPS</span><br />We’ve mentioned before that CUPS was based on the Internet Printing Protocol (IPP), which it<br />is hoped will become a cross-platform standard for network printing. CUPS also provides<br />some additional advantages besides just those presented by IPP.<br /><br />The designers of CUPS have gone to great lengths to make it easy to use and easy to<br />transition to. Administration is simplified through the use of a web-based front end to server<br />configuration (although third-party GUI configuration tools exist as well) and clients often<br />need no configuration at all. Printers are discovered automatically when possible. From the<br />client’s view of printing, CUPS will emulate many of the tools you’ve become used to under<br />lpd-style systems (or System V, if you’ve worked with that elsewhere).<br />CUPS introduces the concept of classes, which allow you to send a print job to a group of<br />printers, and have it printed on the first available machine in that group. This approach to load<br />balancing and failover is carried further with implicit classes, which allow multiple servers to<br />address the same physical printer. When two servers point to a printer of the same name, an<br />implicit class is automatically created with no effort required from an administrator.<br />Printer instances allow multiple queues to point to the same printer with slightly different<br />settings. This makes it really easy to choose between common features that your printer makes<br />available.<br />By using pluggable back ends for the actual output from a queue, not only is it easy to<br />support many types of printer hardware, but third parties can easily add support for output that<br />isn’t bundled in the core package. For example, Windows printing is handled by a back end<br />provided by the Samba team. In addition, CUPS uses a text file called a PostScript Printer<br />Description (PPD) to describe the features provided by a particular piece of printer hardware<br /></div>Muhammad Imranhttp://www.blogger.com/profile/12158641287038478088noreply@blogger.comtag:blogger.com,1999:blog-4938443720602924137.post-56540749807362364742009-11-02T09:05:00.000-08:002009-11-02T09:13:57.584-08:00Pluggable Authentication Modules (PAM)<span style="font-weight: bold;">Pluggable Authentication Modules (PAM)</span><br /><br /><div style="text-align: justify;">Programs which give privileges to users must properly authenticate each user. For instance, when you log into a system, you provide your username and password, and the log in process uses this username and password to verify your identity.<br /></div><div style="text-align: justify;">Pluggable Authentication Modules (PAM) allows the system administrator to set authentication policies for PAM-aware applications without having to recompile authentication programs. PAMdos this by utilizing a pluggable, modular architecture. Which modules PAM calls for a particular application is determined by looking at that application's PAM configuration file in the /etc/pam.d/ directory.<br /></div><div style="text-align: justify;">In most situations, you will never need to alter the default PAM configuration files for a PAM-aware application. Whenever you use RPM to install programs that require authentication, they automatically make the changes necessary to do normal password authentication using PAM. However, if you need to customize the PAM configuration file, you must understand the structure of this<br /></div><br /><span style="font-weight: bold;">Advantages of PAM</span><br />When used correctly, PAM provides the following advantages for a system administrator:<br /><div style="text-align: justify;">. It provides a common authentication scheme that can be used with a wide variety of applications. . It allows great fiexibility and control over authentication for both the system administrator and<br /></div>application developer.<br />. It allows application developers to develop their program without implementing a particular authentication scheme. Instead, they can focus purely on the details of their program.<br /><br /><span style="font-weight: bold;">PAM Configuration Files</span><br />The directory /etc/pam.d/ contains the PAM configuration files for PAM-aware applications. In<br />earlier versions of PAM, the file /etc/pam.conf was used, but this file is now deprecated. The<br />pam.conf file is only read if the /etc/pam.d/ directory does not exist.<br />Each PAM-aware application or service . as applications designed to be used by many users are<br />commonly known . has its own file within the /etc/pam.d/ directory.<br />These files have a specific layout containing calls to modules usually located in the /lib/security/<br />directory. Additionally, each line within a PAM configuration file specifies a module type, a control<br />fiag, a path to the module, and, sometimes, module arguments.<br /><br /><span style="font-weight: bold;">PAM Service Names</span><br />Each PAM configuration file in the /etc/pam.d/ directory is named after the service for which it<br />controls access. It is up to the PAM-aware program to define its service name and install its PAM<br />configuration file in the pam.d directory. For example, the login program defines its service name<br />as /etc/pam.d/login.<br />In general, the service name is the name of the program used to access the service, not the program used to provide the service. This is why the service wu-ftpd, defines its service name as /etc/pam.d/ftp. The next four sections will describe the basic format of PAM configuration files and how they use<br />PAM modules to perform authentication for PAM-aware applications.<br /><br /><span style="font-weight: bold;">PAM Modules</span><br />There are four types of PAM modules used to control access to services. These types correlate to<br />different aspects of the authorization process:<br />. auth . These modules are used to authenticate the user by, for example, asking for and checking<br />a password. It can also set credentials, such as group membership or Kerberos tickets.<br />. account . These modules are used to make sure access is allowed. For example, it can check if<br />the account is expired, or it can check if the user is allowed to log in at a particular time of day.<br />. password. These modules are used to set passwords.<br />. session . These modules are used after a user has been authenticated to manage the user's<br />session. This module type can also perform additional tasks which are needed to allow access, like<br />mounting a user's home directory or making his mailbox available.Muhammad Imranhttp://www.blogger.com/profile/12158641287038478088noreply@blogger.comtag:blogger.com,1999:blog-4938443720602924137.post-17543526012412715532009-10-30T04:48:00.000-07:002009-10-30T04:49:31.375-07:00How to Install and Configure Tomcat on Linux1. First install the rpm of tomcat from tarball in /usr/local dir<br /> <br /> cp jakarta-tomcat-5.0.24.tar.gz /usr/local /<br />2. tar –xzvf jakarta – tomcat-5.0.24.tar.gz<br />3. Make a symbolic link<br /> ln –s /usr/local/Jakarta-tomcat-5.0.24 /usr/local/tomcat <br />4.Go to /etc/profile and add the lines above the following line<br />(export PATH USER LOGNAME MAIL HOSTNAME HISTSIZE INPUTRC)<br />export JAVA_HOME=/usr/java/j2sdk1.4.2_05<br />export CATALINA_HOME=/usr/local/tomcat<br /> <br /> 5. cd /etc<br />6. . . /profile<br />7. echo $JAVA-Home<br />8. echo $CATALINA-HOME<br /><br />Start the tomcat service by<br /> / usr /local/tomcat/bin /startup. Sh<br /><br /> Open the following file <br />9. pico /usr/local /tomcat/conf/tomcat- users.xml and add the following lines<br /> <role rolename =" “manager”/"><br /> <role rolename =" “admin”/"><br /> (</tomcat-users>)<br /> user username = “TomcatAdmin” Password = “password”<br /> Full Name =’” ‘role = “admin, manager , tomcat”/><br /><br />Restart the service of tomcat<br /> /usr/local/tomcat/bin/shutdown.sh<br /> /usr/local/tomcat/bin/startup.sh<br /><br />This will authenicate the user of tomcatAdmin<br /> <br />2. Install the java from the cdrom<br /> rpm –ivh java.xxxx.rpm<br /> 3. Install the mysql from cdrom<br /> rpm –ivh mysql.xxx.rpm<br /><br />You can access the mysql by sqlyog software at windows, but just writing the username “root” without any password. If you want to create some password for some user then follow the following steps<br /> <br />#mysql<br /> mysql> use mysql;<br />Database changed<br /><br /><br />mysql> INSERT INTO user (Host, User, Password, Select_priv) VALUES ('','eis', password('pucit'), 'Y');<br />Query OK, 1 row affected (0.00 sec)<br /><br />mysql> GRANT ALL ON hello.* TO eis;<br />Query OK, 0 rows affected (0.00 sec)<br /><br />Now you can login by using the username “eis” with password “pucit” in sqlyoq.<br /><br /> 4. For to use the admin of jakarta-tomcat you can , access it by<br /> http:// ip-address:8080/admin<br /><br /> It will require the username and password which you have mentioned in the file<br /> / usr / local /tomcat/conf/tomcat- users.xml<br /><br />It will open for you the administration of tomcat, you can create different websites on the same machine<br /><br />5. Now insert a rule of just insert a rule of IPTABLES to redirect the PORT 8080 of tomcat to PORT 80 of HTTP<br /><br />iptables -t nat -A PREROUTING -i eth0 -p tcp -m tcp --dport 80 -j REDIRECT --to-port 8080<br /><br /> 6. For to use the mysql just start its service<br /> /etc/init.d/mysql start<br /> 7. You can restart the tomcat service as<br /> /usr/local/tomcat/bin/shutdown.sh<br /> /usr/local/tomcat/bin/startup.sh<br /><br /> 8. Now you can access your website<br /> http://www.domainname.comMuhammad Imranhttp://www.blogger.com/profile/12158641287038478088noreply@blogger.comtag:blogger.com,1999:blog-4938443720602924137.post-57804999904581443522009-10-27T10:35:00.000-07:002009-10-27T10:37:23.868-07:00What is and How Work Linux Transparent Proxy<span style="font-family: arial;"> What is it?</span><br /><br /><span style="font-family: arial;"> Transparent Proxy is away that proxies connections without client</span><br /><br /><span style="font-family: arial;">noticing. This means that if you browse to www.yahoo.com when this request</span><br /><br /><span style="font-family: arial;">reachs your gateway it will be re-directed to another port where a proxy</span><br /><br /><span style="font-family: arial;">service like squid will be active. The client thinks that it's exchanging</span><br /><br /><span style="font-family: arial;">data with remote host but in the reality it's just exchanging data with the</span><br /><br /><span style="font-family: arial;">gateway. </span><br /><br /><br /><span style="font-family: arial;"></span><span style="font-family: arial;"> How can I support it?</span><br /><br /><span style="font-family: arial;"></span><span style="font-family: arial;"> </span><span style="font-family: arial;"> To support Transparent Proxy once more you'll have to re-compile your</span><br /><br /><span style="font-family: arial;">kernel this time the main features to support are:</span><br /><br /><br /><br /><span style="font-family: arial;">Networking Options --></span><br /><br /><span style="font-family: arial;"></span><br /><br /><span style="font-family: arial;"> (...)</span><br /><br /><span style="font-family: arial;"> [*] IP: firewalling</span><br /><br /><span style="font-family: arial;"> [*] IP: Transparent Proxy support </span><br /><br /><span style="font-family: arial;"> (...)</span><br /><br /><span style="font-family: arial;"> </span><br /><br /><span style="font-family: arial;"> Of course you'll probably enable mascarade on your host, to know which</span><br /><br /><span style="font-family: arial;">options have to be enabled check the IP masquerade section.</span><br /><br /><span style="font-family: arial;"> </span><br /><br /><span style="font-family: arial;"> Configuring</span><br /><br /><span style="font-family: arial;"> -----------</span><br /><br /><span style="font-family: arial;"> </span><br /><br /><span style="font-family: arial;"> Finally to make Transparent Proxy work you have to add a redirection</span><br /><br /><span style="font-family: arial;">action on ipchains just simply giving the command:</span><br /><br /><br /><br /><span style="font-family: arial;"> root@ExampleBox: ~# /sbin/ipchains -A input -p TCP --dport 80 -s</span><br /><br /><span style="font-family: arial;">192.168.0.0/24 -j REDIRECT 8080</span>Muhammad Imranhttp://www.blogger.com/profile/12158641287038478088noreply@blogger.comtag:blogger.com,1999:blog-4938443720602924137.post-59067810865574599692009-10-17T10:41:00.000-07:002009-10-17T10:43:25.637-07:00Problems with Linux Booting into the Graphical Installation<span style="font-weight: bold;">Problems with Booting into the Graphical Installation</span><br />There are some video cards that will not work properly with the Red Hat Linux installation program.<br />The end result will be a problem booting into the graphical installation program.<br />If the installation program will not run using its default settings, it will try to run in a lower resolution<br />mode. If that still fails, the installation program will run in text mode.<br />Users who have video cards that will not run at 800 x 600 resolution should type lowres at the<br />boot: prompt to run the installation program in 640 x 480 resolution.Muhammad Imranhttp://www.blogger.com/profile/12158641287038478088noreply@blogger.comtag:blogger.com,1999:blog-4938443720602924137.post-57416278282104589452009-10-17T03:04:00.001-07:002009-10-17T03:04:57.301-07:00How to Add NEw User in Linux<span style="font-weight: bold;">Required steps:</span><br />– Edit the /etc/passwd file to define the user's account.<br />– Set an initial password.<br />– Create the user's home directory.<br /><span style="font-weight: bold;">• Extra steps (optional):</span><br />– Copy default startup files to the user's home directory.<br />– Add the user to the /etc/group file.<br />– Set the user's mail home and establish mail aliases.<br />– Enter the user in the site-wide user database (NIS).<br />– Configure disk quotas.<br />– Verify that the account is set up correctly.<br />– Record accounting information.Muhammad Imranhttp://www.blogger.com/profile/12158641287038478088noreply@blogger.comtag:blogger.com,1999:blog-4938443720602924137.post-22302574130240198372009-10-14T11:23:00.000-07:002009-10-14T11:25:02.353-07:00Linux 5 Disk Druid's Buttons<div style="text-align: justify; font-family: trebuchet ms;">Disk Druid's Buttons<br />These buttons control Disk Druid's actions. They are used to change the<br />attributes of a partition (for example the file system type and mount point) and<br />also to create RAID devices. Buttons on this screen are also used to accept the<br />changes you have made, or to exit Disk Druid. For further explanation, take a<br />look at each button in order:<br /> New: Used to request a new partition. When selected, a dialog box appears<br />containing fields (such as the mount point and size fields) that must be filled in.<br /> Edit: Used to modify attributes of the partition currently selected in the<br />Partitions section.<br />Selecting Edit opens a dialog box. Some or all of the fields can be edited,<br />depending on whether the partition information has already been written to disk.<br />You can also edit free space as represented in the graphical display to create a<br />new partition within that space. Either highlight the free space and then select<br />the Edit button, or double-click on the free space to edit it.<br />To make a RAID device, you must first create (or reuse existing) software<br />RAID partitions. Once you have created two or more software RAID partitions,<br />select Make RAID to join the software RAID partitions into a RAID device.<br /> Delete: Used to remove the partition currently highlighted in the Current<br />Disk Partitions section. You will be asked to confirm the deletion of any<br />partition.<br /> Reset: Used to restore Disk Druid to its original state. All changes made<br />will be lost if you Reset the partitions.<br /> RAID: Used to provide redundancy to any or all disk partitions. It should<br />only be used if you have experience using RAID. To read more about RAID,<br />refer to the Red Hat Enterprise Linux Deployment Guide.<br />To make a RAID device, you must first create software RAID partitions. Once<br />you have created two or more software RAID partitions, select RAID to join the<br />software RAID partitions into a RAID device.<br /><br />LVM: Allows you to create an LVM logical volume. The role of LVM<br />Logical Volume Manager) is to present a simple logical view of underlying<br />physical storage space, such as a hard drive(s). LVM manages individual<br />physical disks — or to be more precise, the individual partitions present on<br />them. It should only be used if you have experience using LVM. To read more<br />about LVM, refer to the Red Hat Enterprise Linux Deployment Guide. Note,<br />LVM is only available in the graphical installation program.<br />To create an LVM logical volume, you must first create partitions of type<br />physical volume (LVM). Once you have created one or more physical volume<br />LVM) partitions, select LVM to create an LVM logical volume.<br /></div>Muhammad Imranhttp://www.blogger.com/profile/12158641287038478088noreply@blogger.comtag:blogger.com,1999:blog-4938443720602924137.post-88593285527356277052009-10-06T03:19:00.000-07:002009-10-06T03:21:07.749-07:00What is Routing Metrics<div style="text-align: justify;"><span style="font-family: georgia;"><span style="font-weight: bold;">Routing Metrics</span></span><br /><span style="font-family: georgia;">Routing tables contain information used by switching software to select the best route. But how,</span><br /><span style="font-family: georgia;">specifically, are routing tables built? What is the specific nature of the information they contain?</span><br /><span style="font-family: georgia;">How do routing algorithms determine that one route is preferable to others?</span><br /><span style="font-family: georgia;">Routing algorithms have used many different metrics to determine the best route. Sophisticated</span><br /><span style="font-family: georgia;">routing algorithms can base route selection on multiple metrics, combining them in a single (hybrid)</span><br /><span style="font-family: georgia;">metric. All the following metrics have been used:</span><br /><span style="font-family: georgia;">Path Length</span><br /><span style="font-family: georgia;">Reliability</span><br /><span style="font-family: georgia;">Delay</span><br /><span style="font-family: georgia;">Bandwidth</span><br /><span style="font-family: georgia;">Load</span><br /><span style="font-family: georgia;">Communication Cost</span><br /><span style="font-family: georgia;"></span><br /><span style="font-family: georgia;">Path length is the most common routing metric. Some routing protocols allow network</span><br /><span style="font-family: georgia;">administrators to assign arbitrary costs to each network link. In this case, path length is the sum of the costs associated with each link traversed. Other routing protocols define hop count, a metric that specifies the number of passes through internetworking products, such as routers, that a packet must take en route from a source to a destination.</span><br /><span style="font-family: georgia;">Reliability, in the context of routing algorithms, refers to the dependability (usually described in</span><br /><span style="font-family: georgia;">terms of the bit-error rate) of each network link. Some network links might go down more often than others. After a network fails, certain network links might be repaired more easily or more quickly than other links. Any reliability factors can be taken into account in the assignment of the reliability ratings, which are arbitrary numeric values usually assigned to network links by network administrators. Routing delay refers to the length of time required to move a packet from source to destination through the internetwork. Delay depends on many factors, including the bandwidth of intermediate network links, the port queues at each router along the way, network congestion on all intermediate network links, and the physical distance to be travelled. Because delay is a conglomeration of several important variables, it is a common and useful metric. Bandwidth refers to the available traffic capacity of a link. All other things being equal, a 10-Mbps Ethernet link would be preferable to a 64-kbps leased line. Although bandwidth is a rating of the maximum attainable throughput on a link, routes through links with greater bandwidth do not necessarily provide better routes than routes through slower links. If, for example, a faster link is busier, the actual time required to send a packet to the destination could be greater. Load refers to the degree to which a network resource, such as a router, is busy. Load can be calculated in a variety of ways, including CPU utilization and packets processed per second. Monitoring these parameters on a continual basis can be resource-intensive itself.</span><br /><span style="font-family: georgia;">Communication cost is another important metric, especially because some companies may not care about performance as much as they care about operating expenditures. Even though line delay may be longer, they will send packets over their own lines rather than through the public lines that cost money for usage time.</span></div>Muhammad Imranhttp://www.blogger.com/profile/12158641287038478088noreply@blogger.comtag:blogger.com,1999:blog-4938443720602924137.post-24605705230804197512009-09-16T10:34:00.000-07:002009-09-16T10:48:58.350-07:00linux service chkconfig rc.local Linux Listing Services<strong>Chkconfig show you which linux services start in linux startu up.<br />linux start different service on diferent runlevels.<br /></strong><br />#chkconfig --list<br /><br /><br />if you want to start any service in linux startup there is many ways to<br />load or start service in startup<br /><br /><strong>1) chkconfig<br />2) rc.local<br /></strong><br /><strong>chkconfig</strong><br />Only run this command in one time when you install new server like squid dns or dhcp.<br />there is 7 run levels in linux. 3 is command prompt and 5 is graphic interface run level<br /><br />chkconfig --level 35 squid on<br />chkconfig --level 35 named on<br />chkconfig --level 35 dhcpd on<br /><br /><br />this is start up script file, jus add these lines or add any command in<br />this start up script, and also you can add the iptables command's in rc.local files.<br /><br /><strong>rc.local</strong><br />service named start<br />service squid start<br />service dhcpd startMuhammad Imranhttp://www.blogger.com/profile/12158641287038478088noreply@blogger.com