Omada SDN / ER605 fails to track usage across VPN
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Omada SDN / ER605 fails to track usage across VPN
After much fiddling, I was finally able to create a dedicated local LAN subnet and route it across an L2TP client-server tunnel using a Policy Route.
What's interesting is that even though the device is wired direct to the SG-2008P v1 v 1.0.2, the switch port shows 0 bytes even when I have continuous traffic flowing.
it's definitely tracking the usage in the VPN stats
I assume the fact that the switch isn't reporting traffic that's clearly flowing out that port is an error?
<< Boycotting this site and these products until CANADIAN firmwares get some love >>