[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ping -b => DUP !
Finaly I could reproduce the problem with only one MCM connected.
ping -b 172.16.5.255
WARNING: pinging broadcast address
PING 172.16.5.255 (172.16.5.255) from 172.16.4.1 : 56(84) bytes of data.
Warning: time of day goes back, taking countermeasures.
64 bytes from 172.16.4.1: icmp_seq=0 ttl=255 time=88 usec
64 bytes from 172.16.4.241: icmp_seq=0 ttl=64 time=591 usec (DUP!)
64 bytes from 172.16.4.1: icmp_seq=1 ttl=255 time=44 usec
64 bytes from 172.16.4.1: icmp_seq=2 ttl=255 time=47 usec
64 bytes from 172.16.4.1: icmp_seq=3 ttl=255 time=47 usec
64 bytes from 172.16.4.1: icmp_seq=4 ttl=255 time=52 usec
I seems that the network interface crashed. The MCM can not be reach
by the network anymore (WEB, telnet, ping ).
But we can acces by the debug port. It seems to work normaly. I run
ifconfig and here is the result.
eth0 Link encap:Ethernet HWaddr 00:40:8C:00:00:C3
inet addr:172.16.5.255 Bcast:172.16.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:724 errors:0 dropped:0 overruns:0 frame:2
TX packets:277 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:729894 (712.7 kb) TX bytes:30094 (29.3 kb)
Interrupt:17 DMA chan:1
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:35 errors:0 dropped:0 overruns:0 frame:0
TX packets:35 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:3804 (3.7 kb) TX bytes:3804 (3.7 kb)
Henrik Eriksson a écrit:
[mailto:firstname.lastname@example.org] On Behalf Of girerd
Sent: Wednesday, June 30, 2004 5:22 PM
We have duplicated packets when we use the command :
ping -b broadcast_adrress.
We send this command from a PC under linux with two network
Only one MCM 2+8 is connected to eth1.
What this DUP ! messages mean ? (see attached file)
You get multiple responses for each ping, the MCM (172.16.4.241)
and what I assume is eth1 on your linux PC (22.214.171.124) both
respond (as they should do). The ping application warns about
received duplicates even if they come from different destinations.
It is harmless, as it was a broadcast ping.
The messages are correct if we use the ping directly to the MCM.
Also if we try ping -b with fewer MCMs on the same network
the MCMs become
That sounds bad. Unreachable how, the devices crash, become
unresponsive on the network, or something else? And what do you
mean with 'fewer MCMs on the same network', you only mentioned
one MCM above? You haven't accidentally configured the same
address on several MCMs?
Claude GIRERD - Service Electronique
INSTITUT DE PHYSIQUE NUCLEAIRE DE LYON
4, rue Enrico Fermi
69622 Villeurbanne cedex
tel: 33 (0)4 72 43 11 05
fax: 33 (0)4 72 44 80 04