You are here

Issues when installing 3.23.12.0 into hAP ac lite

12 posts / 0 new
Last post
K5RA
Issues when installing 3.23.12.0 into hAP ac lite

I have gone through the AREDN First-Install process several times to load AREDN  3.23.12.0  into a MikroTik hAP ac lite.  Tiny PXE loads the rb.elf file.  I setup the PC for dynamic IP addressing.  I do ipconfig to see that my PC is on 192.168.1.x subnet, browse to 192.168.1.1 and get the NOCALL-72-217-239 page.  I click red  administration page  link, enter UN & PW, and upload sysupgrade file.  The DO NOT REMOVE POWER screen says page will automatically reload in 5 mins.  The URL on the screen is http://NOCALL-72-217-239.local.mesh:8080/  .  After five minutes, a “Hmm. We’re having trouble finding that site” window opens.   

I have a “dumb switch” in my little system, so thought it might be the Ethernet Network Adapter in the PC.  Restarted (not reset) the network adapter.  Browsing to
 http://NOCALL-72-217-239.local.mesh:8080/  still did not work.

In the past, I was able to reach the node by browsing to  localnode.local.mesh , but the last time , I tried browsing to  http://NOCALL-72-217-238.local.mesh:8080/ .  That brought up the NOCALL-72-217-238 screen with the red  setup page  link.  I assume this page is what is supposed to come up automatically five minutes after the sysupgrade file is installed.  Is it what I am doing, or is there something not quite right in the firmware that the second NOCALL screen does not come up automatically? 
 
Another thing happens down near the end.   After I load my Node Name, new password, location, and set transmit power, I click Save Changes and the node reboots.  I thought that the node would restart with its 10.xxxx LAN address.  I waited a couple of minutes, but the Node Status screen did not come back.  I did ipconfig on PC Command Prompt, and found that machine still had a 192.168.1.x IP.   I restarted the Ethernet Network Adapter. When I checked  ipconfig  again, the PC had a 10.xxx IP address.  Click the <node name>.local.mesh:8080/ link, and the Node Status screen came up. 

Am I asking too much for my “dumb switch” communicate new IP address info from the node to my PC?  Is there a PC setting that I need to change so this will work?
 
Thanks to all who help.

Tim  K5RA
 
KD1HA
KD1HA's picture
Did you move the Ethernet
Did you move the Ethernet cable to port 2 and return the your computer to DHCP?
K5RA
Cable Moved
I did move the Ethernet cable to a LAN port (I think I used P3) after the rb.elf file was loaded, and I set the PC to get dynamic IP addressing.  Both IP and DNS addresses should come automatically.

--Tim K5RA

 
KD1HA
KD1HA's picture
Just to be sure...
Just to be sure, after you loaded the elf file you loaded the sys.upgrage file then after 5 minutes or so you made the above port switch (2-3-4 is fine) and back to DHCP?

Denis
K5RA
Steps Taken
Denis -
Here are the steps of my whole adventure.  I have a paper&pen log of the steps and iPhone photos of most of the windows that came up.
Started AREDN upload. 
After rb.elf file goes in, shut off Tiny PXE, enable dynamic IP, move Eth cable to hAP LAN port
After couple of minutes, do  ipconfig, see IPv4 address in  192.168.1.x subnet
Ping 192.168.1.1 works
Browse 192.168.1.1.  AREDN logo NOCALL page opens .  Click red   administration page   link.
Enter UN & PW
Find Firmware Update area, click Browse, find/select sysupgrade file. Click Open. Click Upload.
DO NOT REMOVE POWER window opens after a few seconds.  Has
    http://NOCALL-72-217-239.local.mesh:8080/
After 5 mins, screen appears with "Hmm. We are having trouble finding that site."
I restarted the Ethernet Network Adapter.  Tried browsing to the 239 URL.  Same response.
Browsed to http://NOCALL-72-217-238.local.mesh:8080/, and it worked. 
NOCALL-72-217-238 page came up.
Click red  setup page  link.  Entered  UN & PW
Set Node Name, new PW, ... Click Save Change.  Get   <node name> is rebooting   screen with two URLs to get back to the node.
Nothing happened, so after several minutes  I did  ipconfig, and it said I was still in the 192.168.1.x subnet.
I restarted the network adapter,  ipconfig  showed PC had a 10.xxx xxx xxx IP address. 
I clicked one of the links on the screen, and the Node Status page came up with new node name and other unique data I had entered.

I think the node is AREDN programmed and ready to work.  I just had some wrinkles getting it done.

Thanks for taking time to look at this.

--Tim K5RA
 
KD1HA
KD1HA's picture
After the change back to DHCP
After the change back to DHCP, reboot your new node and it will obtain a 10.xxx.xxx.xxx. I wasn't clear about that sorry, then go to the setup and change your node name U/P and so on.
nc8q
nc8q's picture
automatically reload in 5 mins.
Hi, Tim:
After your load the sysupgrade package you need to have your host computer get a new 10/8 ip address via DHCP.
Try unplugging your ethernet cable until your hist drops its address, then plug the cable in.
73, Chuck

 
K5RA
Restart Network Adapter?
Hello Chuck. 

Does restarting (disable/enable) the Ethernet Network Adapter have the same effect as unplugging the cable? 

--Tim  K5RA
 
nc8q
nc8q's picture
restarting (disable/enable) the Ethernet Network Adapter
Hi, Tim:

Linux: (disconnect/connect) Yes. Thanks.
I just ran my tftp.sh script which sets a 192.168.1.9 address and starts my TFTP server.
I then exited to find my ethernet adapter with IP address 192.168.1.9 .
I then clicked my network icon and then clicked 'Disconnect' under 'Wired connection 1'.
I then clicked my network icon and then clicked 'Wired connection 1'.
I then find my ethernet adapter with a 10.x.x.x address.
:-)

73, Chuck
 
K5RA
Great News
Chuck -

Thanks for this info.  The closest I get to Linux is using the CLI for a few low-level operations on a Raspberry Pi. I think it is good that the restart network adapter function is available in both Windows and Linux. 

73, 

-Tim


 
K7EOK
I think you combined two
I think you combined two steps ...  my recollection is that you first do sysupgrade without changing anything else, reboot, THEN you change UN and PW ... reboot, THEN you can continue.  The process is picky about order, and will not allow multiple things to be set at the same time.  Ed
 
Ping 192.168.1.1 works
Browse 192.168.1.1.  AREDN logo NOCALL page opens .  Click red   administration page   link.
Enter UN & PW
Find Firmware Update area, click Browse, find/select sysupgrade file. Click Open. Click Upload.
K5RA
I'll Check It
Ed -

Thanks for the observations. 

I thought I did things in exactly the order that the screens came up and had me to do them.  The "Enter UN & PW" after the first NOCALL page opened is what I had to do to get to the  administration page.  I should have said "Enter default UN & PW.  Then I got sysupgrade  file.   I did not change the Node Name and PW until getting to the Setup page, which required another entry of the default UN & PW. 

I interpret the instructions as threatening all manner of unfortunate circumstances if you do anything other than exactly what they say:
-Install rb.elf.
-Go to admin page, install sysupgrade.  Should reboot automatically
-Go to setup page, define new node name and PW.  Click Save Changes, and node reboots itself
-Perform rest of Basic Setup

I will go through the process again after converting node back to RouterOS with NetInstall.  Maybe there was something about installing AREDN on top of AREDN that caused hiccups.

73,

-Tim K5RA
 

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer