Error Creating Connection To Test Proxy Dansguardian
Contents |
Preventing Filter Bypass Performance Tuning Customizing the Block Page Allowing A Website Configuring Filter Groups User Identification Methods Bypassing DansGuardian Blacklists Phraselists
Configure Dansguardian
Common Problems Troubleshooting Strategies Wiki Information Contribute! Wiki Syntax Guide Style dansguardian transparent proxy and Editing Guide DokuWiki Documentation Wiki RSS Feed Recent Changes Table of Contents Common Problems and
Dansguardian Ubuntu
their Solutions Allow Traffic Through Firewall/Router Squid Configuration Options & Option Names Permissions And Daemon User Don't Prematurely Lock Down Dueling Log Rotations Phraselists Should Be Selective squid dansguardian howto DansGuardian Doesn't Automatically Start At Boot Squid Logs Only Point At Localhost Many Blacklists Actually Categorize Rathern Than Ban Squid Works By Itself, But Not With DansGuardian It's As Though My "Site" Entries Weren't There Operation Under NetBSD/FreeBSD/OpenBSD Is Somewhat Unreliable Eliminate Weird ClamAV Library Dependency Common Problems and their Solutions Check the entire dansguardian squid documentation portion of this wiki, especially the Filter Usage and Tips section. Also check the Wiki FAQ Allow Traffic Through Firewall/Router A common problem is blocked communications: end user workstations can't communicate with DansGuardian, or DansGuardian can't communicate with its backend proxy (probably Squid), or the DansGuardian filter system can't communicate with the Internet. Usually blocked communications are due to an old/forgotten/erroneous filtering rule in Shorewall or IPtables or your router/NAT box. Double-check your packet blocks, especially the old ones. And watch out for separate rules for ICMP that make `ping` packets behave differently than web surfing packets. End user workstations should have a path to communicate with DansGuardian with destination TCP port 8080 and any source TCP port (assuming something like filterport=8080 and filterip=yourinternalIP in “dansguardian.conf”). DansGuardian should have a path to communicate with its backend proxy with destination TCP port 3128 (assuming something like proxyport=3128 and proxyip=127.0.0.1 in “dansguardian.conf”, http_port 127.0.0.1:3128 in “squid.conf”, and no interfering IPtables or Sho
add on toSquid but I can't get DansGuardian to start, and it's not leaving mewith much information.I added /usr/sbin/dansguardian to /etc/rc.local. Then I changed it to/etc/dansguardian.sh start to try using the provided startup script.Only when I boot the
Dansguardian Bypass
machine does /var/log/messages get an error thatsays "Error creating connection to test proxy". When dansguardian https I try to manuallystart it with the direct commandline or the script, there is about a 5second pause and then it
Dansguardian Blacklist
dies, without error or log message.The DansGuardian archives say to make sure squid is running, but leaveno other suggestions. Squid is accepting connections from loopback,internal, and external interfaces and it doesn't matter if I have http://contentfilter.futuragts.com/wiki/doku.php?id=common_problems PFenabled or not. I can telnet to the squid port just fine fromlocalhost.Does anyone else have a suggestion why I'm not having success?dang yahoo tag:Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!http://platinum.yahoo.com Jyri Hovila 2003-03-19 11:36:53 UTC PermalinkRaw Message Hello David!DN> I added /usr/sbin/dansguardian to /etc/rc.local. Then I changed it toDN> /etc/dansguardian.sh start to try using the provided startup script.DN> Only when I boot the machine http://misc.openbsd.narkive.com/g6nmNOtD/dansguardian does /var/log/messages get an error thatDN> says "Error creating connection to test proxy". When I try to manuallyDN> start it with the direct commandline or the script, there is about a 5DN> second pause and then it dies, without error or log message.DN> The DansGuardian archives say to make sure squid is running, but leaveDN> no other suggestions. Squid is accepting connections from loopback,DN> internal, and external interfaces and it doesn't matter if I have PFDN> enabled or not. I can telnet to the squid port just fine fromDN> localhost.DN> Does anyone else have a suggestion why I'm not having success?I assume you're using Squid compiled from the ports collection.Make sure your Squid configuration allows you to use Squid throughloopback. By default it is *not* allowed. You should have something likethis in squid.conf:acl localhost src 127.0.0.1/255.255.255.255http_access allow localhostFirst line should be there already, but you have to add the second one.Do you start Squid before DansGuardian in your startup scripts? It takessome time for Squid to start up and start accepting connections, and ifDansGuardian is started soon after Squid, Squid may not be ready toaccept connections yet. This will force DG to shut down. You may have toadd a delay of couple of seconds before starting DG.Cheers!- Jyri 1
instructions: Windows Mac Red Hat Linux Ubuntu Click URL instructions: Right-click on ad, choose "Copy Link", then paste here → (This may not be https://sourceforge.net/p/ipcop/mailman/ipcop-user/thread/469BCDDC.20206@emmanuelcomputerconsulting.com/ possible with some types of ads) More information about our ad https://ubuntuforums.org/archive/index.php/t-1078033.html policies X You seem to have CSS turned off. Please don't fill out this field. You seem to have CSS turned off. Please don't fill out this field. Briefly describe the problem (required): Upload screenshot of ad (required): Select a file, or drag & drop error creating file here. ✔ ✘ Please provide the ad click URL, if possible: Home Browse IPCop Firewall Mailing Lists IPCop Firewall Linux firewall distribution geared towards home and SOHO users. Brought to you by: gespinasse, jackb_guppy, owes, riddles Summary Files Reviews Support News Wiki Mailing Lists Tickets ▾ Bugs Feature Requests SVN CVS ipcop-announce ipcop-cvs ipcop-devel ipcop-svn ipcop-user error creating connection ipcop-user [IPCop-user] Help: DansGuardian stopped (Cop+) and blocking everything From:
SmallFebruary 23rd, 2009, 04:45 AMTransparent Web Filtering ░▒▓▓▒░ Introduction This guide will primarily be written for my setup (which I will explain in a minute) but can be applied to any setup with some minor changes. I write this as a guide for transparent web filtering through DansGuardian, but I use several other tools to accomplish the objective. The setup consists of a server which runs Squid and DansGuardian and other client computers running some form of Linux. The clients will use a script that I call 'transproxy' to transparently redirect all traffic to Privoxy which must be configured to route all traffic to the server running DansGuardian. Of course, if you do not have a server, or only have one client computer, you can skip the Privoxy part and just use DansGuardian and Squid if you like. But you will have to adapt that to you current environment. Getting Started To begin, we must have ssh access to the server. This guide is not going to tell you how to install a SSH server. There are plenty of guides out there for that. So you need to login to the box and install Squid and DansGuardian: sudo apt-get install squid dansguardian Squid will automatically start and run on port 3128. There really is not any configuration that you need to do to squid, unless you wish to change the cache_mgr option in the /etc/squid/squid.conf file. DansGuardian on the other hand will not start without first commenting out a line. So we will change into the DansGuardian directory: cd /etc/dansguardian/ and edit the configuration file: sudo vim dansguardian.conf About the 5th line down, you should see something that says: UNCONFIGURED - Please remove this line after configuration Please comment that out with a hash (#), otherwise DansGuardian will still refuse to start. Skip down to the "filterport" and change this to "8181". (The reason I change this to 8181 from 8080, is that some services that you install automatically want to take hold of the 8080 port, so just out of habit I change this.) The "proxyport" should read "3128", as that is what port Squid is listening on. And "accessdeniedaddress" should be changed to reflect URL of your server and to the "cgi-bin/dansguardian.pl" file. (Note, for this to work, you will need apache2 installed. Otherwise you will not get an "Access Denied" page.) Save the file, and you may now proceed in starting DansGuardian: sudo /etc/init.d/dansguardian start Client Setup So long as your server running DansGuardian and Squid have no firewall rules to restrict INBOUND traffic, we may continue on to the client setup