RE: [ECOS] no response from ping

["Trenton D. Adams" <tadams at theone dot dnsalias dot com>]

Actually, I'm not sure that I've seen a ping returned at all.  I think
they've all been arp replies.  I just tested it just now, and they were
all arp replies.

I have another problem as well.  The responses are an extremely long
time later.  The pings don't even reach the target a lot of the time
because the ARPs get in the way.  It's almost as if shutting off
interrupts prevents the pings from getting through because the wavelan
card is too slow.

> -----Original Message-----
> From: ecos-discuss-owner@sources.redhat.com 
> [mailto:ecos-discuss-owner@sources.redhat.com] On Behalf Of 
> Jonathan Larmour
> Sent: December 17, 2001 8:36 PM
> To: Trenton D. Adams
> Cc: 'eCos Discussion'
> Subject: Re: [ECOS] no response from ping
> 
> 
> "Trenton D. Adams" wrote:
> > 
> > What would cause my network driver card not to respond to a 
> ping?  Where
> > should I start looking for this?  Sometimes it responds, 
> and other times
> > it doesn't.  Of course I can't see the response on my PC, but the
> > packets are dumped in eCos.
> 
> So you see the ping packets arrive on the target, but don't 
> see a reply on
> the host? The thing to check is whether the target is trying to send
> anything at all. Firstly use a packet sniffer to see if the target is
> sending something, but invalid. Secondly debug the net stack 
> (over serial!)
> to see if it attempts to transmit a reponse.
> 
> Jifl
> -- 
> Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 
> (1223) 271062
> Maybe this world is another planet's Hell -Aldous Huxley || 
> Opinions==mine
>