You are here

trouble finding localnode:8080 after firmware install

7 posts / 0 new
Last post
KK6NAN's picture
trouble finding localnode:8080 after firmware install

per request I have started this as new thread, original post (bottom) and first response are copied below:

Joe, thank you for your response.  the fully qualified domain name yields same error, with Rocket M2 LAN port wired directly to my iMac ethernet RJ45 port, after unplug/close browser/replug/open browser sequence. 

re assumption, no i was not able to connect to the Rocket directly from my iMac desktop using patch between POE LAN and iMac ethernet port. i plugged the POE LAN patch into my home network router, and was then able to see the AirOS page, run u-boot test, downgrade AirOS firmware, rerun u-boot, and install AREDN firmware. i then saw the Rocket MAC address on my router ARP table, but can't get at the localnode page on a browser.

I've only done work with the Rocket so far. I have a nanostation M2 and a nonobridge M3 to set up too, once I figure this out.  unfortunately i don't have a dedicated windows machine, so maybe there are settings to adjust in the parallels virtualization software (that allows me to run windows 10 on my iMac) to allow windows to see the Rocket?

Frank KK6NAN

repost from general discussion:

Give the fully qualified domain name a try:   http://localnode.local.mesh:8080 .    When ever I use my work laptop, it has policies that spell out domainnames to search through and  it will automatically append my company's domainnames to the hostname.    Maybe there is a similar issue with your setup.

Also, the assumption is this laptop/desktop is connected on the Mesh Node's LAN network and this is not mixed in somehow with the home network.  If default mesh node settings, your windows 10 OS should have received a 10.x.x.x address.

Which device(s) did you load with AREDN firmware?  Is this more than, e.g. a Nanostation and your desktop?  

Joe AE6XE 

Hi, i'm also unable to reach anything at http://localnode:8080.  i have done the following:
- downgraded firmware on my new Rocket M2 to 5.5.11, re-ran u-boot with result = good good
- installed AREDN over AirOS 5.5
- set my pc network interface to DHCP addressing
- steps 3-7 above

... but i get a "this site can't be reached' error, also indicates "localnode's server DNS address could not be found."  ERR_NAME_NOT_RESOLVED

part of this issue may be that i used windows 10 via parallels on my iMac. i was not able to see the initial AirOS page when i had device plugged directly into the iMac ethernet port, but i did see it when i plugged the Rocket LAN port into my home router, which allowed me to proceed to where i am now.  however i can't find an option on the iMac/settings/network windows to "Obtain DNS server address automatically", as indicated in the "Uploading firmware to Ubiquiti" picture/text instructions page. on parallels/windows 10/network connections / properties, IPV4 / properties, the "Obtain DNS server address automatically" button is populated, but after steps 3-7 above i still get "Hmm, we can't reach this page"

Any help much appreciated!!

AE6XE's picture
Frank,  this probably worked

Frank,  this probably worked because your home network must have the same 192.168.1.x subnet in use AND you didn't have another device already claiming the address the Ubiquiti device comes default with.   When you rebooted the Rocket after loading AREDN, it comes live most likely conflicting with your home routers address -- both tying to use .    

Next step is to disconnect from your home network and plug a cat5 directly between the Rocket and your computer.   Your computer will then receive an IP address from the Rocket, then browse to http://localnode:8080 and complete the setup.    After setup and reboot, then repeat to browse to localnode:8080 and everything should then show up as a 10.x.x.x IP addresses, including your computer, and is ready to use.   ...repeat on the other devices.


KK6NAN's picture
that did it, thank you!  i

that did it, thank you!  i turned off the wifi connection on my iMac desktop, shut all the software down, powered down the desktop and unplugged the Rocket, plugged rocket directly into the iMac and turned everything on again, and it worked.   now on the next radios..

No rain in the forecast for tomorrow, so i'll hook the rocket /Omni 2G13 up on the roof of my house tomorrow and see what i can connect to :). 

K9VEG's picture
Linux unable to connect to local node:8080

I have a Linux laptop and a raspberry pi, both of which I have used in the past on these nodes. For some reason I cannot figure out, when I try to access the nodes with http://localnode:8080 or http://localnode.local.mesh:8080. I get the error message that states cannot connect to server. If I plug in the IP address, I can connect, but I can't get into any services that way. No Mesh Chat. I get in ok with a Windows machine and an iMac. Does anyone else use a linux box or a pi to access the bullet? I'm running version on the M2. 

AE6XE's picture
These devices may not be

These devices may not be obtaining an IP address from the mesh node via DHCP.  This process also tells the raspi to use the node's DNS server to resolve hostnames.   do a "nslookup <hostname>" on these devices to see if it can resolve IP addresses of mesh nodes.  This should clue into a setting that needs changed.

Just in case, check out this bug:

We've not been seeing this bug, and 1 suspect instance observed in a while.  But would also explain these symptoms   Do this command on the mesh node, to see if the symptoms go away,  "/etc/init.d/olsrd restart" (and wait a minute or two to test).  


K9VEG's picture
temp work around

I'll try that Joe, thanks. I was able to work around it all by including the host names and IP addresses in the /etc/hosts file on the two linux boxes. That works, but it's not really working the way it's supposed to. I have to use the host name to log in to the M2. I was able to set two of them up and exchange mesh chat messages, so that was good, but I would rather they worked like they should.

Cannot connect after firmware update

Undated the version 2 Tp-Link CPE210 firmware via TP-Link's interface. I did not rename the fireware to the short name as the instructions list this only when updating firmware using the Aredn UI. I got an instant error message, but the update proceeded with a repeat click to 'update firmware' a second time with the long name. Update seemed to complete without incident, with what appeared to be a running node with live signal strengths displayed over time. After closing the TP-Link interface, attempts to connect using all techniques above have not worked. Connecting the ethernet cable from the 210 produces an "unidentified network" "no internet" network available in the live list of networks. IPConfig says: Description . . . . . . . . . . . : Killer E2400 Gigabit Ethernet Controller #2 Physical Address. . . . . . . . . : 4C-CC-6A-81-DB-C9 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::cb9:260d:70c9:c6fd%11(Preferred) IPv4 Address. . . . . . . . . . . : Subnet Mask . . . . . . . . . . . : Default Gateway . . . . . . . . . : DHCPv6 IAID . . . . . . . . . . . : 105696362 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-41-51-20-4C-CC-6A-81-DB-C9 DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 NetBIOS over Tcpip. . . . . . . . : Enabled

I tried disconnecting my wireless network with no effect.

Thank you for any suggestions you may have.

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer