linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ricardo Scop <scop@digitel.com.br>
To: "Jack Liu" <Jack_liu@usish.com>,
	"linuxppc-embedded@lists.linuxppc.org"
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Re: Network problem: Ping is OK, Yet telnet and ftp etc is not working
Date: Wed, 31 Mar 2004 22:18:55 -0300	[thread overview]
Message-ID: <200403312218.55300.scop@digitel.com.br> (raw)
In-Reply-To: <200404010049.i310ni6P006887@ms.usish.com>


Jack

On Wednesday 31 March 2004 21:49, Jack Liu wrote:
>
>  Thanks. This chip is supported in linux kernel by tulip driver. {
> 0x1317, 0x0985, PCI_ANY_ID, PCI_ANY_ID, 0, 0, COMET } And I compared
> the driver with 2.6 driver(Currently I am using 2.4.21 kernel), no
> related difference. So I thought this should not be a bug in this
> driver(maybe). When I ftp and telnet myself, it is ok. So the stack
> should be OK. So now I have no idea about the direction to find the
> problem. Please advice me.

First, my previous advice was related to your ping problem when the interface
was not in promiscuous mode.

For the telnet problem, you have to use a sniffer and see what's happening in
the ethernet... Sorry, I have no further advice unless you provide  more
useful information.

HTH,

> ======= 2004-03-31 15:45:00 Origianl message=======
>
> >On Wednesday 31 March 2004 00:02, Jack Liu wrote:
> >>
> >>      We use ADMTek AN983B chip as our network chip. And I have
> >> porting linux to this MPC8241 platform.Now I have a very strange
> >> problem: If I ping my target, no answer. When I start tcpdump on
> >> my target, the ping ... works fine. Since the hardware is put into
> >> promiscuous mode when tcpdump is running, So I use ifconfig to put
> >> NIC work in promiscuous mode. I thought it can temporarily solve
> >> the problem. Now ping is OK. However When I telnet other machine,
> >> no answer.And When I telnet my target, still no answer. I thought
> >> it may because of firewall. So I undef CONFIG_NETFILTER in .config
> >> and autoconf.h. Still the same. So what could be the problem?
> >
> >Well, check your interface's IP addressing for a wrong broadcast
> >address; your may also have a misconfiguration in your hardware's
> >drivers, related to the the MAC address and/or broadcast address
> >matching.

--
Ricardo Scop.
rscop@matrix.com.br
+55 51 999-36-777
Porto Alegre, RS - BRazil

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-04-01  1:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-01  0:49 Network problem: Ping is OK, Yet telnet and ftp etc is not working Jack Liu
2004-04-01  1:18 ` Ricardo Scop [this message]
2004-04-01 15:19   ` Startup sequence for PPC based Linux kernels ppclinux

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=200403312218.55300.scop@digitel.com.br \
    --to=scop@digitel.com.br \
    --cc=Jack_liu@usish.com \
    --cc=linuxppc-embedded@lists.linuxppc.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).