Noob to Ham mesh here so please forgive me if I've missed something obvious (been trying to address this on my own for several hours) or if I've posted in the wrong forum.
I have a new Ubiquity NanoStationM5. I have successfully flashed the "factory" and the latest firmware. The status page is showing "firmware version: 3.24.6.0" and "model: Ubiquiti NanoStation M5 XW"
The unit is in setup mode and has
Issue #1 - the LAN ports on the unit do not seem to be doing anything (certainly not providing anything via DHCP). I am connecting to the device via the MeshNode2G WiFi and that IS serving DHCP.
Issue #2 - if I take the key "setup" step of changing the password, the device reboots but (2a) LAN ports still do not work, (2b) device no longer broadcasts an SSID so I can't access over WiFi, and (2c) even with a wired connection (I have tried direct and via a dumb switch) and a local IP set to be on the 10.3.x.x subnet, I can't ping the device's supposed IP (10.3.34.137)
What am I missing?
73, W9PJG
I have a new Ubiquity NanoStationM5. I have successfully flashed the "factory" and the latest firmware. The status page is showing "firmware version: 3.24.6.0" and "model: Ubiquiti NanoStation M5 XW"
The unit is in setup mode and has
| 192.168.1.1 / 24 MeshNode2G |
Issue #1 - the LAN ports on the unit do not seem to be doing anything (certainly not providing anything via DHCP). I am connecting to the device via the MeshNode2G WiFi and that IS serving DHCP.
Issue #2 - if I take the key "setup" step of changing the password, the device reboots but (2a) LAN ports still do not work, (2b) device no longer broadcasts an SSID so I can't access over WiFi, and (2c) even with a wired connection (I have tried direct and via a dumb switch) and a local IP set to be on the 10.3.x.x subnet, I can't ping the device's supposed IP (10.3.34.137)
What am I missing?
73, W9PJG
Yes, IIRC, the LAN port on a Nanostation has only DtD tagged on VLAN2.
The Nanostation's LAN network is available on the POE injector.
Issue #2 - if I take the key "setup" step of changing the password, the device reboots but (2a) LAN ports still do not work,
(2c)
...Try with your computer (as a wired connection or via a dumb switch) connected to the POE injector's LAN port.
Seek a DHCP IP address from the Nanostation.
I hope this helps,
Chuck
LAN AP SSID:
192.168.1.1 / 24
MeshNode2G
My Nanostation in setup page see image.
What is 'setup mode' ?
73, Chuck
I am now getting the following and can connect via WiFi but still can not get a wired LAN DHCP; will spend more time tomorrow
Again thanks for the assistance
It seems that you did not complete the AREDN firmware installation.
file:///home/gelmce/Downloads/Ubiquiti_N_First_Install_Checklist-2.pdf
I cannot assist you until the installation is complete.
73, Chuck
My device/software now seems to be in a state where:
It has a new password (not the default password)
It is broadcasting "MeshNode2G" as an SSID
It has a LAN network address of 192.168.1.1 and a mesh address of 192.168.2.1
It is serving DHCP over LAN WiFi but not over wired ethernet
It has not changed its IP addressing pattern to 10.x.x.x
It has retained my name, callsign, and lat/lon/grid square
Please advise on how I might get this into the intended production state
failsafed the M5 and follwed every step
on second to last step, unit rebooted (power LED, LAN1 LED, and rightmost signal LED are on)
M5 Main ethernet port wired to POE port on POE injector, laptop Ethernet (only active network port on laptop) wired to LAN port on POE injector
Laptop requests new DHCP lease from connection on laptop ethernet port; gets nothing and self assigns an IP
M5 is not broadcasting an SSID
In short, I've completed all the steps but the M5 is unreachable by any known methods
channel: 149
channel width: 10 MHz
+1 with Ed.
After loading the factory.bin, changing the password and rebooting,
The Nanostation M5 should return on channel 149 at 10 MHz with
SSID: AREDN-10-v3 in ad-hoc mode...not Access Point mode nor Wi-Fi Client mode.
A computer's Wi-Fi device should not be able to connect to (or display) the M5 because, by default
There should be no IP addresses in 192.168.0.0/16.
There should only be 10.0.0.0/8.
If you had a programmed VLAN switch, then maybe 192.168.0.0/16 or your ISP's assisgned address.
However, you did not mention a VLAN switch.
Something is amiss.
:-|
73, Chuck
The image on post 6 is really fuzzy, but it looks like the node is reporting a mesh address 10.x.x.x so why are you still talking about 192.168.x.x? If you could get as far as showing the setup page you must have fully installed the firmware sysupgrade.
Sometimes a laptop with two network cards will get confused when you try to connect to a new mesh node. The port was getting a 192.x.x.x and if you don't remove the cable and TURN OFF THE OTHER CARD (wifi) it will not release the old ip addresses. Try turning off the wifi and make sure the ethernet port is set for DHCP. Don't proceed until your ipconfig (or whatever it's called on a mac) shows a 10.x.x.x address.
I also don't understand you saying you are connected via wifi. I don't see a wifi capability on the Nanostation M5 specs. It has LAN where Chuck told you and no wifi, only MESH radio VLAN1. So if you are connected via part15 wifi you are going through some other equipment which might be confusing who gets to be the router. The SSID you report is not possible with a fresh AREDN install, you're getting an SSID from a different source.
If this doesn't help ... the only other way I can see getting connected to the device is to get another mesh node, set it to the same channel and see if you can create a mini network of mesh then access the node that way.
Ed
I will take a look at all of that.
I can report with certainty that the only way I was able to display the setup page was by being connected, over WiFi, to the M5, which was advertising an SSID of "MeshNode2G." I am certain that SSID is not being broadcast by any other device. I can get the M5 to broadcast it by using the failsafe 15-second reset. My home network is a 192.168.10.0/24 network so not a source of contention with the 192.168.1.x or 2.x networks that the AREDN seems to use in setup. I'm very confused by this behavior and the inability to get a DHCP lease from a direct wired connection. I have another device on order and will try to create a mini mesh.
It would be helpful to me if someone could explain what is going on with that "MeshNode2G" and why it is present then absent.
I appreciate the help.
73, Paul
Because after first boot,
the Nanostation M5 is on channel 149 at 10 MHz bandwidth with SSID: AREDN-10-v3.
Your computer's Wi-Fi device cannot decode 10 MHz bandwidth Wi-Fi.
73, Chuck
Grasping at straws ... Ed
I am guessing, but not assuming, that there were additional changes made,
at first boot, beyond node name and password.
73, Chuck
I understand that the radio is changing to a mesh frequency and channel
I do not understand why I can't get DHCP LAN server in either first boot condition or subsequent boot condition
so that is the problem I would like help with - is my assumption that the LAN port is supposed to be serving DHCP correct?
And by "LAN Port" I mean the "LAN" port on the PoE injector. My NSM5 "Main" port is wired to the PoE port on the injector. Laptop wired to the "LAN" port on the injector. All other network interfaces disabled. Laptop clean boot then enable wired ethernet only. There is LAN port activity but no DHCP serving.
Ed
I plugged my computer's ethernet port into the LAN port of the M3's POE injector.
My computer is set to request an IP address via DHCP.
- I navigated to Advanced Configuration and clicked 'Reset to Firstboot'.
- I disconnected my ethernet cable and waited for my computer to lose its IP address.
- I reconnected my ethernet cable and in about 2 minutes my computer got an IP address from the M3 in 192.168.1.0/24.
- I change the node name and changed the password and clicked 'Save Settings'.
- The M3 rebooted.
- I disconnected my ethernet cable and waited for my computer to lose its IP address.
- I reconnected my ethernet cable and in about 2 minutes my computer got an IP address from the M3 in 10.0.0.0/29.
- I navigated to localnode.local.mesh and my M3's '/status' page was displayed.
I did step 1. and 2. and moved the ethernet cable to the LAN port on the Nanostation M3.I did steps 3 through 7.
I got the same results.
73, Chuck
On my Nanostation M5, I pressed the reset button for 15 seconds for the failsafe.
As expected this returned the unit to the base image.
I disabled all network ports on my laptop and I disconnected all cables from laptop and M5.
I confirmed (via ifconfig) that all network ports on the laptop were "inactive" and none have any IP addresses assigned (other than the default loopback 127.0.0.1).
I plugged the M5 Main port to the PoE port on the injector and allowed the M5 to boot up fully.
I then connected laptop ethernet port to LAN port on the injector.
I then made the LAN port active on the laptop and confirmed visually that the LAN1 LED on the M5 went from dark to lit and showed several flashes (ethernet port on laptop and M5 definitely exchanging data).
The laptop is configured to request an IP address via DHCP.
After several minutes the laptop defaulted to a "self assigned" IP of 169.254.85.108 indicating that it was not served a DHCP IP from a DHCP server.
The M5 was advertising MeshNode2G as WiFi. I connected to that WiFi and the laptop obtained, via DHCP, IP address 192.168.1.10 (router 192.168.1.1)
With that connection, I navigated to http://localnode.local.mesh:8080/ and naviagted to navigated to Advanced Configuration and clicked 'Reset to Firstboot'.
I disconnected my ethernet cable and waited for my computer to lose its IP address.
I reconnected my ethernet cable and my computer did not get an IP address from the M5.
I connected via WiFi as descirbed above and got a correct DHCP lease via WiFi.
I changed the node name and changed the password and clicked 'Save Settings'.
The M5 rebooted.
I reconnected my ethernet cable and my computer did not get an IP address from the M5.
I can no longer connect via WiFi.
as described in my prior reply, I've followed exactly the steps you described, changed nothing other than name and password, but can not obtain LAN access to the M5
identical results - no DHCP served in firstboot mode; no DHCP served after password and name change reboot
I suppose it is possible that there is a hardware issue with my specific M5 but that seems unlikely
open to suggestions for other debugging paths
I got nothing else ... perhaps you can share the serial number and MAC address. Either it's defective or there is a recent change to that model device the developers need to look at.
Can you put the stock Ubiquity firmware back on it? Will the ethernet ports work then? Perhaps it's time for a return to the seller ...
Ed
when I boot the M5 into TFTP mode I can't ping it at 192.168.1.20 (yes from a PC on the 192.168.1.0/24 subnet) so I might not be able to re-flash it to the stock firmware; the AREDN admin page doesn't recognize the Ubiquity firmware file so won't let me get it back that way
It seems that you have successfully loaded AREDN factory.bin firmware onto your Nanostation M5 XW.
"The unit is in setup mode and has LAN address:"
Rephrase: The unit is in 'FirstBoot' mode and has LAN address:"
The only thing that should be done in this state is to change the nodename and password.
In 'firstboot' state, the device should have a LAN address of 192.168.1.1 and issuing addresses as a DHCP server.
Issue #1:
(a)If your computer fails to get an IP address via ethernet cable,
please try to link by assigning a fixed ethernet address in the range 192.168.1.2 to 192.168.1.254.
You should be able to 'ping' the device at 192.168.1.1.
Issue #2:
(2a) If the LAN ports (secondary LAN on device or LAN on POE injector) do not offer an address via DHCP server,
try step (a) and report results.
(2b) The device no longer is broadcasting an SSID at 20 MHz bandwidth so it is undetectable from the computer's Wi-Fi device.
The device should be broadcasting an SSID at 10 MHz bandwidth.
(2c) "10.3.x.x subnet, I can't ping the device's supposed IP (10.3.34.137)"
Those values are the proposed values that will be set after you click 'Save Changes'.
Those values are not in effect at this point (firstboot mode).
You are missing getting an ethernet connection between the device and your computer.
If you can get the device into TFTP mode and load AREDN firmware, then
it seems that the ethernet port works as a DHCP client.
It seems that the device is not working as a DHCP server!
Please recheck that you have the correct (factory.bin) firmware for your device.
i.e. Is your device a Nanostation XW, XM, or AC?
If your device is an XW, did you load
aredn-3.24.6.0-ath79-generic-ubnt_nanostation-m-xw-squashfs-factory.bin
?
73, Chuck
I have the M5 back to Ubiquity factory state; all done via ethernet so the physical port works
I will re-attempt the AREDN steps
My M5 is an XW and I used the following files the first go-around:
aredn-3.24.6.0-ath79-generic-ubnt_nanobeam-m5-16-squashfs-factory.bin
aredn-3.24.6.0-ath79-generic-ubnt_nanobeam-m5-16-squashfs-sysupgrade.bin
as those are what the chooser dialogue on the website suggested
I will try the file you suggested instead
W9PJG:
Please, URL?
http://downloads.arednmesh.org/snapshots/SUPPORTED_DEVICES.md
ubnt_nanostation-m-xw
73, Chuck
see my subsequent reply - I flashed the other firmware and still no luck on the ethernet ports
I successfully flashed aredn-3.24.6.0-ath79-generic-ubnt_nanostation-m-xw-squashfs-factory.bin
My M5 XW booted up and I can "see" activity on the LAN1 port (flashing green LED on the M5)
M5 is not serving DHCP leases over LAN1 (computer requesting a DHCP lease did not receive one)
I manually configured laptop to 192.168.1.254 mask of 255.255.255.0
From 192.168.1.254, M5 does not respond to a ping of 192.168.1.1 (with AirOS it did respond to a ping of 192.168.1.20)
I was hoping the issue was my use of the wrong firmware file but that didn't correct the issue
My M5 is a new "SWX-M5N" and I can confirm from the AirOS page that it is an XW
Pshew!
We have ridden this horse into the ground.
I am grasping at straws.
Perhaps, try earlier releases, say 3.24.4.0, 3.23.12.0, ...
Although, the world map indicates that there are ~90 Nanostation M5 XW nodes and
50+ are running current stable.
I am baffled.
73, Chuck
I have a MikroTik unit coming that will hopefully yield better results and maybe I'll be able to "see" the M5 in its current condition on the mesh
73, Paul