You are here

Home

Possible Bugs

Your search for "22" gave back 150 results.
Results for Forum Topic

NBM365

published by N7JYS on Thu, 11/01/2018 - 18:16
Forums: 
Possible Bugs

This may be a bug. Just got a 3.65 GHZ Nano Bridge from a friend of mine to test  the Arden firmware out on. Downloaded and installed 3.18.9.0.ubnt.bullet-m-factory.bin into the NanoBridge. Firmware loaded fine. However in the channel listing it sais 5.180 - 5.825 Ghz. Nothing in the 3.380-3.495 Ghz band. I know this Firmware is not tested so maybe this is something to fix? 

Eric

N7JYS

RouterBoard bugs

published by W2TTT on Sun, 12/30/2018 - 23:16
Forums: 
Possible Bugs
Love the RouterBoard implementation!
There are some odd bugs which described here previously, but the GUI blew up so this redo is going to be brief.

1. Seeing "MeshNode" SSID even when the 2 GHz mesh is off.
2. Sometimes the desired  AP SSID does not get broadcast.
3. The "MeshNode" SSID shows up in parallel with either a 2 or 5 GHz AP SSID.
4. The channel choices on the AP change when going from 2 to 5 GHz, but not the other way.

Deaf node

published by KD2EVR on Sat, 12/08/2018 - 21:27
Forums: 
Possible Bugs
We have a xm nanostation m2 that I only have rf access to. I did a ota upgrade to the latest production release. When I checked a day later over rf it had gone "deaf". The mesh status of local node I was using to connect showed an IP address instead of a name for the node in question, good LQ but zero NLQ. I had someone with physical access cylce power for me and it recovered. However a few days later it has gone deaf again. Is this still a known issue? Should I downgrade to the previous production version for now?

Two host names for same node

published by al0y on Mon, 01/07/2019 - 10:03
Forums: 
Possible Bugs

Hello, all....

I am running through a weird bug on my node.
I am running AREDN on a MikroTik Router Board hAP AC Lite with the night build: 586-6728fba
My node name is "AL0Y-RB-MAIN" and is a tunnel server for three clients. It has no RF neighbors. 

The problem is my node is showing to my clients (and their neighbors) with two hostnames as:

hAP RF mesh gone [solved]

published by aj3di on Sun, 01/27/2019 - 19:29
Forums: 
Possible Bugs

After using the DtD port, the hAP no longer produces mesh 2.4 rf.

Yes it is enabled.

Yes it worked prior to DtD.

Wifi scan is not working. Well, it works, just nothing heard.

Nightly 648.

Just a heads up.

Don't think the hardware coincidentally died on 2 different devices at different locations.

NANO VLAN issue - NO WAN

published by aj3di on Tue, 02/12/2019 - 20:09
Forums: 
Possible Bugs

3 Nanos. NO WAN. 3.18.9.0

tp-link no problem. Netgear GS105Ev2.

Support data attached.

Going to try a nightly on one of them....

Nightly 705-711fe96 WORKS

Services not being deleted

published by KC5LIO on Tue, 02/26/2019 - 03:44
Forums: 
Possible Bugs
Running 3.18.9.0 on a NSM2 XM
--------------------------------------------

Nameservice after Tactical name addition/change

published by AA7AU on Mon, 11/06/2017 - 15:05
Forums: 
Possible Bugs

While clawing thru the forum posts and documentation, I noticed the very nice feature of being able to assign a Tactical name to a node. Makes sense ...

So I tested that out with one of my nodes, which was initially setup as "AA7AU-example.local.mesh" and was seen by all of the several nodes on our local proof-of-concept build-out mesh network, along with the instance of MeshChat on my node on all those other status pages.

RF Settings issue in 746-f6e5832

published by KE6MTO on Fri, 03/15/2019 - 13:00
Forums: 
Possible Bugs

Just an FYI, when on firmware 746-f6e5832​ I was having WiFi issues as seen on the status screen below:
 

TP-Link Internal Switch config?

published by w6bi on Mon, 03/25/2019 - 20:13
Forums: 
Possible Bugs
With the latest code, the internal switch in the Ubiquiti Nanostation XW hardware was converted to a vanilla, non-VLAN-aware switch, as far as I understand.

I put the latest code on a TP-Link CPE210 (v1.0) and found that its switch configuration is unchanged; the stock configure has VLAN 1 on the primary port and VLAN 2 on the secondary port.  This can be changed by modifying /etc/config/network, but it's a transient change; won't survive a reboot.

Are there plans to convert the TP-Link internal switch the same as has been done with the Ubiquiti?

Orv W6BI

Pages

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer