Message-ID: <3F28B955.3050405@2rosenthals.com>
Organization: Rosenthal & Rosenthal
User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.4; MultiZilla v1.4.0.4A) Gecko/20030622
MIME-Version: 1.0
References: <auto-000175436123@admin.nni.com>
In-Reply-To: <auto-000175436123@admin.nni.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Date: Thu, 31 Jul 2003 02:38:20 EST5EDT4,M4.1,M10.5
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: OS/2 Wireless Users List: Still Don't Get It.

Wow, Stan, that sure was a mouthful...!

Okay, only a few things, as my brain is pretty fried at this point. I 
think Jonas, Jens, or Oliver can pretty much cover the specifics of the 
driver issues you've uncovered (great beta report, btw).

See below...

Stanley Sidlov wrote:

>I have to say, I don't have this problem in WinXP. This is a TP23, newly minted by IBM.
>
>I am using the Latest Dani Drivers with the PCCard Support, and I had/have the PCCard Director 
>installed (4.22). When I was using the IBM drivers, the WiFi could turn off the Card's radio, now, it 
>says it did but the card's led keeps blinking. Are there any IBM drivers for the PCCard Director that 
>should not be used with the DANI drivers? I am using the suggested settings in the DANI documentation. 
>  
>
I think you just need to have four components from the PC Card Director 
package:

    * IBM2SS14.SYS
    * PCMCIA.SYS
    * AUTODRV2.SYS
    * $ICPMOS2.SYS

And add VPCMCIA.SYS for DOS sessions which need to see the card. Also, 
the IBM2SS14.SYS should be the latest one from SWC or eCS. The others 
can be from the earlier released packages (IIRC; I think Oliver made a 
mention of some of the newer packages actually downleveling things other 
than IBM2SS14.SYS).

What does your DANI line look like, at this point?

>I have a SMC2655W Access Point. The only time that I can connect to the card is when I set WiFi Stat 
>to ADHOC which is NOT the way it is setup. I am using a card specific driver which I'm not supposed to 
>discuss, but I see that the IBM Prism NIF file is nearly identical except for the manufacturer's id's 
>and using "MIB" for the default SSID.
>
>I don't know if on the AP the key is shared or open which is configurable in the NIF, it appears to 
>work either way, that is I connect to 'something' -- XP doesn't show any other networks but mine when 
>it is connected, at least none that have a visible SSID. 
>
>I know what the network SSID is, and in the Wifi profile it is configured correctly, but when the card 
>does connect it never ever shows the SSID, but it shows:
>
>Connected to IBSS
>SSID: non-spec @ 2 or sometimes 11 Mbs
>
>Now, this is sort of strange since it won't connect when BSS is the choice, yet, it finds a BSS when 
>ADHOC. I have yet to see the Green Bar showing signal strength, and the AP is about a foot away with 
>the attennae horizontal. This gives a 100% signal strength in WinXP. 
>
This all seems very odd. Did it behave like this using the IBM drivers 
which you mentioned earlier?

>Also, DHCP is unable to obtain a lease after shutting down Lan0.
>
You mean:

ifconfig lan0 down
route -fh
arp -f
ifconfig lan0 up
dhcpstrt -i lan0

doesn't obtain an address?

> [Again, Lan0 would be the first NIC 
>in the MPTS? and LAN1 would be the second. Right?**]
>
You are correct, sir. lan0 is the NIC listed in the leftmost position 
for the TCPIP binding. The one which follows the first comma (if 
present) is lan1, etc.

>  I assume that the card would not say "Connected" 
>if it was unable to communicate with the AP,
>
Not getting an IP does not mean that it isn;t communicating with the AP. 
This is akin to getting a link light on a wired NIC.

> but again, I expected that it would say the SSID of the 
>network in the WiFi profile when it did.  
>
I believe (and someone please jump in and clarify this if I'm too far 
gone to be opening my mouth this late) that if the AP is configured to 
not broadcast its SSID, you will not see it even if the card is able to 
connect as "ANY". However, as my setup has never connected with SSID 
broadcast turned off, I can't confirm this.

[snip...]

>Here's one that I don't find consistent:
>
>[IRQ]
>Display = "IRQ Number"
>Type = Decimal
>Set = 3, 4, 5, 7, 9, 10, 11, 12, 14, 15
>Optional = YES
>Editable = YES
>Help= "You can specify an IRQ number to be used with this module."
>
>
>SO HOW do you specify the IRQ? Is it on the driver for the PCMCIA card? the NIF? Does this require a 
>DEFAULT = statement aka DEFAULT = 10?  I would like to change the IRQ it interferes with a Modem card. 
>
If you set the card to IRQ 10 in PROTOCOL.INI, the driver should then 
initialize the card there (assuming the resource is available). In this 
way, PROTOCOL.INI functions as a .cfg for the device driver.

>And this one brings up questions, like what MAC does it show without a default? 
>
The one burned into the card.

>Or if you use MAC 
>Address as part of your security, do you have to put the MAC address in?
>
No, as long as the security you have in place is set to the card's 
burned-in MAC address. The entry in PROTOCOL.INI is an override.

> (I turned this off in the AP 
>so that I could try to get this card configured without additional problems.)
>
Good idea.

>Questions, questions. I need some guidance, and answers.  
>
I think you came to the right place. Sorry I haven't been able to shed a 
brighter light on these tonight.

>** MPTS question, you can't have two networks setup for DHCP, but the command line net start commands 
>will overide this.
>
How do you mean? Under OS/2, only one adapter can ever be enabled for 
DHCP. You can switch to another one, but only one adapter at any given 
moment may be configured using DHCP.

> What does everyone else use for the information in the Wireless or '2nd' NIC? 
>1.1.1.1 as the manual address? Blanks? 
>
If the interface is brought down, then nothing. If you just mean as a 
placeholder while the NIC is down, then any valid construct can go here 
(obviously, 255.255.255.255 would probably cause MPTS to issue you an 
error message about an invalid address). If you configure your stuff 
manually, then you should be able to leave this entitrely blank when you 
have the NIC toggled down. Did I miss your point?

-- 
Lewis
---------------------------------------------------------------------
Lewis G Rosenthal, CNA
Rosenthal & Rosenthal            :  Accountants / Network Consultants
New York / Northern Virginia     :                www.2rosenthals.com
Novell Users International       :                 www.whytheylie.com
OS/2's new face is eComStation   :                www.ecomstation.com
--------------------------------------------------------------------- 
This OS/2 system (Apollo) uptime is 0 days 04:39 hours and 02 seconds


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

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).

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=