fake.e-mail@stonyx.com hath wroth:
>On Aug 15, 5:27 pm, Jeff Liebermann <je...@cruzio.com> wrote:
>But isn't an ad-hoc network configuration an example of clients
>talking to clients and not to an access point?
Correct. However, you didn't say anything about either infrastructure
mode or ad-hoc mode. Since infrastructure is far more common, I
assumed that this is what you're doing. If you have an access point
or wireless router, you have an infrastructure mode network. If you
don't, then it's probably ad-hoc.
>Is it possible to have
>some sort of combination where the access point talks to the machine
>on the main level and the machine on the main level talks to the one
>in the basement? Just throwing ideas out there.
Well, actually it's possible. It might be worth the effort if you
don't mind a major exercise in software development to save the cost
of a WDS bridge. Some of the mesh networks are essentially
combination client bridges and repeaters. For example, Meraki
<http://meraki.com>
is selling radios that do this. Each client radio repeats the traffic
from other client radios that eventually end up at a central access
point. You could build such a system inside your house, which will
pass traffic between floors and radios. There are also a variety of
open source efforts to do the same thing:
<http://pdos.csail.mit.edu/roofnet/doku.php>
There are a few others, but I can't seem to find them.
It might also be possible to install two wireless cards or devices in
your middle PC, and set them up as some kind of repeater. Offhand, I
don't know how this can be done and really don't want try and
guess(tm) how to do it. Besides, I thought you had a "quick"
question.
For only a single hop, methinks a WDS bridge will be a much simpler
and cheaper solution.
--
Jeff Liebermann
jeffl@cruzio.com
150 Felker St #D
http://www.LearnByDestroying.com
Santa Cruz CA 95060
http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558