You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Insight, I see all my interfaces for IN, but only a few for OUT and at least one of them has the wrong label.
Here is what I see in OUT
wan
the VLANs
one OpenVPN connection with the wrong label
I know the label is wrong because lots of traffic is going in and out of a different VPN connection and it's reported as such by the traffic page.
I would expect to see all the active VPN connections in OUT, but looking at the details in the "Top usage ports", I can see that the Out is 0 for the interfaces which are missing from the graphs, which is incorrect.
Also, I'm not sure what wan is supposed to show. wan OUT seem to aggregate all the connections, but IN is not.
I'm using gateway groups for the VPN connections, so maybe the collector is having a hard time matching traffic measured at the hardware level with the virtual interfaces?
The text was updated successfully, but these errors were encountered:
In my list of interfaces I've selected
In my list of "Egress only", I've selected
In Insight, I see all my interfaces for IN, but only a few for OUT and at least one of them has the wrong label.
Here is what I see in OUT
I know the label is wrong because lots of traffic is going in and out of a different VPN connection and it's reported as such by the traffic page.
I would expect to see all the active VPN connections in OUT, but looking at the details in the "Top usage ports", I can see that the Out is 0 for the interfaces which are missing from the graphs, which is incorrect.
Also, I'm not sure what wan is supposed to show. wan OUT seem to aggregate all the connections, but IN is not.
I'm using gateway groups for the VPN connections, so maybe the collector is having a hard time matching traffic measured at the hardware level with the virtual interfaces?
The text was updated successfully, but these errors were encountered: