USG clients activity through LAN connection reporting as 0bps

Associate
Joined
18 Jun 2020
Posts
354
Location
Warminster
I'm having fun with my new USG setup, it's fascinating having a better insight into the goings on in my network. However, I have a quick question...

For all my WiFi clients, I can see their activity (activity, activity down, activity up). However, for my wired clients, this information is all blank. I'm assuming this is something to do with the fact that I'm not running them through Unifi switches?

Assuming the above assumption is correct, will I need to replace all my switches with Unifi switches, or would it only need to be the switch immediately after my USG?

Current set up is USG -> 8 port switch -> 24 port switch. I have clients running off both switches.

(Originally posted in UI Community, but no luck getting any help there :( )
 
Assuming, you’re not shutting down the controller then it’s completely normal. DPI is broken and has been for a long time. Are you using a separate DNS server? If you want DPI to be anything remotely accurate you have to use the USG as the DNS server for everything.
 
Assuming, you’re not shutting down the controller then it’s completely normal. DPI is broken and has been for a long time. Are you using a separate DNS server? If you want DPI to be anything remotely accurate you have to use the USG as the DNS server for everything.

My controller is hosted on my Raspberry Pi, so never shut down. The Pi is also running Pi-hole.

Why do my WiFi clients have stats, but my LAN clients don't? Is this, as I was suggesting in my OP, something to do with the fact I'm not using Unifi switches?
 
My controller is hosted on my Raspberry Pi, so never shut down. The Pi is also running Pi-hole.

Why do my WiFi clients have stats, but my LAN clients don't? Is this, as I was suggesting in my OP, something to do with the fact I'm not using Unifi switches?

No, all WAN traffic passes through the USG so it’s all being logged by the router. You do have DPI enabled in the controller I take it?
 
And all the clients use the USG as their DNS server and the USG uses the Pi Hole address?

Well no - the clients are all given the Pi-hole address as DNS server, as this (apparently) is the only way of getting the Pi-hole to report on their activity individually, rather than just reporting all activity as the USG's address.

However, as far as I can remember, the stats weren't appearing before I made the change in Settings > Networks > LAN, setting the Pi address as manual DHCP Name Server
 
Well no - the clients are all given the Pi-hole address as DNS server, as this (apparently) is the only way of getting the Pi-hole to report on their activity individually, rather than just reporting all activity as the USG's address.

However, as far as I can remember, the stats weren't appearing before I made the change in Settings > Networks > LAN, setting the Pi address as manual DHCP Name Server

Why would the USG be any different to the Pi Hole? The WLAN stats are fed back to the controller directly from the access point but it’s the USG that reports the LAN client activity because unless it knows the categorisation of each request, it can’t categorise the data. I suspect even your WLAN stats are wrong.
 
Why would the USG be any different to the Pi Hole? The WLAN stats are fed back to the controller directly from the access point but it’s the USG that reports the LAN client activity because unless it knows the categorisation of each request, it can’t categorise the data. I suspect even your WLAN stats are wrong.

I asked the question about whether the USG forces clients to use it as their DNS server in this question on the Ubiquiti community - https://community.ui.com/questions/...f#answer/98c6c883-061d-48df-977a-72d9a0bb5400 - and was advised to change the DHCP Name Server to the Pi-hole's IP address

Whether the WLAN stats are right or wrong, I'm unsure. However, the fact remains that something at least is being reported for my WiFi clients, but nothing at all being reported for my LAN clients
 
My set up shows (or doesn't show) the same information. IP addresses and traffic stats are fine for wireless clients. Nothing for wired.

A bit of research and elimination and I've just put it down to a fault with the Controller. My Controller is also a Pi and I was using the same for Pi-hole but I've moved to solely OpenDNS for the time being because I noticed the Pi-hole was slowing requests down, probably due to the resource heavy controller on the same Pi. I need another Pi to resolve this.

So, I eliminated the Pi-hole causing issues. I don't have a USG yet but I do have a couple of Flex Mini switches so I was also able to eliminate any non-Unifi switches. Nothing changed so I think it is the controller that doesn't report these stats correctly.
 
My set up shows (or doesn't show) the same information. IP addresses and traffic stats are fine for wireless clients. Nothing for wired.

A bit of research and elimination and I've just put it down to a fault with the Controller. My Controller is also a Pi and I was using the same for Pi-hole but I've moved to solely OpenDNS for the time being because I noticed the Pi-hole was slowing requests down, probably due to the resource heavy controller on the same Pi. I need another Pi to resolve this.

So, I eliminated the Pi-hole causing issues. I don't have a USG yet but I do have a couple of Flex Mini switches so I was also able to eliminate any non-Unifi switches. Nothing changed so I think it is the controller that doesn't report these stats correctly.

Thanks @batfink for sharing your experience. Glad to hear I'm not going mad! However, I'm more than open to suggestions @WJA96 if you think there are any config changes I can make?
 
Back
Top Bottom