On Mar 31, 9:52 am, "yawnmoth" <terra1...@yahoo.com> wrote:
> i'm considering buying a wireless to wired network bridge (WET54G) and
> am not really sure how it'd work. say you're wireless network is
> using WEP or WPA. how do you tell the bridge that?
>
> the user guide (page 22) suggests that the WET54G has a web interface
> (presumably for this very reason).

YES


the default ip address to this web
> interface is 192.168.1.226. what happens, however, if your network
> configuration uses ip addresses of the form 10.*.*.*? i assume
> 192.168.1.226 wouldn't work, at that point.
>

You can change the bridge's address to whatever you want once you are
in the interface.


> ...or what if the ip addresses that are assigned by the router aren't
> internal - what if they're directly route-able to the internet? eg.
> what if, when i plug two computers into a hub that's plugged into the
> WET54G's lone ethernet port, i'm supposed to get two IP addresses that
> the outside world can see? 192.168.1.226 obviously wouldn't work,
> then...

The address of the actual bridge is not the address the attached
computer(s) will use, though it does have to be in the same subnet.
If you don't give them static ip addresses, then they can get their
addresses by DHCP from the central router that the bridge is connected
to.

I don't know if you can actually run two computers through the bridge
or not.

By the way, the cheaper way to do this is to use a router that can be
set to serve as a client. The Buffalo WHR-G54S will do this and sells
for under $50. Many others (Like the Linksys WRT54GL) can also do
this if running aftermarket firmware like DD-WRT.

Items sold exclusively as client bridges cost more and do less.

Steve