Reply
New Member
Posts: 8
Registered: ‎02-13-2016
Kudos: 1
Solutions: 1

Re: [USG] Firmware v4.4.36 now available

I am having similar issues with any firmware greater than 4.4.22. I provided more details along with USG logs in a specific post [1]. That post ins't getting any love for the moment but the issue is consitent across all sites I manage, and a serious pain. Can you review that post and see if you have similar log entries around the time of the errors? If so, please +1 the case I created so that we can get traction on the remediation. Thanks!

 

[1] - https://community.ubnt.com/t5/UniFi-Routing-Switching/USG-connectivity-issues-since-4-4-29-usg-mcad-...

Established Member
Posts: 1,064
Registered: ‎02-18-2017
Kudos: 358
Solutions: 33

Re: [USG] Firmware v4.4.36 now available


@misterxav wrote:

I am having similar issues with any firmware greater than 4.4.22. I provided more details along with USG logs in a specific post [1]. That post ins't getting any love for the moment but the issue is consitent across all sites I manage, and a serious pain. Can you review that post and see if you have similar log entries around the time of the errors? If so, please +1 the case I created so that we can get traction on the remediation. Thanks!

 

[1] - https://community.ubnt.com/t5/UniFi-Routing-Switching/USG-connectivity-issues-since-4-4-29-usg-mcad-...


Have you tried turning off Speedtest?

New Member
Posts: 8
Registered: ‎02-13-2016
Kudos: 1
Solutions: 1

Re: [USG] Firmware v4.4.36 now available

Giving this a shot now. I thought this was specifically what firmware 4.4.29 addressed though.
New Member
Posts: 5
Registered: ‎11-02-2018

Re: [USG] Firmware v4.4.36 now available (logs from dropping WAN)

Trying to troubleshoot this, I went thru 3MB worth of logs. Here is a pattern that repeats itself.

Added comments as >>> ALL CAPS COMMENTS

 

they key problem is this:

[2019-01-12 10:32:20,529] <inform-25> INFO dev - saveDeviceAttr(): device[fc:ec:da:d7:07:3c][ip]=0.0.0.0 (orig=24.16.30.7)
[2019-01-12 10:32:20,534] <inform-25> INFO dev - [state] dev[fc:ec:da:d7:07:3c] UNKNOWN->CONNECTED, state_expire=0

 

 

UniFi Security Gateway

 

>>> PROPER WAN ADDRESS (I CHANGED IT)


[2019-01-12 10:29:26,039] <inform-35> INFO inform - from [fc:ec:da:d7:07:3c](net-vsh-usg, UGW3, 4.4.36.5146617): state=UNKNOWN, last_inform=40, ext/stun_ip=10.70.1.1, dev_ip=24.16.30.7, up=3029

 

>> LOADS OF THESE

[2019-01-12 10:29:34,185] <pool-6-thread-1> INFO AwsIotConnection - Connection is being retried

[2019-01-12 10:29:34,201] <MQTT Con: b340d6e3-89ae-4658-92f8-b0143e12cbc1> WARN AwsIotMqttConnectionListener - Connect request failure
MqttException (0) - java.net.UnknownHostException: xxxxxxxxxxxxxxxxxx.iot.us-west-2.amazonaws.com
at org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:38)
at org.eclipse.paho.client.mqttv3.internal.ClientComms$ConnectBG.run(ClientComms.java:664)
at java.lang.Thread.run(Unknown Source)
Caused by: java.net.UnknownHostException: xxxxxxxxxxxxxxxxxx.iot.us-west-2.amazonaws.com
at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at sun.security.ssl.SSLSocketImpl.connect(Unknown Source)
at org.eclipse.paho.client.mqttv3.internal.TCPNetworkModule.start(TCPNetworkModule.java:70)
at org.eclipse.paho.client.mqttv3.internal.SSLNetworkModule.start(SSLNetworkModule.java:86)
at org.eclipse.paho.client.mqttv3.internal.ClientComms$ConnectBG.run(ClientComms.java:650)
... 1 more


[2019-01-12 10:29:34,205] <pool-6-thread-1> INFO AwsIotConnection - Connection temporarily lost

 

[2019-01-12 10:30:04,206] <pool-6-thread-1> INFO AwsIotConnection - Connection is being retried
[2019-01-12 10:30:04,234] <pool-6-thread-1> INFO AwsIotConnection - Connection temporarily lost

 

[2019-01-12 10:30:34,237] <pool-6-thread-1> INFO AwsIotConnection - Connection is being retried
[2019-01-12 10:30:34,273] <pool-6-thread-1> INFO AwsIotConnection - Connection temporarily lost

 

