 |
 |
I can answer the second question. Yes it is possible to route specific traffic through the MSU VPN (Juniper Network Connect). I have done it for both Windows and Mac using the route command, which is available on both Mac OS X and Windows XP (maybe 2000) and higher. Our department subnet is not in the 35.8,9,10,11,12,13,14 or 35.15 subnets, so traffic to our servers is not routed through the MSU VPN by default. I am curious about the answer to the first question. Are we allowed to route MSU traffic through the vpn even though the addresses are not 35.x addresses? -Stefan On 11/15/2010 3:24 PM, Carl Raymond wrote: > I'm not getting any less paranoid as I get ready to start gently beginning > to approach middle age, and I have decided I don't want to do much of > anything online over an unsecured WiFi network. Now with Firefox plugins > like Firesheep it's all too easy to snoop browser cookies. So I want to use > a VPN pretty much all the time. > The MSU VPN protects traffic to and from MSU destinations only (right?). > Is it possible to use the MSU VPN on all my traffic, by changing the default > route? Specifically, is this allowed, and will it work? I can see why that > might be against policy, because of the extra traffic load. > If that's not an option, can anyone recommend a simple appliance that I > can install at home for this? I'd much prefer an out-of-the-box solution, > provided it's not crazy expensive. But if I have to I can find an old > vacuum cleaner and install Linux on it, or get a Linksys router and use > DD-WRT. But six months from now I bet I won't remember all the details. > > Any recommendations? Oh yeah: it needs to work with both Windows and OS > X. >