You are here

Home

Possible Bugs

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

Nodes "going to sleep"

published by w6bi on Tue, 08/29/2017 - 18:19
Forums: 
Possible Bugs

Can someone shed some light on this?

 Situation:  Different hardware, on different bands, some linked with DtD, some linked with RF, in several different locations (but fairly close geographically) - some are running RC code and others the release code.  

Issue:  About a third of them appear to "go to sleep" (some at the same time) ie, they disappear, both - both RF and DtD links go away, and wake up 16-17 minutes later, without having rebooted.   

PowerBeam identified as NanoStation on map with 3.17.1.0RC1

published by k0tan on Thu, 08/24/2017 - 10:41
Forums: 
Possible Bugs

We just deployed a new PowerBeam M5 with 3.17.1.0RC1.  Works well, but we noticed it is identified as NanoStation on Map.

Unable to post a screen shot but node is K7TJH-PB1 in north Lake Havasu City, AZ.

 

Stuck in upgrade mode after reboot

published by w6bi on Sun, 09/17/2017 - 14:39
Forums: 
Possible Bugs

This may be hardware-related, but since it's running RC code I thought I'd post it.
This Nanostation M2 has been running the RC code since it became available.   Occasionally I'd get this when trying to ssh to it.  Retrying a bit later works:

[root@w6bi-shack-pc ~]# ssh -p 2222 w6bi-vc-siminorth-2g
ssh: connect to host w6bi-vc-siminorth-2g port 2222: Connection refused

I decide to reloaded the RC code.  It rebooted, and now the node is here:

This node is currently in upgrade mode

Node Type field missing in setup page

published by KD9FRS on Wed, 01/31/2018 - 22:14
Forums: 
Possible Bugs
Hello AREDN. I've searched for anyone else having an issue with node configuration, specifically the setup page not showing the "Node Type" field. I see the field when looking at screenshots in the documentation, but that field is not present on my two nodes. These are NanoStation Loco M2 units with the XW chipset (that's what Amazon sent).

I've used this nightly build: AREDN-develop-172-69937359-ubnt-loco-m-xw-squashfs-factory.bin

3.16.1.1 Instability

published by kc0wkp on Sat, 03/10/2018 - 11:21
Forums: 
Possible Bugs

I did not see a post on this so sorry if it has already been addressed. I recently started getting all the nodes up to 3.16.1.1 from 3.16.1.0. However the nodes seem to be somewhat unstable now. Uptime never seems very long and it seems as if the node is constantly restarting. I have dumped my support file if that helps. Sometimes it take multiple attempts just to get to the local node.

Hostname displays as IP address on DtD link - nightly build

published by w6bi on Wed, 07/11/2018 - 13:32
Forums: 
Possible Bugs

Upgraded a node to nightly build aredn-develop-21-develop-360786c.  One DtD link (the first DtD link in the list of Current Neighbors) continues to display IP address rather than hostname.   It is resolvable, however.   Maybe related to issue #41 on Github?  See screenshot and Support Data file (as soon as I figure out how to attach them...)

 

Not exactly a bug

published by w6bi on Fri, 09/07/2018 - 15:05
Forums: 
Possible Bugs
I went through this this morning:

Main NSM2 on nightly build 221

Attempted to upgrade to build 247: removed vtun package, uploaded 247 nightly build

Ended up with apparent continuous reboot cycle, based on a repetitive ping success / fail cycle
and found this:

[obeach@jethro_house ~]$ ssh -p 2222 root@w6bi-vc-qth-2g
ssh: connect to host w6bi-vc-qth-2g port 2222: Connection refused

Power-cycled node; returned on build 221

Build 283 VLAN issue?

published by w6bi on Thu, 09/20/2018 - 21:22
Forums: 
Possible Bugs

I applied the latest nightly release this morning to a test node and it lost all DtD links.

Comparing two NSM5 XWs, both with Ethernet cable plugged into the Secondary Port.
This one is working, running Nightly Build 221:

Occasional DNS resolution/broadcast failures (?) in new release.

published by w6bi on Fri, 09/28/2018 - 20:22
Forums: 
Possible Bugs
We're seeing occasional DNS broadcast failures (IP address showing instead of hostname) on DtD links of perhaps a half dozen nodes.  Sometimes they'll go away after several hours or several days, sometimes they persist.  (See attached screenshot).
All of the affected nodes are running the latest production release code.  They're all high-level nodes, all Rockets (which may not be relevant).
Any ideas?

Orv W6BI

tcpdump package missing?

published by N2MH on Tue, 10/30/2018 - 10:00
Forums: 
Possible Bugs

On Build 385, the tcpdump utility seems to be missing. Has it been renamed or something else?

Pages

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer