|
|
Use a VPN without it taking over the network
The issue lies in the fact that OS X does not support source-based routing. Any traffic that is not link-local is going to be sent out via your default route, which by default is going to be your IPSec tunnel when your VPN connection is active. When he's connecting from work to his home computer, his home machine sees an incoming connection from his office WAN IP: a publicly routable IP, notes that it is not link-local, and then fires the response via default route, straight down the VPN tunnel and ultimately to a destination that's going to drop it. Setting the internal subnet to be the default interface would then make all traffic go out through the nat router. Your still not going to have a problem on the VPN side, as the company subnet appears to be link-local. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.34 seconds |
|