Message-ID: <436FAAA3.2030306@clanganke.de>
User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.7.10) Gecko/20050726
MIME-Version: 1.0
References: <200511071448.jA7Em6lt002275@sputnik.hautspot.com>	 <7234a03c0511070735s3f7ffb08y252692993cd18ab@mail.gmail.com>	 <436F793C.1070604@ptdprolog.net> <7234a03c0511070826x1fb21a79l2de115b7adfc2516@mail.gmail.com>
In-Reply-To: <7234a03c0511070826x1fb21a79l2de115b7adfc2516@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Date:  Mon, 07 Nov 2005 20:27:31 +0100
Sender: os2-wireless_users-owner <os2-wireless_users-owner@2rosenthals.com>
Reply-To: os2-wireless_users@2rosenthals.com
From:  Christian Langanke <os2-wireless_users@2rosenthals.com>
To:  os2-wireless_users@2rosenthals.com
Subject: [OS2Wireless] XWLAN Binding Problem (Was: Problem with new XWLan 2.0 (Oh and BTW, GenMac 1.0 is out))

Jeroen, Mark,

thank you for your postings. For this problem I'll write to this list 
instead of the gmane lsit unless the problem is solved.

Jeroen Besse wrote:

>>I tried replying to your post on the wlan forum but neither Pronews or web
>>interface seem to work for me.  Is there a TCP/IP page in your xWlan properties
>>notebook?  There is none here.
>>    
>>
Sure. V2.00 does not have it any more. It is not longer necessary (as 
long as everything works well).

>
>In 1.2 there was a page on which you could bind the wlan application
>to a netx interface. 
>
So far, so wrong. The property to specify the IP interface on that 
properties page did not bind any IP interface to your card. Instead only 
MPTS does so, and no other piece of software. XWLAN V1.2, unlike the new 
version, was not able to determine the IP interface bound to your WLAN 
device, so you had to specify it - according to the MPTS binding.

>This is removed in 2.0. However, I think that the
>problem is somewhere there... 
>
Yes, obviously. I am very confident that XWLAN V2.00 well determines the 
correct IP interface correctly. The fact that TCP/IP is disabled, does 
not mean that XWLAN uses the wrong one. It just states that it cannot be 
configured (due to whatwever reason).

>I'll try to remove my net1 (wired
>ethernet) from mpts, to see whether that fixes it. I already tried to
>swith places between the wired and wireless interface, but that didn't
>resolve it. I hope to come back on this tonight (CET).
>  
>
Unfortunately I cannot reproduce the error. When I go back to V1.2 and 
forth again to V2.00, everything works fine.

To compare the properties between V1.2 and V2.0, launch an ini editor 
and check:

V1.2
Application: "Wireless LAN Monitor:Properties"
Keys: "IPInterface_<drivername>"  (e.g. "IPInterface_CWL350$")
Value: nummeric string from 0 to 7 specifying lan0 to lan7

V2.0:
Application: "Wireless LAN Monitor:Bindings"
Keys: "<drivername>" (e.g. "CWL350$")
Value: nummeric string from 0 to 7 specifying lan0 to lan7

Note that the V1.2 setting is not longer used with V2.0. If your system 
does not carry the V2.0 setting, please let me know - then the automated 
determination of the binding failed.

thanx, Christian

-------------------------------------------------

Christian Langanke
COS2E & CWSE
Team OS/2 Ruhr e.V.
cla@clanganke.de





=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

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)

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=