From: Church, Chuck (cchurch@wamnetgov.com)
Date: Fri Jul 02 2004 - 12:04:34 GMT-3
I think this is normal. Many devices treat the subnet address the same
as the broadcast address. So it's responding like it normally would.
Not all devices respond to subnet/broadcast pings though. I don't think
any of the Windows flavors will. But most Ciscos do.
Chuck Church
Lead Design Engineer
CCIE #8776, MCNE, MCSE
Wam!Net Government Services - Design & Implementation Team
1210 N. Parker Rd.
Greenville, SC 29609
Office: 864-335-9473
Cell: 703-819-3495
cchurch@wamnetgov.com
PGP key:
http://pgp.mit.edu:11371/pks/lookup?op=index&search=cchurch%40wamnetgov.
com
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Guilherme Correia
Sent: Friday, July 02, 2004 9:36 AM
To: ccielab@groupstudy.com
Subject: Ping the subnet address
Hi
I am experiencing this weird issue that when I ping the subnet address,
one of the routers respond.
For example, when I ping 172.24.18.4 (subnet 172.24.18.4/30) one of the
routers with an interface on the subnet responds:
7204-1#ping 172.24.18.4
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 206.24.18.4, timeout is 2 seconds:
Reply to request 0 from 172.24.18.5, 1 ms Reply to request 1 from
172.24.18.5, 1 ms Reply to request 2 from 172.24.18.5, 1 ms Reply to
request 3 from 172.24.18.5, 1 ms Reply to request 4 from 172.24.18.5, 1
ms
How can I stop this?
TIA
This archive was generated by hypermail 2.1.4 : Sun Aug 01 2004 - 10:11:45 GMT-3