It depends what separates the subnets.
If they're all running over the same cable then thats not a problem, you
should be able to point all clients at the current IP of the squid box.
You might want to keep things a little tidier, and use IP Aliasing on the
ethernet card in the squid server, and allocate a specific IP in the subnet,
then on the squid box
ifconfig eth0:1 192.168.1.2
ifconfig eth0:2 192.168.2.2
etc
Another option is to actually not do this at all, but to use transparent
proxying at the gateway. This assumes that your gateway is the same for all
subnets (probably). Then you'd simply use the gateway to redirect all port
80 requests to another machine (requires 2.4 and IPtables) or to a squid
process on the gateway itself (this is the only way with 2.2 kernels - but
you can make this squid process fairly lightweight and use a better box as
an upstream cache.) One advantage is that clients don't know about the
proxying, and you don't need to configure them all
God I wish DHCP had a "www proxy" field - it'd make life so much easier :)
Of course you could build another squid box for each subnet, but it'd be a
costly way to go.
> ----------
> From: Mark Novak[SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, August 28, 2001 7:09 AM
> To: [EMAIL PROTECTED]
> Subject: Bind to more than one NIC?
>
> I have multiple network subnets in my building. I would like to just add
> another NIC (or virutal IP address) to the Squid computer and have it
> server both of my subnets.
> Is this possible?
> Do I need to just build another Squid proxy for the other subnet?
>
