ethernet port problem

hi,
i have a fedora core 3 machine, but have the following network problem:
one of the ethernet ports (eth1) appears to be up and running but the
machine has no connectivity if just eth1 is connected:
here is the route:
Destination Gateway Genmask Flags Metric Ref Use
Iface
205.150.209.0 * 255.255.255.0 U 0 0 0
eth0
205.150.209.0 * 255.255.255.0 U 0 0 0
eth1
169.254.0.0 * 255.255.0.0 U 0 0 0
eth1
default mci209.3z.ca 0.0.0.0 UG 0 0 0
eth0

i wander since this configuration shows eth0 to be configured
differently might be the reason that i can only connect to the internet
using eth0 and not eth1.

i dont know much about linux networking but am trying to learn; maybe
someone could help me with this:
this is the ifconfig:
eth0 Link encap:Ethernet HWaddr 00:11:43F:53:23
inet addr:205.150.209.3 Bcast:205.150.209.255
Mask:255.255.255.0
inet6 addr: fe80::211:43ff:fedf:5323/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4135701 errors:0 dropped:0 overruns:0 frame:0
TX packets:2505588 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:737287409 (703.1 MiB) TX bytes:2629587235 (2.4 GiB)
Base address:0xecc0 Memory:dfae0000-dfb00000

eth1 Link encap:Ethernet HWaddr 00:11:43F:53:24
inet addr:205.150.209.2 Bcast:205.150.209.255
Mask:255.255.255.0
inet6 addr: fe80::211:43ff:fedf:5324/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1944111 errors:0 dropped:0 overruns:0 frame:0
TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:457356068 (436.1 MiB) TX bytes:3910 (3.8 KiB)
Base address:0xdcc0 Memory:df8e0000-df900000

(E-Mail Removed) wrote:
> hi,
> i have a fedora core 3 machine, but have the following network problem:
> one of the ethernet ports (eth1) appears to be up and running but the
> machine has no connectivity if just eth1 is connected:
> here is the route:
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 205.150.209.0 * 255.255.255.0 U 0 0 0 eth0
> 205.150.209.0 * 255.255.255.0 U 0 0 0 eth1
> default mci209.3z.ca 0.0.0.0 UG 0 0 0 eth0

(I've deleted one routing entry that isn't relevant to this discussion.)

The "default" entry determines what happens to traffic sent anywhere but
205.150.209.0 - it is sent to mci209.3z.ca, which is supposed to be
directly accessible via eth0. When eth0 is shut down, the default entry
goes away.

eth1 will never be used for outgoing traffic unless eth0 is shut down.
Reverse DNS suggests you are trying to run web servers at both IP
addresses, so this may not be a good thing.

Note that I said "shut down", not "disconnected". Nothing changes if
you pull the plug on eth0.

Why don't you tell us what you are trying to do. Looking at archives of
this newsgroup or some networking FAQ's would be good idea also.

thanks allen,
i am just trying to aggregate the links for failover.
so that when eth0 is unplugged eth1 takes over.
i tried by creating a bonding interface.
when i shut down eth0 to test it; eth1 does not take over as expected.

i will do a bit more research on this newgroup. cheers, ervin.

Check out the LARTC howto:
http://lartc.org/howto/lartc.rpdb.multiple-links.html
There is everything you need.

(E-Mail Removed) wrote:

> 169.254.0.0 * 255.255.0.0 U 0 0 0
> eth1


Does'nt that mean eth1 is set up for DHCP and cannot get an address?

On Tue, 28 Feb 2006 05:57:45 -0800, Radge wrote:

>
> (E-Mail Removed) wrote:
>
>> 169.254.0.0 * 255.255.0.0 U 0 0 0
>> eth1
>
>
> Does'nt that mean eth1 is set up for DHCP and cannot get an address?

Sorry. No. 169.254.x.y is a APIPA address range.
Ref can ne found at ftp://ftp.rfc-editor.org/in-notes/rfc3927.txt

It means "Automatic Private IP Addressing"

It is a range of IP addresses that a computer will assign itself if
one it is not able to get one from either a static configuration or
from a network server (BootP or DHCP.)

So in effect it cannot receive an address. But it doers not mean
that DHCP was configured.

An effect of APIPA address is that no default gateway (default router) or
DNS is set therefore, not much real networking is done.

In effect, it is used mostly by software. So software designed with
networking in mind does indeed find an IP address even though a
communication with it is limited to other hosts in the same APIPA range
that support some naming global broadcast capacity...

Hope it help.