Re: [squid-users] Squid acl containing hostnames issue
* Jason Bassett [EMAIL PROTECTED] wrote: I am therefore looking for the easiest and most time effective method of blocking rooms when required. Hostnames seemed to be the best way. Any ideas on this issue? Restricting access an a per user Basis can also be done... just install an ident daemon with your netlogon script and forbid / allow access, based on them. Ident daemons are availably for most (all?) Openrating Systems... I have written a redirector, were you can allow / disallow access to users / hosts per webinterface on-the-fly ... maybe that's also an point :) See http://www.mcmilk.de/projects/squidwall/ for more information about the redirector. -- regards, TR
[squid-users] Squid acl containing hostnames issue
Hello I work in a secondary school with 5 IT suites each with 20-30 computers. I have created an acl for each room containing the hostnames of the machines for examle, an acl called R32 for room 32 contains: R32001 R32002 ... R32030 If I set this acl to deny, not all machines are denied access only a random group within the room. I originally run a GNU/Linux dhcp server to allocate static IPs to all network machines and then created acl's based on the IP ranges of machines in each room. This worked perfectly but now Research Machines who support us have demanded I remove the GNU/Linux dhcp server otherwise they will not support our installation. I am therefore looking for the easiest and most time effective method of blocking rooms when required. Hostnames seemed to be the best way. Any ideas on this issue? Thanks Jason
Re: [squid-users] Squid acl containing hostnames issue
Jason Bassett wrote: Hello I work in a secondary school with 5 IT suites each with 20-30 computers. I have created an acl for each room containing the hostnames of the machines for examle, an acl called R32 for room 32 contains: R32001 R32002 ... R32030 If I set this acl to deny, not all machines are denied access only a random group within the room. I originally run a GNU/Linux dhcp server to allocate static IPs to all network machines and then created acl's based on the IP ranges of machines in each room. This worked perfectly but now Research Machines who support us have demanded I remove the GNU/Linux dhcp server otherwise they will not support our installation. I am therefore looking for the easiest and most time effective method of blocking rooms when required. Hostnames seemed to be the best way. Any ideas on this issue? Thanks Jason How are IP addresses going to be supplied? Static assignment? Or is a Windows server going to be providing DHCP (Can you just have the Windows server supply the DHCP reservations)? How is the network set up? Could each room be set up on its own subnet (most gateways support DHCP pass through)? An other alternative: 1. Assign your Squid server an IP address for each room (e.g. 192.168.0.32, 192.168.0.33, etc). 2. Have each room use it's assigned IP for proxy (Room 32 uses 192.168.0.32:3128 for proxy). 3. Use acl myip 192.168.0.32/32 to prevent access. Chris
