Hi, Thanks for your kind reply, Yes i have used different * IP Subnets*

The IPs and subnet details I use is
1. eth0(configured through u-boot env settings)->> 192.168.174.231 and 
subnet is 255.255.255.0 
2. eth1(configured after kernel is up)--> 192.168.33.64 and subnet is 
255.255.248.0

Even i tried by connecting second eth to host PC using cross cable as a 
stand-alone network but even "ping" did not work.. 



Thanks & Regards
 MANJUNATH AM
 Senior Software Engineer
 Emsys
 Larsen & Toubro Limited
 Mysore-570018
 Mobile:9886375926




Vitaly Bordug <[EMAIL PROTECTED]> 
02/20/2007 09:30 PM

To
Alex Zeffertt <[EMAIL PROTECTED]>
cc
Manjunath AM <[EMAIL PROTECTED]>, [email protected]
Subject
Re: enabling two eths






On Tue, 20 Feb 2007 15:31:54 +0000
Alex Zeffertt <[EMAIL PROTECTED]> wrote:

> 
> Manjunath AM wrote:
> > 
> > Hi,
> > 
> > We are using MPC8272 based target board, we use montavista Linux 
version 
> > 2.6.10 kernel image (with NFS enabled) to our target board,
> > 
> > Our board has  2 FCCs (eth0 and eth1). bot the eth's works perfectly 
> > when we use them independently, but when we are trying to enable 
second 
> > one after the kernel is up using linux command  "ifconfig eth1 
> > 192.168.33.64 up"(IP address)nothing is working.
> > Please suggest how to enable second eth (either 0 or 1) once the 
kernel 
> > is up with NFS file system
> 
> 
> Have you made sure that eth0 and eth1 are on *different* IP subnets?
> If they are on the same subnet, or intersecting subnets, your routing
> will get confused.
> 
It depends :)

I used to test functionality such a way to have two enets in same subnet, 
then ifdown one of them.

At least with mvista RFS, one enet  handles NFS, other is up but all the 
packets are routed to it via
the first one. And when the first one got ifdown, routing switches to the 
remaining enet...
-- 
Sincerely, 
Vitaly

_______________________________________________
Linuxppc-embedded mailing list
[email protected]
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

Reply via email to