|
Hurm. Gee, I stuffed that up. The cut'n'paste I did was when I was fiddling
around with different settings.. Here's what I really should have said!
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
I'm trying to redirect 203.41.13.1: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.41.13.1 8079
connection refused (this is good, what it's meant to do)
telnet 203.41.13.1 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]#
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$
Oh, and yes, I can connect to the machines I'm trying to redirect to:
[root@proxy0 vs-0.3]# telnet 203.63.158.2 8080
Trying 203.63.158.2...
Connected to 203.63.158.2.
Escape character is '^]'.
[various Squid error messages here 8-)]
Anyone with a clue? The redirecting machine is running a totally clean
2.0.35, with a tulip based network card.
--Rob
|
