[OS2Wireless] XWLAN Bugfix Release V1.11 for DHCP problems
Date:
Sat, 11 Dec 2004 21:24:11 -0800
To:
os2-wireless_users@2rosenthals.com
I have finally found time and a machine to try XWLAN v1.11, and this is how it
worked.
wired = LAN0, dhcp, configured in setup.cmd
wireless = LAN1, dhcp, not configured in setup.cmd
I have two wireless cards, an Ambicom, and a Cisco 350.
For my Ambicom card, I can be in a wired mode, and slip in the PC Card, and it
switches to wireless. I have to configure XWLAN to use lan1, and I seemed to
have to make a profile with my SSID. I'm not completely certain about that. See
below.
When I eject the card, I still need to issue a DHCPSTRT -i LAN0 command.
Everything else is handled by XWLAN.
I made my new Cisco 350 card LAN2, and I select that in XWLAN, and my SSID, and
nothing happens. It does not recognise the card. My script is similarly
useless. I have no idea why this doesn't work. I have two wireless cards, and I
should be able to support both of them, one as LAN1 and one as LAN2. In MPTS, I
should just be able to add both adapters, each with only TCP/IP, and it ought
to work.
I made the Cisco 350 LAN1, and now XWLAN works just fine for that, too. I still
have to issue DHCPSTRT -i LAN0 when I eject the card.
I've edited c:\ecs\system\ewps\plugins\xcenter\xwlan\script\xwlan.cmd to do the
dhcpstrt command, and now it seems to be as automatic as I wanted.
I deleted my profile that names my SSID, and just made a blank profile. It now
connects to my access point with no problems.
I'll try taking this to a public hotspot for a test later.
Neil
On Tue, 30 Nov 2004 01:03:54 +0100, Christian Langanke <cla@clanganke.de> wrote:
> Please be so kind and post back your experiences (especially Neil) as an
> answer to this mail (keep the subject please).
>
> thanx, Christian
>
> P.S.: @Neil: I reread the part on your scripts, deactivation lan0 or
> lan1 depending on what you are using. I just want to say that the TCP/IP
> interface of the Wireless LAN card is always activated or deactivated by
> XWLAN where appropriate, so your scripts will at least not have any
> impact on that interface when executed before connecting/disconnecting.
>
> PP.S.:Concerning the wired interface, there has been a suggestion to let
> XWLAN as well configure that (by DHCP) if XWLAN did not detect any
> wireless device (this would be a workaround for the fact that to my
> knowledge no piece of OS/2 software can currently detect or be notified
> if a network cable is plugged or unplugged, so XWLAN would make a
> guess). Does that make sense to everybody ? (I am not sure...)
>
> -------------------------------------------------
>
> Free utilities for OS/2 and eComStation at
> -> http://www.clanganke.de/os2
>
> Christian Langanke
> COS2E & CWSE
> Team OS/2 Ruhr e.V., Germany
> cla@clanganke.de
--
Neil Waldhauer, neil@blondeguy.com
Remove clothes to reply
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
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)
back to list