|
Hi Rob,
If you want to upgrade your virtual proxy server, I strongly suggest
you try VS-Tunneling or VS-DRouting. Because they are really
efficient to build a virtual proxy server.
Rob Thomas wrote:
> Well. I've finally done it. I bit the bullet, and I've upgraded my
> 213-day-old proxy server (I just love linux. It worked. And it stayed
> working, without crashing, until I wanted to upgrade it 8-) to 2.2.10
> and ipvs-05-2.2.9.
>
> But, the main bit I wanted (the local server part) isn't working! Argh!
>
> Anyone clue me up?
>
> [Background. eth0 == 203.63.158.2, eth1 = 203.63.12.1]
>
> I can do this:
>
> [telnet 203.63.12.1 8082, connects, talks to squid. no probs.]
>
> ipvsadm -A 203.63.158.2:9999 -s wrr
> ipvsadm -a 203.63.158.2:9999 -R 203.63.12.1:8082
>
> Looks good. Except, uh, it doesn't work. When I try to connect to
> 203.63.158.2 9999 (both locally and remotely) I get a connection
> refused.
>
Your command is to use VS-DR, because it is the default if you
don't specify the dispatching technique.
As for VS-NAT, you should add -m option (masquerading).
By the way, the VS-NAT cannot direct the connection to
the other port on its own interfaces, because the response
packets cannot be rewritten back.
>
> Everything else is working -- I have 4 other machines in
> 203.63.12.[2345] that quite happily load balance, but I am hoping to
> make this machine act as a proxy too, so I don't have to buy another one
> just yet 8-)
>
> Any clues? Do I have to tell ipchains to masquerade 127/8 or something?
>
Please check the VS-NAT, VS-Tunneling and VS-DRouting pages
on LVS project, which were updated several days ago.
Good luck,
Wensong
>
> --Rob
|
