Message-ID: <41DF399B.8010609@hccnet.nl>
Organization: CFM$-FC (Coalition for Micro$oft-Free Computing)
User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; nl-NL; rv:1.7.5) Gecko/20041220
MIME-Version: 1.0
References: <E1ClvFB-0000J2-00@pop-a065d01.pas.sa.earthlink.net> <41DB0D2F.3070504@hccnet.nl> <41DCC86C.2070908@2rosenthals.com> <41DD00FA.3030000@hccnet.nl> <41DD65CA.3000105@2rosenthals.com> <41DDBD7D.2070504@hccnet.nl> <41DEEC4F.4020109@2rosenthals.com>
In-Reply-To: <41DEEC4F.4020109@2rosenthals.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Date:  Sat, 08 Jan 2005 02:38:35 +0100
Sender: os2-wireless_users-owner <os2-wireless_users-owner@2rosenthals.com>
Reply-To: os2-wireless_users@2rosenthals.com
From:  Kris Steenhaut <os2-wireless_users@2rosenthals.com>
To:  os2-wireless_users@2rosenthals.com
Subject: [OS2Wireless] wlanstat question



Lewis G Rosenthal schreef:

> On 01/06/2005 05:36 pm, Kris Steenhaut thus wrote :
>
> <snip>
>
>> Hmm, may I remind you, before you bothering all, I already have done 
>> the obvious, that is:
>>
>> just the Artem driver in the config.sys
>> just in setup.cmd: dhcpstrt -i lan0 and the loopback etc.
>>
> Actually, your wireless adapter is lan1 (according to the data you 
> posted from netstat), so the command should be:
>
> dhcpstrt -i lan1
>
As it is now yes. But I began the message with: "Prior to bothering 
you", remember? (incidentally, for some messages it took a weird long 
time before the appeared here).

> However, I don't think this will make a difference...
>
>> Should have worked, shouldn't it?
>>
> Well, assuming the correct interface is specified, yes, it should.
>
The correct interface was specified indeed. To specify to correct 
interface, that's one of the few things within the scope of simple human 
beings.

>>
>> I have checked with Frank Vos, he has exactly the same card as I 
>> have, and at his Laptop, a T23 IIRC, DHCP is working with Artem 
>> drivers as well as with Genprism (remember, Artem drivers don't work 
>> here at all, except for the flashing lights).
>>
> Which again leads me to believe that this is software-related (somewhere),

That's what I thought too.

> and probably in the DHCP client and not the router (good news, actually).
>
>>
> internal card. As IP isn't bound to the internal card (for obvious 
> reasons), it can't be interfering with obtaining an address. The 
> router obviously doesn't see the card, either.
>
I think the router does see the card. If it were otherwise, there would 
be no way wlanstat could tell me "connected to SMC", couldn't it. (SMC 
is the router's SSID, in protoco.,ini just is stated "Any")

BTW: following a cut from the router's security log:

01/07/2005  02:38:03 sending OFFER to 192.168.2.101
01/07/2005  02:37:25 192.168.2.102 login success
01/07/2005  02:36:53 sending OFFER to 192.168.2.101
01/07/2005  02:36:04 sending OFFER to 192.168.2.101
01/07/2005  02:35:25 sending OFFER to 192.168.2.101
01/07/2005  02:35:05 sending OFFER to 192.168.2.101
01/07/2005  02:34:55 sending OFFER to 192.168.2.101
01/07/2005  02:34:39 sending OFFER to 192.168.2.101


As you do know already, 192.168.2.101 is the IP address assigned by the 
router to the jacaranda (and we are sure coz the router lists the 
jacaranda MAC address too.

So, it seems  the laptop for one reason or another doesn't reply to or 
doesn't see the "offer".

The "01/07/2005  02:37:25 192.168.2.102 login success" was listed after 
I switched to manual 192.168.2.102 instead of DHCP.


-- 
Groeten uit Gent,

   Kris

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

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)

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=