At 19:53 98-12-30 +0100, Peter Ke{e wrote:
>
>Hi!
>
>I have tried to set up a Virtual Server thru IP Tunneling but
>had no success. I have tested VS on a two machine configuration,
>both, the server and the router has only one ethernet adapter.
>Following is my (telnet port) configuration:
>
>ROUTER: IP_ADDRESS=192.168.1.55, VIRTUAL_ADDRESS=192.168.1.10
> janus:/root# insmod /lib/modules/2.0.35/net/new_tunnel.o
> janus:/root# insmod /lib/modules/2.0.35/ipv4/ipip.o
> janus:/root# echo "1" > /proc/sys/net/ipv4/ip_forward
> janus:/root# ifconfig eth0:0 192.168.1.10 up
> janus:/root# ippfvsadm -A -t 192.168.1.10:23 -R 192.168.1.101
>
>SERVER: IP_ADDRESS=192.168.1.101
> momo:/root# insmod /lib/modules/2.0.35/net/new_tunnel.o
> momo:/root# insmod /lib/modules/2.0.35/ipv4/ipip.o
> momo:/root# ifconfig tunl0 192.168.1.10 up
> momo:/root# echo "1" > /proc/sys/net/ipv4/ip_forward
> momo:/root# route add -host 192.168.1.10 dev lo
>
>When I try to telnet to 192.168.1.10 on the ROUTER, the tcpdump tells me,
>that the ROUTER sends the TCP packets to 192.168.1.10 (virtual address),
>instead of encapsulating them and sending them to the SERVER.
For the ROUTER, if you remove the "ippfvsadm -A -t 192.168.1.10:23 -R
192.168.1.101" command, could you telnet to 192.168.1.10 and the janus
appears? As I know, I usually make the ip alias work with two commands
ifconfig and route, for your example,
ifconfig eth0:0 192.168.1.10 up
route add -net 192.168.1.0 netmask 255.255.255.0 dev eth0:0
See what happens.
If it still doesn't work, please let me know it. However, you can still try
the following way which I did tests on it before.
ROUTER: IP_ADDRESS=192.168.1.55, VIRTUAL_ADDRESS=192.168.1.10
janus:/root# echo "1" > /proc/sys/net/ipv4/ip_forward
janus:/root# ippfvsadm -A -t 192.168.1.55:23 -R 192.168.1.101
SERVER: IP_ADDRESS=192.168.1.101
momo:/root# insmod /lib/modules/2.0.35/net/new_tunnel.o
momo:/root# insmod /lib/modules/2.0.35/ipv4/ipip.o
momo:/root# ifconfig tunl0 192.168.1.55 up
Note that there is no need to let ip tunnel up in the ROUTER, and there is
no need to enable ip forward in the SERVER.
Please telnet to 192.168.1.55, see what happens.
>
>The tunneling works fine if I avoid using Virtual Server and set up the
>tunneling device as follows:
> janus:/root# ifconfig tunl0 192.168.1.55 pointopoint 192.168.1.101 up
> janus:/root# route add -host 192.168.1.10 dev tunl0
>
>Can anyone give me a hint?!
>
>Happy New Year!
> Peter
>
Happy New Year too,
Wensong
|