I tried to load the downgrade using the AirOS but it tells me that I have the wrong firmware. Never used the TFTP I don't see the Bullet M2 with the XW fireware on the Ubiquity fireware list with version 5.x.x.
Ideas
Thanks
Rick Bunn
N4ASX
ALexandria, VA
You are here
Bullet M2hp with XW firmware
Thu, 10/04/2018 - 13:26
#1
Bullet M2hp with XW firmware
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer
It doesn't exist. You can't downgrade AirOS on that device to a 5.5 version. You must directly TFTP AREDN 3.18.9.0
I think the issue here is not the method of loading, but rather the fact that there is no bullet-m-xw firmware -only bullet-m.
Does single Bullet version listed cover both the XM and XW Bullet hardware?
oh! i'm sorry. I get it now. Need to check on that.
Yea, we've not see the Bullet M2 XW hardware before. Need the AirOS board info file and dmesg output. Then, can determine if another existing image will work or if we need to do some surgery in the code. Best guess, you could try the Rocket-m-xw image. It is the bullet image + USB drivers. (some of the older rocket models had a USB port). ...standard disclaimer that you might brick the device :) .
joe AE6XE
Rick,
Go ahead and open a new issue on this on https://github.com/aredn/aredn_ar71xx/issues
Please include the following from AirOS:
- the file: /board.info
- the output of the command: dmesg
Attach those to the issue when you open it.
Thanks
I added a ticket for the Bullet M2 XW with the board.info and dmesg information.
Good Afternoon everyone, I have a brand new Bullet M2HP XW that won't load either, but I'll take the chance of bricking it if a nightly build is done for it. Of course, I didn't know it was going to be a XW when I ordered it... Got a POE, airGrid antenna, and the Bullet M2HP for a good price...
Please advise,
Allen
Allen, the Bullet M2 XW is defined and working in the nightly build. Load the rocket-m-xw image.
Joe AE6XE
Roger that, didn't want to just willy-nillly load something... Will reply back if it works for me. This is my first device, so I hope I don't screw it up.
Thank you,
Allen
Well after verifying ping to 192.168.1.20 worked, I was able to use TFTP2 program to transfer the Rocket M2 XW firmware to the Bullet M2-HP device. Worked first try (helps to have correct firmware, lol). BUT... After going through the setup and changing to callsign and password, Bullet looked like it did a reset. I can reach the node, but when I type the user id and password, I'm locked out...
Please help,
Allen
Hey guys, I got it. Didn't realize root part is still used but it works with my new password. All good now. Just need to get it onto a pole this next weekend.
Thanks guys,
Allen
Hello everyone,
Was able to got to lowes today and buy 2" EMT conduit and stuff to get Bullet and antenna up. Connection to Bullet seems perfect, on WiFi scan I see lots of otehr radios, but no luck linking to any AREDN node. I'll attach files to help out...
Thank you for all of your support,
Allen
Allen, I'm not familiar with your area, but most AREDN groups are using 10MHz or 5MHz channel widths. These widths offer higher throughput of data over a 20MHz channel for the longer distance links generally in use. It appears you are on 20MHz channel width in basic setup, since the received signals are standard Wifi. Wifi Scan shows only signals for the channel width the node is set to.
Joe AE6XE
Ok, I'll try 10MHz... thank you for your time Sir...
Allen
Yeah, I'm up and running now, even connecting to local Las Vegas Valley Mesh Network... Wow, what a lot of settings and determination to get it done right...
Thank you all that have help. I'm hooked now...
Allen
Congratulations! But, just in time to see Potosi drop off-line for unknown reasons today at approx 1620 local here in LV.
- Don - AA7AU
What a bummer, just my luck....
Allen
Potosi stopped responding at approx 1620 yesterday pm. However, it appears to be still powered up and on RF, three of us here in LV still see Potosi by using the WiFi scan from our nodes. It is just NOT handshaking and OLSR can't find it so there's no network route as the IP doesn't actually exist on our network. Look for a line in your scan results which includes this as hostname 10.54.129.153 and this MAC address DC:9F:DB:36:81:99 - if you see it, please report back the strength (-db, first column under "sig") you get. It's at -72 here.
There are other nodes scattered about the valley, depending on your location but apparently there currently is no overall mesh here as Potosi was the central "location". Any of the nodes which you might see here where the names include "HARC" are part of our Henderson ARC and should have an instance of shared MeshChat running - try that.
Good luck - we're all struggling,
- Don - AA7AU
If you have a direct RF path to Potosi, then try to access it at "http://10.54.129.153:8080". Grab a support download data file, hopefully via RF, or if you have to go to the site, get the support data from a locally connected laptop on the LAN, before rebooting the node. Let's see what is going on. If there is an IP address, then reboot your local node, to be sure the arp table is cleared, do another wifi scan -- does it still show an IP address in wifi scan? If so, I'd suspect that OLSR is still running and the signal is too weak -- power or antenna problem? What firmware version is it running?
Joe AE6XE
This node belongs to Don Hill (who knows it's down) but it was installed by a local friend iof his here who has access to the site up at Potosi.
Potosi node is still on RF with pretty good strength but they only way we know that is from the WiFI scan - showing its MAC address. It is NOT connecting over the mesh whatsoever and does NOT show up in Mesh Status etc. This was sudden, late yesterday pm. It does NOT respond to any IP access. There is a node with a dish at another location which always seemed to have 90-100 LQ and it's not showing up there either (but I have limited access there),
WiFi scan shows MAC and some see the IP as the hostname, and others see question marks as the hostname. I moved my 90* sector away from Potosi such that it's now on my very left hand edge and I still get this from a WiFi scan:
For some strange reason, it's running 3.18.9.0RC1
If I had physical access to it, I'd power cycle it. But I'm told that this mtn top is difficult to get to with the storms and the season etc. Going to try to contact initial installer. We've been busy trying to tie other pieces together here today.
What else I can I do/provide?
Thanks,
- Don - AA7AU