-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
James Wilkinson wrote:
| Kevin Fries wrote: | |> OK, maybe I am simplifying things a bit more than I should be, so |> let me ask: |> |> My conceptual understanding of VPN was that computerA needs |> access to NetworkB as if it were located on the physical network |> even though it is somewhere else. | | | That's one option. | | The one we mainly use at work looks like this: | | Main Site Remote Site 192.168.1.0 | <--- VPN ---> 192.168.2.0 | | Essentially, we have a conventional routed network. It's just that | the traffic goes over an encrypted channel. | | We used to do this over a leased line, a "private network" (as | opposed to the public Internet). | | Now we use encryption, encapsulation, and the Internet to achieve | the same effect. It's a virtual "private network".
ahhh, I see my shortsightedness now. I am trying to deal with road warriors, not remote offices. Your explanation makes perfect sense, I was just not thinking of it that way. I probably did not make that part as clear as I thought I had. The website for openvpn seems to spend allot of time on this scenario, but claims to handle the road warrior also. I will be testing that assumption this week since openvpn seems to be everyones favorite.
Kevin Fries
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFB4zOSiFq1Eo16+CgRAt8aAKDHu/GsdC0/1ezWFQdUs1TK7I01HgCgnQIK F807943i0ywjS2hl1Ypn2QM= =ODO3 -----END PGP SIGNATURE-----
