On Friday, June 10, 2011 02:20:49 AM errno wrote:
* the single instance listening on multiple ip:port http_ports:
192.168.1.2:80, 192.168.1.2:8080, 192.168.1.2:80 and
192.168.1.2:8080
Damn, that should have said:
* the single instance listening on multiple ip:port http_ports:
192.168.1.2:80
On Friday, June 10, 2011 07:33:07 AM Amos Jeffries wrote:
snip
... behaved as intended: when clients went through
the http_port listener 192.168.2.2:80, the tcp_outgoing_address
worked as expected, wherein http://www.whatismyip.com
displayed 192.168.2.2 rather than 192.168.1.1.
*
I've got squid conf that looks a bit like the following snippet:
# ...
acl ip-192.168.1.2 myip 192.168.1.2
http_port 192.168.1.2:80 name=ip-192.168.1.2
http_port 192.168.1.2:8080 name=ip-192.168.1.2
tcp_outgoing_address 192.168.1.2 ip-192.168.1
# ...
Question: do those http_port directives
On Thursday, June 02, 2011 01:03:06 AM Amos Jeffries wrote:
On 02/06/11 19:41, errno wrote:
Just to confirm:
If I have multiple ip aliases assigned to the same physical nic, will
there still be port conflicts on an ip (aliased) based multi-instanced
squid server?
There is rarely
On Friday, June 03, 2011 02:10:09 PM MrNicholsB wrote:
anyone getting my mails?
affirmative
Just to confirm:
If I have multiple ip aliases assigned to the same physical nic, will there
still be port conflicts on an ip (aliased) based multi-instanced squid server?
For example:
eth0 - 192.196.0.2
eth0:1 - 192.196.0.3
eth0:2 - 192.196.0.4
squid_192.196.0.2.conf
# ...
http_port
'm still getting my bearings w/ squid, so apologies if I'm asking
particularly stupid questions.
Is it possible to configure a scenario that facilitates per-user
max connection limits? For instance, user1 might have a
max connection limit of 10, while user3 has a max connection
limit of 50;
Thankyou for the advice and pointers, much appreciated!
On Tuesday, May 10, 2011 08:49:44 PM Amos Jeffries wrote:
On Tue, 10 May 2011 15:10:12 -0700, errno wrote:
I'll be doing major upgrades to a few of our old systems that are
running older versions of squid (2.5 era).
I'll be doing major upgrades to a few of our old systems that are running
older versions of squid (2.5 era). On each of these boxes, we have a
largish number of aliased virt ips. In the past it appeared that squid
needed a separate .conf file for each ip; but we'll be moving to squid
3.1... is
