On Demand Connections for Cascade Client?
Posted: Mon Aug 17, 2015 4:09 pm
I setup an HUB with cascade connections to multiple remote locations.
This allows me to manage all access from one place; wonderful.
Unfortunately, each cascade connection appears to be very overhead chatty (even with no intended traffic to the remote site) and eats up significant WAN bandwidth. I have tried multiple access control and filtering methods to remove broadcasts as well as limit cascade TCP connections to 1 or 2 but each cascade connection still generates significant overhead. Chatty as defined to be about 2-3Gig a month.
So, assuming no great ideas from you smart people on filtering methods....
Please consider adding an "on demand" cascade connections. The demand could potentially be identified by VLAN ID, remote Site IP subnet, other? One could consider it as well for the VPN client.
deep thoughts....
This allows me to manage all access from one place; wonderful.
Unfortunately, each cascade connection appears to be very overhead chatty (even with no intended traffic to the remote site) and eats up significant WAN bandwidth. I have tried multiple access control and filtering methods to remove broadcasts as well as limit cascade TCP connections to 1 or 2 but each cascade connection still generates significant overhead. Chatty as defined to be about 2-3Gig a month.
So, assuming no great ideas from you smart people on filtering methods....
Please consider adding an "on demand" cascade connections. The demand could potentially be identified by VLAN ID, remote Site IP subnet, other? One could consider it as well for the VPN client.
deep thoughts....