On 20/03/11 21:40, Elazar Leibovich wrote:
On a side note, the VPN client on windows shoves entries to the
routing table which seems to depend on the actual network I'm
connecting to (192.18.4.* for instance, I don't think it does so for
all networks), how does it know the destination network topology.
It communicates with the server. All VPN solutions I know do this
(including openvpn).
On another side note, what does it do if I'm having a 192.168.4.*
internal network?
Then you are @!#*%!@#$@!)(!@#&%@#! !@(%!@#()#!@$!@%#. VPN is designed to
connect disparaged networks as if they are close together. My Mom
thought about connecting to the insurance company's VPN. They allocated
her a 10/8 based address. There were two such companies. One allocated
the address, and the other told us to use the address allocated by the
first one. That's just how things are done. I'm not sure what they'd do
had we told them we do not carry policies for the first one.
The good news is that RFC 1918 has so many IP addresses, you are almost
bound to be able to use an address with a small enough mask to be unique
even when your clients go to random hotels around the globe.
Shachar
--
Shachar Shemesh
Lingnu Open Source Consulting Ltd.
http://www.lingnu.com
_______________________________________________
Linux-il mailing list
Linux-il@cs.huji.ac.il
http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
