In changing our campus squid proxy to transparent mode (which only handles
plain http traffic, not SSL), we are faced with having to NAT our SSL traffic,
while still wishing to maintain tight control over access and logging.
I'm interested in recommendations for logging such traffic a in way that can be
used for monitoring or tracing activity when necessary. Although we've run
shorewall for several years, we have not relied on the logs much, as until now,
most of our traffic has gone through squid. We have 650 active users on a 1Gb
gateway, with about 4-6Tb of traffic monthly, so logs could be quite large
(squid logs are >2Gb daily).
In addition to logging, we require time-based rules for NAT access per VLAN. We
can use our Cisco 6500 for this, or our Aruba wireless controller, but I'm
interested in hearing about methods employed with shorewall (cron, etc.) .
Thanks
Shawn Wright
I.T. Manager, Shawnigan Lake School
http://www.shawnigan.ca
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Shorewall-users mailing list
Shorewall-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shorewall-users
