I was able to get the actual inform url by SSHing into another AP that is recognized by the controller. I did a set-inform for the troublesome AP. I tried the DNS name, the IP, https/http, 8080, 8443... I tried every form of url I could think of, but set-inform does not work. I also rebooted the controller last night.

Resetting doesn't work. The thing is, when I use a laptop as the controller on the same subnet, it sees it. But the controller's main IP is on another subnet- there's just a route to the other subnet.

So like:

Controller is on 192, and wireless is on 10.0.

Controller is able to ping all AP's...even the troublesome one. Wireshark on the controller picks up TCP/HTTP traffic to the trouble AP- so they're communicating...

Yet after hours of testing this, the controller still doesn't show the AP!

I even have the AP set as the exact same IP as it used to be, and with the laptop as its controller, I was able to set the right dns settings as well, so it should see the controller's A record. Regardless, the other AP's have their inform url set to its IP- no big deal, I already tried that.

I think I've exhausted all possibilities here- I'm really not sure what to try next!

30 Replies

can you print the Controller from the AP? if not it will cause the problem with the set inform url. You could try resetting the AP, join it to the controller in the same network and then move it to the other network.

When I do the
syswrapper.sh restore-default, it gets an IP on the right subnet (that's great right, supposedly),

yet two things:

Default ssh pwd doesn't work: ubnt, and my former ssh pwd doesn't work- how am I supposed to set the inform-url?

And of course, the controller doesn't see it.

I can use the laptop as the controller again, but that's just doing what I was doing before.

Seeing the tail log too, I saw it kept trying to contact the laptop's IP's. 1st the right subnet, and then the 192.168 default IP subnet that factory default goes to.

Our firewall has multicast support disabled.

From your article:

"
Its much easier to just plug in the factory default device, use Ubnt Discovery tool to set the inform to your remote hosted controller, and be done with it."

I tried running the discovery tool on the laptop, my desktop, and the controller server and it doesn't function...it doesn't do anything. I tried clicking Scan and typing the IP subnet..not sure. I watched the video on it and it says the AP's are supposed to show up, but nothing does.

It seems as the AP cannot contact your Controller as far as the logs show. You will still need to reset the AP so it does not use the IP of the laptop as the controller. After the reset then you can adopt to the new controller. You can try even checking the controller on the laptop and it will show up the AP.