Hi, still struggling to make sure my old NanoStations XM resist tech
evolution : )
Ilario Gelmetti:
On 5/2/21 12:33 AM, amuza wrote:
Ilario Gelmetti:
On 5/1/21 12:40 AM, amuza wrote:
I followed your recommendations to install my
nanostation M5 XM and,
after several issues, I managed to do it. However, it has no wifi.
Any advice on how to troubleshoot it?
I ssh it through ethernet and see memory is ok (it is indeed an XM!),
wifi is enabled (etc/config/wireless shows option disabled 0), and the
lime-autogen file shows the same contents as a healthy nanostation M5 XW
that is working ok.
Hey Amuza!
Interesting that the wifi is not working... :/
Could you upload somewhere (any pastebin service will do) the output of
the lime-report command?
Maybe it is not present in your device as it was not included in the
really minimal install...
In this case, take the installable package from here (and install it
with opkg):
https://github.com/libremesh/lime-feed/tree/gh-pages/v2020.1
or just download the only lime-report file from here:
https://github.com/libremesh/lime-packages/tree/master/packages/lime-report…
Hopefully this will help understanding what's happening there...
Thank you Ilario. Please find it attached.
The lime-report output looks good to me...
The other mesh nodes are even possible to reach through the wifi mesh
interface.
Please remember that the AP interface is on the 5 GHz band, so that for
seeing it you'll need a 5 GHz-capable client device.
Yes, I have tried with two different 5GHz-capable clients, SSIDs are not
seen.
And also check running "opkg list-installed"
if uhttpd is installed. It
should not be there, as all the LibreMesh-related packages depending on
it are deselected (lime-app, check-date-http and firstbootwizard).
In case it is, means that the ".config" file in your compilation
directory needs to be deleted and the "make menuconfig" issued again
selecting again the minimal packages set.
"opkg list-installed" does not show uhttpd.
Perfect :)
Still, from the "free" command in lime-report seems that there are just
4 MB of free RAM, I'm not sure if that's enough when the antenna will
have some activity...
Maybe disabling the AP and APname (if you don't use it anyway...) could
save more RAM?
The way to disable AP and APname is to add a configuration line in
/etc/config/lime-node in the wireless section, like this:
config lime wifi
list modes 'ieee80211s'
which will overwrite the whole "modes" list effectively removing the
other two default entries (ap and apname).
Thank you, that is a good idea. Actually a very good one, because
disabling AP and APname makes no difference. I mean I was not able to
see any SSID anyway, that never worked.
Meshing, which is the use I want now for these Nanostations XM, seems to
work.
Another interesting option for having lower RAM usage
(and a simpler
architecture) would be to have a network with only one of the two
routing protocols but this currently does not work. If you're interested
in this check out some related issues:
https://github.com/libremesh/lime-packages/issues/666
https://github.com/libremesh/lime-packages/issues/468
It's a pity that is not implemented yet. I think it would save many
resources to have only-layer2 nodes in the inner network and layer2+3
nodes as edge/border routers at the outer network.
If you happen to have any other idea to save memory please let me know.
I still do not understand why I see 4 'adhoc' wifi options, I thought
this 802.11s thing replaced 'adhoc'.
And the same happens in the network config, I see many options and
protocols about things that I thought they were not needed (bmx6, bmx7
and olsr).
Weren't BATMAN and Babel the only needed protocols?
As far as I
know, the Main port of a LiMe Nanostation has always been a
DHCP client, hasn't it?
I tried to verify this checking in the OpenWrt code, and it looks like
this changed over time, can anyone confirm??
In the original implementation (I just found it for the XW model) seems
that the Main (eth0.1?) was LAN and Secondary (eth0.2?) was WAN:
https://git.openwrt.org/?p=openwrt/openwrt.git;a=blobdiff;f=target/linux/ar…
but at some point seems that this got inverted (is Main eth0 and
Secondary eth1?):
https://github.com/openwrt/openwrt/blob/openwrt-19.07/target/linux/ath79/ba…
Is this right?? Weird and annoying that these things can change.
Currently, as far as I can see, with the current version of LibreMesh, a
Nanostation M5 XM has the following configuration in their ports:
- DHCP server in its "Main" port.
- DHCP client in its "Secondary" port.
I had always found a DHCP client in the "Main" port of Nanostations M5,
but I think I only played with XW. I do not know how XM ports were before.
On the Nanostation M5 XW, I played with it few months ago and and I
think they still had a DHCP client in its "Main" port.
Ciao!
Ilario
Thank you again!!