Message-ID: <42ED6590.3010306@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.10) Gecko/20050726
MIME-Version: 1.0
References: <42D1A31D.9060702@2rosenthals.com> <42D1A744.7090106@2rosenthals.com> <42D24247.1060603@hccnet.nl> <42D422DE.6030408@2rosenthals.com> <42D45149.1050500@hccnet.nl> <42ED3F05.1010006@2rosenthals.com>
In-Reply-To: <42ED3F05.1010006@2rosenthals.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Date:  Mon, 01 Aug 2005 01:58:08 +0200
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] A cisco-350 weirdness



Lewis G Rosenthal schreef:

> Sorry for the extremely late reply, Kris. Your reply got buried in my 
> folder...
>
Of course I've been messing around meanwhile ....

>>>
>> wired intel nic = lan 0
>> jacarando = lan1
>> cisco350 = lan2
>>
>>> When you switch cards, I'm assuming you tell XWLAN to switch to the 
>>> other interface (LAN2, etc.).
>>>
>> Yep.
>>
>> Looks like I have to start from scrtach again.
>
--- and have restarted from scratch, moving the cisco350 to lan0 and got 
things working again. Meaning xlan works, wlanstat doesn0t work. But we 
can't have it all, can we? (otoh, when the jacarando card is selected 
xwlan and wlanstat work both properly).

> Not necessarily. This is sounding more and more like an arp or a 
> default route problem. Are you using DHCP? If so, try opening an OS/2 
> window and:
>
Now I am.

> arp -f <Enter>
> route -f <Enter>
>
> Then tell XWLAN to (re)configure the interface (when you have the 
> Cisco card installed).
>
> If you're not using DHCP, be sure that you have a default route entry 
> for the Cisco card configured in XWLAN

I had a default route for about 5 months and suddenly it didn't work 
anymore. Changed to DHCP and then the cisco worked again.

> (Add/Edit Profile | {Profile Name} | TCP/IP tab | More TCP/IP Options 
> button).
>
>> Now, supposing I'll rem out wired intel nic as well as the jacarando, 
>> how is the setup.cmd supposed to be? Or don't I need setup.cmd when 
>> using xwlan?
>>
> No need to fool with setup.cmd when using XWLAN.
>
>
So, as I understand it now, setup.cmd only has to be used with/for wired 
connections. Right?

btw: any news about the iNtel 2200 driver thinghy?

-- 
Groeten uit Gent,

   Kris

http://www.taartenbakkerij.com/bestanden/warpstock-europe-2005-dresden.jpg

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

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)

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=