Can't connect to Wi-Fi client bridge and Internet at the same time How Can I Fix This

In network terms, a bridge is transparent, passing data from each side to the other side (wireless to wired, wired to wireless). Thus in normal operation it doesn't have any use for IP addresses, just MAC addresses.

However, because of the need to manage Wi-Fi operation (SSID selection, WEP/WPA security, etc.), a Wi-Fi client bridge will typically have configuration screen(s) at a specified private IP address (e.g., 192.168.0.254) that can be accessed with a standard Web browser (e.g., Microsoft Internet Explorer) from a local computer. Unfortunately, unlike with a Wi-Fi router, a computer connected to a Wi-Fi client bridge can't normally communicate with both the client bridge configuration and the Internet at the same time.

How To Configure a Wi-Fi client bridge.

Problem: The NIC on a local computer needs a manually-assigned IP on the same subnet to connect to the client bridge config interface but then can't access the Internet, and when configured for DHCP through the client bridge can then talk to the Internet but not the client bridge.

Solutions:

Multihoming of the NIC (single link, multiple IP addresses)
For Microsoft Windows XP, see "Configuring Multiple IP Addresses on a Network Adapter" in Configuring IP Addressing and Name Resolution. Note: This only works with all manual addresses, not DHCP, which can be problematic when roaming unless managed with configuration manager software.

Two NICs in one computer, both connected to the client bridge:
one manually configured to talk to the client bridge config
the other with DHCP for the Internet.

Different computers for
client bridge config (manually configured)
Internet access (DHCP).

Connection manager software for rapid changing of NIC configuration profiles try theese.

Boingo Wi-Fi software (free)
Mobile Net Switch
NetSwitcher