Message-ID: <41DCC791.5010901@2rosenthals.com>
Organization: Rosenthal & Rosenthal
User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.8a6) Gecko/20041130 MultiZilla/1.6.4.0b Mnenhy/0.6.0.104
MIME-Version: 1.0
References: <41D85AE5.5040502@hccnet.nl> <20050102211847.E40042A02A4@postfix4-2.free.fr> <4652-SnapperMsg4EDDFFFDBDFE3636@68.246.139.135> <41D9BDAC.8050907@clanganke.de>
In-Reply-To: <41D9BDAC.8050907@clanganke.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Date:  Thu, 06 Jan 2005 00:07:29 -0500
Sender: os2-wireless_users-owner <os2-wireless_users-owner@2rosenthals.com>
Reply-To: os2-wireless_users@2rosenthals.com
From:  Lewis G Rosenthal <os2-wireless_users@2rosenthals.com>
To:  os2-wireless_users@2rosenthals.com
Subject: [OS2Wireless] wlanstat question)

On 01/03/2005 04:48 pm, Christian Langanke thus wrote :

> Lewis G Rosenthal wrote:
>
>> My NetWare servers handle DHCP on my networks, so I leave the DHCP 
>> server turned off in the routers/AP's. XWLAN has no problem getting 
>> an address, as all it does is start the DHCPCD, anyway.
>>
> Yes, and no, it really fires of a dhcpstrt command! just launching the 
> client deamon would not do that.
>
Yes, of course. I should have rephrased... :-)

>> If there's a problem getting parameters, I'd suggest bumping up the 
>> timeout setting for DHCPCD; it may just be a lazy DHCP server.
>>
> I assume you mean the timeout parameter for the DHCPSTRT command.

Yes.

> If so I think you may misunderstand this parameter  -it only tells how 
> long dhcpstrt should wait for a response of dhcpcd. XWLAN (of course) 
> does not use it, but sets it to zero, because for an event driven GUI 
> it is useless to block the own program like this. Instead, the DHCPCD 
> will try it anyway, no matter if and how long dhcpstrt will wait for a 
> response.

Right; I forgot about this. We've discussed it offlist.

>
> XWLAN also waits forever, but uses its own "GUI app method", showing 
> the "configuration status" bitmap as long as the IP interface did not 
> get configured, what is checked about every 200ms. Until that (or 
> until the dhcpcd is killed or stopped), the daemon repeats the DHCP 
> RECOVER command again and again (you can determine the period by 
> activating the log - see dhcpcd.cfg  for details). Having said all 
> that, no parameter change will stop that or even improve anything.

Okay, so then it appears that XWLAN may be having some difficulty 
determining the IP address already assigned, as Kris has said that the 
router shows an IP address assigned to the MAC of the card.

-- 
Lewis
------------------------------------------------------------
Lewis G Rosenthal, CNA 
Rosenthal & Rosenthal, LLC
Accountants / Network Consultants 
  New York / Northern Virginia           www.2rosenthals.com
eComStation Consultants                  www.ecomstation.com
Novell Users International        www.novell.com/linux/truth
------------------------------------------------------------ 

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

To unsubscribe from this list, send a message to
steward@2rosenthals.com with the command
"unsubscribe os2-wireless_users" in the body
(omit the quotes).

For help with other commands, send a message
to steward@2rosenthals.com with the command
"help" in the body (omit the quotes).

This list is hosted by Rosenthal & Rosenthal
P.O. Box 281, Deer Park, NY 11729-0281. Non-
electronic communications related to content
contained in these messages should be directed
to the above address. (CAN-SPAM Act of 2003)

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=