Bug #290
closed
It may be due to a wrong configuration of DansGuardian. Typically when DansGuardian fails to start, web pages are not reachable but networking is working. Further investigation is then needed…
- Due date set to 08/29/2011
- Status changed from New to In Progress
- % Done changed from 0 to 20
- Estimated time set to 1:00 h
For an unknown reason Squid and Dansguardian are not started while network is brought up, which makes any web page request fail.
- % Done changed from 20 to 50
It seems the directory /etc/dhcp3/ has just moved to /etc/dhcp/ :).
- Status changed from In Progress to Ready for test
- % Done changed from 50 to 100
The problem is reproduced at the latest Russia ??
- Status changed from Ready for test to In Progress
- % Done changed from 100 to 50
I figured out that it works only if you're manually invoking a DHCP lease, what I've done in my tests. If you let Network-manager do the stuff, it doesn't call DHCP directly anymore, as it did in Gondwana. I guess it is because it can now use fixed IP's, thus without any DHCP.
As a result it seems we have to make a dupe of our DHCP script in /etc/NetworkManager/dispatcher.d/. The best option seems to make it call /etc/dhcp/dhclient-exit-hooks.d/squid-dansguradian. The strange thing is that Network-manager is supposed to call ifup scripts in /etc/network/, it should then start Squid and DansGuardian but it doesn't.
- Status changed from In Progress to Ready for test
- % Done changed from 50 to 100
Our scripts were not written to start Squid/DansGuardian from if-up. It is now the case, a new custom Debian package dansguardian-squid has been created on purpose to deal with the issue.
- Status changed from Ready for test to Closed
Also available in: Atom
PDF
Updated by 
Updated by