> heh, this was asked about a week ago. I think that in the end the guy
> went for this solution:
> 
> what you might want to do is to set up a proxy (maybe squid?) somewhere
> on your network, and then using ipchains you can "invisibly" redirect
> all traffic on port 80 to that host (with the exclusion of that host,
> because otherwise you'd just be redirecting it to itself when it wants
> to make a real request:). then you can just look at the output of your
> proxy log files and see who's doing what. that way it is completely
> transparent to the end user, and you don't have to reconfigure any web
> browsers at all.
> 
> 
> this has some good points to it:
> 1) it makes it really hard to surf the web without being logged. I won't
> say impossible, because I've got some nice code here that will allow me
> to do that :)
> 
> 2) you create another service to your users and improve their web
> browsing experience.
> 
> it also has some bad points, but the only one that I can think of is
> that you need more disk space to cache web pages...
> 
> someone else mentioned some package for filtering out the logs into a
> nicer format if you don't like the raw logs. can't remember what is was
> called though...
> 
> we briefly touched on other solutions as well. there is software for
> windows called Webboy which does this (www.ngdsoftware.com). or, using
> libpcap you can write a program that will listen to traffic and sift out
> all the http requests. that's a little harder. I was going to give that
> a shot last week, but, well, I never got around to it :)
> 
> hope that helps!
> sugarboy
 
Thanks, I will try squid.


-- 
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.

Reply via email to