enabling two eths

Leisner, Martin Martin.Leisner at xerox.com
Thu Feb 22 03:28:10 EST 2007


 
Send the results of 
ifconfig
and
route -n
 
I take it eth0 works fine...
 
Have you tried swapping the assignments and see if eth1 works (to
eliminate faulty hardware).
 
marty


________________________________

	From:
linuxppc-embedded-bounces+martin.leisner=xerox.com at ozlabs.org
[mailto:linuxppc-embedded-bounces+martin.leisner=xerox.com at ozlabs.org]
On Behalf Of Manjunath AM
	Sent: Tuesday, February 20, 2007 11:50 PM
	To: Vitaly Bordug
	Cc: linuxppc-embedded at ozlabs.org
	Subject: Re: enabling two eths
	
	

	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 <vbordug at ru.mvista.com> 

02/20/2007 09:30 PM 

To
Alex Zeffertt <ajz at cambridgebroadband.com> 
cc
Manjunath AM <Manjunath.AM at Lntemsys.com>, linuxppc-embedded at ozlabs.org 
Subject
Re: enabling two eths

	




	On Tue, 20 Feb 2007 15:31:54 +0000
	Alex Zeffertt <ajz at cambridgebroadband.com> 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
	
	

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20070221/f776612c/attachment.htm 


More information about the Linuxppc-embedded mailing list