X-Account-Key: account1 X-UIDL: 126187 X-Mozilla-Keys: Return-Path: X-ListServer: CommuniGate Pro LIST 5.1.3 List-Unsubscribe: List-ID: List-Archive: Precedence: list Message-ID: Reply-To: "OS/2 Wireless Users Mailing List" Sender: "OS/2 Wireless Users Mailing List" To: "OS/2 Wireless Users Mailing List" From: "Al Heath" Date: Thu, 4 Oct 2007 15:28:53 -0500 X-Original-Message-ID: MIME-Version: 1.0 Content-type: multipart/alternative; Boundary="0__=09BBF9F9DFFDAC838f9e8a93df938690918c09BBF9F9DFFDAC83" Subject: Re: [OS2Wireless] LinkSys WRT54G bridge help? --0__=09BBF9F9DFFDAC838f9e8a93df938690918c09BBF9F9DFFDAC83 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: quoted-printable > From Mike Luther's post >> But what isn't often realized, for folks who are using startup >> DCHP addressing for the LAN, is that you have to be connected >> to SOMETHING which will give you a discrete private address for >> the LAN you want to use with Seamonkey BEFORE you can connect >> to the router or the bridge! One thing that is handy to remember about OS/2 is that it is very easy = to open up a command line window and temporarily give yourself a fixed IP address on the subnet you want without messing up your boot up DHCP configuration, or going thru the TCP/IP configuration panels, etc... Simply release any DHCP address you previously were assigned, stop the monitor and issue some commands to flush things and assign a new IP add= ress for while you are configuring the local hardware boxes... for example, = on a 192.168.1.x network on a typical wired port (lan0): route -fh arp -f ifconfig lan0 192.168.1.99 netmask 255.255.255.0 (Naturally, you could have an address conflict with other devices if th= e host value you picked (99 in this example) was already in use (so you p= ick another one...), but typically you might be only trying to change the settings on a wireless bridge and only need to address the bridge.... o= r on a router as the only device on that subnet. i.e. all 'setup' type of things you only do once in a while.... To switch addresses again, you can always do a 'ifconfig lan0 delete' a= nd flush and do again.... and optionally if you want to route things past this subnet and you do = have a router on the subnet ... assuming your router is at 192.168.1.1 route add default 192.168.1.1 -hopcount 1 and you can test further connectivity... and IF you really want, you can always edit the \mptn\etc "resolv2" to = put in a DNS address or even point it to your router (assuming it has a DNS= forwarder like most home routers do...) such as "nameserver 192.168.1.1= " etc... Thus you don't necessarily need to "get an address from a compatible DHCP server and unplug cables and jam...." as suggested: >> you jam the connection cable from the WET54G wireless bridge into th= e >> LAN port you just vacated on your Thinkpad or whatever. You do *NOT= * mess >> with DCHP and trying to fuss with your 'connection' to your LAN. Despite the >> fact that your DCHP connection is broken by this act .... Al H= --0__=09BBF9F9DFFDAC838f9e8a93df938690918c09BBF9F9DFFDAC83 Content-type: text/html; charset=US-ASCII Content-Disposition: inline Content-transfer-encoding: quoted-printable

> From Mike Luther's post
>> But what isn't often realized, for folks who are usi= ng startup
>> DCHP addressing for the LAN, is that you have to be connec= ted
>> to SOMETHING which will give you a discrete private addres= s for
>> the LAN you want to use with Seamonkey BEFORE you can conn= ect
>> to the router or the bridge!

One thing that is handy to remember about OS/2 is that it is very e= asy to open up a command line window and temporarily give yourself a fi= xed IP address on the subnet you want without messing up your boot up D= HCP configuration, or going thru the TCP/IP configuration panels, etc..= . Simply release any DHCP address you previously were assigned, s= top the monitor and issue some commands to flush things and assign a ne= w IP address for while you are configuring the local hardware boxes... = for example, on a 192.168.1.x network on a typical wired port (lan0): route -fh arp -f ifconfig lan0 192.168.1.99 netmask 255.255.255.0 (Naturally, you could have an address conflict with other devices i= f the host value you picked (99 in this example) was already in use (so= you pick another one...), but typically you might be only trying to ch= ange the settings on a wireless bridge and only need to addres= s the bridge.... or on a router as the only device on that sub= net. i.e. all 'setup' type of things you only do once in a while.= ... To switch addresses again, you can always do a 'ifconfig lan0 delet= e' and flush and do again.... and optionally if you want to route things past this subnet and you= do have a router on the subnet ... assuming your router is at 192.168.= 1.1 route add default 192.168.1.1 -hopcount 1 and you can test further connectivity... and IF you really want, you can always edit the \mptn\etc "res= olv2" to put in a DNS address or even point it to your router (ass= uming it has a DNS forwarder like most home routers do...) such as &quo= t;nameserver 192.168.1.1" etc... Thus you don't necessarily need to "get an addres= s from a compatible DHCP server and unplug cables and jam...." as = suggested: >> you jam the connection cable from the WET54G wire= less bridge into the >> LAN port you just vacated on your Thinkpad or whatever. = You do *NOT* mess >> with DCHP and trying to fuss with your 'connection' to your LA= N. Despite the >> fact that your DCHP connection is broken by this act ....= Al H= --0__=09BBF9F9DFFDAC838f9e8a93df938690918c09BBF9F9DFFDAC83--