Re: [ECOS] Ping test question

[Gary Thomas <gthomas at redhat dot com>]

On 18-May-00 Nicolas Gerber wrote:
> 
> 
>> On 18-May-00 Nicolas Gerber wrote:
>> > Hi all,
>> > I'm trying to run the TCP/IP stack test programs on an edb7209-2C.0
> board.
>> > I have disabled DHCP and enabled manual IP address configuration.
>> >
>> > So my board looks totaly outside the network.
>> > Is there any special point in the edb72xxx ethernet configuration that I
> forget?
>> >
>> My best guess is that you have not modified your hardware (per the
> README).  This
>> particular board cannot generate ethernet interrupts (required by the
> driver) unless
>> you physically remove resistor R168 and all jumpers from JP45.
> 
> I remove the resistor R168 and all jumpers from JP45, and unfortunately, it
> doesn't change anything.
> 

Good.  At least we know this isn't the problem :-)

>> Do you know what the board actually sends on the wire?
> I get the following output with the 'set net_debug = 1' command :
> 
   <snip>
> Sending 42 bytes
> xmit 42 bytes at 523AE
> 000523AE: FFFF FFFF FFFF 0888  1234 5678 0806 0001   |.........4Vx....|
> 000523BE: 0800 0604 0001 0888  1234 5678 0A14 02CA   |.........4Vx....|
> 000523CE: 0000 0000 0000 0A14  02CA                  |..........      |
> PING server 10.20.2.215
> Tx event: 8
> Sending 42 bytes
> xmit 42 bytes at 5252E
> 0005252E: FFFF FFFF FFFF 0888  1234 5678 0806 0001   |.........4Vx....|
> 0005253E: 0800 0604 0001 0888  1234 5678 0A14 02CA   |.........4Vx....|
> 0005254E: 0000 0000 0000 0A14  02D7                  |..........      |
> Tx event: 8
> recvfrom: Operation timed out
> 

This all looks correct to me.  The first packet is an ARP "I'm at" packet
where the board is announcing itself on the LAN.  The second packet is the
board asking for the MAC (ESA) address of 10.20.2.215.  However, it seems
to not get an answer.  It really can't go on until your 10.20.2.215 host
answers back.

> Is it a problem related with my IP address configuration?
> 

I don't think so.  This does look OK, even though as I pointed out before
the display of your hardware address is bogus (since you used manual IP
configuration).

Can you "watch the wire" using some sort of network sniffer/dumper?  If
you're running on Linux, just use 'tcpdump'.  Sorry, but I'm not a Windows
user, so I can't give pointers there.