Important exeption is the channel sidebands and baseband filters fall-off. You
sholdn't use adjacnt channels for different networks. At least 40MHz gap
should be left between H20 channels, and as much as 80MHz between HT40+ and
HT40- channels.
On Mon, Aug 01, 2011 at 11:19:03AM +0600, Alex Hacker
I've also noticed that there's sometimes quite noticable differences
in how clean the output is from various NICs.
Eg, when pushing the SR-2 or SR-71A at max power, versus the Unex DNMA
series high power NICs. The Unex ones are much, much cleaner.
Adrian
On 1 August 2011 16:31, Alex Hacker
Hi, Adrian!
Yeah, the Ubiquity is young company trying to get his place on the market.
So that they like to overdrive Sirenza RF PAs to impermissible levels. This
leads to raising unwanted emission in adjacent channels, but I don't
believe that they have a fake FCC certificate. :) Another issue
I bet there's some RF leaking out, either from the TX, or maybe the PLL/clock.
I wonder why the two antennas on a single card don't interfere with each other?
Unfortunately it's the kind of thing you can only diagnose with a
sensitive spectrum analyser.
I had that problem with a box w/ two
On 1 August 2011 03:27, Grant emailgr...@gmail.com wrote:
I bet there's some RF leaking out, either from the TX, or maybe the
PLL/clock.
I wonder why the two antennas on a single card don't interfere with each
other?
That's a question for the RF/baseband engineers, who likely know more
I've installed my Ubiquity SR71-E with a PCIe adapter but I get:
wlan0: direct probe to xx.xx.xx.xx.xx.xx (try 1/3)
wlan0: direct probe to xx.xx.xx.xx.xx.xx (try 2/3)
wlan0: direct probe to xx.xx.xx.xx.xx.xx (try 3/3)
wlan0: direct probe to xx.xx.xx.xx.xx.xx timed out
I'm connecting to a
* On 31.07.2011 01:41 AM, Grant wrote:
It's fixed! The problem was actually interference from an ath5k
802.11g card I had in the same system. I've noticed that any wireless
card installed in the system will pump out enough RF to interfere with
any other card in the system even if the
I bet there's some RF leaking out, either from the TX, or maybe the PLL/clock.
Unfortunately it's the kind of thing you can only diagnose with a
sensitive spectrum analyser.
I had that problem with a box w/ two (high powered) NICs in 2ghz mode,
and I only discovered this issue with a spectrum
On Fri, Jul 29, 2011 at 12:01 AM, Grant emailgr...@gmail.com wrote:
I've installed my Ubiquity SR71-E with a PCIe adapter but I get:
wlan0: direct probe to xx.xx.xx.xx.xx.xx (try 1/3)
wlan0: direct probe to xx.xx.xx.xx.xx.xx (try 2/3)
wlan0: direct probe to xx.xx.xx.xx.xx.xx (try 3/3)
wlan0:
On Fri, Jul 29, 2011 at 12:04 PM, Mohammed Shafi
shafi.wirel...@gmail.com wrote:
On Fri, Jul 29, 2011 at 12:01 AM, Grant emailgr...@gmail.com wrote:
I've installed my Ubiquity SR71-E with a PCIe adapter but I get:
wlan0: direct probe to xx.xx.xx.xx.xx.xx (try 1/3)
wlan0: direct probe to
I've installed my Ubiquity SR71-E with a PCIe adapter but I get:
wlan0: direct probe to xx.xx.xx.xx.xx.xx (try 1/3)
wlan0: direct probe to xx.xx.xx.xx.xx.xx (try 2/3)
wlan0: direct probe to xx.xx.xx.xx.xx.xx (try 3/3)
wlan0: direct probe to xx.xx.xx.xx.xx.xx timed out
I'm connecting to a
I've installed my Ubiquity SR71-E with a PCIe adapter but I get:
wlan0: direct probe to xx.xx.xx.xx.xx.xx (try 1/3)
wlan0: direct probe to xx.xx.xx.xx.xx.xx (try 2/3)
wlan0: direct probe to xx.xx.xx.xx.xx.xx (try 3/3)
wlan0: direct probe to xx.xx.xx.xx.xx.xx timed out
I'm connecting to a WPA2 AP
12 matches
Mail list logo
