Automatic association ROAMING CLIENT - SITE based on the Roaming client IP
Danny Trèves
We would like to see automatic Site/Policy and roaming client association implemented based on the IP of a roaming client.
For example, if a roaming client connects from a private network (IP SMARTWORKING) it should be automatically associated with the “IP SMARTWORKING SITE.”
Conversely, if a roaming client connects from a corporate network (IP CORPORATE Y) it should be automatically associated with the “IP CORPORATE Y SITE” site.
This would help to figure out which site each roaming client is in and then define site-specific policies for each site.
A default site could also be created if the roaming client does not connect from a defined IP.
Currently, there is no automatic association between a roaming client's IP and a site defined in DNSFILTER.
S
Stephen Frost
I want to lend my strong support to this proposal. It would add flexibility to deployment in a working-from-home world where staff with the roaming client installed are sometimes at home and other times at the office (where internal and external DNS is different a.k.a. split brain config)