Broadband-Hamnet™ Forum :: Firmware
Welcome Guest   [Register]  [Login]
 Subject :Changed Node to "Standard Access Point" - can't get out of i.. 2014-02-16- 00:41:06 
W4LLZ
Member
Joined: 2014-01-25- 09:13:12
Posts: 11
Location

Help!

I switched my Mesh Node to "Standard Access Point" within the "Basic Setup".  Couldn't get it to work so I attempted to connect to my node to switch it back to "Mesh Node" using the "http://localnode.8080" entry and it doesn't work. I tried http://<callsign>.8080 as well and that didn't work either.

How do you get back into Mesh Node from Standard Access Point?  Is it permanently stuck in "Standard Access Point" mode now?

IP Logged
 Subject :Re:Changed Node to.. 2014-02-16- 06:15:13 
KF5JIM
Future Astronaut
Joined: 2013-07-17- 12:13:36
Posts: 250
Location: Nederland

From doing a quick google search for, "HSMM-MESH Access Point," here are the first two returns:

Also, from the help file on the mesh node there is a nifty section that talks about just this:
Mesh Access Point considerations

When a device is configured in Mesh Access Point mode it is essentially 'transparent'. You are going through the device to reach a mesh node, and there is no need to get to the device unless you wish to change its configuration. When the time comes to reconfigure a device in this mode be aware that it is not running its own DHCP server because that is the job of the mesh node it is connected to. You will need some other way to configure your computer's network interface. There are two ways to do this:

  • Manual configuration
    Connect only your computer to the LAN port. Set your IP address to 172.27.0.100 and your netmask to 255.255.255.0. No other settings are needed.
  • Automatic configuration
    You will need another mesh node that is using NAT mode on its LAN, and using the default LAN IP address of 172.27.0.1. Both of these are required, otherwise this method will not work. Connect both your computer and the LAN of the Mesh Access Point to the LAN of the mesh node.

In this mode the default IP address on the LAN port is 172.27.0.2. After one of the above steps you should be able to send your browser to http://172.27.0.2:8080/. If you used automatic configuration you should also be able to go to http://localap:8080/. Like the name "localnode", an automatically generated name exists called "localap" which is set to the localnode address plus one, but only when the node LAN mode is set to NAT. If you changed the default IP address of a Mesh Access Point you will have to modify these instructions accordingly.

IP Logged
My opinions and views expressed here are solely my own.
 Subject :Re:Changed Node to "Standard Access Point" - can't get out o.. 2014-02-16- 15:08:13 
W4LLZ
Member
Joined: 2014-01-25- 09:13:12
Posts: 11
Location

Thank you!  I got it back....finally. 

I followed the instructions inserted in your post for "Manual Configuration" as far as setting the IP Address and netmask manually.  (did a search on google to find out how to manually change those).

Then using the second article you hyperlinked to in your response, (ie., connecting a computer to the LAN port on the access point, and then connecting the mesh-node to access point with a CAT 5 via the LAN ports).  Then I was able to pull up the "lost" mesh node and get into it and change it back from an Access Point to a Mesh Node.  At that point, I thought everything was ok.  It wasn't - I had to go back and change the IP Address / Netmask back from the "static" setting to "obtain IP Address Automatically".

I did a search on "How to Assign a Static IP Address" and got instructions on how to do that. 

Took me a few hours to get it - but its done.  Won't do THAT again.  Thanks.

IP Logged
 Subject :Re:Changed Node to.. 2015-06-29- 15:55:01 
WB0NIU
Member
Joined: 2014-05-07- 21:44:09
Posts: 11
Location
This thread seems to morph from "Standard Access Point" to "Mesh Access Point". I have a Standard Access Point (loaded with firmware version 3.1.0) that is working as I set it, but I can't connect to it to make changes. Connected as noted above, it does not respond to http://172.27.0.2:8080, or localap, or anything else I can think of. The mesh node in NAT mode does respond to 172.27.0.1:8080 as expected. Help!
IP Logged
 Subject :Re:Changed Node to "Standard Access Point" - can't get out o.. 2015-06-29- 18:58:23 
NG5V
Admin
Joined: 2010-01-18- 23:06:23
Posts: 43
Location

Getting a node into the Standard AP or Mesh AP mode and losing control of it is a very common problem.

Keep in mind that both of those operating modes turn off the DHCP server in the access point node. this is mentioned in the help screens within the mesh node. There is some good reading there. You can get past this by connecting the node with the problem to a normal mesh node back to back on the lan.  To do this, take a cat5 cord and plug into one of the 4 lan jacks on one device and connect the other end to the same set of jacks on the other device. 

Plug your control computer into a lan jack on either node and use http://localnode:8080/ to log in. You can then hop over to the other device and enter it's management screen to change the operating mode back to mesh node. Do not use the WAN plug on either device.

Remember that when you first load firmware, make a change in which operating mode you are using, or do any of several other things, the IP address will need to change. Be sure to remove the network cable on your control computer, wait 30 seconds and then insert it again. In most cases, you will have to close your web browser and then restart it after you see the new IP address issued (network cable connected) notice.

IP Logged
 Subject :Re:Changed Node to.. 2015-06-30- 02:27:30 
WB0NIU
Member
Joined: 2014-05-07- 21:44:09
Posts: 11
Location
Hi, Thanks for the reply! >You can then hop over to the other device I'm having a problem with this step because I don't know the address of the other device. I tried localap:8080 and WB0NIU-2401:8080 (the lost node's name). Neither worked. I also tried putting the mesh node in NAT mode, then using the fixed IP's, with the computer at 172.27.0.100. I tried: 172.27.0.0:8080 through 172.27.0.4:8080 (.1 was the mesh node), localap:8080, WB0NIU-2401:8080. None of these worked. I also tried the fixed IP's with only the lost node hooked up, and connected either to a LAN port or to it's wifi. Thanks for your continuing assistance, Erik
IP Logged
 Subject :Re:Changed Node to.. 2015-06-30- 02:27:40 
WB0NIU
Member
Joined: 2014-05-07- 21:44:09
Posts: 11
Location
Hi, Thanks for the reply! >You can then hop over to the other device I'm having a problem with this step because I don't know the address of the other device. I tried localap:8080 and WB0NIU-2401:8080 (the lost node's name). Neither worked. I also tried putting the mesh node in NAT mode, then using the fixed IP's, with the computer at 172.27.0.100. I tried: 172.27.0.0:8080 through 172.27.0.4:8080 (.1 was the mesh node), localap:8080, WB0NIU-2401:8080. None of these worked. I also tried the fixed IP's with only the lost node hooked up, and connected either to a LAN port or to it's wifi. Thanks for your continuing assistance, Erik
IP Logged
 Subject :Re:Changed Node to.. 2015-07-02- 18:44:56 
WB0NIU
Member
Joined: 2014-05-07- 21:44:09
Posts: 11
Location
SUCCESS! Thanks to a tip from Jim, K5KTF, I found the node at 172.27.1.1:8080.
IP Logged
Page # 


Powered by ccBoard


SPONSORED AD: