| ???: |
"Neil Waldhauer" <os2-wireless_users@2rosenthals.com> |
?? ????
????????? |
| ???: |
os2-wireless_users-owner <os2-wireless_users-owner@2rosenthals.com> |
| ??: |
[OS2Wireless] Wireless LAN Monitor |
| ??: |
Thu, 25 Nov 2004 12:23:52 -0800 |
| ??: |
os2-wireless_users@2rosenthals.com |
|
|---|
First, thanks for the information about how to tell what interface is my
wireless card. In my case, it is LAN 1.
I have things working perfectly with my scripts, as Stuart Updike recommended.
I have posted these scripts here many times before, and they are also the
scripts on Jonas Buys website.
But I was hoping that the XWLAN could operate my wireless card without the
scripts. I have the situation, which I doubt is unusual, of having a notebook
computer with a wired lan built in, and a wireless card.
>From what you say, I should now be able to ignore my scripts, and when I plug
in my wireless card, it should just connect.
OK, that is just what it does. That is cool. I needed to have properties:
Radio: Activate radio on startup. Also I needed to have TCP/IP: LAN 1
But I still can't figure out how to switch from wireless back to wired. There
are some things missing. But my scripts do not always work for this, either.
Ideally, when the card is inserted, the computer activates LAN1 and deactivates
LAN0, and when the card is ejected, the comptuer activates LAN0 and deactivates
LAN1.
But I do now have it working without my scripts for the simplest case. Start
the computer with a wire, it uses LAN0. Start the computer with nothing, and
plug in the wireless card, then it uses LAN1.
Neil
On Thu, 25 Nov 2004 18:47:50 +0100, Christian Langanke <cla@clanganke.de> wrote:
> Neil Waldhauer wrote:
>
> >On Thu, 25 Nov 2004 09:44:27 -0600, Stuart Updike <stuupdike@mindspring.com>
> >wrote:
> >
> >
> >
> >>I would think you could still use your scripts to change to the wireless
> >>card, in which case you should set XWLAN to lan1. That is essentially
> >>what I've been doing with my T21.
> >>
> >>
> >
> >You are right. If I continue to use my scripts, then networking continues as
> >normal. But I had hoped that my scripts functionality would have been included
> >in the new XWLAN.
> >
> >XWLAN calls scripts on "disconnect" and "connect". Are these events when the
> >card is inserted and ejected? Can I call my scripts from XWLAN?
> >
> >Neil
> >
> >
> Hmm, I do not remember what your scripts are doing, and I think you
> should not be require to use scripts to configure the lan interface of
> the TCP/IP interface of your Wireless LAN device (also not the script
> solution that XWLAN offers) - I think we discussed that once. If you
> have a cabled interface on your notebook as well, this should not
> disturb, unless you don't configure it. In any case it is highly
> recommended to notconfigure the TCP/IP interface within the TCP/IP
> configuration program.
>
> In order to find out which TCP/IP lan interface is boud to your Wireless
> LAN device, just open MPTS and check the adapter number left to the
> entry "TCP/IP" protocol underneath the driver for your Wireless LAN
> device. When you then select this interface in the TCP/IP properties
> page, XWLAN should be able to configure this interface. But after having
> made that change, nothing happens, until you take further action.
>
> Taken that you are in range of the hotspot that the selected access
> point would match to, you would reconfigure (in this case reissue the
> DHCP request) by selecting "TCP/IP interface - (re)configure..
>
> Instead, in order to connect to any hotspot, select the menu item
> "Public hotspot". This will automatically launch a DHCP request. Only
> when this returns successfully, the IP interface is being configured
> (not by XWLAN, but rather by the DHCP client daemon), and only after
> _that_ has succeded, XWLAN will call its script (once you have
> configured that) for the connect event. So the script events connect and
> disconnect are not to configure or unconfigure the LAN interface of the
> Wireless LAN device, instead they are called when the configuration has
> succeeded or the IP interface was unconfigured.
>
> After having connected to a public hotspot, you then may want to create
> a dedicated connection profile out of the connection, just by selection
> the appropriate menu item within the hotspot menu.
>
> Please let me know it it works.
>
> bye, 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)
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
--
Neil Waldhauer, neil@blondeguy.com
The greater the task to be done, the more insignificant the work which must precede it.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
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)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
|