|
OK, No I think that it was never working properly.
I think that telnet worked from my shell account from a previously
configured ipmasqadm portfw....I now turned that off, and here is the
problem:
I changed the setup as Wensong suggested (if I understood correctly):
Director:
eth0: 166.84.192.35
eth1: 192.168.1.1
eth1:1: 192.168.2.1
ipchains -A forward -s 192.168.1.0/24 -j MASQ
ipchains -A forward -s 192.168.2.0/24 -j MASQ
ipvsadm -A -t 166.84.192.35:80 -s wlc {correct place this time }
ipvsadm -a -t 166.84.192.35:80 -R 192.168.2.80 {-m or -g see below}
Web Server (real server)
eth0: 192.168.2.80
dummy0: 166.84.192.35 (arp hidden with 2.2.14 kernel through procfs)
default GW: 192.168.2.1
Now if I use -m when adding the real server, I can access it from
external network, but not from 192.168.1.*.
If I use -g it never connects from either network.
Any ideas, or debugging suggestions?
-Nissim
----------------------------------------------------------------------
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
To unsubscribe, e-mail: lvs-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxx
For additional commands, e-mail: lvs-users-help@xxxxxxxxxxxxxxxxxxxxxx
|
