|
Julian Anastasov wrote:
Hello,
On Tue, 15 Jan 2002, Padraig Brady wrote:
Hi,
I'm having problems with local routing, i.e.
I can't telnet to port 111 or 112 with the
following config. I immediately get
connection refused. What am I doing wrong?
p.s. there definitely is a realservice listening
on ports 89 and 98.
The trick you are trying works only when the port
is preserved, you can't alter the port. I'm not sure whether
ipvsadm should return error on such setup.
Ah it is a trick :-)
If you add the 127.0.0.1:port and also specify masq (-m)
it retains the port like I demonstrated before, but
if you dont specify -m it changes the port to be the
same as the virtualservice like you say is required.
So ipvsadm should at least be consistent in changing
the port in both cases and ALSO it should print a warning
saying it has done so.
As you say the following does work:
TCP 172.24.1.156:112 lc
-> 127.0.0.1:112 Local 1 0 2
A small point is the server must bind(INADDR_ANY). Binding to
127.0.0.1 or 172.24.1.156 alone does not work?
Also for completeness, this does not work (connection refused):
TCP 172.24.1.156:112 lc
-> 172.24.1.156:112 Local 1 0 0
What I'm trying to do is create a fallback realservice on the
director machine that can be added into any virtualservice as
appropriate, for e.g. to display a "sorry page" to a web client.
Any ideas?
thanks,
Padraig.
|
