ethernet interface problem with kernel 2.6.14 on MPC8343E

ethernet interface problem with kernel 2.6.14 on MPC8343E

[Luong Ngo]

[-- Attachment #1: Type: text/plain, Size: 805 bytes --]

Hello,

I am having a problem with the interfaces eth0 and eth1 when running
2.6.14kernel on a board with MPC8343E. The problem I encounters is
only one of the
eth interface is really working. Only the one that is configured first,
using "ifconfig eth[0/1] 192.168.1.1 netmask 255.255.255.0" can ping and be
pinged from another host. I wonder if there is setup difference between the
TSEC1 and TSEC2 or this is not related to hardware but rather something in
the kernel. When I ping from other host, from within the Gianfar driver, I
can see the packet is received on both interfaces but only one responds.
When pinging from the system itself, only the working interface sending out
packet, the other interface does not send anything. Please advise me what I
am doing wrong or missing.

Thank you,
L. Ngo

[-- Attachment #2: Type: text/html, Size: 905 bytes --]

ethernet interface problem with kernel 2.6.14 on MPC8343E

[Luong Ngo]

[-- Attachment #1: Type: text/plain, Size: 805 bytes --]

Hello,

I am having a problem with the interfaces eth0 and eth1 when running
2.6.14kernel on a board with MPC8343E. The problem I encounters is
only one of the
eth interface is really working. Only the one that is configured first,
using "ifconfig eth[0/1] 192.168.1.1 netmask 255.255.255.0" can ping and be
pinged from another host. I wonder if there is setup difference between the
TSEC1 and TSEC2 or this is not related to hardware but rather something in
the kernel. When I ping from other host, from within the Gianfar driver, I
can see the packet is received on both interfaces but only one responds.
When pinging from the system itself, only the working interface sending out
packet, the other interface does not send anything. Please advise me what I
am doing wrong or missing.

Thank you,
L. Ngo

[-- Attachment #2: Type: text/html, Size: 1082 bytes --]

Re: ethernet interface problem with kernel 2.6.14 on MPC8343E

[Andy Fleming]

On Nov 6, 2006, at 17:51, Luong Ngo wrote:

> Hello,
>
> I am having a problem with the interfaces eth0 and eth1 when  
> running 2.6.14 kernel on a board with MPC8343E. The problem I  
> encounters is only one of the eth interface is really working. Only  
> the one that is configured first, using "ifconfig eth[0/1]  
> 192.168.1.1 netmask 255.255.255.0" can ping and be pinged from  
> another host. I wonder if there is setup difference between the  
> TSEC1 and TSEC2 or this is not related to hardware but rather  
> something in the kernel. When I ping from other host, from within  
> the Gianfar driver, I can see the packet is received on both  
> interfaces but only one responds. When pinging from the system  
> itself, only the working interface sending out packet, the other  
> interface does not send anything. Please advise me what I am doing  
> wrong or missing.
>

It sounds like both work for you, but not at the same time?

If you set them both to the same IP address, it won't work.   
Actually, it won't work if you set them to different IP addresses on  
the same subnet (as defined by their netmasks).

I think you are trying to get Linux to do something that it doesn't  
do.  Try setting them to different IP addresses, like 192.168.1.1 and  
192.168.2.1

Andy

Re: ethernet interface problem with kernel 2.6.14 on MPC8343E

[Luong Ngo]

[-- Attachment #1: Type: text/plain, Size: 1614 bytes --]

Hi,

It is working now. Thanks for the help. I am just curious that linux kernel
does not know 1 interface's connection is down and check the other interface
to see if it can reaches the destination with other interfaces?

Thanks,
l.ngo

On 11/7/06, Andy Fleming <afleming@freescale.com> wrote:
>
>
> On Nov 6, 2006, at 17:51, Luong Ngo wrote:
>
> > Hello,
> >
> > I am having a problem with the interfaces eth0 and eth1 when
> > running 2.6.14 kernel on a board with MPC8343E. The problem I
> > encounters is only one of the eth interface is really working. Only
> > the one that is configured first, using "ifconfig eth[0/1]
> > 192.168.1.1 netmask 255.255.255.0" can ping and be pinged from
> > another host. I wonder if there is setup difference between the
> > TSEC1 and TSEC2 or this is not related to hardware but rather
> > something in the kernel. When I ping from other host, from within
> > the Gianfar driver, I can see the packet is received on both
> > interfaces but only one responds. When pinging from the system
> > itself, only the working interface sending out packet, the other
> > interface does not send anything. Please advise me what I am doing
> > wrong or missing.
> >
>
> It sounds like both work for you, but not at the same time?
>
> If you set them both to the same IP address, it won't work.
> Actually, it won't work if you set them to different IP addresses on
> the same subnet (as defined by their netmasks).
>
> I think you are trying to get Linux to do something that it doesn't
> do.  Try setting them to different IP addresses, like 192.168.1.1 and
> 192.168.2.1
>
> Andy
>

[-- Attachment #2: Type: text/html, Size: 2149 bytes --]