From: "Christian Langanke" Received: from mxout1.mailhop.org ([63.208.196.165] verified) by 2rosenthals.com (CommuniGate Pro SMTP 5.0.1) with ESMTP id 183438 for os2-wireless_users@2rosenthals.com; Sun, 25 Jun 2006 10:13:29 -0400 Received: from mxin2.mailhop.org ([63.208.196.176]) by mxout1.mailhop.org with esmtp (Exim 4.51) id 1FuVMY-000DPT-Kt for os2-wireless_users@2rosenthals.com; Sun, 25 Jun 2006 10:13:22 -0400 Received: from waldorf.webpack.hosteurope.de ([217.115.142.71]) by mxin2.mailhop.org with esmtp (Exim 4.51) id 1FuVMY-000PEP-BM for os2-wireless_users@2rosenthals.com; Sun, 25 Jun 2006 10:13:22 -0400 Received: by waldorf.webpack.hosteurope.de running Exim 4.51 using esmtpsa (TLSv1:RC4-MD5:128) from p5084aedc.dip0.t-ipconnect.de ([80.132.174.220] helo=[172.32.16.110]) id 1FuVMS-00067g-8L; Sun, 25 Jun 2006 16:13:16 +0200 Message-ID: <449E9A91.9070607@clanganke.de> Date: Sun, 25 Jun 2006 16:15:45 +0200 User-Agent: Thunderbird 1.5 (OS/2/20060113) MIME-Version: 1.0 To: OS/2 Wireless Users Mailing List Subject: Re: [OS2Wireless]xwlan 2.14 References: In-Reply-To: Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mail-Handler: MailHop by DynDNS X-Spam-Score: -2.6 (--) Hi Dave, Dave Saville wrote: > I upgraded to 2.14 because of the new bits for switching wired/wireless but it > seems worse than before, maybe 2.10. This is with the generic PRISM driver - > My Artem card is not supported by Genmac. > > I always assign a dummy IP to the unused NIC and do that in the xwlan.cmd file > > on CONNECT > > if WLan._Profilename = "Home" then do > 'ifconfig lan0 192.168.200.250'; > > on DISCONNECT > > if WLan._Profilename = "Home" then do > 'ifconfig lan1 192.168.201.251'; > > I would not do so. The best approach is to remove the obsolete interface. So setup.cmd should execute ifconfig for the wired interface and do nothing for the wireless interface. If then XWLAN connects to the same network IP range via wireless, it will disable the cabled interface (ifconfig delete). To switch back, it is best to execute "disable IP interface" in the XWLAN menu, this will delete the wireless interface. Then XWLAN shoul run setup.cmd and everything is fine. > Otherwise the NICs get addressed via DHCP. What seems to happen now is that, > say going wireless -> wired. The WIFI drops and the IP gets assigned as above > and then nothing. A netstat -r at this point will show only the local loopback, > & lan0 and 1 as above addresses. dhcpmon shows lan1 released. > > The only way to get things back is to manually find and kill DHCPD.EXE and then > run setup from x:/MPTN/bin. I have "Run setup" checked in the WIFI profile. > This is what I don't understand. setup.cmd should run. I just checked the code: setup.cmd is executed before the XWLAN script. I suggest you let setup.cmd write a flagfile ("type nul > C:\setupran.txt") an check if it was really executed. bye, Christian ------------------------------------------------- Christian Langanke, Christian ------------------------------------------------- Christian Langanke COS2E & CWSE Team OS/2 Ruhr e.V. cla@clanganke.de COS2E & CWSE Team OS/2 Ruhr e.V. cla@clanganke.de