Re: Multiple IP Addressing
On Tue, 16 Nov 1999, Jason Taylor wrote:
> I am new to the Debian world and am working on a new in house system that
> has 2 3com 10/100 PCI NIC's in it. I got the system to find the NIC's okay
> now I am wondering how I configure /etc/init.d/network file to load balance
> between the NIC's. I added a seperate script in /etc/init.d/network for eth1
> but it overwrites eth0 default route which is destination - default
> gateway - 131.107.2.15 genmask - 0.0.0.0 flags - UG metric - 1 ref - 0 use -
> 0 iface - eth1. I would think that I need a default route for both NIC's?
> TIA..
>
> below is the output of ifconfig -a
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
> UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1
> RX packets:278 errors:0 dropped:0 overruns:0 frame:0
> TX packets:278 errors:0 dropped:0 overruns:0 carrier:0
> Collisions:0
>
> eth0 Link encap:Ethernet HWaddr 00:50:DA:08:5D:09
> inet addr:131.107.2.216 Bcast:131.107.2.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:845 errors:47 dropped:0 overruns:0 frame:71
> TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
> Collisions:0
> Interrupt:11 Base address:0xec00
>
> eth1 Link encap:Ethernet HWaddr 00:50:04:73:C6:A9
> inet addr:131.107.2.217 Bcast:131.107.2.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:436 errors:47 dropped:0 overruns:0 frame:71
> TX packets:367 errors:0 dropped:0 overruns:0 carrier:0
> Collisions:0
> Interrupt:10 Base address:0xe880
>
I don't think what you are trying to do makes any sense. It seems that you
are trying to connect both NICs to the same Ethernet segment. This, and
your words "load balance" seem to imply that you think that 1 NIC can't
keep up with the traffic load on that Ethernet segment that is destined
for your machine. I think this is mistaken, 1 NIC should easily be able to
keep up with the traffic of the one Ethernet segment to which it is
connected. Second, I'm not aware of any capability within the Linux IP
layer to "load balance" between network interfaces connected to the same
network. This is partly why the addition of the second default route for
eth1 overwrites the default route for eth0.
I think it might help if you explained what your end goal is.
Reply to: