Err lol, I guess you forgot the actual MAIN use case of a VPN which is as a virtual PRIVATE network to connect your private home network to another one, like work-which is exactly what all the VPNs we use at work for do! :P
In which case it is most explicitly to route RFC1918 addresses over the VPN! Though on the VPN profile, since we're all mostly network folks ourselves, we let the users select which routes to route over the VPN (configurable on the client side), and we also can enable or disable local LAN access with a switch for printing and file sharing while connected (security vs ease-of-use), and we also control whether you have split DNS (let DNS requests go to both the local and VPN vservers). In any case, I'm sure you've realized this all by now, and this is more informational for anyone else wondering...HTH! BINO > From: [email protected] > Date: Tue, 27 Apr 2010 11:55:41 -0400 > To: [email protected] > Subject: Re: [H] VPN connection seals computer off from LAN > > That doesn't make any sense - 10. addresses cannot be routed via VPN, same > as 192. Both of those address ranges are explicitly defined as private and > cannot be routed on the Internet. The minute any packet with a 10. or 192. > or any other private range hits an internet router it gets dropped. > > I think on my end the issue was with the public vs private network > designations in Windows 7. I had the VPN connection defined as public which > means it is untrusted and Windows won't allow network discovery or file > sharing. I think somehow Windows got confused with the machine being on a > private (trusted) LAN and public (untrusted) WAN at the same time. Not sure > tho. > > --------------------------- > Brian Weeden > Technical Advisor > Secure World Foundation <http://www.secureworldfoundation.org> > +1 (514) 466-2756 Canada > +1 (202) 683-8534 US > > > On Tue, Apr 27, 2010 at 11:12 AM, Hunter, Gary > <[email protected]>wrote: > > > I had the same issue it was down to all 10. Addresses being routed down the > > VPN. I changed my home network to 192.168.. and now everything works fine, > > > > > > > > Gary Hunter > > Consulting Engineer > > Travelport GDS > > T: (+1) 303 - 397 - 5035 > > M:(+1) 720 - 231 - 0965 > > E: [email protected] > > SITA: HDQOK1G > > Travelport Product Development Center > > 6901 S Havana St > > Centennial, CO 80112 > > > > -----Original Message----- > > From: [email protected] [mailto: > > [email protected]] On Behalf Of Brian Weeden > > Sent: Sunday, April 25, 2010 10:45 AM > > To: hwg > > Subject: [H] VPN connection seals computer off from LAN > > > > This is very weird. I have a VPN setup and it's been acting weird - when I > > connect to it using one of the machines on my LAN, that machines > > effectively > > drops off the network. It can browse the internet just fine, but none of > > the other machines on the LAN can connect to it. Interestingly, although > > it > > says its LAN IP is still 10.0.1.2, I can't ping it with that IP. I have > > been using this VPN on this particular machine for months with no problems > > until recently. > > > > However, using the same VPN setup on another machine on the same LAN, it > > will connect to the VPN and still be visible on the LAN and can still > > connect to other clients on the LAN. I've double checked the VPN settings > > are they are exactly the same on both machines. > > > > Any ideas? > > > > --------------------------- > > Brian Weeden > > Technical Advisor > > Secure World Foundation <http://www.secureworldfoundation.org> > > +1 (514) 466-2756 Canada > > +1 (202) 683-8534 US > > If you are not the intended recipient of this e-mail message, please notify > > the sender > > and delete all copies immediately. The sender believes this message and any > > attachments > > were sent free of any virus, worm, Trojan horse, and other forms of > > malicious code. > > This message and its attachments could have been infected during > > transmission. The > > recipient opens any attachments at the recipient's own risk, and in so > > doing, the > > recipient accepts full responsibility for such actions and agrees to take > > protective > > and remedial action relating to any malicious code. Travelport is not > > liable for any > > loss or damage arising from this message or its attachments. > > > > > >
