Controllerless Networks

 View Only
last person joined: 3 days ago 

Instant Mode - the controllerless Wi-Fi solution that's easy to set up, is loaded with security and smarts, and won't break your budget
Back to discussions
Expand all | Collapse all

iAP - lost GUI when I updated the code

This thread has been viewed 1 times

  • 1.  iAP - lost GUI when I updated the code

    Posted Aug 06, 2013 06:49 PM

    I just installed an iAP (or rather had a technician install it) at a remote location, where it obtained an IP address from DHCP and I connected to the GUI.

     

    First step I upgraded the code to 3.4 (it shipped to us on 3.1)

     

    After the reboot, I can't connect on HTTP/S -- It starts to connect and eventually times out.

    If I try to connect on port 443 I get redirected to 4343, and then time out.

     

    Is there a way to get it to check in to Airwave from the CLI so I can push a full configuration out to it?

    Or a way to fix the GUI?



  • 2.  RE: iAP - lost GUI when I updated the code

    Posted Aug 06, 2013 07:03 PM
    Can you connect using the IP ?


  • 3.  RE: iAP - lost GUI when I updated the code

    Posted Aug 06, 2013 08:07 PM

    I was able to connect to SSH, but not to http or https (443 or 4343) all to the IP address of the iAP

     

    I logged in to the CLI and gave it a name, organization, VC ip-address, ams ip-address and ams key.

     

    After an hour it turned up in Airwave as a new device.

     

    I've been able to put it in the proper group and push the config template and all is much better.



  • 4.  RE: iAP - lost GUI when I updated the code

    Posted Aug 06, 2013 08:11 PM

    Correction, now its checked in to Airwave and the template has been applied, but I still can't load the GUI - timeout.

    Rebooting the iAP to see if it will respond better after a quick nap.



  • 5.  RE: iAP - lost GUI when I updated the code
    Best Answer

    Posted Aug 06, 2013 08:20 PM

    Never mind.

     

    Forgot that the new code moves management from https to 4343 (didn't forget, event tested it)

    Forgot that the firewall doesn't know that.

     

    add one magic firewall rule, and say the magic words...

     

    ...working just fine.

     

    Sorry to waste the bandwitdh, hopefully someone else will stumble on this thread and save himself some trouble.