locationd wifi scanning creates network latency
I'm at my wits end, so I thought I'd post what I'm seeing here in case it possibly reaches someone that can resolve this problem. I've seen reference to this issue in a few threads now, with no real solutions. What I'm seeing is that any time I connect over WIFI to my Company's VPN (F5 VPN appliance) to work remotely, locationd begins scanning for new networks every 10 seconds. You can see clearly in the console log that each time locationd triggers this scan, latency increases and packets are sometimes even completely lost for a few seconds. Normally I'm sure this would go unnoticed, but traffic over the VPN stalls completely and makes the experience extremely frustrating for remote sessions like ssh or really any long lived TCP stream. I've been round with Apple support a few times and really just got a suggestion of sending feedback via the website, but I'm quite certain now that this is a bug on the Apple and/or possibly F5 side. Just curious if anyone has experienced this and has an actual solution to disable locationd scanning, or a pointer on how to get someone to actually look at this problem to resolve it.
The locationd entries in console log look like the below. Again, this doesn't happen unless I'm connected to the VPN. I assume it's something about the interface or routing changes the VPN makes that cause this madness in locationd:
default 19:53:25.754000 -0500 locationd CoreWLAN event <private>, resultCount, <private>
default 19:53:25.754073 -0500 locationd WIFI_LOC: location services are disabled, ignore scan result
default 19:53:26.045685 -0500 locationd CoreWLAN event <private>, resultCount, <private>
default 19:53:26.045762 -0500 locationd WIFI_LOC: location services are disabled, ignore scan result
MacBook Pro TouchBar and Touch ID, macOS High Sierra (10.13.6)