LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

RE: Squid + LVS - tunneling

To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx, 'Elías' <esandoval@xxxxxxx>
Subject: RE: Squid + LVS - tunneling
From: Peter Mueller <pmueller@xxxxxxxxxxxx>
Date: Sat, 30 Nov 2002 20:41:57 -0800
Hi Elias,

> Hi Peter. Thank you for your help.

np: I just hope I can help you solve your issue.

> oldprox3:/usr/local/squid/etc# netstat -anp | grep LISTEN | more
> tcp        0      0 142.10.1.94:8080        0.0.0.0:*              
> LISTEN      8834/(squid)
> tcp        0      0 142.10.1.93:8080        0.0.0.0:*              
> LISTEN      8834/(squid)
> ---------------------------------
> Perhaps I must write a iptable's rule in order to redirect 
> port 8080 to
> 8834?. So, if I've write this port and IP in squid.conf, I 
> think it must
> work, isn't it?. I write here the first lines of squid.conf,

I think the 8834 is listing the PID, not listening port.  The redirecting
isn't such a bad idea; with my LVS I like to use redirects instead of
ethernet aliases.  It's worth a shot if you are stuck.  Here's what I use on
my boxes.

$IPTABLES -t nat -A PREROUTING -p tcp -d VIP --dport 8080 -j REDIRECT
--to-port 8080

> oldprox3:/usr/local/squid/etc# cat squid.conf|more
> http_port 142.10.1.93:8080
> http_port 142.10.1.94:8080
.................

Having used squid only a few times for ad-blocking I don't know that I can
comment on your configuration other than to say it looks ok to me.  It does
seem like SYN packets come into the squid server and then somehow don't get
to it.  Maybe there is some binding issues?  Maybe a google check of "IP
alias" and "squid.conf" will tell you something.

Happy thanksgiving weekend

Peter


<Prev in Thread] Current Thread [Next in Thread>
  • RE: Squid + LVS - tunneling, Peter Mueller <=