Good Jobs, and My thanksIn next Beta you will be able to turn on/off the wireless carrier detection (CSMA), which will apparently solve the subj. problem that was much discussed earlier. This will be ONLY for NSTREME and of course, test at your own risk.
no, without nstream polling, csma is absolutly required in order for the wireless link to function... the reason for removing csma was because polling removed the necessity for that protocol to exist. When running 2 different contention meathods (polling and csma both qualify independantly as contention protocols) you end up wasteing airtime not transmitting, even if you would otherwise usually get a good signal across.Can we get this as an option without NStreme?
Can you give us a look at the config for either endpoint you applied? I have a couple of similar 5ghz links that I'm working on which would benifit from this.
Regards,
Omega
/interface wireless
set 0 ack-timeout=dynamic adaptive-noise-immunity=yes allow-sharedkey=no \
antenna-gain=0 antenna-mode=ant-a area="" arp=enabled band=2ghz-5mhz \
basic-rates-a/g=6Mbps basic-rates-b=1Mbps burst-time=disabled comment="" \
compression=no country=no_country_set default-ap-tx-limit=0 \
default-authentication=yes default-client-tx-limit=0 \
default-forwarding=yes dfs-mode=none disable-running-check=no disabled=no \
disconnect-timeout=3s frame-lifetime=0 frequency=907 \
frequency-mode=regulatory-domain hide-ssid=no hw-retries=15 \
mac-address=00:15:6D:93:25:39 max-station-count=2007 mode=ap-bridge \
mtu=1500 name="wlan900" noise-floor-threshold=default \
on-fail-retry-time=100ms periodic-calibration=default \
periodic-calibration-interval=60 preamble-mode=both \
proprietary-extensions=post-2.9.25 radio-name="xxxxxxxxxxx\
Lake Test" rate-set=configured scan-list=default security-profile=default \
ssid="LLBL" station-bridge-clone-mac=00:00:00:00:00:00 \
supported-rates-a/g=6Mbps,9Mbps,12Mbps,18Mbps,24Mbps \
supported-rates-b=1Mbps,2Mbps,5.5Mbps,11Mbps tx-power-mode=default \
update-stats-interval=disabled wds-cost-range=50-150 \
wds-default-bridge=none wds-default-cost=100 wds-ignore-ssid=no \
wds-mode=disabled wmm-support=disabled
/interface wireless
set 0 ack-timeout=dynamic adaptive-noise-immunity=yes allow-sharedkey=no \
antenna-gain=0 antenna-mode=ant-a area="" arp=enabled band=2ghz-5mhz \
basic-rates-a/g=6Mbps basic-rates-b=1Mbps burst-time=disabled comment="" \
compression=no country=no_country_set default-ap-tx-limit=0 \
default-authentication=yes default-client-tx-limit=0 \
default-forwarding=yes dfs-mode=none disable-running-check=no disabled=no \
disconnect-timeout=3s frame-lifetime=0 frequency=917 \
frequency-mode=manual-txpower hide-ssid=no hw-retries=15 \
mac-address=00:15:6D:93:25:4C max-station-count=2007 mode=station mtu=1500 \
name="wlan900" noise-floor-threshold=default on-fail-retry-time=100ms \
periodic-calibration=default periodic-calibration-interval=60 \
preamble-mode=both proprietary-extensions=post-2.9.25 radio-name="xxxxxxxxxxxxxxxx" rate-set=configured scan-list=default \
security-profile=default ssid="LLBL" \
station-bridge-clone-mac=00:00:00:00:00:00 \
supported-rates-a/g=6Mbps,9Mbps,12Mbps,18Mbps,24Mbps \
supported-rates-b=1Mbps,2Mbps,5.5Mbps,11Mbps tx-power-mode=default \
update-stats-interval=disabled wds-cost-range=50-150 \
wds-default-bridge=none wds-default-cost=100 wds-ignore-ssid=no \
wds-mode=disabled wmm-support=disabled
That's pretty a pretty funny comment. "I believe" too, but this isn't a faith-based technology.I believe you are having problems with FHSS gear such as Alvarion from what you are describing.
Quoting an earlier post in the thread removes the opportunity for confusion.George,
No need to flame my post. I was directing it at GWISA not you.
I'm not nearly that defeatist. Canopy is far from perfect and isn't fond of noise right on top of an AP either. I also don't believe in rewarding government-subsidized incompetence.If you have 11 Canopy 900 AP's near by good luck. You'd have been better off switching to Canopy yourself and syncing with your competition than working against them.
In the wireless world Canopy always wins.
the SR9's (like any 802.11 based radio) uses 20Mhz wide channels unless otherwise specified to use 5 or 10Mhz channels. The 900 Mhz band is 902-928, only 26Mhz wide, if you put a SR9 with the center channel on 912 or 917 (the only options when using 20Mhz wide channels), you are going to be using nearly the entire band... so things weren't necessarly configured wrong, just default...I would venture to say that you had things configured wrong if you were picking up the SR9 across the entire band.
Yes, you are most likely correct, this at least explains what I saw. I am so used to working with the trango gear having a 20mhz channel may not have registered properly with my brainthe SR9's (like any 802.11 based radio) uses 20Mhz wide channels unless otherwise specified to use 5 or 10Mhz channels. The 900 Mhz band is 902-928, only 26Mhz wide, if you put a SR9 with the center channel on 912 or 917 (the only options when using 20Mhz wide channels), you are going to be using nearly the entire band... so things weren't necessarly configured wrong, just default..
technically a 2.9 client will connect to a 3.0 ap with nstream enabled and csma disabled, the 3.0 ap will transmit with csma disabled, the 2.9 client will transmit as normal.Quick question on disabling CSMA. As CSMA is controlled from the AP end does only the AP need to be running V3 or will all clients also need to be running V3?
In what way does it work better? It is easy to upgrade a single AP and role back if there are issues (still RC release after all) but if you upgrade an AP and all the clients then find an issue it's a lot of work to role everything back.that said, keep them the same version, it works better.