Reply
Member
Posts: 211
Registered: ‎07-03-2015
Kudos: 22
Solutions: 4

Re: [FIRMWARE] 3.9.19.8123 for UAP/USW has been released


bw1 wrote:

@UBNT-jeff

 

I'm not following. I haven't experienced any problems, and I've always used http:// for the inform URL.

 

I have never seen anything using https:// for inform in any official manner, so I question why these people are doing so, unless I've missed an updated how-to somewhere along the line.

 

1.) Is inform using http:// a security risk / is this an encrypted request over non-encrypted channel?

2.) What is the proper way to go foward if we currently have a ton of devices using http:// for hard-set inform?


The logic is probably because you use HTTPS to connect to the controller web site so it would make sense when giving the URL of the controller to use HTTPS. 

New Member
Posts: 49
Registered: ‎07-25-2012
Kudos: 48

Re: [FIRMWARE] 3.9.19.8123 for UAP/USW has been released

Upgrade works well. So far no issues exept:

Outdoor mode still not working:

 

[   57.854000] outdoor=1, freq=5300 invalid for cc=00000028 regdmn5g=00000130
[   57.854000] outdoor=1, freq=5320 invalid for cc=00000028 regdmn5g=00000130
[   57.854000] outdoor=1, freq=5320 invalid for cc=00000028 regdmn5g=00000130
[   57.854000] outdoor=1, freq=5320 invalid for cc=00000028 regdmn5g=00000130
[   57.899000]  DEVICE IS DOWN ifname=ath2
[   57.901000]  DEVICE IS DOWN ifname=ath2
[   58.550000] br0.100: port 2(ath1) entering forwarding state
[   58.753000] br0.100: port 1(ath0) entering forwarding state
[   62.097000] wlan_get_active_vport_chan: ch=0
[   62.097000] cac_start chan 5680 timeout 62 sec, curr time: 4294729 sec
[   62.099000] br0.101: port 1(ath2) entering learning state
[   63.099000] br0.101: port 1(ath2) entering forwarding state
[  124.098000] cac_timeout cac expired, chan 5680 curr time 4294791
[  124.098000] ath_dfs_clear_cac: Exit DFS_WAIT state 1
[  373.078000] sig1 rx_clear is set 0x9c24 8104
[  794.360000] dfs_process_radarevent: FILTER 0 - MATCH FOUND.
[  794.360000] dfs_process_radarevent: Radar found on channel 136 (5680 MHz)
[  794.360000] ath_net80211_dfs_clist_update: called, cmd=1, nollist=8290a540, nentries=1
[  794.360000] ath_net80211_dfs_clist_update: radar found = chan=83020d8c, freq=5660, vht freq1=5000
[  794.360000] ath_net80211_dfs_clist_update: radar found = chan=83020da0, freq=5680, vht freq1=5000
[  794.361000] ath_net80211_dfs_clist_update: radar found = chan=83020db4, freq=5680, vht freq1=5000
[  794.361000] ath_net80211_dfs_clist_update: radar found = chan=83020dc8, freq=5680, vht freq1=5000
[  794.361000]
[  794.361000]  Changing to channel 40 (5200 MHz) chanStart -1979711488
[  794.361000]
[ 2594.360000] ath_net80211_dfs_clist_update: called, cmd=1, nollist=(null), nentries=0
[ 2594.360000] ath_net80211_dfs_clist_update: NOL clear = chan=83020d8c, freq=5660, vht freq1=5000,
[ 2594.360000] ath_net80211_dfs_clist_update: NOL clear = chan=83020da0, freq=5680, vht freq1=5000,
[ 2594.360000] ath_net80211_dfs_clist_update: NOL clear = chan=83020db4, freq=5680, vht freq1=5000,
[ 2594.360000] ath_net80211_dfs_clist_update: NOL clear = chan=83020dc8, freq=5680, vht freq1=5000,
BZ.v3.9.19#

 

 

th0      IEEE 802.11na  ESSID:"Hotspot Wels"
          Mode:Master  Frequency:5.2 GHz  Access Point: xx:xx:xx:xx:xx:xx
          Bit Rate:6 kb/s   Tx-Power=14 dBm
          RTS thrMan Surprisedff   Fragment thrMan Surprisedff
          Encryption keyMan Surprisedff
          Power ManagementMan Surprisedff
          Link Quality=255/94  Signal level=-1 dBm  Noise level=-114 dBm
          Rx invalid nwid:1301  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Emerging Member
Posts: 104
Registered: ‎12-02-2017
Kudos: 71

Re: [FIRMWARE] 3.9.19.8123 for UAP/USW has been released

 

I upgraded just 1 AP for now, for testing purposes.  It failed twice when I tried to upgrade from the GUI, saying "download failed".  I cached the firmware and tried again, which allowed the upgrade to complete.  I'll monitor this AP and patch more if this works well.

 

Any idea about the "download failed" error?  I haven't set any inform URLs (I don't know how to at this point).

 

