X-Account-Key: account1 X-UIDL: 30342 X-Mozilla-Keys: Return-Path: os2-wireless_users-owner@2rosenthals.com Received: from 192.168.100.5 (hawking [192.168.100.5]) by 2rosenthals.com (Hethmon Brothers Smtpd) id 20041026143544-10208-7 ; Tue, 26 Oct 2004 14:35:44 -0400 (Hethmon Brothers Smtpd) id 20041026143543-35033-7 ; Tue, 26 Oct 2004 14:35:43 -0400 Received: from mx1.mailhop.org ([63.208.196.170]) by mxout-1.mailhop.org with esmtp (Exim 4.34) id 1CMWAi-0008XA-5g for os2-wireless_users@2rosenthals.com; Tue, 26 Oct 2004 14:35:56 -0400 Received: from waldorf.webpack.hosteurope.de ([217.115.142.71]) by mx1.mailhop.org with esmtp (Exim 4.42) id 1CMWAg-000Enp-Du for os2-wireless_users@2rosenthals.com; Tue, 26 Oct 2004 14:35:50 -0400 Received: from p5084b405.dip0.t-ipconnect.de ([80.132.180.5] helo=clanganke.de) by waldorf.webpack.hosteurope.de with asmtp (TLSv1:RC4-MD5:128) (Exim 4.34) id 1CMWAR-0004WR-R6 for os2-wireless_users@2rosenthals.com; Tue, 26 Oct 2004 20:35:36 +0200 Message-ID: <417E9902.5010906@clanganke.de> User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.4a) Gecko/20030401 X-Accept-Language: en MIME-Version: 1.0 References: <417D11B4.2000903@verizon.net> In-Reply-To: <417D11B4.2000903@verizon.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-HE-MXrcvd: no X-Mail-Handler: MailHop by DynDNS.org X-Spam-Score: -4.6 (----) Date: Tue, 26 Oct 2004 20:35:46 +0200 Sender: os2-wireless_users-owner X-Listname: os2-wireless_users@2rosenthals.com Reply-To: os2-wireless_users@2rosenthals.com From: Christian Langanke To: os2-wireless_users@2rosenthals.com Subject: [OS2Wireless] [Fwd: [Fwd: Re: eCS 1.2/DSL]] X-List-Unsubscribe: Send email to mailusers-request@2rosenthals.com X-List-Owner: mailusers-owner@2rosenthals.com Marcus H. Russell, P.E., L.S. wrote: > > > -------- Original Message -------- > Subject: [Fwd: Re: eCS 1.2/DSL] > Date: Mon, 25 Oct 2004 09:29:10 -0400 > From: Marcus H. Russell, P.E., L.S. > Reply-To: markrussell1@verizon.net > Organization: Russell & Associates > To: steward@mail.2rosenthals.com > > > > Please find my correspondence with Mensys that got me no help. Has > any body figured out how to get a eCS system to talk, via wireless > routers, to router connected to a DSL line? Mark Hi Mark, >>> Here is what I did. Installed a Belkin NIC, which eCS 1.2 >>> recognized when I installed 1.2. BTW, 1.2 install was a breeze. I >>> bought a Linksys Wireless-B Broadband Router and connected it to the >>> Belkin NIC. DHCP is apparently loading at boot because there is a >>> long delay before boot finishes. Now what? How do I get eCS router >>> to talk to the Linksys Wireless-G router that is connected to the >>> DSL line, which is connected to the Lindows PC being used to write >>> this? I feel that I am almost there but don't know how to open the >>> door. And yes I read so much that I am more confused than ever!! Mark >>> >> You write about a Wirlesss-B router, a Wireless-G router (can the second be a mistyping?), an eCS router (I bet you are talking about the eCS system in general) and a Lindows PC. Hmm. I suppose that the Linksys device is the gateway to the internet (via DSL). I also assume that this device is able to play DHCP server. Before this can work, you obviously have to configure your Linksys router, this is what Roderick wanted to tell you. So I would try the following - find out to which IP address/netmask your Linksys router is configured by default. This may _for example_ be 192.168.0.1 and 255.255.255.0. This information must be provided somewhere in the manual, look for factory defaults or alike. - now set the IP interface of the Nelkin nic to an IP address of the same IP subsegment. A good way to do this is to use the same netmask and an IP address being identical up to the third byte, but being one higher in the fourth byte. Following to the example above you would configure it to 192.168.0.2 and netmask 255.255.255.0. You do that with the following command on the commandline: ifconfig lan0 192.168.0.2 255.255.255.0 given that lan0 is the correct interface name (if the Belkin NIC is the only adapter that you bound the TCP/IP protocol to, it _is_ lan0). - now ping the address of the router - in our example: 192.168.0.1 (make sure the cable is still plugged ;-) ) - if that succeeds, start mozilla and enter as URL: http://192.168.0.1 Here I assume that the complete device can be configured via HTTP... In that configuration you need to enable the DHCP service. After that you can use DHCP for the (cabled) network adapters of the Lindows and the eCS system. Moreover, you will need to tell the Linksys device all paramaters for the DSL-dialin hpe that helps, Christian ------------------------------------------------- Christian Langanke COS2E & CWSE Team OS/2 Ruhr e.V. cla@clanganke.de =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 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) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=