You are here

NanoBeam NBE-M2-13 firmware

14 posts / 0 new
Last post
N3KAL
NanoBeam NBE-M2-13 firmware

Hi. I just acquired the nbe-m2-13 as listed on the supported hardware list but it does not appear in the firmware download list.
http://downloads.arednmesh.org/firmware/ubnt/html/stable.html


Since I can't seem to find an actual NanoBeam M5-13 hardware device, I need to ask if this is a typo-error in the web site which actually should be for the M2-13?
Is the aredn-3.18.9.0-ubnt-loco-m-xw-factory,bin file correct for the 2.4GHz NanoBeam NBE-M2-13?

Thanks,
Rob

K6AH
K6AH's picture
The ​nbe-m5-13 is a misprint

The ​nbe-m5-13 is a misprint.  There is no such device.  It should be listed as the nbe-m2-13.  The 5GHz version is the ​nbe-m5-16.  We'll get it changed.  Thanks for pointing it out.  And yes, you've identified the correct image.

Andre, K6AH
 

N3KAL
Thank you for the timely

Thank you for the timely response! I can't wait to get 'meshing'!
Rob N3KAL

K9CQB
K9CQB's picture
RBLHG-2HPnD-XL also doesn't exist

Andre,
I bought a MikroTik RBLHG-2nD-XL thinking that it was just a typo from the Supported Platform Matrix. labeled "​RBLHG-2HPnD-XL." Because the "​RBLHG-2HPnD-XL" doesn't exist anywhere I could find.
I hope this is just a typo and the ​RBLHG-2nD-XL really is supported for nightly builds. However, I do not see it in the nightly builds list.
Please tell me it's not a typo or accidental double-tap on the Supported Platform Matrix for the RBLHG-5HPnD-XL.

Thank you so much,
Damon K9CQB
 

K6AH
K6AH's picture
​RBLHG-2HPnD-XL doesn't appear to exist

It appears the 2GHz version of that device only comes in the non-HP version.  That being said, yours will likely be the 1st  device of its type, so be sure to send Joe a Support File on first boot.

Andre

K5DLQ
K5DLQ's picture
The page has been corrected. 

The page has been corrected.  nbe-m2-13 now.
 

N3KAL
I've downloaded the 'factory'

I've downloaded the 'factory' binary listed above and I can see the Nanobeam with AirOS from the factory v5.6.11 (xw).
My tftp session seems to connect okay but the file transfer timesout. Any thoughts?

  • NBE-M2-13 (Nanobeam 2.4GHz)
  • AirOS v5.6.11 (xw)
    • (I don't believe downgrading is needed with current AREDN firmware)
  • AREDN firmware file aredn-3.18.9.0-ubnt-loco-m-xw-factory.bin per the download page
  • Nanobeam is in the 1-3, 2-4 flash mode
  • Connection: laptop----->POE injector----->nanobeam (cat6 cable)
  • IP laptop is static; I can access from Firefox, sign into AirOS and navigate nanobeam fine



Thanks,
Rob

K6AH
K6AH's picture
What syntax are you using?

What's the syntax you're using for the tftp command?  Here's the approach I use:
First change the working directory to where the AREDN image resides.  In a Windows CMD window it should look like this:

​C:\Users\Andre>cd documents\aredn\firmware\
C:\Users\Andre\documents\aredn\firmware>tftp -i 192.168.1.20 PUT aredn-3.18.9.0-ubnt-loco-m-xw-factory.bin

This works reliably for me.
 
Andre, K6AH
 
K5DLQ
K5DLQ's picture
did you verify that the
  1. did you verify that the device is indeed in TFTP mode?   The signal strength LEDS should be alternating:   1&3, 2&4, 1&3, 2&4, 1&3, 2&4. (if you held the reset button down long enough.
  2. you computer should have an address like 192.168.1.5
  3. ping 192.168.1.20 and ensure a good reply before proceeding.
  4. your tftp client should be in BINary mode.

Are you on on Windows 7, 10, OSX, linux?

N3KAL
I tried both Windows 10 &

I tried both Windows 10 & linux (Mint 19.1).
The following is from win10:
I added both telnet & tftp clients from the Add Windows Features (Microsoft built-in, not 3rd party); I also tried the pumpkin-2.7.3.exe GUI from the ubnt.com recommendation with similar results.

laptop address is 192.168.1.88; subnet is 255.255.255.0 default gateway is 192.168.1.20

ping time is 1ms 4 sent 4 returned 0 lost
I am in the path where the binary file is located.
The 1-3,2-4 sequence is blinking when I execute tftp -i 192.168.1.20 PUT aredn-3.18.9.0-ubnt-loco-m-xw-factory.bin

the sequence blinks uninterrupted and then the timeout occurs with 'Connect request failed'

K6AH
K6AH's picture
Confirm your computer is trying to talk to the device you think

After pinging the node, enter the following command in a CMD window:
>arp -a

Interface: 192.168.1.100 --- 0x3
  Internet Address      Physical Address      Type
  192.168.1.1          4c-5e-0c-8a-c5-a5     dynamic
  192.168.1.10        00-14-38-d1-97-e4    dynamic
  192.168.1.11        08-00-37-c4-c4-0b     dynamic
  192.168.1.20        08-00-37-c4-1a-fe      static
  192.168.1.111       e4-8d-8c-db-bc-52     dynamic
 

The response lists the IP addresses of the devices your computer sees on the LAN and their corresponding MAC addresses.  Now compare the mac of the node your trying to load with the one listed for IP address 192.168.1.20

This will confirm whether your computer is trying to talk to the device you think it is.

Andre, K6AH
 

N3KAL
interface 192.168.1.88   --

interface 192.168.1.88   --(my laptop)
192.168.1.20  - dynamic
192.168.1.255 - static
224.0.0.22 - static
224.0.0.252 - static
239.255.255.250 - static

I'm going straight through the POE.  there are no other devices.

N3KAL
When the device is in the 1-3

When the device is in the 1-3 2-4 mode, should I be able to ping it? I can only ping when it is NOT in the 1-3 2-4 mode.
Also, 192.168.1.20 is tied to the WLAN0 MAC not the LAN0 MAC. (I found this in the AirOS interface. Maybe dynamic with Ubiquiti firmware?)

N3KAL
Well, I got it to flash. No

Well, I got it to flash. No clue what changed but it finally recognized the LAN0 port as 192.168.1.20. pinged & loaded.
Now the AREDN screen is coming up with UNTESTED HARDWARE in the web page.  Can still navigate but it is extremely slow.

Thank you for your efforts!
Rob

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer