I have 2 Rocket M2 XW (verified as XW through AirOS prior to flashing) - initially had AirOS 6.1.5 on each unit. I downloaded the appropriate firmware (checked it 3 times prior to flashing the units) and flashed - the flash completed and the devices rebooted. Now NEITHER of the units is issuing an IP address via DHCP. Have used mulitple laptops to try and get a lease but "no go."
The units both actually start up, Green light on the left, a green network light when the cable is plugged in, and after booting, a solid green light on the right-hand side as well.
Here's the good news - they're not bricked: I *can* connect to the units by attaching via WiFi to SSID MeshNode and then browsing to http://localnode.local.mesh:8080.
I'm absolutely, 100% positive that I flashed the units with the proper firmware from the matrix. I have done no further configuration (each unit is still at the "just flashed" stage and are asking to change the root password on the home page.
Obviously, the ethernet ports aren't bad because I used a cable and TFTP to flash them.
Any thoughts or ideas on how to salvage these?
N5GER, We need the /etc/board.info file from AirOS off this device -- don't yet have the specific power settings for this device. For the moment, to get this working, load the "loco-m-xw" image instead to get the ethernet ports working. Then, you'll need to edit /www/cgi-bin/perlfunc.pm to add a section that looks like this:
'0xe868' => {
'name' => 'Rocket M2 XW',
'comment' => '',
'supported' => '1',
'maxpower' => '18',
'pwroffset' => '10',
'usechains' => 1,
'rfband' => '2400',
},
It will then function until we confirm power setttings and get this into the nightly build.
Joe
Joe,
This is a stupid question, but ...
how do i get into the AREDN software on the node and edit the perlfunc.pm file?
FWIW - these boards have no usb header on them either.
N5GER, this does require basic unix knowledge with use of telnet and vi. Maybe there is someone local with this knowledge if you are still soaking it in?
To access the node, from the attached laptop: "telnet localnode" Once logged in as "root" with your password, "vi /www/cgi-bin/perlfunc.pm" and edit the appropriate lines to ensure this Rocket M2 XW definition exists (there's an entry like this for every supported device, so you can edit one that is close to this model). Just have to figure out the secret 'vi' commands to do the edit :) .
Joe AE6XE
Got it - just wasn't sure whether the AREDN software had telnet ports open by default. Piece of cake. Thanks for all of your help. Wish I had saved one of the two - but I didn't know you didn't have a configuration for it yet.
N5GER, I have the AirOS power settings now. The correct and confirmed settings should be:
'0xe868' => {
'name' => 'Rocket M2 XW',
'comment' => '',
'supported' => '1',
'maxpower' => '21',
'pwroffset' => '7',
'usechains' => 1,
'rfband' => '2400',
},
So to confirm (please reference attached file):
I initially loaded the software highlighted in YELLOW (aredn-3.18.9.0-ubnt-rocket-m-xw-factory.bin)
Currently I can only access the node via the WiFi from the AREDN node.
Now, to make it work, I should us the sysupgrade procedure from the AREDN node and flash it with the software circled in RED (aredn-3.18.9.0-ubnt-loco-m-xw-sysupgrade.bin).
I should NOT use the sysupgrade circled in blue.
Once i get this done, I should make the power edits and all should work (DHCP, etc.)?
Yes, this path and steps are correct for the 3.18.9.0 version. Alternatively, tomorrow the definitions for Rocket M2 XW should be in the nightly build version available. The nightly build options (still using the local-m-xw flavor or the equivilent red circled version) will give you more improvements and fixes and considered as stable as the 3.18.9.0 release.
Joe AE6XE
Thanks, Joe. I'll give that a shot in the next day or two.
I don't have another one to get you that info - hopefully someone else has an unadulterated unit.
Gary
Between you and KE5GDB, the 2 known owners of a Rocket M2 XW, I'm hoping to obtain this information to be able to get into the nightly build. Maybe you are on the same mesh island and know each other already?
Joe AE6XE
sadly, no.
To make things easier working directly on nodes, you might consider using Winscp. It has an easy to use text editor for modifying files.
Port 2222 for AREDN flashed nodes.
I would continue on with the setup information and see what happens with the ethernet. In the setup state, the node is still on 192.168.1.1 and then changes to 10. with dhcp service after initial setup.
Worst would be be the need to reload firmware.
Sometimes browsers hang on to strange stuff in their cache while flashing nodes. I prefer to use Chrome, but sometimes a 2nd opinion helps.
I had a similar problem with an Ubiquiti Rocket M2 (another person with an XW) a few hours before this post on the Forum; and to my surprise I found this post later in the day,with the answer. Thanks to N5GER for the post and to AE6XE for the solution. I made the modification using "vi" and it worked like a charm. Since then, I updated using the nightly update; and surprise, it works as well.
If you used the page "http://downloads.arednmesh.org/firmware/ubnt/html/stable.html" and selected "sysupgrade" or "factory" for the Rocket M2 (XW), would it work, or would you have the same problem I had before, with the hardwired LAN not working? I am curious if those files have been fixed?
We had a mistake in the 3.18.9.0 downloads page. The Rocket M2 (XW) is not supported under the 3.18.9.0 release. It is now in the nightly builds.
The downloads page has been corrected.
I applied last night's Nightly Build to both nodes and they're running like champs.
Thanks Joe and K5DLQ for all the help!
Hi All,
I was following this thread, waiting for my Rocket M2's to arrive from Amazon.
Since there were a progression of steps presented over time, can I get a summary of where things should be as of today (Jan 27th 2019) ?
Here's what I did...
1) downloaded nightly build aredn-648-ef24633-ubnt-rocket-m-xw-factory.bin
2) reset and uploaded the firmware via tftp
3) the lights appear to be operating correctly
4) LAN port does not provide DHCP
5) Can connect to MeshNode2G via WiFi and see the AREDN config web page, can also connect via Telnet (over WiFi)
6) Checked perlfunc.pm and the additions noted above are there
Should I be using a different build (i.e. Loco?)
Thanks in advance,
Jay, KA1PQK
I'll follow up with a little more info...
Just tried using the Loco nightly image: aredn-648-ef24633-ubnt-loco-m-xw-factory.bin and the LAN port works as expected.
Seems like something is configured wrong in the Rocket M2 XW image?
--Jay
The Rocket M2 XW has a different ethernet chip than the older XM hardware. The driver for this chip is in the loco-xw image and is not built into the rocket-xw image. The images for each model to use are found in the README from the nightly build. The nightly build may be in advance of what the documentation of what is in other documentation.
Nightly build README (scroll down): https://github.com/aredn/aredn_ar71xx
Joe AE6XE
Thanks!
I should have read the README...
--Jay