From: Received: from mxout2.mailhop.org ([63.208.196.166] verified) by 2rosenthals.com (CommuniGate Pro SMTP 5.1.3) with ESMTP id 875864 for os2-wireless_users@2rosenthals.com; Tue, 13 Feb 2007 15:46:39 -0500 Received: from mxin2.mailhop.org ([63.208.196.176]) by mxout2.mailhop.org with esmtp (Exim 4.63) (envelope-from ) id 1HH4Xp-0005Up-KY for os2-wireless_users@2rosenthals.com; Tue, 13 Feb 2007 15:46:36 -0500 Received: from www8.cruzio.com ([63.249.95.19]) by mxin2.mailhop.org with esmtp (Exim 4.63) (envelope-from ) id 1HH4Xp-0009iJ-BB for os2-wireless_users@2rosenthals.com; Tue, 13 Feb 2007 15:46:33 -0500 Received: from eisenpress.com (localhost.cruzio.com [127.0.0.1]) by www8.cruzio.com with ESMTP id l1DKkVWB041324; Tue, 13 Feb 2007 12:46:31 -0800 (PST) To: "OS/2 Wireless Users Mailing List" Subject: Re: [OS2Wireless]Wireless LAN Mon3, Genmac 2 and Injoy Firewalls wrapper, xWlan detecting wrong lan Date: Tue, 13 Feb 2007 15:46:31 -0500 Message-Id: <20070213203520.M94515@eisenpress.com> In-Reply-To: References: X-Mailer: Open WebMail 2.51 20050317 X-OriginatingIP: 209.216.79.101 (afecu) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Mail-Handler: MailHop by DynDNS X-Originating-IP: 63.249.95.19 X-Spam-Score: 0.6 (/) On Tue, 13 Feb 2007 06:22:12 +0000, Chris Hodgkins wrote > Hi Gents, > > Is there anyway in XWorkplace Wireless LAN Mon3 widget to tell it which > lan interface to use? I have a similar problem (I think) with the standalone XWLAN monitor - in some cases when I insert the wireless card, the interface that XWLAN tries to set up isn't the same one that is defined to TCP/IP. One case is when I have both the wired and wireless interfaces defined in procotol.ini, but the wired PCCARD is not installed when I boot (it's not built-in on my laptop). Thus there's no LAN0 there; when I insert the wireless card it's assigned LAN0, but XWLAN then tries to set it up as LAN1 (I think because it's the second interface defined in protocol.ini). This also prevents me from defining more than one wireless card in protocol.ini as the second one ends up as LAN2 but TCP/IP sets it up as LAN1 (assuming LAN0 does get set up). Maybe this is a bug, though, since shouldn't XWLAN be able to tell which interface the card has been assigned? Thanks, Aron P.S. Has anyone else found that the drivers for the IBM High Rate Wireless Card (both ibmwifi2 and genprism) seem unable to get the MAC address if the card is inserted after bootup? I never had this problem with the Cisco 350 (which I don't have with me right now since I needed support for WEP), and it had me practically tearing my hair out until I figured that out.