Message-Id: <200305191914.0857794.6@mail1.bbfprinting.com>
In-Reply-To: <E19HnIy-0007LK-00@albatross.mail.pas.earthlink.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Date: Mon, 19 May 2003 19:15:03 EST5EDT4,M4.1,M10.5
Sender: os2-wireless_users-owner <os2-wireless_users-owner@2rosenthals.com>
Reply-To: os2-wireless_users@2rosenthals.com
From:  "BBF Tech. Support" <os2-wireless_users@2rosenthals.com>
To:  "os2-wireless_users@2rosenthals.com" <os2-wireless_users@2rosenthals.com>
Subject: OS/2 Wireless Users List: Success with built-in & wireless NICs!

congrats!
I know how it feels, I'll have to try it with out a reboot!




On Mon, 19 May 2003 12:19:34 EST5EDT4,M4.1,M10.5, Randy Fowler wrote:

>Keith & Neil,
>
>OK. I've been using the built-in NIC by itself in my ThinkPad T22 running MCP2 
>for some time, so it was already set up as the Intel Pro PCI adapter as 
>adapter# 0, with protocols OS/2 Netbios and TCP/IP.
>
>In preparation for the Cisco 350, I had to first add the OS/2 Card Services as 
>described in the Cisco 340 driver's readme.txt. Then using MPTS, I added the 
>Cisco 340 as adapter# 1, with protocol TCP/IP. 
>
>Previously assigned under TCP/IP config notebook: Lan0, the built-in NIC, has a 
>static IP address of 192.168.0.11   The IP address of my LinkSys Router at home 
>is 192.168.0.1, so I had also defined a default route to it.  Accordingly, 
>here's my setup.cmd file, which didn't change BTW after installing the 340:
>
>(this file is located in \mptn\bin; written by tcpip configuration notebook; 
>REM lines have been removed for readability)
>  
>---
>route -fh
>arp -f
>ifconfig lo 127.0.0.1
>ifconfig lan0 192.168.0.11 netmask 255.255.255.0 metric 1 mtu 1500
>route add default 192.168.0.1 -hopcount 1
>ipgate off
>---
>
>So when I boot, the built-in NIC gets configured with a hard IP address and a 
>default route to my home Router 192.168.0.1.  Whenever I go to the office, I 
>run the following cmd file to switch over to its Router at 192.168.0.99:
> 
>--- SetRoute-Work.cmd ---
>route delete default 192.168.0.1
>route add default 192.168.0.99 1
>ping 192.168.0.99 56 1
>pause
>
>
>Then when I return home, I run this cmd file to put things back:
>
>--- SetRoute-Home.cmd ---
>route delete default 192.168.0.99
>route add default 192.168.0.1 1
>ping 192.168.0.1 56 1
>pause
>
>
>I hardly ever boot my ThinkPads... I always Suspend them and they will 
>automatically do the ThinkPad Hibernation if I don't Resume within 90 mins.
>
>OK, now for switching over to use the wireless NIC.  First, here's what my 
>routing looks at home with my cat5 cable plugged in to the built-in NIC:
>
>---
>[C:\]netstat -r
>  destination             router                netmask     metric flags intrf
>
>default                192.168.0.1            0.0.0.0           1  UGSP   lan0
>127.0.0.1              127.0.0.1              255.255.255.255   0    UH     lo
>192.168                192.168.0.11           255.255.255.0     0    UC   lan0
>---
>
>Now, I unplug the cat5 and insert the Cisco 350.  Card Services plays a beep 
>and the lights come on.  Now, I have to delete the default route because it's 
>pointing to lan0 (which is now unplugged):
>
>route flush
>
>Now I have to delete lan0 entirely (just downing lan0 doesn't allow the new 
>default route to point to lan1).
>
>ifconfig lan0 delete
>
>I have my LinkSys router setup for a DHCP server, with IP address set for .100 
>and above.  I want the 350 to use DHCP, so I issue this command:
>
>dhcpstrt -i lan1
>
>After a few seconds, that command completes.  My routing now looks like this:
>
>---
>[C:\]netstat -r
>  destination             router                netmask     metric flags intrf
>
>default                192.168.0.1            0.0.0.0           0   UGP   lan1
>127.0.0.1              127.0.0.1              255.255.255.255   0    UH     lo
>192.168                192.168.0.101          255.255.255.0     0    UC   lan1
>---
>
>That's it... I'm now surfing using the LinkSys Access Point attached to my 
>LinkSys Router.
>
>Putting things back is pretty much the same.  Now I have to create some command 
>files to automate these steps.
>
>HTH,
>
>Randy Fowler
>Columbia, SC
>
>=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
>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).
>
>=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
>
>

Allan L. Stephan (Al)
Director ITS
BBF
Largo, FL
OS/2 loves ya baby!


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

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).

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=