Hi all, I am setting up a mesh with several rockets, nanostations and bullets and everything works nicely :)
I got an existing nanobridge M5 previously used as a ptp and loaded the AREDN SW ... the setup is OK but when going to the mesh status I just get it in the mesh but I am unable to connect to it : I just get LQ=100 and NLQ=0
Could anybody give me any hint trying to figureout what is happening and how to fix this issue ?
Thanks in advance....
Mike
I got an existing nanobridge M5 previously used as a ptp and loaded the AREDN SW ... the setup is OK but when going to the mesh status I just get it in the mesh but I am unable to connect to it : I just get LQ=100 and NLQ=0
Could anybody give me any hint trying to figureout what is happening and how to fix this issue ?
Thanks in advance....
Mike
If you do a "Wifi Scan", does it change the LQ/NLQ numbers?
all the nodes have a distance set to 3.000 m ; tryed to do a wifi scan from the nanobridge, then back to the mesh status ... still LQ=100 NLQ=0 ...
by looking the archived signal from a node of the mesh I get the evidence as in the attached image
apparetnly the nanobridge radio start working then shutdown its tx signal... then after some time cyles again...
[ 10.940000] cfg80211: Calling CRDA to update world regulatory domain
[ 10.940000] cfg80211: World regulatory domain updated:
[ 10.950000] cfg80211: DFS Master region: unset
[ 10.950000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 10.960000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 10.970000] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 10.980000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[ 10.990000] cfg80211: (5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A, 2000 mBm), (N/A)
[ 10.990000] cfg80211: (5250000 KHz - 5330000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[ 11.000000] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[ 11.010000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[ 11.020000] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
...
[ 11.180000] ath: EEPROM regdomain: 0x2a
[ 11.180000] ath: EEPROM indicates we should expect a direct regpair map
[ 11.180000] ath: Country alpha2 being used: US
[ 11.180000] ath: Regpair used: 0x2a
[ 11.210000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 11.220000] ieee80211 phy0: Atheros AR9280 Rev:2 mem=0xb0000000, irq=40
[ 11.250000] cfg80211: Calling CRDA for country: US
[ 11.250000] cfg80211: Regulatory domain changed to country: US
[ 11.260000] cfg80211: DFS Master region: FCC
[ 11.260000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 11.270000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
[ 11.280000] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 1700 mBm), (N/A)
[ 11.290000] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz), (N/A, 2300 mBm), (0 s)
[ 11.300000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A)
[ 11.300000] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
...
[ 24.120000] cfg80211: Calling CRDA for country: HX
[ 24.180000] cfg80211: Regulatory domain changed to country: HX
[ 24.180000] cfg80211: DFS Master region: unset
[ 24.190000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 24.200000] cfg80211: (2300000 KHz - 2600000 KHz @ 40000 KHz), (N/A, 4000 mBm), (N/A)
[ 24.200000] cfg80211: (5170000 KHz - 6500000 KHz @ 40000 KHz), (N/A, 4000 mBm), (N/A)
Your device is not getting the right regulator domain necessary for part 97 for some reason. You might change to a part 15 channel, e.g. 149 and see if it works to confirm. channel 168 in use is outside part 15 (note 20Mhz width will overlap with part 15, you might want to go to a higher channel in the end). Here is only what your device is showing:
[ 13.800000] ath: phy0: Ignoring endianness difference in EEPROM magic bytes.
[ 13.810000] ath: EEPROM regdomain: 0x0
[ 13.810000] ath: EEPROM indicates default country code should be used
[ 13.810000] ath: doing EEPROM country->regdmn map search
[ 13.810000] ath: country maps to regdmn code: 0x3a
[ 13.810000] ath: Country alpha2 being used: US
[ 13.810000] ath: Regpair used: 0x3a
[ 13.840000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 13.850000] ieee80211 phy0: Atheros AR9280 Rev:2 mem=0xb0000000, irq=40
This is a new symptom, going to have scratch the head on this one for a minute... might be related to flash EEPROM saved settings or read/write issues. need to review some other uboot versions, etc.
Joe AE6XE
thanks for your attention...
I am running this mesh in italy ... the allowed frequencies in italy for the radio amateur service are the ones reported in the attached fig. so the ch 168 does fit exactly in the 20 Mhz allowed for the HAM radio service in italy: this is why we use this channel.
Regarding the regulatory domain I do not have any idea how this is actually managed by the AREDN SW so I was assuming that the channel 168 was selectable .... BTW I have other nodes (bullet, rocket,nanostation) with this SW and apparently everything works correctly...
This node is the only one giving this strange issue...
Mike I8FUC
I understand, should have caught your location from the callsign. The AREDN firmware doesn't seem to be getting a trigger (at least the linux log file has nothing recorded) to switch the 802.11 driver into the necessary regulatory domain setting to enable transmit on ch 168.
Since this is the latest nightly build, can you please roll back to 3.16.1.0 release and confirm it works or fails? The nightly build has a major upgrade of linux and other things underneath. We need to isolate the issue and confirm if this is a new introduced defect in the upgrade or something else. It is the bleeding-edge nightly build :) .
Also confirm, is this a NB-M5-22 or the NB-M5-25? I recently acquired the larger one, but I've not loaded the nightly build on it yet--and will now do so.
Added edit: I just noticed, which image did you load to this, the support dump says "Ubiquiti Nanostation M". Make sure you load the AREADN 'bullet' image (in the firmware name) to a NanoBridge M5. Which one was loaded?
Joe
... you are right ... I loaded may be a wrong image ....
I just have now loaded the standard bullet image from the Latest Stable version 3.16.1.0 and from the CPU info now the cpu is recognized as a bullet... the dmesg looks now like the ones you reported before in the 80211 parts
I attach the new support info for your review.
... Unfortunatelly the result in the mesh is not changed.... what I have noticed is that my remote test node in receiving a strong -64 db signal, but the LQ/NLQ stays zero and no ip connection is available...
if a replace this radio with a bullet , the same remote node gets a signal of -72 db with 100/100 LQ/NLQ and more then 50 mbps bandwidth....
may be this can suggest what is wrong...
Mike I8FUC
Ideally, peak out on the SNR realtime chart on the mesh node the dish is pointing to.
Joe AE6XE
made following tests:
1) refining antenna alignement: now I have an increased signal seen from my test remote node ( -57 db) : no change in the LQ/NLQ issue :(
2) installed an additional bullet radio with an omnidirectional antenna dow my home building out from the main nanobridge radiation pattern.... signal level -78 db same LQ/NLQ issue :(
3) installed an additional rocket wuth MIMO omni antenna close to the nanobridge and both the remote test nodes as above give much lower signal but LQ/NLQ 100/100 ..
apparently the problem seems to stay on the nanobridge .....
Mike I8FUC
Could this NBM5 be defective? It was working with other firmware before, correct?
Joe AE6XE
The rocket+MIMO omni is colocated with the NBM5 ...
I attach the support data for the rocket..
Thanks for your support :)
Mike I8FUC
Is this a Ubiquiti international version? or is this a US part 15 certified device on the label? If this is made for EU, there may be other hardware limits. Try the Rocket and this device on ch 136 or 140 with AREDN to see if the results are different. Is there a yellow banner at the top of the AREDN status page with testing or not-yet-supported language on the NBM5?
First answers to your questions:
- the device I am using has been taken in europe few years ago; it is EU marked
- there is no yellow banner on the GUI for this device SW
The tests I made today:
- moved on ch 136 both the NBM5 and a bullet with omni antenna
- a new network is formed and is seen as foreign by the other nodes.
- by wifi scanning from a remote node in the original aredn network the new network is seen on the ch 136 correctly
- The new network link reports a LQ/NLQ 80/100 from the NBM5 e viceversa from the bullet extrema when running the NBM5 at 16 dbm tx power level
- made tests by changing the NBM5 tx power level and check the NL/NLQ of the link... the best is 80/100 at 16 dbm, all other tx power level give a worst value like 56/78 at 23dbm
- the attached image is the signal level diagram while making the tx power level change test: you can see how the signal level spread also here is apparently better with the intermediate TX levels.
- during this tests NEVER experienced the suddenly ON/OFF of the TX signal from the NBM5 or the zero tx power issue
- So after all these tests my feeling is the following:
-a) running the NBM5 isochannel with the other nodes create the problem we are investigating
-b) the NBM5 gets the best LQ when the tx power in NOT the max value.
-c) question is if this behaveure is related to the directional antenna pattern (multipath ????) or to the radio...
Mike I8FUC
Best to compare TxMbps values instead of LQ/NLQ, this will give a better characterization of the link. You might have higher TxMbps with lower NLQ giving a different story.
I have not in hand any of these devices at moment with the AirOS Sw on it so I cannot check.
All the devices I got are for european market anyway.
I do understand your point regarding the calibration versus domains ...
Regarding the other devices at moment I have a working link at ch 168 between a rocket and a nanostation M5 on a 1.3 Km link with a signal around 72 db, LQ/NLQ stable at 100/100 and around 50-51 Mbps;
another link beetwen a nanostation M5 and a bullet M5 with omni antenna have signal levels around 80-85 db ( very very low) with a LQ/NLQ variable around 50/50 and a around 20 Mbps .
All are running on ch 168 with a 20 Mhz band.
I was surprised on these two links because on the firsts one I have virtually no packet loss while the other have a very low packet loss or just zero !
Thanks again for your cooperation.
Best 73
Mike I8FUC
Following the yesterday tests, this morning I decided to move the NBM5 again on channel 168, but setting the TX power to 20dbm instead of the maximun that is 23dbm....
I got a wonderfull link with my remote test node with a signal around -60db and a 117 topping 130 Mbps.... stable all the day .....
this evening just for confirmation I set the TX power to 23dbm .... immediately the signal seen by the remote node incresead few db ... and the lLQ/NLQ went down to 100/0 ..... few minutes after I lowerd the power from 23 to 20 db and immediately the links was restored and getting 117 Mbps...
So at this point I think there is a clear relation beetwen the issue and the TX power level at witch the NBM5 is set.
Mike I8FUC
Joe AE6XE
it is not so easy to get to the antenna on the roof ....
Mike I8FUC
BTW I attach the output of iw phy0 info where I see 22dbm as apparently the max tx power... may be this can help
Mike I8FUC
root@IQ8SO5A-80-198-114:~# iw phy0 info
Wiphy phy0
max # scan SSIDs: 4
max scan IEs length: 2261 bytes
Retry short limit: 7
Retry long limit: 4
Coverage class: 7 (up to 3150m)
Device supports AP-side u-APSD.
Device supports T-DLS.
Available Antennas: TX 0x3 RX 0x3
Configured Antennas: TX 0x3 RX 0x3
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* WDS
* monitor
* mesh point
* P2P-client
* P2P-GO
Band 2:
Capabilities: 0x11ce
HT20/HT40
SM Power Save disabled
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT TX/RX MCS rate indexes supported: 0-15
Frequencies:
* 5180 MHz [36] (22.0 dBm)
* 5200 MHz [40] (22.0 dBm)
* 5220 MHz [44] (22.0 dBm)
* 5240 MHz [48] (22.0 dBm)
* 5260 MHz [52] (22.0 dBm)
* 5280 MHz [56] (22.0 dBm)
* 5300 MHz [60] (22.0 dBm)
* 5320 MHz [64] (22.0 dBm)
* 5370 MHz [74] (22.0 dBm)
* 5375 MHz [75] (22.0 dBm)
* 5380 MHz [76] (22.0 dBm)
* 5385 MHz [77] (22.0 dBm)
* 5390 MHz [78] (22.0 dBm)
* 5395 MHz [79] (22.0 dBm)
* 5400 MHz [80] (22.0 dBm)
* 5405 MHz [81] (22.0 dBm)
* 5410 MHz [82] (22.0 dBm)
* 5415 MHz [83] (22.0 dBm)
* 5420 MHz [84] (22.0 dBm)
* 5425 MHz [85] (22.0 dBm)
* 5430 MHz [86] (22.0 dBm)
* 5435 MHz [87] (22.0 dBm)
* 5440 MHz [88] (22.0 dBm)
* 5445 MHz [89] (22.0 dBm)
* 5450 MHz [90] (22.0 dBm)
* 5455 MHz [91] (22.0 dBm)
* 5460 MHz [92] (22.0 dBm)
* 5465 MHz [93] (22.0 dBm)
* 5470 MHz [94] (22.0 dBm)
* 5475 MHz [95] (22.0 dBm)
* 5480 MHz [96] (22.0 dBm)
* 5485 MHz [97] (22.0 dBm)
* 5490 MHz [98] (22.0 dBm)
* 5495 MHz [99] (22.0 dBm)
* 5500 MHz [100] (22.0 dBm)
* 5520 MHz [104] (22.0 dBm)
* 5540 MHz [108] (22.0 dBm)
* 5560 MHz [112] (22.0 dBm)
* 5580 MHz [116] (22.0 dBm)
* 5600 MHz [120] (22.0 dBm)
* 5620 MHz [124] (22.0 dBm)
* 5640 MHz [128] (22.0 dBm)
* 5660 MHz [132] (22.0 dBm)
* 5680 MHz [136] (22.0 dBm)
* 5700 MHz [140] (22.0 dBm)
* 5745 MHz [149] (22.0 dBm)
* 5765 MHz [153] (22.0 dBm)
* 5785 MHz [157] (22.0 dBm)
* 5805 MHz [161] (22.0 dBm)
* 5825 MHz [165] (22.0 dBm)
* 5665 MHz [133] (22.0 dBm)
* 5670 MHz [134] (22.0 dBm)
* 5675 MHz [135] (22.0 dBm)
* 5685 MHz [137] (22.0 dBm)
* 5690 MHz [138] (22.0 dBm)
* 5695 MHz [139] (22.0 dBm)
* 5705 MHz [141] (22.0 dBm)
* 5710 MHz [142] (22.0 dBm)
* 5715 MHz [143] (22.0 dBm)
* 5720 MHz [144] (22.0 dBm)
* 5725 MHz [145] (22.0 dBm)
* 5730 MHz [146] (22.0 dBm)
* 5735 MHz [147] (22.0 dBm)
* 5740 MHz [148] (22.0 dBm)
* 5750 MHz [150] (22.0 dBm)
* 5755 MHz [151] (22.0 dBm)
* 5760 MHz [152] (22.0 dBm)
* 5770 MHz [154] (22.0 dBm)
* 5775 MHz [155] (22.0 dBm)
* 5780 MHz [156] (22.0 dBm)
* 5790 MHz [158] (22.0 dBm)
* 5795 MHz [159] (22.0 dBm)
* 5800 MHz [160] (22.0 dBm)
* 5810 MHz [162] (22.0 dBm)
* 5815 MHz [163] (22.0 dBm)
* 5820 MHz [164] (22.0 dBm)
* 5830 MHz [166] (22.0 dBm)
* 5835 MHz [167] (22.0 dBm)
* 5840 MHz [168] (22.0 dBm)
* 5845 MHz [169] (22.0 dBm)
* 5850 MHz [170] (22.0 dBm)
* 5855 MHz [171] (22.0 dBm)
* 5860 MHz [172] (22.0 dBm)
* 5865 MHz [173] (22.0 dBm)
* 5870 MHz [174] (22.0 dBm)
* 5875 MHz [175] (22.0 dBm)
* 5880 MHz [176] (22.0 dBm)
* 5885 MHz [177] (22.0 dBm)
* 5890 MHz [178] (22.0 dBm)
* 5895 MHz [179] (22.0 dBm)
* 5900 MHz [180] (22.0 dBm)
* 5905 MHz [181] (22.0 dBm)
* 5910 MHz [182] (22.0 dBm)
* 5915 MHz [183] (22.0 dBm)
* 5920 MHz [184] (22.0 dBm)
valid interface combinations:
* #{ managed, WDS } <= 2048, #{ AP, mesh point } <= 8, #{ P2P-client, P2P-GO } <= 1, #{ IBSS } <= 1,
total <= 2048, #channels <= 1, STA/AP BI must match
HT Capability overrides:
* MCS: ff ff ff ff ff ff ff ff ff ff
* maximum A-MSDU length
* supported channel width
* short GI for 40 MHz
* max A-MPDU length exponent
* min MPDU start spacing
Joe AE6XE