On 9 Aug 2006 04:52:14 -0700, "Skip - Working on the boat"
<SkipGundlach@gmail.com> wrote in
<1155124334.440405.73680@75g2000cwc.googlegroups.c om>:
>Hi, Guys,
>
>Well, between you, there seems to be direct disagreement.
There really isn't -- Jeff and I disagree from time to time on fine
details and perspectives, but not on basic facts.
>On the one hand, "there shouldn't be any IP conflict" -- yet, that's
>what killed all attempts to merely communicate, before.
What I actually wrote was quite different:
"The IP conflict should be avoidable."
What was implied: "If the hardware is configured properly."
I've frankly had a great deal of difficulty following all your attempts
(and have been frustrated by your not following suggestions), but I've
nonetheless seen some obvious problems.
>On the other, we have Jeff's somewhat more erudite
>reasoning/explanation of why I got clashes.
Jeff commented on SSID issues, not IP address issues.
>Is it that Windoze is calling clashes IP conflicts when it's really not
>that problem, but they label it that way so as not to confuse the hoi
>polloi?
Windows reports of IP address clashes are real conflicts detected at the
network level, not something else.
>And, regardless of labeling (we already know I'm clueless, so I'll not
>apologize for not being able to come up with the right terminology, if
>that's what's at root of the differences between all of us), is it, in
>fact, possible to set an AP and a bridge on the same netclass, have the
>bridge scanning for open sites (and exclude, somehow, my AP right next
>to it or 60 feet away belowdecks, perhaps), and not have conflicts?
As I wrote, IP conflict should be avoidable. I say that with confidence
because I've set this kind of thing up successfully many times.
Unfortunately, you haven't provided the kind of sufficiently detailed
and accurate information that I need to figure out what's wrong in your
case. (As a result, I've spent far more time and effort getting nowhere
than it would normally take to fix the problem, which is frustrating.)
>Much more importantly to me, is it possible for *any* setup to allow me
>to use a configuration tool to see, and select from, available APs
>without having to do the manual resetting/configuration of some unit,
>whether by wifi or ethernet cable, as is the case now (understanding
>that I'm so thrilled with the end result that doing so is now a minor
>inconvenience)?
That depends on the client bridge. If it can do that, then yes you can.
What you need is a reliable way of communicating with the client bridge:
1. You don't want the client bridge being configured by DHCP, since the
address might well change. You need to configure it manually at an
address that won't conflict with anything else. A good choice for this
purpose is an address in the special auto-configuration range (that
Windows uses when DHCP fails): 169.254.0.0/16
2. To reliably connect to the client bridge, you need an IP address in
the same netblock. If you follow my advice above, that won't happen
with DHCP. Switching IP configurations is fast and easy with a
connection manager (see wikis below). If you don't want to do that,
then you'll need a second Ethernet adapter with a manual IP address in
the same netblock, since Windows doesn't seem to be able to handle dual
homing of a single adapter with DHCP as one of the two configurations.
>And, finally, now that the concept has ultimately been proven after
>months of failures, even from (another forum) having someone who'd had
>multiple dual-2611 setups (in a different environment but
>electronically similar to mine) not be able to resolve the conflict
>issue - other than to, also, suggest the insertion of a router (I'm
>guessing he had his tied to a specific SSID, negating my problem) -
>I'm willing to go afield.
No offense intended and with all due respect, I don't think there was
ever any real question that it could be made to work had you followed
proper procedures. That's something to bear in mind when going afield.
>What would you suggest for a replacement to
>the bridge which would both be a better piece of kit, as well as not
>have the b-g issue?
Senao Wireless Outdoor Multi-Client Bridge/AP/WDS-NOC-3220
>Having a bit of voice training would be nice (not
>an opera singer, just a good vocalist - say, 200mw) to help get to
>shore; the antenna seems to be adequate already...
More power probably won't help. As Jeff Liebermann puts it, "This is
commonly known as an alligator, which is an animal with a big mouth and
small ears. The xmit amplified [radio] can be heard over a much larger
area than it can hear the replies from the [other radios]. Unless the
[other] radios have a similar power amplifier, the system [becomes]
asymmetrical, with more range in one direction than the other."
>I'm (reasonably) sure having an 'a' unit is of little to no value, as
>there's no time I'll need that kind of throughput, and any
>organization/gamer who needed it likely would have it encrypted,
>anyway,
I agree that "a" is of little or no value. "g" is as fast as or faster
than "a".
>but we've had direct illustration of why a g is valuable.
A painful and expensive lesson.
>Given that the Vonage unit has to plug its ethernet into *something*
>I'll likely have to have it between whatever bridge and the ap, anyway,
>and likely have it downstairs, so that's not an issue.
Arrgggthhhh! You *don't* want a router "between" the client bridge and
the access point! Hang both the Vonage router and the access point off
a small hub or (better) switch *if* the Vonage router will work through
another NAT. I'm guessing the NAT could be a problem, and that you'd be
better off with a simple Vonage adapter (e.g., D-Link VTA).
If you want my help, no offense intended and with all due respect,
you'll have to resist the apparently strong urge to experiment wildly on
your own, not follow suggestions, and argue with those trying to help
you.
>I have the
>appropriate length crossover and standard cables.
Way down the priority list.
--
Best regards, FAQ for Wireless Internet: <http://Wireless.wikia.com>
John Navas FAQ for Wi-Fi: <http://wireless.wikia.com/wiki/Wi-Fi>
Wi-Fi How To: <http://wireless.wikia.com/wiki/Wi-Fi_HowTo>
Fixes to Wi-Fi Problems: <http://wireless.wikia.com/wiki/Wi-Fi_Fixes>