Except it's not effecting the ap's further out. Even if they were on a
different segment they should still pick up the interference from the ap's
right?
Marlon
(509) 982-2181 Equipment sales
(408) 907-6910 (Vonage) Consulting services
42846865 (icq) And I run my own wisp!
64.146.146.12 (net meeting)
www.odessaoffice.com/wireless
www.odessaoffice.com/marlon/cam
----- Original Message -----
From: "Lonnie Nunweiler" <[EMAIL PROTECTED]>
To: "WISPA General List" <wireless@wispa.org>
Sent: Tuesday, May 09, 2006 5:55 PM
Subject: Re: [WISPA] Weird problem - 20 seconds latency and other oddness
I agree it could be noise but a bridge runaway will give you the 10+
second pings and with that much traffic being echoed ALL of your AP
and Clients are spewing. It would look like a massive RF flood on the
Spectrum Analyzer. Think about what the air wave look like when you
have full radio usage. To nearby units and competitors it would be a
massive increase in the noise floor.
Lonnie
On 5/9/06, David E. Smith <[EMAIL PROTECTED]> wrote:
Lonnie Nunweiler wrote:
> Any confirmation on this? A customer router plugged in with LAN to
> the WAN or not getting a DHCP entry or even a DNS entry has caused
> many bridges to collapse and appear as if it is noise, simply because
> the bridges are all echoing the massive broadcast traffic.
There's no DHCP anywhere on the network, and the DHCP UDP ports are
filtered out at every POP, so that specifically is a bad example. :)
Sorry for not getting back to this, we've had massive weirdness on our
dialup gear too (mostly related to moving it).
Yes, our network is part bridged/part routed.
I'm pretty sure it's a real RF problem, because we pulled out the
Bumblebee and my field guy said he saw crazy mad noise all across the
2.4 spectrum a couple days ago, when we were having this weird hiccup.
(And another local WISP operator reportedly has had similar issues,
though I didn't talk to him personally; that's the boss' department.)
We'll probably just have to use some old-school triangulation and such
to find out where it is, if it's something we even can find. For
instance, today was a cool and cloudy day, and this problem didn't show
up all day. Thus, I blame sunspots. :D
(Honestly, I'm stumped, but at least we're now reasonably certain it's a
real RF issue.)
If/when we sort it out, I'll report back.
David Smith
MVN.net
--
WISPA Wireless List: wireless@wispa.org
Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless
Archives: http://lists.wispa.org/pipermail/wireless/
--
Lonnie Nunweiler
Valemount Networks Corporation
http://www.star-os.com/
--
WISPA Wireless List: wireless@wispa.org
Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless
Archives: http://lists.wispa.org/pipermail/wireless/
--
WISPA Wireless List: wireless@wispa.org
Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless
Archives: http://lists.wispa.org/pipermail/wireless/
