I've dealt with this problem of allowing some terminals to do web browsing but not others. It really comes down to discriminating between them based on X display. As others have mentioned, IP controlls whether in Squid or firewall rules do not work, since the LTSP server is originating all traffic.
My "solution" was to tweak the browser proxy settings before running the browser. See my writeup with example scripts at: http://www.bolis.com/amillar/linux/ Yes, the knowledgeable user can bypass by changing settings after the browser is running. I don't know of any fix for this, but I haven't pursued that angle. A better solution would be to steer the workstations to one LTSP server that is allowed or to a different one that isn't allowed, based on DHCP. Then typical IP-based rules would work. But of course that would require two servers. - Alan -- Alan Millar --==> [EMAIL PROTECTED] <==-- ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
