From: Vitaly Bordug <vbordug@ru.mvista.com>
To: Alex Zeffertt <ajz@cambridgebroadband.com>
Cc: linuxppc-embedded@ozlabs.org, Manjunath AM <Manjunath.AM@Lntemsys.com>
Subject: Re: enabling two eths
Date: Tue, 20 Feb 2007 19:00:11 +0300 [thread overview]
Message-ID: <20070220190011.09b6b8e6@vitb.dev.rtsoft.ru> (raw)
In-Reply-To: <45DB146A.7010302@cambridgebroadband.com>
On Tue, 20 Feb 2007 15:31:54 +0000
Alex Zeffertt <ajz@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 prev parent reply other threads:[~2007-02-20 15:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 13:21 enabling two eths Manjunath AM
2007-02-20 13:44 ` Vitaly Bordug
2007-02-20 15:31 ` Alex Zeffertt
2007-02-20 16:00 ` Vitaly Bordug [this message]
2007-02-21 4:50 ` Manjunath AM
2007-02-21 16:28 ` Leisner, Martin
2007-02-22 4:24 ` Manjunath AM
2007-02-22 20:38 ` Leisner, Martin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070220190011.09b6b8e6@vitb.dev.rtsoft.ru \
--to=vbordug@ru.mvista.com \
--cc=Manjunath.AM@Lntemsys.com \
--cc=ajz@cambridgebroadband.com \
--cc=linuxppc-embedded@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).