From: "Carl Gehr" <os2-wireless_users@2rosenthals.com>
Received: from mxout2.mailhop.org ([63.208.196.166] verified)
  by 2rosenthals.com (CommuniGate Pro SMTP 5.0.9)
  with ESMTP id 415475 for os2-wireless_users@2rosenthals.com; Sun, 08 Oct 2006 01:04:36 -0400
Received: from mxin1.mailhop.org ([63.208.196.175])
	by mxout2.mailhop.org with esmtp (Exim 4.51)
	id 1GWQpl-00042D-Sy
	for os2-wireless_users@2rosenthals.com; Sun, 08 Oct 2006 01:04:19 -0400
Received: from mail-out2.fuse.net ([216.68.8.175] helo=smtp2.fuse.net)
	by mxin1.mailhop.org with esmtp (Exim 4.51)
	id 1GWQpX-000H0P-0O
	for os2-wireless_users@2rosenthals.com; Sun, 08 Oct 2006 01:04:12 -0400
Received: from gx4.fuse.net ([208.102.7.45]) by smtp2.fuse.net
          (InterMail vM.6.01.04.04 201-2131-118-104-20050224) with ESMTP
          id <20061008050223.LVYQ15823.smtp2.fuse.net@gx4.fuse.net>
          for <os2-wireless_users@2rosenthals.com>;
          Sun, 8 Oct 2006 01:02:23 -0400
Received: from localhost ([208.102.7.45]) by gx4.fuse.net
          (InterMail vG.1.02.00.02 201-2136-104-102-20041210) with ESMTP
          id <20061008050223.YAEB11137.gx4.fuse.net@localhost>
          for <os2-wireless_users@2rosenthals.com>;
          Sun, 8 Oct 2006 01:02:23 -0400
To: "OS/2 Wireless Users Mailing List" <os2-wireless_users@2rosenthals.com>
Date: Sun, 08 Oct 2006 01:02:19 -0400 (EDT)
Reply-To: "Carl Gehr" <Carl.Gehr@attglobal.net>
Priority: Normal
X-Mailer: PMMail 2.20.2382 for OS/2 Warp 4.5
In-Reply-To: <list-415171@2rosenthals.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Re: [OS2Wireless]Re: T23 internal cards success
Message-Id: <20061008050223.YAEB11137.gx4.fuse.net@localhost>
X-Mail-Handler: MailHop by DynDNS
X-Spam-Score: -2.5 (--)

On Sat, 07 Oct 2006 19:46:52 -0400, Lewis G Rosenthal wrote:

>On 10/07/06 03:43 pm, Carl Gehr thus wrote :
>> Lewis,
>> I went through exactly the steps, in the sequence shown below.
>> 	#2 Killed it.
>> 	#3 Reran the script which restarted DHCPCD
>> And, as you can see, #4 Closed DHCPMon and Restarted it.
>>
>>   
>Oops. Yes, now how did I miss that when I read your post the first time? 
>Too much on my mind...
>> Just for the exercise, I reran the script again just now.  The PID for
>> the DHCPCD changed from 109 as it was after the previous exercise and
>> it is now showing as 216.
>>
>> If there's something else to look at [and you can tell me how], I'll be
>> happy to try.
>>
>> I think I mentioned this originally, but if I just bring the system up
>> with a cable attached at boot-time, DHCPMon displays what it should. 
>> The script changes what is displayed to that shown below.
>>
>>   
>All I can tell you Carl is that I get the same issue here, so I just run 
>the script a couple more times until DHCPMON picks up on it. I don't 
>close DHCPMON, either; I just rerun the script, and eventually, DHCPMON 
>allows me to select the alternate interface.
>
><snip>

We're getting closer to communicating with each other now...

I agree with the delay in switching the interface being monitored... 
Eventually, it does get it right.  So, we're the same there.

Where we differ [I think], is that even though the correct interface is
finally monitored, the monitor still does not show an IP address,
apparantly because it says:
	"DHCP client is not running."
Now, the client *is* running.  So, why does the monitor fail to
recognize the client and, therefore, display the IP address instead of
saying the IP address is "Not configured"...????

This used to work.  Doesn't now...
       I don't know why; what changed; nor how to fix it.

Carl