Not 100% sure, but I may have found a bug. I was in my setup page and making a change, I think it was to the number of users. I clicked save. The page spent a long time waiting to reload. After about 15 minutes I just closed the window. Now I can't get back into my node at all from the web page perspective (status/setup/supporttool). The meshchat is running but I can't get into it at all.
So one question, did I uncover a bug? (Or did I do something stupid?)
Second question, how do I recover it?
--Chip/N1MIE
So one question, did I uncover a bug? (Or did I do something stupid?)
Second question, how do I recover it?
--Chip/N1MIE
Hi, Chip:
I do not recall ever setting the number of users on a node running AREDN firmware.
"Now I can't get back into my node at all from the web page perspective (status/setup/supporttool)."
A web browser is not the best choice as a trouble-shooting tool.
"The meshchat is running but I can't get into it at all."
Are we talking about trouble with an AREDN node or a Meshchat service?
Is this Meshchat running on your hAP-ac3 or on your Raspberry Pi?
73, Chuck
If not the web browser, then what? I was unable to connect via telnet or ssh or anything else.
The meshchat is running on the hAP AC3. And it was sort of working. I looked at it closer. The page loads but it never sends a message. So perhaps it is just in the web cache. Not sure.
If so then your node's entire LAN will be different. Have you tried disconnecting your computer from the node and then reconnecting? Or disabling your computer's network interface and then re-enabling it? That will force your computer to ask for a new IP address from your node.
I thought I needed to have a static IP if I wanted to be able to get things to a specific computer. I'm going to describe because I don't want to confuse things with misuse of terminology on my end.
I have a Raspberry Pi connected to a network switch (per the directions to do the initial firmware update on my Mikrotik router). The network switch is connected to the mesh router (Mikrotik hAP ac3). At some point the mesh router will be connected to a mesh network. Once that happens I may want to be able to have services running on the RPi that other folks can reach (chat, mail, video, web server, whatever). Don't I need a static IP on the RPi so that the mesh router knows where to direct incoming traffic that needs to be handled by the RPi? If I want to access something out on the network using the RPi, the mesh router doesn't need to have a static IP for the RPi, but if there is something incoming I think it would. Am I explaining that well? Also I'm thinking of things that won't be happening any time soon. There are no other mesh routers within RF range of me at this moment. There are a couple in RI I might be able to reach once I have an external antenna/router (it's on order). But that is also only a maybe at this time.
Anyway, I've only had this router running for a couple of days, so I'm still very new. I had experimented with mesh networking back in the hsmm days, but never got more than establishing my own small mesh network. I am looking forward to growing the network in my region (New England), but that will take some time.
Thanks again for the quick help and the patience with me.
Orv W6BI
Ala...