ADMZ HH4000/Giga Hub Latency

[DPS1]

Hi All - I've posted a few times about this over the past year plus. I've tried ADMZ on several HH firmwares and just tried again on the latest (1.9x). I'm using a UNIFI Next Gen Firewall which displays latency. Within minutes of rebooting the HH and the UNIFI router, i receive a public IP and all working. But as you can see from the image i attached, i start immediately to get up to 70ms of latency. I switched back toa  double NAT and the latency disappears which you will see in the image. And yes ive tried PPOE with several routers including a XEON based Pfsense and i just cant get much bandwidth (1.4 down and 300 up). ON ADMZ i get 7.5Gigs up and down and same on the double NAT. Bottom line the firmware still isn't working well. 

[Vanadiel]

I use a Dream machine Pro SE without any latency issues. Did you reboot both devices after configuring ADMZ? Apparently some people with unifi devices have to do that in order to get it to work properly.

[DPS1]

Thank you very much for the tip. I did reboot both the home hub and my gateway device a few times in order to pick up the public IP. Once I got the IP, I didn’t reboot again. But I will enable the ADMZ once more and do a couple of reboots after I get the IP and report back

[DPS1]

Three reboots and still high latency. Only a yellow bar, no green on the internet health display. 

[Vanadiel]

I am assuming you are using ping.ui.com as internet verification server?

[DPS1]

No - either 8.8.8.8 or 1.1.1.1. Always founding using ui caused the devices to fail over incorrectly. 

[Vanadiel]

Try WinMTR and to 1.1.1.1 or 8.8.8.8.

ping.ui.com should work fine, it does on mine? 

[DPS1 · Accepted solution]

I ended up doing a factory reset, and when I set up the UXG pro, I pointed the echo to the IP of my core switch and it’s now running 100% without latency, I’m not doing any failover, so there was no need to go to a public IP. 

[Vanadiel]

I guess you could ping a switch on your LAN, but it would not provide any indication of internet services being up or down. That's the main purpose of the auto ping functionality of the unifi equipment. It's not so much to check latency, as it is to check connectivity to the internet.

[DPS1]

Yes, and no. The echo feature is really designed for failover. So if you lose Internet, the second link takes over. But if you don’t have one in my opinion, it’s a joke of a feature. So why not pinging an internal switch. And then if the Internet is down, it’s down anyway there’s not much you can do about it

[coolspot]

I'm having high latency issue in 1.19.5.1 firmware - with both PPPoE and ADMZ. The moment pfSense passes any traffic over the Gigahub, my latency skyrockets to 1,000+ ms.

Interestingly, I can still do a speed test and get a decent result, but surfing the web is vey slow due to latency.

The moment I failover to my Rogers Cable connection, latency returns to normal on the Bell link (since minimal traffic is being passed).

[DPS1]

I had very similar results with two different pfSense routers. I even bought their top-of-the-line unit with the Xeon processor, thinking that would help with PPOE processing but it didn’t. There’s been thousands of posts here and elsewhere about the fact that PPOE being a dinosaur technology will never work in terms of supporting full bandwidth. But I was able to get the latency to disappear using a UniFi gateway. And still getting full bandwidth.

[Vanadiel]

Ah yes, I see what you are saying. That does make sense. I use it to see when the modem rebooted last. That way I can keep track of firmware updates on the modem, and it's logged in the unifi logging system.

It will also show latency over a 24 hour period (14 msec flat line for me), and there's also the option to do an automatic speed test to keep track of that over a period of time.

[Doc132]

Experiencing the same high latency issues with pfsense on the latest FW Giga Hub 4000.

PPPoe had worked flawless till recently. Swapped out different hardware, same deal. Swapped out bell modems, no difference. Tried every tweak I could find for PPPoe on freebsd, no luck.

Speeds are good but the latency goes up to 300+ms in waves and comes back down to under 5ms and then back up again. Load or no load doesn't make a difference.

[coolspot]

In my case, it went away mysteriously after a week... it was an awful unusable week.