|
At 21:02 99-1-1 +0100, Peter Ke{e wrote:
>
>Wensong Zang wrote:
>> I usually make the ip alias work with two commands
>> ifconfig and route, for your example,
>> ifconfig eth0:0 192.168.1.10 up
>> See what happens.
>
>
>Hi!
>
>Thanks for your mail, it was of great help. Installing eth0:0 solved
>the problem.
>
>My tunneling configuration now reads as follows:
>
>ROUTER CONFIGURATION:
>IP address eth0 = 192.168.1.55
>Virtual IP eth0:0 = 192.168.1.10
>
> echo "1" > /proc/sys/net/ipv4/ip_forward
> ifconfig eth0:0 192.168.1.10 arp up
> ippfvsadm -A -t 192.168.1.10:23 -R 192.168.1.101
>
>SERVER CONFIGURATION:
>IP address eth0 = 192.168.1.101 ...
>
> modprobe new_tunnel.o
> modprobe ipip.o
> ifconfig tunl0 192.168.1.10 up
>
>
>The configuration without tunneling would be:
>
>ROUTER CONFIGURATION:
>IP address eth0 = 192.168.1.55
>Virtual IP eth0:0 = 192.168.1.10
>
> ifconfig eth0:0 192.168.1.10 arp up
> ipfwadm -F -p deny
> ipfwadm -F -a m -S 192.168.1.0/24 -D 0.0.0.0/0
> echo "1" > /proc/sys/net/ipv4/ip_forward
> ippfvsadm -A -t 192.168.1.10:23 -R 192.168.1.101:23
>
>SERVER CONFIGURATION:
>IP address eth0 = 192.168.1.101
>
> route del default
> route add default gw 192.168.1.55
> route del -net 192.168.1.0 netmask 255.255.255.0
It is not necessary to set the default route of server to the load balancer
in the virtual server via IP tunneling.
In the virtual server via IP tunneling, the real servers can be
geographically distributed.
>
>
>I thought maybe you could publish a similar configuration somewhere on
>the web site, to help other people resolve similar problems.
>
I will, but would you please tell me what you use it for?
>Cheers,
> Peter
>
Have a good day,
Wensong
|
