Correction to the "Ethernet problem"

[Leon Pollak]

Sorry, the information about 7s was incorrect - now I received the case when 
it was also insufficient. :(

But one thing is undoubted - when there is the first packet lost, there is 
also doubled arp request. Below is the tcpdump printout (133=rtems, 57=pc):

Packet is lost:
arp who-has 192.168.50.133 tell 192.168.50.133 <====WHY IS THIS?
arp who-has 192.168.50.57 tell 192.168.50.133
arp reply 192.168.50.57 is-at 00:19:db:ed:16:94
arp who-has 192.168.50.57 tell 192.168.50.133 <====WHY IS THIS?
arp reply 192.168.50.57 is-at 00:19:db:ed:16:94
IP (tos 0x0, ttl 64, id 2, offset 0, flags [none], proto UDP (17), length 74) 
192.168.50.133.33100 > 192.168.50.57.33100: UDP, length 46
	My Data:1111111111111111
IP (tos 0x0, ttl 64, id 3, offset 0, flags [none], proto UDP (17), length 74) 
192.168.50.133.33100 > 192.168.50.57.33100: UDP, length 46
	My Data:2222222222222222

	
Packet is not lost:
arp who-has 192.168.50.133 tell 192.168.50.133
arp who-has 192.168.50.57 tell 192.168.50.133
arp reply 192.168.50.57 is-at 00:19:db:ed:16:94
IP (tos 0x0, ttl 64, id 1, offset 0, flags [none], proto UDP (17), length 74) 
192.168.50.133.33100 > 192.168.50.57.33100: UDP, length 46
	My Data: 0000000000000000
IP (tos 0x0, ttl 64, id 2, offset 0, flags [none], proto UDP (17), length 74) 
192.168.50.133.33100 > 192.168.50.57.33100: UDP, length 46
	My Data: 1111111111111111
IP (tos 0x0, ttl 64, id 3, offset 0, flags [none], proto UDP (17), length 74) 
192.168.50.133.33100 > 192.168.50.57.33100: UDP, length 46
	My Data: 2222222222222222


Any help, please?
-- 
Leon