Emerging Member
Posts: 67
Registered: ‎01-22-2016
Kudos: 13
Solutions: 3

Re: [FIRMWARE] 3.9.19.8123 for UAP/USW has been released


Vestas wrote:

All UAP-AC-LRs are failing to upgrade with a totally unhelpful error message :

 

upgrade failed: download failed (error: unknown)

 

Multiple sites, multiple ISPs so its clearly not a local issue.

 

The UAP-AC-LRs then stay in an unadopted state (with the old firmware) until they are manually power-cycled.

 

After SIX attempts I finally have one back up and running.

 

This firmware is NOT ready for release. I strongly recommend that if you are updating remote devices/sites that you do not take part in testing this beta firmware (that's what it is).

 

NB - this only applies to UAP-AC-LR, other models update correctly.


I have the same download error message on one US-8-60W.  It restarts and then shows as adopted but with the old firmware.  I can no longer ping it, nor can I ssh into it.  It does, however, still continue to power 1 x US-8, 1 x UAP-AC-IW, 1 x UAP-AC-IW-PRO and a Cloud Key, all of which can be managed and were successfully upgraded.

 

It responds to reboot requests via the controller.  There isn't any firmware cached on the controller so the fix described by bcruze in Post 22 doesn't work.

 

I'm about to go on site to sort things out.

Member
Posts: 190
Registered: ‎03-21-2013
Kudos: 60
Solutions: 8

Re: [FIRMWARE] 3.9.19.8123 for UAP/USW has been released

Upgrade of AC HD & AC Pro went very smooth but the performance of my iOS devices dropped by 50% - 70% in troughput. 

I'm unable to get more that 130Mbps to the device. Downgrading to .15 fixes it right away, back to 400Mbps on device.

 

Member
Posts: 217
Registered: ‎12-26-2017
Kudos: 38
Solutions: 5

Re: [FIRMWARE] 3.9.19.8123 for UAP/USW has been released

[ Edited ]

I actually see the same performance issues with iOS devices as @Cloudz but seems to degrade download more than upload at least in my initial testing.

Emerging Member
Posts: 67
Registered: ‎01-22-2016
Kudos: 13
Solutions: 3

Re: [FIRMWARE] 3.9.19.8123 for UAP/USW has been released

[ Edited ]

I can confirm that with an old Macbook Pro (Late 2009) running OS X 10.11.6 I'm getting 154Mbps with 3.9.19.8123 on 5GHz but on 3.9.15.8011 I'm seeing 214Mbps so there does seem to be an issue.

Emerging Member
Posts: 104
Registered: ‎12-02-2017
Kudos: 71

Re: [FIRMWARE] 3.9.19.8123 for UAP/USW has been released

[ Edited ]

 

To help the testing, I am not seeing any real difference in download speed on a MacBook Air or an iPad Pro using 3.9.15.8011 on one AP vs 3.9.19.8123 on the test AP I upgraded.

 

 

 

 

Emerging Member
Posts: 67
Registered: ‎01-22-2016
Kudos: 13
Solutions: 3

Re: [FIRMWARE] 3.9.19.8123 for UAP/USW has been released

That could possibly be because 802.11ac isn't affected but 802.11n is.  Just a thought.

Emerging Member
Posts: 104
Registered: ‎12-02-2017
Kudos: 71

Re: [FIRMWARE] 3.9.19.8123 for UAP/USW has been released

 

I did a test on an iPad Air (maxes out at n) and got similar results on 3.9.19 ad 3.9.15  (granted speed tests on iOS seem a bit less reproducable/consistent than on MacOS).

 

I hope this helps in any testing.  

Emerging Member
Posts: 62
Registered: ‎09-07-2017
Kudos: 12
Solutions: 1

Re: [FIRMWARE] 3.9.19.8123 for UAP/USW has been released

Upgraded from 3.9.15.8011 and no issues detected. Both my WAP-AC-PRO and US-8-60W are working fine.

Highlighted
New Member
Posts: 4
Registered: ‎05-31-2015
Kudos: 1

Re: [FIRMWARE] 3.9.19.8123 for UAP/USW has been released

upgraded 3 of 100+ AP's in my controller to 3.9.19.8123 no issues... procedded to upgrade many others upon successful upgrade of the 3... now no connection of the other upgrades preformed.  Controller is running 5.6.29 in my house, all AP's & gateways are offsite. Rebooted controller, still no connection? However the original 3 are still connected. Man Sad

Member
Posts: 190
Registered: ‎03-21-2013
Kudos: 60
Solutions: 8

Re: [FIRMWARE] 3.9.19.8123 for UAP/USW has been released

Tested on iPhone X, iPhone 7 & iPad Pro 10 - all on latest OS releases. Should be no problem.
They are connected to the 5Ghz/80Mhz band. 

Emerging Member
Posts: 58
Registered: ‎05-16-2013
Kudos: 16
Solutions: 3

Re: [FIRMWARE] 3.9.19.8123 for UAP/USW has been released

updated both UAP-AC-Lite and USW-8-60W.

 

both device working fine however, the debug terminal doesn't work on the UAP. (it stopped working after the pervious firmware update but I forgot to report it)

 

Any idea how to fix it?

 

Cheers

 

Greg

Member
Posts: 130
Registered: ‎10-29-2015
Kudos: 22
Solutions: 1

Re: [FIRMWARE] 3.9.19.8123 for UAP/USW has been released

Beginning of this week I've upgraded my UAPs and at the same time applied some changes to one of my VLANs.

After that I got random reconnects by some of my WiFi ip cameras. Step by step I've been reverting the changes and at last I've just downgraded one of my UAPs to 3.9.15 since reverting the other changes had no effect.

Will report back if this has resolved the recconects. Cams (Dahua) are connected on separate 2.4Ghz SSID and VLAN and were stable before.

It would have been better to try one change at the time and monitor the effect in the first place, but lack of time just had me do it all togheter. Man Wink

Synology DS918+ running Debian 9.4 on a VM with Unifi controlling USG, 2 USW and 3 UAP-PRO.

Simplicity is the ultimate sophistication.
New Member
Posts: 24
Registered: ‎01-18-2016
Kudos: 3

Re: [FIRMWARE] 3.9.19.8123 for UAP/USW has been released

All of my AP-LR's upgraded first time without issues.

AP-AC-Pro and AP-AC-Lite AP's failed on the first attempt. The controller logged an alert "Upgrade Failed, Download Failed (Error unknown)". On second attempt upgrade suceeded.

 

Not sure why its necessary to initiate the upgrade twice for the AC type AP's.

 

I might leave it until next week before I upgrade my AC-HD I ave no spare units of that type.

 

Upgrading from 3.9.15.11 to 3.9.19.8123 on 5.6.26 controller.

New Member
Posts: 12
Registered: ‎02-02-2016
Kudos: 1

Re: [FIRMWARE] 3.9.19.8123 for UAP/USW has been released

[ Edited ]

I performed an upgrade from a remote controller on an UAP-AC-LR, I just installed this week and it just didn't come back online on the controller. I'm afraid i have to go on site again and see howto fix it, somehow. 

 

Update: My statement appears not to be true, it just took a long time for the UAP AC-LR to come back online in the controller. Must haven been almost 30 minutes, But all seems OK now.

Emerging Member
Posts: 85
Registered: ‎04-07-2013
Kudos: 11
Solutions: 2

Re: [FIRMWARE] 3.9.19.8123 for UAP/USW has been released

[ Edited ]

I've always done my inform with https.

 

I upgraded one site and none of the Uap-ac-lites came back to the controller but were still serving clients.

 

Got an unknown[11] error on inform.

 

I was able to get them back on the controller by issue an inform http.

 

But, I have 100's of devices that are already informed via https spread over about a 100 sites. What do I do?

New Member
Posts: 18
Registered: ‎02-15-2016
Kudos: 39

Re: [FIRMWARE] 3.9.19.8123 for UAP/USW has been released

[ Edited ]

Same issue here. Setup my controller with real SSL and had used https for all my informs. Upgrade took every one offline. Thankfully I only upgraded a few to test out. 

 

But can't imagine if I had hundreds of devices to manually fix. 

 

And seriously using port 8080 as instructed wasn't really doing https anyway? Sigh

 

UPDATE

 

So my first one, I logged in, set inform using http and 8080, Snapped right back online. Then set https with 8443 and it stayed online. info command shows it connected as does UniFi. Wireless was active the whole time. and the AP had actually upgraded to 3.9.19.

 

But I've tried to ssh into two others - and I can't login. The APs won't take my credentials or the defaults. Which makes fixing this kind of difficult... Still digging... Don't understand why the credentials aren't working...

 

I always forget the sites have unique passwords for SSH now Man Very Happy

 

UPDATE 2

 

Weird thing. As I'm logging into more UAPs (have about 8 to fix - they were my first test wave). I'm noticing when I so set-inform with http and 8080, sometimes it takes immediately, other times it doesn't. info says 'Unable to resolve' but the URL is correct. Running an nslookup on the hostname (executed on the UAP), returns the right IP. But it doesn't connect. Issue the command enough (up arrow repeat), and after a few attempts - it pops up online and shows connected with the info command. Bizarre.

Member
Posts: 268
Registered: ‎05-28-2016
Kudos: 90
Solutions: 4

Re: [FIRMWARE] 3.9.19.8123 for UAP/USW has been released

@itxpress You don't need https on the inform URL, since the communication between the AP and controller is encrypted via another method (I believe some variant of SSH). The only thing I can imagine that would do is add overhead, since the communication would get encrypted twice. And of course you'll get bugs, since almost everyone uses http for their inform URL and ubiquiti probably doesn't test using https.

 

@mrbrivalen You should be able to change the inform URL through Settings > Controller > Controller Hostname/IP, enter the hostname or IP address of your controller (without http:// or https://) and check the box that says "Override inform host with controller hostname/IP."

Reply