Mailing List os2-wireless_users@2rosenthals.com Archived Message #2622 | back to list |
|
---|
Sorry for the extremely late reply, Kris. Your reply got buried in my folder...Of course I've been messing around meanwhile ....
--- 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).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.
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
(Add/Edit Profile | {Profile Name} | TCP/IP tab | More TCP/IP Options button).So, as I understand it now, setup.cmd only has to be used with/for wired connections. Right?
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.
Subscribe: Feed,
Digest,
Index. Unsubscribe Mail to ListMaster |