X-Account-Key: account1 X-UIDL: 125552 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: Tue, 2 Oct 2007 10:55:33 -0500 X-Original-Message-ID: MIME-Version: 1.0 Content-type: multipart/alternative; Boundary="0__=09BBF9FBDFC661738f9e8a93df938690918c09BBF9FBDFC66173" Subject: Re: [OS2Wireless] LinkSys WRT54G bridge help? --0__=09BBF9FBDFC661738f9e8a93df938690918c09BBF9FBDFC66173 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: quoted-printable For what it is worth, I'd check to make sure that the local IP address assigned to your thinkpad(s) is in the subnet compatible with the local= bridge address. i.e. It would be possible for the bridge to be passin= g the DCHP address requests up the line and your thinkpad getting back an= address like 192.168.37.123 subnet 255.255.255.0 (or even a 172.x.x.x o= r 10.... and an appropriate subnet mask) and thus the direct addressing t= o the standalone wireless bridge at 192.168.1.x subnet would be incompati= ble. In which case, you could hard code your IP address back to the 192.168.= 1.x 255.255.255.0 subnet to allow you to connect locally to the bridge and change its settings ... such as putting it onto the subnet the DHCP ser= ver is providing, changing encryption keys, etc... then resetting your IP address back to getting a DHCP address and thus both your thinkpad(s) a= nd the bridge are on the same subnet and can be accessed at the same time.= I use a NetGear 101 bridge sometimes and have to do this occassionally = when I travel and need to change the wireless settings in the bridge for different hotels. Other times, it doesn't matter if I can't directly access the bridge as the traffic can flow across it anyway (providing t= he encryption, etc, settings are compatible.) Al H= --0__=09BBF9FBDFC661738f9e8a93df938690918c09BBF9FBDFC66173 Content-type: text/html; charset=US-ASCII Content-Disposition: inline Content-transfer-encoding: quoted-printable

For what it is worth, I'd check to make sure that the local IP addre= ss assigned to your thinkpad(s) is in the subnet compatible with the lo= cal bridge address. i.e. It would be possible for the bridge to be pa= ssing the DCHP address requests up the line and your thinkpad getting b= ack an address like 192.168.37.123 subnet 255.255.255.0 (or even a 172.= x.x.x or 10.... and an appropriate subnet mask) and thus the direct add= ressing to the standalone wireless bridge at 192.168.1.x subnet would b= e incompatible. In which case, you could hard code your IP address ba= ck to the 192.168.1.x 255.255.255.0 subnet to allow you to connect loca= lly to the bridge and change its settings ... such as putting it onto t= he subnet the DHCP server is providing, changing encryption keys, etc..= . then resetting your IP address back to getting a DHCP address and thu= s both your thinkpad(s) and the bridge are on the same subnet and can b= e accessed at the same time.

I use a NetGear 101 bridge sometimes and have to do this occassionally = when I travel and need to change the wireless settings in the bridge fo= r different hotels. Other times, it doesn't matter if I can't directly= access the bridge as the traffic can flow across it anyway (providing = the encryption, etc, settings are compatible.)

Al H= --0__=09BBF9FBDFC661738f9e8a93df938690918c09BBF9FBDFC66173--