[2019-01-12 10:31:04,275] <pool-6-thread-1> INFO AwsIotConnection - Connection is being retried
[2019-01-12 10:31:15,324] <pool-6-thread-1> INFO AwsIotConnection - Connection temporarily lost

 

[2019-01-12 10:31:45,325] <pool-6-thread-1> INFO AwsIotConnection - Connection is being retried
[2019-01-12 10:31:56,377] <pool-6-thread-1> INFO AwsIotConnection - Connection temporarily lost

 

>> AFTER MANY RETRIES, THE IP FROM USG INFORM COMES BACK AS 0.0.0.0

 

[2019-01-12 10:32:20,528] <inform-25> INFO inform - from [fc:ec:da:d7:07:3c](net-vsh-usg, UGW3, 4.4.36.5146617): state=UNKNOWN, last_inform=174, ext_ip=10.70.1.1, dev_ip=0.0.0.0, up=155

 

>>> THE USG TAKES WHAT WAS THE VALID IP ADDRESS AND SAVES 0.0.0.0 AS VALID. CLEARLY NOT GOOD GIVEN THE NETWORK CONNECTION IS IN FACT UP.


[2019-01-12 10:32:20,529] <inform-25> INFO dev - saveDeviceAttr(): device[fc:ec:da:d7:07:3c][ip]=0.0.0.0 (orig=24.16.30.7)
[2019-01-12 10:32:20,534] <inform-25> INFO dev - [state] dev[fc:ec:da:d7:07:3c] UNKNOWN->CONNECTED, state_expire=0

 

>>> FOLLOWING THS PERSISTENCE OF 0.0.0.0, THE USG BELIEVES IT IS NOW CONNECTED AND ACTS THAT WAY FROM HERE ON OUT.


[2019-01-12 10:32:20,536] <inform-25> INFO event - [event] Gateway[fc:ec:da:d7:07:3c] was connected
[2019-01-12 10:32:21,106] <inform-27> INFO inform - from [fc:ec:da:d7:07:3c](net-vsh-usg, UGW3, 4.4.36.5146617): state=CONNECTED, last_inform=1, ext_ip=10.70.1.1, dev_ip=0.0.0.0, up=160

 

