sound like a good idea.
Linux - I love it when stuff just works.
Windows - I wish stuff would just work!
I have said these things about these two OS's many times.
sound like a good idea.
Linux - I love it when stuff just works.
Windows - I wish stuff would just work!
I have said these things about these two OS's many times.
□ΞVΞ□
Just try not to wind the workforce up too much or they'll be about as productive as a pebble, you're a sys admin - not God
I’m an IT / Networks Manager thank you very much.
As for winding the workforce up, I don't think it will do that but I think it’s irresponsible to give them complete access to the internet
It’s like saying to a child “there are guns, drugs and porn over there but don't touch them!”
You know that they will.
□ΞVΞ□
It was said in jest, hence the smiley
It is a valid point though, by all means implement controls but speak to the staff and let them know why you're having to do it and what's acceptable use of the network. If you don't speak to them and people just start getting disciplinary actions against them you won't be the most popular person around.
I agree and if they are not first informed then no action can be taken using the evidence from the logs anyway.
□ΞVΞ□
any one know a way arounf this...
"I’m currently still evaluating several log file analysis and reporting tools for use with Squid and DansGuardian. If you only run Squid, I’ve pretty much settled on SARG. However, this tool is of limited use if you are also using DansGuardian. Since all HTTP traffic gets forwarded to 8080 (DansGuardian), and then DanGuardian makes the request to 3128 (Squid), all requests in the Squid logs show as coming from 127.0.0.1. So really, in this case, if you want to monitor individual users, you must analyze the DansGuardian logs. At this time, I do not have a recommendation on a good DansGuardian log analyzer."
The log just shows 127.0.0.1 for anyone routed to port 8080
□ΞVΞ□
my Virtualisation Blog http://jfvi.co.uk Virtualisation Podcast http://vsoup.net
sorted...
In dansguardian.conf you need "forwardedfor = on" its in the Misc
settings.
And if you want Squid to act on the IP's you are passing then look for
"follow_x_forwarded_for" in squid.con to allow all
this will then add the info to the header of the forwarder from Dans to squid and squid will add thisto the log and not 127.0.0.1
just a quick note if you use the Tail command you can also have a real time log on screen of what is being accesse by who.
tail -f /var/log/squid/access.log
□ΞVΞ□
In terms of getting good web reports from Squid I've been having success with NetFox Online (netfox dot com) - it's worth checking out as well
There are currently 1 users browsing this thread. (0 members and 1 guests)