You are here

Home

Possible Bugs

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

SCS-2017-001

published by K7DXS on Sun, 03/05/2017 - 14:03
Forums: 
Possible Bugs
I looked at the release notes for the latest release and became curious about the DoS vuln. What happened when someone decided to upload a file to a page that didn't expect it?

3.16.1.1 upgrade failure

published by KQ6EO on Mon, 03/06/2017 - 16:11
Forums: 
Possible Bugs
I tried to update 3 nodes and they all failed.  One bullet with direct connection, one NanoStation XM OTA, and one NanoStation XW OTA.  They all seemed to upload the new firmware OK and rebooted several times and then the LEDs indicated that they were loaded and ready.  I am sure that I used the correct upgrade bin file for each upload and had the keep config box checked.  None of them would reconnect to the mesh or allow connection over a direct Ethernet cable.  I was able to TFTP the factory bin file to them and reconfigure and they were fine.  No tunnels are setup and I tried the old 3.16.1

WinSCP fails to connect after upgrade to 3.16.1.1

published by VE3OY on Thu, 03/09/2017 - 20:18
Forums: 
Possible Bugs


I'm experiencing an oddity with the new firmware ...
NanoBridge M2 (XM) had 3.16.1.0 on it and everything was fine.
I could PUTTY SSH into it, and WinSCP connected fine.

Now, after upgrading WinSCP is giving this error:
"Couldn't agree a client-to-server cipher (available: aes128-ctr, aes256-ctr)"

I can still PUTTY SSH into the NBM2 fine.

So, I thought maybe it was a case of installing SSH keys.
I followed the instructions from  "How To Use PuTTYGen to Make SSH Keys and Use Them on AREDN Nodes".

more OLSR restarts

published by kg6wxc on Wed, 03/22/2017 - 02:16
Forums: 
Possible Bugs
I hear you guys might be trying to track this down... This is from one of the higher level nodes on the Santa Barbara network. I'm wondering if there is actually something wrong with the device due to very very poor performance. I am seeing the "OLSR restarts" area in the bottom left corner of the status page. I've never seen this before on our network. I also went around to all our nodes and only this one that has this message on it's status page. OLSR restarts 2 runtime 2 - 16:04:20

Bug Report

published by N2MH on Mon, 04/24/2017 - 20:04
Forums: 
Possible Bugs


I'd like to report a few bugs:



I guess this brings up the age-old philosophical question: Would you rather be the Bug or would you rather be the Node?

73, Mark
 

DHCP doesn't work on 4th local computer.

published by K7WWP on Sat, 06/17/2017 - 17:04
Forums: 
Possible Bugs
I've loaded AREDN-3-16.1.1-ubnt-airrouter-squashfs-factory.bin onto an air router.  I configured it for 13 host Direct.

I plugged 4 computers, all windows 7, all configured identically into the LAN ports on the air router.  The computer plugged into port 4 of the air router does not get a DHCP address.  If I swap computers, it's always the one on port 4.

I have two air routers, and I get the same problem on the second air router.  The computer plugged into port 4 does not get an address assigned to it.

DHCP Reservation issues

published by WD6EBY on Mon, 06/12/2017 - 17:04
Forums: 
Possible Bugs

Hello All,

NLQ is 0% via DTD connection

published by WD6EBY on Thu, 06/22/2017 - 00:48
Forums: 
Possible Bugs

Hi All,
I have two UBNT Rocket nodes each showing a NLQ of 0%.  They have different version, v3.16.1 and v3.17.1.0rc.  If yoc could provide any suggestions or comments I would be appreceative.
See attached Screen Shot

Thank you.

Paul
WD6EBY
 

Mystery Mac address on Wi-Fi scan

published by kk6fut on Tue, 08/08/2017 - 18:57
Forums: 
Possible Bugs
I noticed recently that all of the nodes I've spot checked in our mesh (even in geographically different RF areas in different valleys) have a similar node lurking under "WiFi scan":

Mac Address:
EE:93:5A:69:75:97  (My Ad-Hoc Network)

Does anyone else see this doing a Wi-Fi scan?

If so, is this possibly the artifact of a index or buffer overrun? (It has no operational impact, but perhaps a bug nonetheless?) Or why would *all* of our nodes see this node, everywhere?

The node shows up on 3.16.1.0, 3.16.1.1, and 3.17.1.0RC1.

Iperfspeed and 3.17.1.0RC1?

published by w6bi on Fri, 08/11/2017 - 23:15
Forums: 
Possible Bugs
Has anyone successfully loaded Iperfspeed on a node running 3.17.1.0RC1?

When I do so the packages install OK and the  service displays properly, but upon clicking it we get:
 

Not Found

The requested URL /iperfspeed was not found on this server.

and yes, I rebooted after installation...

Pages

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer