Im trying a 411 with a SR9. The SR9 works fine in a 133c with -58 signal.
In the 411 it shows up but when i scan for APs none show up. Freq usage shows signal from the AP.
I upgraded to 3.1 & still no luck. Is there something im missing here.
Thanks for any help.
Kell
Try re-seating the SR-9 and make sure the pigtail is functional and installed properly.
Double check that you are using the proper antenna port.
Have you compared board settings used in the RB/133 versus the RB/411, make sure you are using the proper freq, channel width, etc…
In terminal run the following command for the RB/133 & the RB/411;
interface wireless print
Now with these values from the RB/133 make settings comparisons to the RB/411.
Thanks for your help. Here is the settings on both.
RB133c
Flags: X - disabled, R - running
0 name=“wlan1” mtu=1500 mac-address=00:15:6D:93:2A:7D arp=enabled
disable-running-check=no interface-type=Atheros AR5213 radio-name=“”
mode=station ssid=“TEST” area=“” frequency-mode=manual-txpower
country=no_country_set antenna-gain=0 frequency=2432 band=2.4ghz-b
scan-list=default rate-set=default
supported-rates-b=1Mbps,2Mbps,5.5Mbps,11Mbps
supported-rates-a/g=6Mbps,9Mbps,12Mbps,18Mbps,24Mbps,36Mbps,48Mbps,
54Mbps
basic-rates-b=1Mbps basic-rates-a/g=6Mbps max-station-count=2007
ack-timeout=dynamic tx-power=28 tx-power-mode=card-rates
noise-floor-threshold=default periodic-calibration=default
periodic-calibration-interval=60 burst-time=disabled dfs-mode=none
antenna-mode=ant-a wds-mode=disabled wds-default-bridge=none
wds-default-cost=100 wds-cost-range=50-150 wds-ignore-ssid=no
update-stats-interval=disabled default-authentication=yes
default-forwarding=yes default-ap-tx-limit=0 default-client-tx-limit=0
proprietary-extensions=post-2.9.25 hide-ssid=no
security-profile=default disconnect-timeout=3s on-fail-retry-time=100ms
preamble-mode=both compression=no allow-sharedkey=no
RB411
Flags: X - disabled, R - running
0 name=“wlan1” mtu=1500 mac-address=00:15:6D:93:16:EB arp=enabled
interface-type=Atheros AR5213 mode=station ssid=“TEST” frequency=917
band=2.4ghz-b scan-list=default antenna-mode=ant-a wds-mode=disabled
wds-default-bridge=none wds-ignore-ssid=no default-authentication=yes
default-forwarding=yes default-ap-tx-limit=0 default-client-tx-limit=0
hide-ssid=no security-profile=default compression=no
Has anyone used a SR9 in a RB411 & got it to work.
Thanks again for any help.
Kell
Something wierd is going on. If I use the align tool the AP shows -76 sig but it doesnt in the scan window.
I have tried with same results on 2 RB411s.
Kell
I don’t know much about it, but I think ‘frequency=917’ in RB411 could be the problem.
Regards.
Xevi is correct in pointing out ‘frequency=917’.
You should be seeing ‘frequency=2437’, that would be a big problem.
Also, be sure to match data rates between the 411 and the 133, or most importantly to match the AP data rate configuration to your new 411.
I’m not positive if this is a required setting but I would assign the country code to the router also.
The SR9 work’s with RB/411’s, I know another operator using an SR9 based system prently.
In my network I use XR9 based AP’s and CPE’s with a mix of RB/112, 411, 133.
I provided an example from one of my clients 411/XR9 CPE’s;
0 R name="wlan1" mtu=1500 mac-address=00:15:6D:94:0B:21 arp=enabled interface-type=Atheros AR5413
mode=station ssid="GigaNet" frequency=2437 band=2.4ghz-b/g scan-list=default antenna-mode=ant-a
wds-mode=disabled wds-default-bridge=none wds-ignore-ssid=no default-authentication=yes
default-forwarding=yes default-ap-tx-limit=0 default-client-tx-limit=0 hide-ssid=no
security-profile=network_WPA2_Profile compression=no
Hope this helps you out?
Regards
I have thought that might be the problem but the only setting I have is 912 or 917 without downgrading “I THINK”
Giganet what version OS is on ur 411. I cant seem to find older versions for this board. It had 3.6 & it was the same way.
Thanks
Kell
My RB/411 are running 3.10
I have downgraded to 3.0 & it still shows 912 & 917 Im not sure that is the problem. I dont know what else to try.
Thanks Kell
Just to let everyone know. I upgraded the 133c that was working to 3.10 & it stoped working to. If u have a SR9 for an AP that is below v3.0 it will not connect with a SR9 client v3.0 or above.
Version 3 reflects the correct frequency. It no longer shows up as a 2.4 frequency…
I recently upgraded an AP from 2.9 to v3 and all of a sudden none of the 2.9.x clients would connect. My ap was running in 2ghz-B mode. The clients wouldn’t even see the AP in a scan. I set the ap to 2hgz-5mhz mode then drove to each client and made the simple change on them too and every single one of them connected right up.