wireless/wired bridge update

On the wired/wireless bridge query I made recently, and whether this
should work under Linux as a way to sort of turn a wired NIC into a
wireless connection: while in the computer store the other day, I decided
to look at wireless bridges. Guess what: they didn't have any! But I did
run across something called a "pocket router" that looked interesting.
Reading about it, I understood it works in several modes--including one
called "client mode." So, it seems like it can act like a wireless/wired
bridge in this regard. Furthermore, it can plug into a USB port for power,
thus decreasing the dreaded excess hardware syndrome. In other words, no
need to carry around the power supply: just the pocket router itself (and
it's USB and UTP cable). I'm going to have to think hard about getting one
of these. They're costing around $70 right now, which is about the same as
the latest, greatest (unsupported) wireless NIC's, and substantially less
than really high quality but supported NIC's (e.g., Cisco aironet). Heck
with this driver business. If this thing works under Linux, like it seems
it should, it looks like the thing to get. It even serves more than one
function to boot. Description appended below.

James

PS Dave, you said the bridge you had trouble using as a wireless NIC under
Linux was a D-Link: please don't rain on my parade and tell me it was this
one?!

D-Link Wireless Pocket Router/AP
DWL-G730AP

The Pocket Router/AP might be small in size, but is huge in functionality.
The DWL-G730AP supports multiple operation modes including: Access Point
(AP) mode to create a wireless connection; Router mode to share an
Internet connection; and Wireless Client mode to connect an existing
wireless network. Easily switch between these modes by using the 3-way
configuration switch located at the bottom.

In AP mode, the DWL-G730AP can be used to create a wireless network in a
room where a single Ethernet port is provided. Now multiple wireless
clients can connect to the network at the same time to share resources and
files.

In Router mode, the DWL-G730AP can be used to share a single broadband
Internet connection, such as in a hotel room. The internal DHCP server
automatically assigns IP addresses to ensure everyone in the room can
connect to the Internet. In addition, the DWL-G730AP supports VPN
Pass-through and firewall features including Network Address Translation
(NAT) and MAC filtering to protect your wireless network from malicious
attacks.

When set in Wireless Client mode, the DWL-G730AP allows connection to an
existing wireless network, without having to install complicated drivers
or additional software. For added mobility, the DWL-G730AP can be powered
over USB if power outlets are not available.

The Pocket Router/AP supports WPA-PSK to secure your wireless data
communications. In AP mode, the DWL-G730AP adds support for 802.1x user
authentication with an external RADIUS server. For setup and configuration
the DWL-G730AP can be accessed via D-Link's user-friendly Web-based
utility.

Easy to pack and convenient for traveling, the DWL-G730AP comes with an
attractive traveling case which also provides accessories including cables
and a power adapter. Increase productivity and enjoy the benefits of
wireless connectivity while on the road with D-Link's Pocket Router/AP.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: wireless/wired bridge update

On Sun, 6 Feb 2005, James Miller wrote:

> it should, it looks like the thing to get. It even serves more than one
> function to boot. Description appended below.
>

> D-Link Wireless Pocket Router/AP
> DWL-G730AP
>
> The Pocket Router/AP might be small in size, but is huge in functionality.

I evaluated this product recently and have to say I'm dissapointed. Seemed
like it might be a great alternative for a simpler wireless solution under
Linux, but my experience indicates it's not. This is owing to what seems
to me non-interoperability, sometimes called "vendor lock-in." I can't
rule out that my sketchy understanding of wireless and networking
principles may be at fault here as well, though. Anyway, here's a bit
about the device. It has a switch on the bottom for selecting between
access point, router, and client modes. To configure it, you plug it in
and hook a UTP cable between the device and your computer's NIC. Then, you
assign your NIC an address in the 192.168.0.x range and log into the
device at 192.168.0.30. That gives you a little web configuration
interface page--after you log in. Depending on how you've set the switch
(access point, router, or client) you get different options here. The way
I was able to make the device work somewhat was by running a netwrok
detection utility from that interface, and telling the device to use the
network it found. I wasn't quite sure what to do after this. I finally
decided on entering the address of the device as the gateway for my
machine. I was able to browse the network after setting that 192.168.0.30
address as the gateway. The device is not really suitable for the
following reasons: it's too clunky to get on the network. Having to assign
your machine's NIC an IP is not a big deal. But having to manually enter a
gateway address--*in addition to* having to log into the web interface and
have the thing detect the local network--every time you want to go online
with this thing is just too unwieldy. In short, it's not very portable:
unless you're always using it in the same environment, you will encounter
hassles getting online. Another problem crops up with older machines that
may not have up-to-date browsers capable of using the web interface the
thing gives you for configuring it. Overall, I was disappointed. Maybe
I'll just try out a regular bridge next time.

The thing that leads me to believe that vendor lock-in is at work to some
degree here is the fact that the device did not autodetect and get on the
local network. Looking at the quick-start manual, I also noted that the
device is said to be able to communicate with other d-link wireless
components "out of the box." In other works, forcing the thing to detect
the network is not necessary if you're in an environment that uses d-link
wireless components.

James
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs