If you choose to take the beta release out for a spin, here's a few pointers (not in any particular order):
1) As usual, not for production usage and not for an emcomm use until proven.
2) If you have AREDN3.0.2 installed, there is an "Over the Air" patch on the experimental downloads page. Upload this (as if it was an image), refresh the Admin page and a check box will appear "keep settings". Now load the appropriate "sysupgrade" beta image for your device with this box checked. Takes about 3 minutes and keeps all your settings.
3) Check for existing bugs submitted--to avoid know pitfalls and duplicate bug submissions. Look for "Issue Tracker" option on main page of AREDN website or [LINK REMOVED] We are very interested to know about bugs that have not yet been found. (We would like to avoid unnecessary effort on repeated questions about the same bug.)
4) Coordinate with your local ATV folks who have likely moved to the new part 97 only channels as well.
5) Revert back to AREDN3.0.2 by uploading the appropriate 'sysupgrade' image.
6) There is no formal support on using the Beta. We are busy supporting a group of Beta Testers working through a formal test plan. While we'd like to think the beta is perfect, we may also be preoccupied fixing a few bugs.
7) What is in the Release number (3.15.1.0b01)?
"3" = protocol compatibility with other nodes on other releases (both AREDN and BBHN)
"15" = year 2015
"1" = first release in the year
"0" = patch level
"b01" = beta release 01
Joe AE6XE
When is b02 scheduled for release Joe?
Interested in the integrated tunnel functionality which seems to be broken in b01.
Hilary
VK2IUW
very soon... ;-)
Like it's been published soon? :)
Just curious - when this version leaves beta will it be 3.15.1.0?
Yes
Beta b02 is NOW on the experimental downloads. ...we're working to get the website notice up. I'm loving that OTA (Over the Air) 'keep settings" upgrade! I did my first 5+mile remote over RF upgrade and saved an afternoon and a long uphill hike. This is on a 3Ghz beta node. I'm going to be doing my remote 2.4G and 5G production nodes next. This ch -2 significantly improved link quality results we are seeing is compelling...
These are 'clean' image upgrades that minimize memory usage. When we 'patch' nodes to upgrade/fix, this is a memory additive process, e.g. a replaced file still has old/new in the file system memory--changes are a file system overlay. The OTA upgrade is as if you did a TFTP clean image load and pulls the config file settings across.
For those of you with tunnels, You do have to go back in and click on the "install tunnel" button. But after this click and reboot, all tunnel settings are preserved and back. (We are not pulling add-on 'packages' like vtun across in OTA by design.)
AirGrid M2.
Initial Version installed: 3.0.2
I uploaded the OTA patch all ok.
Upgraded to b02 all ok.
When I went to install the Tunnel server I got an error message "Package installation failed"
Other than that, b02 seems to be working.
I am going to revert back to 3.0.2 and try again...
Hilary
Confirming that you do have internet access on the airgrid available, right? (to download the tunnel packages)
Also, did you have the tunnel add-on installed on 3.0.2 before you started? If YES, then:
Just to be clear.
Can I use the OTA if I currently have the previous 3.15 beta installed?
JJ
Yes. If you have b01 installed, you can upgrade with the "keep settings" checkbox checked. (Ie. OTA upgrade)
Yes, internet access is available on the AirGrid.
Yes, the tunnel add-on was installed on 3.0.2.
I installed 3.0.2 again, but when it came up, the node status WiFi address said: "none".
Did a reboot, but still the same; no WiFi address.
Did a System FW install of Beta b02
Now all ok and then Tunnel server installed ok.
Go figure;-)
I am upgrading my Nanostation M2 also.
Everything installed ok, but when I add a tunnel client entry I get an error message saying: Configuration saved however: Problem restarting vtund".
I am going to go back to 3.0.2 again and do a System install of b02.
Don't you love computers?
Hilary
--
NanoStation M2
went back to 3.0.2 without saving settings.
Installed OTA update.
upgraded to Beta b02.
Installed Tunnel Client.
When it had finished installing the tunnel client, it automatically loaded the tunnel server page with an error saying it had failed install.
Going to the tunnel client page it seems to have installed.
So now both the tunnel server and client seem to be installed even though I only tried to install the client, but obviously with errors.
Unless there is something else you would like me to try, I think i'll go back to 3.0.2.:-)
Incidentally, on the AirGrid I was able to load the Factory image via administration, but the Nanostation produces an error saying: "The uploaded file is not recognised".
Hilary
So, let me understand...
At this point, did it reboot after installing?
Yes, all your points are correct.
After clicking the Tunnel Client "ïnstall" it came up with the error and did not reboot.
Question: So does clicking on "install" in either the client or server tunnel page install both client and server?.
Regards
Hilary
--
yes. the "Install" button does the exact same thing from either page. It installs the server and the client files.
On both the AirGrid M2 and Nanostation M2 I did a Sysupgrade directly to Beta b02 including install of Tunnel.
Everything went ok this time - no errors, and each one rebooted after the tunnel install.
When I add a tunnel client entry to either, I get an error message saying: "Configuration saved, however: Problem restarting vtund".
Hilary
VK2IUW
--
Ok. Can you go to the Admin page and click the "Download Support Data", save it, and email it to me at mycallsign@arrl.net
thanks
Thanks Darryl,
Support data sent...
Regards
Hilary
VK2IUW
bug logged: [LINK DELETED]
and fixed.
WORKAROUND: make sure that you have at least one alphabetic char in a tunnel client's password.
Aren't you lovin that support download button! Might have taken a week of sending details back and forth to fix otherwise.
Thanks for your help Darryl,
Still doesn't explain why the Tunnel install failed though.
Anyone want to test out my new Tunnel server or Client?
There are a distinct lack of nodes here in Sydney, but I'm trying my hardest to get interest going.
Did a demo at the local club on Friday night, and got lots of questions and interest.
Hilary
Vk2IUW
Yeah. We have a ticket open regarding tunnel installation failure. I haven't been able to reproduce it yet, unfortunately.
Great news on the demo! Let us know if you need anything!
Thanks to Darryl K5DLQ...we were able to catch the tunnel install failure and generate some output for troubleshooting. Here's the ticket for reference....
[LINK REMOVED]
It was also great to use D-STAR to chat while we were doing the troubleshooting. If any other AREDN hams are interested, I hang out on Reflector 51D. Besides experimentation with AREDN, I've got two D-STAR repeaters I've helped build that use the G4KLX software on Raspberry Pis, interfacing with some Motorola CDM radios.
Great job guys,
Keep up the excellent work!
Hello all,
I have just upgraded from a Linksys node and have to say I like the Ubnt hardware. I am working with some of the guys in a nearby city and playing around with the tunnels until we can get the infrastructure to get an RF link up.
He was running the Beta on his Ubiquity node and had this same problem. When we go to the "Mesh Status" page it says OSLR is not running?
I am running a Bullet M2.
I have backed up to the "Stable" load of the firmware and was able to get the tunnel server and client loaded up. And for the meantime it will work fine until I get some more nodes up around here, but with a high RF noise, we would like to take advantage of the -1 and -2 channels.
Thanks
Dave N6DLH
Hi Dave and welcome to the group!
Can you say exactly the upgrade process that you went thru?
What version did you start with on the Bullet?
Did you have the tunnel add-on already installed on the "old version"?
Did you revert back to AREDN 3.0.2 and it DOES work ok?
thanks,
Darryl - K5DLQ
I started with 3.15.1.0b02 Factory file, and it was uploaded directly through the Air OS admin page.
Yes I reverted back to 3.0.2 and it is working fine. Let me upgrade it back and get a screen shot and config dump.
Can you also attach a "support dump" (Look for "download support data" at bottom of Administration page). This tells all on the node to pin point the issue.
Ok it seems this problem only happens in the Negative channels....
Also I am finding that when using the beta firmware, I loose all meshing with the other nodes here, On 3.0.2 they all mesh fine. Is that normal?
Sorry everyone, I realized I forgot to resize the picture. it will not let me upload a support dump.
paste in link to dropbox, google docs, etc. for support dump.
http://qsl.net/n6dlh/supportdata-N6DLH-100-201507310059.tgz
Here is the support dump. I have now migrated it back to the 3.10.0. I have some work to do tonight on the network, but I can play around with it more on Sunday.
Thanks for all the hard work!
Dave
The image upload has been modified to resize pictures and there is a new support file upload button below the Comments editor box.
Ok link is broken lets try this
http://qsl.net/n6dlh/supportdata-N6DLH-100-201507310059.tgz
Just to confirm, this was taken WHILE the error about OLSR not running was displayed correct?
Yes it was
Dave, can you run the following command on the node (with 3.15.1.0b2) when you get a chance?
echo /all | nc 127.0.0.1 2006
Capture and post the output here please. thanks.
Darryl, There's no data in the output as if olsr is not running at all--shown in the support dump. The olsrd process exists, there's log output, but no smoking gun that pops out. Something unusual in that it starts up twice in 10 seconds, but acts as if it is not running at all. hotplug issue? Conrad, anything jump out to you?
Dave, what kind of switch do you have this plugged into? I see it has a 192.x.x.x address from your home network.
Joe AE6XE
We aren't capturing STDERR in the supportdump. That's what we're interested in.
(the ps command does show olsrd running)
ie. 1734 root 1660 S /usr/sbin/olsrd -f /var/etc/olsrd.conf -nofork
Joe I am using a Netgear GS105Ev2 switch that is configured with Vlan for Lan and Wan connections.
Darryl, I will do that either tonight or tomorrow. I have the node rolled back to 3.10.0, but I do not mind doing some leg work to try and figure this out. Now normally I would assume the problem is on my end (PEBUAK). But 2 other locals having the same issue, I am going to make a phone call today and get some details on their hardware and see if they can send me the support dumps so I can post it. I am relatively sure that Richard is running an Bullet M2, not sure what Rich is running, but they both had problems with OSLR not running messages.
Dave
Actually when I flash the node to the beta firmware I can open port 2222 and provide the login to one of you guys so you can SSH into the node.I also have a port redirect through my dynamic DNS service that will allow access to the admin page of the node from the internet. Just let me know if that is easier or not.
Thanks
Dave
Thanks Dave. That will help. Send me an email and I will send you back my SSH public key that you can load into your node (on the Admin page). No password would be required then. k5dlq@arrl.net
Hi Dave, I found your N6DLH-1 node running on CH2 (not Ch3).
I changed the N5DHL-100 node to Ch2 and I can see/connect to it just fine. No OLSR errors and it appears to be working fine.
Can you check the channel settings on N6DLH-1 to verify ch2 or ch3?
You MAY be experiencing the Linksys “channel drift” hardware bug.
Darryl got me strait after my stupid oversight. After this flash of the Beta Build, the OSLR was working fine on the negative channel, so not sure what was happening. Thanks you to everyone.
Dave