|
At 17:51 98-11-16 +1100, Robert Thomas wrote:
>As there's not much of a FAQ I can find, can someone clue me up on why
this is
>not working?
>
>eth0 -- 203.41.13.1
>eth0:1 -- 203.63.158.10
>
>I'm trying to redirect 203.63.158.10:8080 to 203.63.158.2:8080 and .9:8080
--
>it's in the kernel, it seems to be there it creates the redirection, BUT:
>
>telnet 203.63.158.10 8079
>connection refused (this is good, what it's meant to do)
>telnet 203.63.158.10 8080
>just sits there, no connect -or- connection refused.
>
>Here's some snapshots:
>
>[root@proxy0 bin]# ippfvsadm -A -t 203.41.13.1:8080 -R
>203.63.158.9:8080
>[root@proxy0 bin]# ippfvsadm -A -t 203.41.13.1:8080 -R 203.63.158.2:8080
>[root@proxy0 bin]# ippfvsadm -L
>IP Port Forwarding & Virtual Server Table
>Protocol Local Addr:Port ==>
> Remote Addr:Port Weight
> ...
>TCP 203.41.13.1:8080 ==>
> 203.63.158.2:8080 1
> 203.63.158.9:8080 1
>[root@proxy0 bin]#
>
You must set the default route of hosts 203.63.158.2 and 203.63.158.9 to
203.63.158.10. Because in the current virtual server implementation, the
virtual server box need to change the real server IP address & port to the
virtual server IP address & port in the replying packets, this can make the
parallel service on a cluster to appear on a single IP address. So, the
replying packets must be routed through the virtual server box.
By the way, you can use the private internet for your proxy servers.
I am also considering to make another virtual server implementation to let
the replying packets by-pass the virtual server box based on IP tunneling,
also make the parallel service to appear on a single IP address. However,
it has limitation, it will require the real servers to support IP
tunneling, maybe limit the real servers to run only Linux OS.
Good luck,
Wensong
>
>Looks sane to me. But, if I try to -connect- to it:
>
>envy:/redir/rob/www$ telnet 203.41.13.1 8080
>Trying 203.41.13.1...
>[just sits there, doing nothing, so I hit ^C]
>envy:/redir/rob/www$ telnet 203.41.13.1 8079
>Trying 203.41.13.1...
>telnet: Unable to connect to remote host: Connection refused
>envy:/redir/rob/www$
>
>Anyone with a clue? The redirecting machine is running a totally clean
>2.0.35, with a tulip based network card.
>
>--Rob
>
>
|
