From: "Michael Warmuth" Received: from mxout4.mailhop.org ([63.208.196.168] verified) by 2rosenthals.com (CommuniGate Pro SMTP 5.0.9) with ESMTP id 192420 for os2-wireless_users@2rosenthals.com; Tue, 27 Jun 2006 03:56:53 -0400 Received: from mxin1.mailhop.org ([63.208.196.175]) by mxout4.mailhop.org with esmtp (Exim 4.51) id 1Fv8RH-000Ez9-VN for os2-wireless_users@2rosenthals.com; Tue, 27 Jun 2006 03:56:52 -0400 Received: from mail01.etel.at ([194.152.104.3]) by mxin1.mailhop.org with esmtp (Exim 4.51) id 1Fv8RH-000Jj1-Fm for os2-wireless_users@2rosenthals.com; Tue, 27 Jun 2006 03:56:51 -0400 Received: from warmuth.at (85-90-130-88.DSL.ycn.com [85.90.130.88] (may be forged)) by mail01.etel.at (8.13.5.20060308/8.13.5) with SMTP id k5R7ujPJ020403 for ; Tue, 27 Jun 2006 09:56:45 +0200 Received: from [10.1.1.40] (localhost.warmuth.at [127.0.0.1]) by warmuth.at (Weasel v1.76) for ; 27 Jun 2006 09:41:38 Message-ID: <44A0E131.1080209@warmuth.at> Date: Tue, 27 Jun 2006 09:41:37 +0200 Organization: Michael Warmuth - EDV-Dienstleistungen User-Agent: PmW-Tb 1.5.0.4 (OS/2/20060518) MIME-Version: 1.0 To: OS/2 Wireless Users Mailing List Subject: Re: xwlan 2.14 References: In-Reply-To: X-Enigmail-Version: 0.94.0.0 OpenPGP: url=http://www.warmuth.at/certs/michael@warmuth.at_pub.asc Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: ok; using Norman AV 5.90.21, version 5.90.00 of 2006/06/26 02:02:34 X-Mail-Handler: MailHop by DynDNS X-Spam-Score: -2.5 (--) Dear Lewis, Lewis G Rosenthal wrote: [...] > Per your second point, Michael, how do you propose setting the host ID > correctly such that a single address is associated with it? In my > experience, having two non-teamed NICs connected to the same subnet has > resulted in a tons of dropped packets and overall poor communication, > aside from the probable packet storm from other clients trying to reach > one interface and hitting the other. As I said in my first post: They are never connected at the same time - they are just configured (until XWLAN is running). First the LAN interface - it get's is configuration using DHCP (and if it does not get a lease it is configured statically). Then the WLAN interface (statically): as the LAN interface has set the hostid and the route to the subnet everything works - even starting the requester. When I later switch from LAN to WLAN interface I pull out the LAN cable, and turn on WLAN using XWLAN. Then the requester still works - even a domain logon. (TCPBEUI is configured for both interfaces) All other solutions I tried do not work or not fully work (e.g. I can connect to a specific server, even the domain controller, but I cannot log on to the domain). And no the requester does not start when both interfaces are bound to TCPBEUI and one is not configured. [...] > From the Help file: > > This script is executed after the TCP/IP interface has been either > configured or unconfigured. > > I use XWLAN 2.14 and when I turn on the WLAN it does: 1) Turns on the card 2) Searchs for a WLAN 3) Connects to the WLAN 4) Does run xwlan.cmd 5) Configures the IP interface Greetings Michael -- Michael Warmuth, Manager IT, michael@warmuth.at Michael Warmuth - EDV-Dienstleistungen, www.warmuth.at Waldegghofgasse 27, A-1170 Wien, Austria - EUROPE Tel: +43-676-3863440, Fax: +43-1-4892728-99 Austria -- The place in the heart of Europe where no kangaroos are hopping around.