From: "Al Heath" Received: from [192.168.100.201] (HELO mail.2rosenthals.com) by 2rosenthals.com (CommuniGate Pro SMTP 5.1.16) with ESMTP id 2647943 for os2-wireless_users@2rosenthals.com; Tue, 14 Jul 2009 12:32:08 -0400 Received-SPF: pass (secmgr-ny.randr: domain of us.ibm.com designates 32.97.110.151 as permitted sender) client-ip=32.97.110.151; envelope-from=aheath@us.ibm.com; helo=e33.co.us.ibm.com; Received: from e33.co.us.ibm.com ([32.97.110.151]) by secmgr-ny.randr with esmtps (TLSv1:AES256-SHA:256) (Exim 4.43) id 1MQkvD-000316-6B for os2-wireless_users@2rosenthals.com; Tue, 14 Jul 2009 12:32:07 -0400 Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by e33.co.us.ibm.com (8.13.1/8.13.1) with ESMTP id n6EGTj3f001660 for ; Tue, 14 Jul 2009 10:29:45 -0600 Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v9.2) with ESMTP id n6EGVxnQ163558 for ; Tue, 14 Jul 2009 10:31:59 -0600 Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id n6EGVwdR013088 for ; Tue, 14 Jul 2009 10:31:58 -0600 Received: from d03nm122.boulder.ibm.com (d03nm122.boulder.ibm.com [9.17.195.148]) by d03av02.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id n6EGVv0N012843 for ; Tue, 14 Jul 2009 10:31:57 -0600 Importance: Normal Sensitivity: Subject: Re: [OS2Wireless] Re: D-Link DWL-G730AP To: "OS/2 Wireless Users Mailing List" Date: Tue, 14 Jul 2009 11:31:54 -0500 Message-ID: X-MIMETrack: Serialize by Router on D03NM122/03/M/IBM(Release 8.0.1|February 07, 2008) at 07/14/2009 10:31:56 MIME-Version: 1.0 Content-type: multipart/alternative; Boundary="0__=09BBFF60DFC9A8228f9e8a93df938690918c09BBFF60DFC9A822" Content-Disposition: inline X-Spam-Score: 0.9 (/) X-Spam-Report: 0.9 HTML_10_20 BODY: Message is 10% to 20% HTML --0__=09BBFF60DFC9A8228f9e8a93df938690918c09BBFF60DFC9A822 Content-type: text/plain; charset=US-ASCII > Try > ping 192.168.1.255 (for 192.168.1 substitute whatever your subnet is). That may not get responses from all devices. i.e. my subnet is 172.16.240.0, so I would ping to 172.16.15.255 and I get:. PING 172.16.15.255: 56 data bytes 64 bytes from 172.16.9.42: icmp_seq=0. time=0. ms 64 bytes from 172.16.9.150: icmp_seq=0. time=10. ms 64 bytes from 172.16.9.42: icmp_seq=1. time=0. ms 64 bytes from 172.16.9.150: icmp_seq=1. time=0. ms 64 bytes from 172.16.9.42: icmp_seq=2. time=0. ms 64 bytes from 172.16.9.150: icmp_seq=2. time=0. ms But also there are other devices on my subnet, such as a specific ping to PING 172.16.9.102: 56 data bytes 64 bytes from 172.16.9.102: icmp_seq=0. time=0. ms 64 bytes from 172.16.9.102: icmp_seq=1. time=0. ms PING 172.16.9.254: 56 data bytes 64 bytes from 172.16.9.254: icmp_seq=0. time=0. ms 64 bytes from 172.16.9.254: icmp_seq=1. time=0. ms 64 bytes from 172.16.9.254: icmp_seq=2. time=0. ms FWIW, Al H --0__=09BBFF60DFC9A8228f9e8a93df938690918c09BBFF60DFC9A822 Content-type: text/html; charset=US-ASCII Content-Disposition: inline

> Try
> ping 192.168.1.255  (for 192.168.1 substitute whatever your subnet is).

That may not get responses from all devices. i.e. my subnet is 172.16.240.0,
so I would ping to 172.16.15.255 and I get:

PING 172.16.15.255: 56 data bytes
64 bytes from 172.16.9.42: icmp_seq=0. time=0. ms
64 bytes from 172.16.9.150: icmp_seq=0. time=10. ms
64 bytes from 172.16.9.42: icmp_seq=1. time=0. ms
64 bytes from 172.16.9.150: icmp_seq=1. time=0. ms
64 bytes from 172.16.9.42: icmp_seq=2. time=0. ms
64 bytes from 172.16.9.150: icmp_seq=2. time=0. ms

But also there are other devices on my subnet, such as a specific ping to
PING 172.16.9.102: 56 data bytes
64 bytes from 172.16.9.102: icmp_seq=0. time=0. ms
64 bytes from 172.16.9.102: icmp_seq=1. time=0. ms

PING 172.16.9.254: 56 data bytes
64 bytes from 172.16.9.254: icmp_seq=0. time=0. ms
64 bytes from 172.16.9.254: icmp_seq=1. time=0. ms
64 bytes from 172.16.9.254: icmp_seq=2. time=0. ms

FWIW,
Al H --0__=09BBFF60DFC9A8228f9e8a93df938690918c09BBFF60DFC9A822--