<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>On 15 Feb 2017, at 15:46, Hugh Glaser <<a href="mailto:hg@ecs.soton.ac.uk">hg@ecs.soton.ac.uk</a>> wrote:</div><div><br></div><blockquote type="cite"><div><span>Wow.</span><br><span>Yeah, I had a feeling that it was part of the Cisco vision - can't have those pesky users not going through the corporate network, etc..</span><br><span>Mustn't even give them the option by hiding it somewhere.</span><br><span>Since you haven't mentioned it, I am guessing there isn't some obvious plist file that cane hacked, or some routing table "improvements" I can do?</span><br></div></blockquote><br><div>See <a href="http://superuser.com/questions/91191/how-to-force-split-tunnel-routing-on-mac-to-a-cisco-vpn">http://superuser.com/questions/91191/how-to-force-split-tunnel-routing-on-mac-to-a-cisco-vpn</a> ? Not tried it, but it makes sense, i.e. add a route for 152.78.0.0/16 down the tunnel, and everything else via your home router IP address.</div><div><br></div><div>Tim</div></body></html>