>>> YET, IOT CONNECTIONS CONTINUE TO FAIL FOR OBVIOUS REASONS (0.0.0.0 IS BEING ATTEMPTED

 

[2019-01-12 10:32:26,379] <pool-6-thread-1> INFO AwsIotConnection - Connection is being retried
[2019-01-12 10:32:37,419] <pool-6-thread-1> INFO AwsIotConnection - Connection temporarily lost

[2019-01-12 10:32:37,449] <inform-91> INFO inform - from [fc:ec:da:d7:07:3c](net-vsh-usg, UGW3, 4.4.36.5146617): state=CONNECTED, last_inform=6, ext/stun_ip=10.70.1.1, dev_ip=0.0.0.0, up=176

House: 1x USG4, 1x sw-48x500w, 1x sw-8x60w, 3x sw-8, 2x ap-NanoHD, 1x ap-LR, 1x Cloudkey2
Cabin:1x USG3, 1x sw-8x60w, 3x sw-8, 1x ap-NanoHD, 1x Win10-Cloudkey
New Member
Posts: 3
Registered: ‎12-20-2017

Re: [USG] Firmware v4.4.36 now available


@bretm wrote:

WAN1 speed has dropped from 900mbps+ to ~40mbps after this upgrade.  Wasn't having much trouble before this, except failover didn't seem to work particularly well.

 

Odd thing is that when I disconnect WAN1, and plug the same cable into WAN2, I get back to 900mbps+ performance.

 

Both WAN1 & 2 autonegotiate to gigabit speed.

 

I've tried chatting w/ Ubiquiti, but I keep getting disconnected during debugging efforts, and tossed back into the end of the queue.

 

This is maddening.


@bretm - Were you ever able to find a fix for this?  I unfortunately haven't had any luck when switching from WAN1 to WAN2, but the othher symptopms sounded exactly like what I'm dealing with right now. 

 

(my issue for reference: https://community.ubnt.com/t5/UniFi-Routing-Switching/USG-upgrade-to-4-4-36-killed-my-download-speed...)



New Member
Posts: 7
Registered: ‎01-03-2018
Kudos: 1

Re: [USG] Firmware v4.4.36 now available

[ Edited ]

What version of USG firmware was bad for you guys?

I have this prompt... 4.4.29.5124210 to 4.4.36.5146617

Curious if 4.4.36 will get some love based on this thread to a newer version for download?

 

Is there a stable version between 29 and 36?

 

https://www.ui.com/download/unifi-switching-routing/usg

 

Member
Posts: 120
Registered: ‎11-08-2017
Kudos: 17
Solutions: 5

Re: [USG] Firmware v4.4.36 now available

[ Edited ]

V4.4.36 is definitely tainted, it was switching backwars and forwards between wans with only one wan plugged in.

 

See my comment further up for further info. I have backed down to 4.4.34 but haven't tested dual wan failover operation on that firmware.  Its probably something i can test today. 

New Member
Posts: 29
Registered: ‎03-09-2018
Kudos: 3

Re: [USG] Firmware v4.4.36 now available

4.4.34 and .36 have been good to me. 

 

One USG w/ IPS enabled

Two switches

Two APs

New Member
Posts: 19
Registered: ‎09-02-2015
Kudos: 1

Re: [USG] Firmware v4.4.36 now available

i believe dual wan has always been broken.  In 4.4.36, if a failure occurs on WAN1, it does switch over to WAN 2, but will not switch back when the link is restored.  

A pervious version(i dont recall which one), actually worked when failing back.  Site to Site vpn would not reinitialize though.

 

i just end up rebooting the router when a failback occurs.  

New Member
Posts: 21
Registered: ‎04-23-2016
Solutions: 1

Re: [USG] Firmware v4.4.36 now available

[ Edited ]

Upgrade ok.

 

But Usg 4p wan2 failover. Works if only to surfing on the web.  Can not get to My servers externaly.

When My isp1 in wan1 cuts out, wan2 takes over but i get the same ip on wan2 and wan1.

Only way to get my servers to connect to external is by put wan2 in wan1. 

 

I do not know if this is a problem past the last update or not, or if is unifi controller software problems. 

 

It looks like port forwarding is only wan1. Not wan1 and 2. Or problem with wan1 and 2 gets the same ip for wan2. The port wan1 is activ because mobem is still function for isp1.

1 Usg 4p 4.4.36 , 1 Usg 4.4.36
1 Us 16 150w 4.0.21
3 Ap ac pro 4.0.21 , 1 UAP-AC-PRO 4.0.22
unifi cloudkey 0.13.4 , Unifi 5.10.17
New Member
Posts: 21
Registered: ‎04-23-2016
Solutions: 1

Re: [USG] Firmware v4.4.36 now available

https://help.ubnt.com/hc/en-us/articles/235723207-UniFi-USG-Port-Forward-Port-Forwarding-Configurati...

Was the answer to my problem, 
next question then is , when can we expect wan1 and wan2 rules for firewall and port forwarding in the unifi software??

1 Usg 4p 4.4.36 , 1 Usg 4.4.36
1 Us 16 150w 4.0.21
3 Ap ac pro 4.0.21 , 1 UAP-AC-PRO 4.0.22
unifi cloudkey 0.13.4 , Unifi 5.10.17
Emerging Member
Posts: 71
Registered: ‎12-02-2016
Kudos: 9

Re: [USG] Firmware v4.4.36 now available

Yea it would be nice if they would FIX the port forwarding issues... Like common we need the WAN2 to be able to have port forwarding rules!

New Member
Posts: 7
Registered: ‎01-03-2018
Kudos: 1

Re: [USG] Firmware v4.4.36 now available

[ Edited ]

I upgraded from 4.4.29 up to 4.4.34 without issue.  Will not go further due to reports in this thread for now.

 

Memory utilization dropped from 27% to 19% as a trend... might just be that this reload freed up some memory however.

 

I like updating to get new updates/features/bug requests but the old idea to not be too aggressive on updates applies... do your research.

Member
Posts: 226
Registered: ‎01-23-2017
Kudos: 66
Solutions: 4

Re: [USG] Firmware v4.4.36 now available

My site-site VPN performance is very good between a pair of USG3! Seeing 45-50mbps on iperf.

 

Awesome. Need DASHBOARD STATUS!

New Member
Posts: 34
Registered: ‎01-09-2018
Kudos: 8

Re: [USG] Firmware v4.4.36 now available

I upgraded from  4.4.29 to 4.4.36.5146617 without any problem

New Member
Posts: 2
Registered: ‎05-30-2016
Kudos: 1

Re: [USG] Firmware v4.4.36 now available

I'm getting the freezing on the office USG 4P. I'm looking like an absolute numpty when the thousands of $$$ worth of Unifi is out performed by a $4.27 Huawei - that is gimped by a Filipino Telco to boot....

 

The USG has been banned by management despite being the ideal oslution to the various network requirements.

 

Z...

Highlighted
New Member
Posts: 14
Registered: ‎09-03-2014
Kudos: 3

Re: [USG] Firmware v4.4.36 now available

[ Edited ]

Slightly off topic and does not obsolve Ubiquiti here but you do know that Huawei is a risk - right?  There is a reason (other than trade or ideology) for the ban in the US and that Europe is considering to do the same.

New Member
Posts: 19
Registered: ‎10-21-2017
Kudos: 3
Solutions: 1

Re: [USG] Firmware v4.4.36 now available

4.4.36 crashed on a live setup today. Only real extra configuration is traffic shaping on the upload. Going to 4.4.34.

New Member
Posts: 28
Registered: ‎10-29-2015

Re: [USG] Firmware v4.4.36 now available

USG Just Went Dead/Frozen/Non Responsive on V 4.4.36.5146617 (running for a while)
I pinged, I SSH'ed, port 80/443 and everything else I could think of and it just had zero response.
It happened at almost exactly midnight - well 00h:01m:41s to be exact.
I unplugged the LAN connection and laptop'ed directly in with static IP and nothing.
Blue Light was Solid and Network Lights Flashing like normal.
The Wan interface was not showing even 1 byte transferring when I did a monitor from the modem side.
So it was like the entire USG was technically frozen.
Finally had to pull the power lead and boom it powered back up no problem.
It looks like it wiped most of the log though but I saved everything I could see on USG and Controller.
No other part of the network had failed, not the modem (uptime ages), switch all good and I can SSH it.

Model:UniFi Security Gateway 4P running PPPoE over Bridge Modem


Version:4.4.36.5146617

Strangly it kicked the bucket near midnight but last log listed is 07:38 before issue (should have been like 00:01) and then after reboot I got it back up at 00:26!

 

Feb 13 07:38:18 UNIFI-USG-PRO4 kernel: IPv4: martian source 255.255.255.255 from 192.168.160.1, on dev eth2
Feb 13 07:38:19 UNIFI-USG-PRO4 ntpd[3229]: ntpd 4.2.6p2@1.2194-o Wed Dec 5 04:33:35 UTC 2018 (1)
Feb 13 07:38:19 UNIFI-USG-PRO4 ntpd[3230]: proto: precision = 30.206 usec
Feb 13 07:38:20 UNIFI-USG-PRO4 ntpd[3230]: ntpd exiting on signal 15
Feb 13 07:38:21 UNIFI-USG-PRO4 kernel: ll header: 00000000: ff ff ff ff ff ff 60 e3 27 a7 75 90 08 00 ......`.'.u...
Feb 13 07:38:22 UNIFI-USG-PRO4 ntpd[3307]: ntpd 4.2.6p2@1.2194-o Wed Dec 5 04:33:35 UTC 2018 (1)
Feb 13 07:38:22 UNIFI-USG-PRO4 ntpd[3308]: proto: precision = 26.201 usec
Feb 13 07:38:22 UNIFI-USG-PRO4 ubnt-service-ssh: waiting for netplugd to be started...
Feb 13 07:38:22 UNIFI-USG-PRO4 ubnt-service-gui: waiting for netplugd to be started...
Feb 13 07:38:24 UNIFI-USG-PRO4 kernel: IPv4: martian source 255.255.255.255 from 192.168.160.1, on dev eth2
Feb 13 07:38:26 UNIFI-USG-PRO4 xl2tpd[3471]: setsockopt recvref[30]: Protocol not available
Feb 13 07:38:27 UNIFI-USG-PRO4 kernel: IPv4: martian source 255.255.255.255 from 192.168.160.1, on dev eth2
Feb 13 07:38:27 UNIFI-USG-PRO4 kernel: ll header: 00000000: ff ff ff ff ff ff 60 e3 27 a7 75 90 08 00 ......`.'.u...
Feb 13 07:38:28 UNIFI-USG-PRO4 dhcpd: WARNING: Host declarations are global. They are not limited to the scope you declared them in.
Feb 14 00:26:47 UNIFI-USG-PRO4 kernel: IPv4: martian source 255.255.255.255 from 192.168.160.1, on dev eth2

 

and this in the controller log


[2019-02-14 00:00:00,437] <inform-193> INFO inform - from [********](UNIFI-USG-PRO4, UGW4, 4.4.36.5146617): state=CONNECTED, last_inform=96, ext/stun_ip=********, dev_ip=********, up=1484532
[2019-02-14 00:01:41,333] <inform-186> INFO inform - from [********](UNIFI-USG-PRO4, UGW4, 4.4.36.5146617): state=CONNECTED, last_inform=101, ext/stun_ip=********, dev_ip=********, up=1484625
[2019-02-14 00:03:55,474] <devmgr> INFO dev - [state] dev[********] CONNECTED->HEARTBEAT_MISSED, state_expire=0

Reply