Re: Initial setup help request - can't ping VIP??

[Tim Burke <burke@xxxxxxxxxxxxxxxxxxxxxxxx>]

I figured out that the cause of my problems is that the kernel option

IP: aliasing support

is required when using NAT.  When this option is not included in the kernel the result is that all the VIP's will fail to ifconfig.  It would help others from falling into this trap if the kernel patch instructions were updated accordingly.  Thanks.

Tim Burke wrote:

> So I tried to manually run this command and here's what I get:
> [root@iclu7 /root]# /sbin/ifconfig eth0:1 192.168.5.254 up
> SIOCSIFADDR: No such device
> SIOCSIFFLAGS: No such device
> SIOCSIFFLAGS: No such device
> Naturally, after this, ifconfig -a has no mention of the eth0:1 interface.
>
> For sanity sake, the following command does succeed:
> /sbin/ifconfig eth0 192.168.5.7 up
>
> Now I'm beginning to wonder if there is a kernel option that I'm missing.  Following the instructions in the LVS
> patch readme, I have included the following:
>
> Kernel Compile Options:
>
> Code maturity level options ---
>         [*] Prompt for development and/or incomplete code/drivers
> Networking options ---
>         [*] Network firewalls
>         ....
>         [*] IP: firewalling
>         ....
>         [*] IP: masquerading
>         ....
>         [*] IP: masquerading virtual server support
>         (12) IP masquerading table size (the Nth power of 2)
>         < > IPVS: round-robin scheduling
>         < > IPVS: weighted round-robin scheduling
>         < > IPVS: least-connection scheduling
>         < > IPVS: weighted least-connection scheduling
>
> I also added in:
>         [*] IP: aliasing support

-- 
Tim Burke                                      Tel. 978-446-9166 x232
Mission Critical Linux, LLC                    burke@xxxxxxxxxxx
http://www.missioncriticallinux.com