I am unable to bring up the airOS page.
My home has TWC cable attached to a simple Netgear router. The router is not strong enough to cover the house so I have a Netgear extender. The wifi signal is great and has served me well in the past and I have flashed a Bullet, an airGrid, and a Rocket with the same laptop.
When I made the connections, my laptop revealed an unknown wifi source, presumably the Airrouter HP. I turned off my regular wifi, went to network settings (Ethernet) and opened the Ethernet network, changed the properties to use the recommended static IP address, went to my browser and tried to go to the devices airOS page I received a request from Microsoft Edge that a server was requesting my user name and password from my router attached to my TWC cable source. Sadly, I don't remember that password and user name anymore.
Since I don't need Internet to flash the Airrouter HP, could a guy just unplug my router down in the basement for a bit until I get the device flashed?
Sorry if this post shows my sheer ignorance.
scott
You are here
Difficulty flashing my AirRouter-HP
Mon, 02/22/2016 - 16:47
#1
Difficulty flashing my AirRouter-HP
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer
It is not necessary to use wifi when configuring a mesh node for the first time. This can be done 100% via a cat5 cable to avoid any collisions/interference/confusion with your home wifi network.
1) download the appropriate AirOs v5.5.x image (if the airRouter came with v5.6.x) to your laptop from your home internet connection
2) download the AirRouter AREDN beta image to your laptop from the AREDN website
3) turn off wifi on the laptop (to avoid any related issues) and connect with a cat5 to the AirRouter. Laptop is statically configured to use something like 192.168.1.2 with subnet of 255.255.255.0.
3) connect to airOS on the router at http://192.168.1.20, then upload the images v5.5.x image, the subsequently the AREDN image to the ArrRouter
Joe AE6XE
Received a "Hmm, we can't reach this page" (http://192.168.1.20) 401 unauthorized message.
close browser.
unplug cat5 cable from computer
re-plug cat5 cable
open browser
http://192.168.1.20
good, it sounds like you have it configured now.
Here are a few tips to start you off in operating a mesh node:
Hope this helps get you started!
73, Darryl
EDIT: changed a few due to the use of the AirRouter HP.
Thanks Daryl. I haven't actually gone beyond the flashing of the devices I had mentioned.
By the way, if anyone is interested in the AirGateway, they can be found on Amazon fairly cheap. A great way to add local wifi access points to the mesh.
http://www.amazon.com/Ubiquiti-airGateway-802-11n-Wireless-Access/dp/B013Y80PMM/ref=sr_1_5?ie=UTF8&qid=1456287385&sr=8-5&keywords=Ubiquiti+AirGateway
Thanks
AC8PT, If there are no other RF mesh nodes in your area, then to get started on a mesh network, you may want to consider going into setup to install the tunnel client, then find someone to connect to that has setup a tunnel server. If you only have a 1 node mesh, it won't really be a 'network' to do interesting things across. With the tunnel you can then pretend you have a cross-country microwave link :) , until you do. 1) Plug the AirRouter's wan port into your home network (and thus access to internet); 2) then plug your laptop into the AirRouter's LAN port. Be sure to have the laptop set back to DHCP. 3) In setup, click on Tunnel Client to install. 4) someone with a tunnel server can send you the information to type in and connect over the internet to their mesh network.
Joe AE6XE
Joe,
A club, of which I am a member, wishes to start a mesh network in their area. I live about 23 miles away and unless I put in a 300' tower (not) I cannot link with them. One of the hard working members had gone to the trouble to place a mobile node in his vehicle, as well as 2 nodes in prominent/high positions in hopes of supporting other hams in the area who wish to place nodes. Some have placed a couple of bullets, but most have placed Linksys equipment. I thought I could help him and our group by investing in a bit of kit and learning about it. I am in a better position than most to afford the gear.
So, I planned a RM2/AMO-213G to be installed in a prominent place for the Club, despite being so far away, and to hopefully use that node to have a number of useful services available for the other hams. I got the AirRouter-HP for my home to be a tunnel client for him. Finally, I got the BM2-Ti/HG-2415U-Pro and the airGrid to be used together or independently as a competent mobile installation. I want to use the Toughswitch,configured in a way, that I could make use of my laptop, Raspberry Pi (LAMP server), IP phone, and video camera (UVC), and I wanted to have Internet access (which may not be all that necessary). WS2U was helpful with the switch configuration. Both Daryl and you have also been helpful, thanks.
scott
Hi, folks. I just configured an airrouter, test date in july 2015, Airos 5.58. The web interface was at 192.168.1.1, NOT 192.168.1.20 like all the other UBNT stuff. I had no difficulty getting mine set up once I read that in the 'getting started' guide.
I flashed mine last night and the web interface was on 192.168.1.1. I had to roll back the firmware from 5.6 but after I did I was able to upload the v3.16.1.0b01 without issue.
Enjoying my new toy, just wish I had more folks around me to test my other nodes.
Douglas
W7ADD
Something I don't think I have seen mentioned are two things regarding updating the AirRouter. I made the mistake of trying to communicate with the router through the WAN/POE port. This works initially but after you load AREDN Firmware, and sometimes other AIROS downgrades, it is best to communicate via ethernet cable to one of the REGULAR ports - probably port 1, NOT THE WAN PORT! This is especially important once you get the AREDN Firmware loaded because it won't talk back through the WAN port very well. The other thing I have found helpful is the use of the UBNT Device Discovery Tool for anything Ubiquiti that has their firmware on it. A quick connection and scan will reveal the IP address(es) available as well as the Firmware version.