Bluehost.com Web Hosting $6.95

multiple NIC / same subnet

This is a discussion on multiple NIC / same subnet within the Linux Networking forums, part of the Linux Forums category; Hi Kernel : 2.4.19 I have 2 NICs on same subnet with IP 192.168.0.76(eth0) and ...


Go Back   Usenet Forums > Linux Forums > Linux Networking

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 07-29-2003
ssk
 
Posts: n/a
Default multiple NIC / same subnet

Hi
Kernel : 2.4.19

I have 2 NICs on same subnet with IP 192.168.0.76(eth0) and
192.168.0.72(eth1).

I initiated a data transfer from another machine to a server running
on the above machine. I gave the server IP as 192.168.0.72 on the
client side. During the transfer if i unplug eth0,
- the data transfer is hanging
- iam unable to reach the server machine even thru eth1 which is
connected
- iam not able to reach any machine on 192.168.0.0 network from the
server machine

I understand this is bcos the route to 192.168.0.0 is using the device
eth0 which is the first entry in the routing table. is there anyway to
avoid this , so that linux will automatically failover to the second
route?

thanks
ssk
Reply With Quote
  #2 (permalink)  
Old 07-29-2003
jack
 
Posts: n/a
Default Re: multiple NIC / same subnet

ssk wrote:
> I have 2 NICs on same subnet with IP 192.168.0.76(eth0) and
> 192.168.0.72(eth1).


Having two NICs on the same subnet is never a good idea; this has
been discussed here multiple times over...


> I initiated a data transfer from another machine to a server running
> on the above machine. I gave the server IP as 192.168.0.72 on the
> client side. During the transfer if i unplug eth0,
> - the data transfer is hanging
> - iam unable to reach the server machine even thru eth1 which is
> connected
> - iam not able to reach any machine on 192.168.0.0 network from the
> server machine


There are two reasons that You cannot get to Your server/service on
that box: Firstly, depending on the service, if it is configured to
only listen on the eth0 IP, it will not listen on eth1. Secondly,
even if it serves the other IP, it will try to send the reply via
eth0, which will fail when eth0 is no longer connected. So on the
remote end, it looks like "unreachable", although it is the other
way around: You can reach the server very well, but the server can-
not reach You any more.


> I understand this is bcos the route to 192.168.0.0 is using the device
> eth0 which is the first entry in the routing table. is there anyway to
> avoid this , so that linux will automatically failover to the second
> route?


Correct. - If You remove eth0 from Your routing table, things will work
again.
As for automatic failover and things, see the Linux Advanced Routing
HowTos which You will find spread everywhere over the net.


Cheers, Jack.

--
----------------------------------------------------------------------
My personal reading of the string "MicroSoft" expands to "NanoWeak"...

Reply With Quote
Reply
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On




All times are GMT +1. The time now is 08:49 AM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0