kevin_standlee: (Kevin and Lisa)
kevin_standlee ([personal profile] kevin_standlee) wrote2011-08-31 09:00 pm
Entry tags:

So Much for Simple

We bought a Wireless bridge (specifically, a Cisco-Linksys WET200 Wireless-G Business Ethernet Bridge) for use in the trailer. From the way the product was documented, it appeared that you could use it to connect to a wireless network, then connect devices to it by Ethernet cable. The idea was that we could use that as the access point to the RV park wireless network, then connect it to the small network Lisa has wired within the trailer.

I can't make it work.

The first time I tried it was in the RV park, where I could easily connect the wireless on my laptop to the RV park's network. I then turned on the bridge and connected my laptop to it by Ethernet cable. (Even this took a bit of doing to find out how to configure my network settings, since the bridge is not a DHCP server and thus you have to manually set an IP address.) I could access the bridge's settings. I could tell the bridge to look for local wireless networks, and I could connect it to the RV park's network — the same one that I'd directly connected to from my laptop. But there it stops. Even though it says it's connected, it refuses to connect to any internet site.

I brought the thing back to Fremont and set it to talking with my home network. Even here, where I have complete control over all of the settings on the WAP as well as the bridge, I still can't reach out to the internet. I know it must be connecting to the WAP, because I can access the WAP's settings once it connects, but nothing in the outside world connects.

I'm afraid I don't have time for this. I'm sending it back for a refund. It would be much easier if we could make this work in the trailer (since we could actually run up external outside antennas to pick up the wi-fi, thus avoiding the connectivity problems of trying to use wi-fi inside of a metal box), but when you do everything the Cisco documentation (both paper supplied with the box and on their web site, for which I had to connect directly from my laptop rather than through the bridge) says to do and nothing happens, you get the impression that there's some expert-level setting that some super-duper network guru would say, "Oh, of course you need to make thus-and-such setting change that nobody ever writes down in the documentation because we already know how it works."

Considering that I'm pretty good with computers, situations like this really boil me. You shouldn't need a degree in electrical engineering to set up this sort of connection.

[identity profile] kalimac.livejournal.com 2011-09-01 04:37 am (UTC)(link)
Does any mysterious add-on gadget of this kind ever work? Not in my experience.

[identity profile] bovil.livejournal.com 2011-09-01 05:43 am (UTC)(link)
I'm running a previous generation of the device and it's worked beautifully for several years.

It may just be a bad model, or a lemon.

[identity profile] travelswithkuma.livejournal.com 2011-09-01 04:42 am (UTC)(link)
Grrrrrrrrrrrrrrrrrrrrrrrs ats nautys boxes

[identity profile] scott-sanford.livejournal.com 2011-09-01 04:58 am (UTC)(link)
This is not as bad as the time Linus Torvalds had to give up and admit he couldn't get a particular linux distribution to install and boot...but it's not good. The last time I configured something like this (a Linksys wifi hub) it was fairly quick & painless. I'm with you in blaming the box.

[identity profile] twilight2000.livejournal.com 2011-09-01 05:40 am (UTC)(link)
Man, given your experience with hardware *and* software, if *you* couldn't make it work, the rest of us are HOSED!
howeird: (Default)

[personal profile] howeird 2011-09-01 06:47 am (UTC)(link)
Methinks it needs to use the DHCP of whatever network it is getting its signal from.

[identity profile] dd-b.livejournal.com 2011-09-01 01:56 pm (UTC)(link)
Yes, that's the first thing I was suspicious about. If it doesn't do DHCP it also probably doesn't do NAT, and is in fact just a bridge, and in the end your IP must be configured by (or at least to fit within) the external network you're trying to connect to.

There may be a two-step shuffle involved -- maybe you have to connect to a default IP for the box to perform initial configuration? But after that revert to DHCP to get an IP from the network you're bridging from?

However, I've never worked with a wireless bridge box (I've implemented bridge code for ordinary router boxes, and was a voting member of the 802.1d committee when bridging was being standardized, but that's not actually of any use diagnosing this problem in a much later-generation device!).