|
Julian Anastasov wrote:
> Here is one example:
>
> ip rule add prio 100 from 192.168.0.1 table 100
^^^^^^^
I assume this should be 10.0 ?
> ip route add table 100 10.0.0.1 via 192.168.1.2 dev eth0 src 192.168.1.3
I have a VS-DR LVS. One of the real-servers is telnet'ing
to the outside world with NAT, using your instructions of 25 Sep 2000.
I haven't tested, but I presume these NAT'ed packets
arrive with s_addr = the IP (on eth0) of the director. I would like them
to arrive with s_addr = VIP (on eth0:1)
the realserver is 192.168.1.12. The VIP is 192.168.2.110 (eth0:1
on the director), the director's NIC facing the outside world is 192.168.2.1.
All IPs are pingable from the director (only the realserver's IP is not
on the director.)
To get telnet packets from the real-server to emerge with s_addr = VIP,
I tried
ip rule add prio 100 from 192.168.1.12 table 100
ip route add table 100 192.168.1.12 via 192.168.2.1 dev eth0 src 192.168.1.110
the last command gives the error
RTNETLINK answers: Network is unreachable.
Do you know what's going on?
Joe
--
Joseph Mack PhD, Senior Systems Engineer, Lockheed Martin
contractor to the National Environmental Supercomputer Center,
mailto:mack.joseph@xxxxxxx ph# 919-541-0007, RTP, NC, USA
|
