Archives


- Beowulf
- Beowulf Announce
- Scyld-users
- Beowulf on Debian

About the usage of a dual port card

Many of your questions may have already been answered in earlier discussions or in the FAQ. The search results page will indicate current discussions as well as past list serves, articles, and papers.

Search

Jacques B. Siboni jacsib at lutecium.org
Wed Oct 3 23:20:25 PDT 2001


Can't you avoid to use the same broadcast ip for the 2 nics?

Jacques


Thomas Lorenzen wrote:
> 
>      Hi'
> 
>    In our linux cluster our server has a dual port intel
> nic. Both ports are configured to be on the same net as are
> all the clients of the cluster. The clients boot as diskless
> clients using the server.
> 
>    My question is, if there is a way to make a specific
> interface, to which a packet comes, also answer this
> request. What happens at the moment is, that if one pings
> eth2, then eth1 answers, and in general eth1 answers all
> requests unless this line is saturated, in which case eth2
> takes over. This is immediately seen from the output of RX
> and TX records below.
> 
>    Below I present the relevant output of ifconfig.
> 
> eth1      Link encap:Ethernet  HWaddr 00:03:47:3B:27:EE
>           inet addr:192.168.200.100  Bcast:192.168.200.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:399607 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:1070472 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           Interrupt:19 Base address:0x4000
> eth2      Link encap:Ethernet  HWaddr 00:03:47:3B:27:EF
>           inet addr:192.168.200.200  Bcast:192.168.200.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:142634 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:104 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           Interrupt:16 Base address:0x6000
> 
>    Below I present the relevant output of route.
> 
> 192.168.200.0   *               255.255.255.0   U     0 0 0 eth1
> 192.168.200.0   *               255.255.255.0   U     0 0 0 eth2
> 
>    In brief I would like, that if I contact an interface
> ethX using ping, say, then that particular interface ethX
> should also answer the request. Would anybody know of the
> possibility of doing so and what is in that case the trick
> to do.
> 
>    Thanks for any help in advance.
> 
>    Best Regards.
> 
>      Thomas.

-- 
Dr. Jacques B. Siboni mailto:jacsib at Lutecium.org
8 pass. Charles Albert, F75018 Paris, France
Tel. & Fax: 33 (0) 1 42 28 76 78
Home Page: http://www.lutecium.org/jacsib/




More information about the Beowulf mailing list