On Tue, Aug 6, 2013 at 4:52 AM, David Sommerseth
<[email protected]> wrote:
>
> * Learn about TCP/IP networking, read especially chapter 3.1 in this
> book: <http://www.redbooks.ibm.com/redbooks/pdfs/gg243376.pdf>. I'll
> repeat: You MUST know how network traffic travels between hosts and routers.
Maybe, maybe not... Lots of people would be perfectly happy with a
bridged configuration - which isn't recommended because of performance
issues on large scales. And at least an equal number would be happy
with the openvpn host doing NAT on its LAN interface. But that's not
quite within the scope of openvpn itself, so not very clearly
documented. In either of those scenarios, you don't really need to
know much about network routing or the rest of the topology other than
perhaps the remote LAN's netmask. I'd guess that the main problem
people have is getting the remote side to route back, since unless you
design that way from the start, the openvpn gateway won't already be
the default router for the LAN you want to reach and bridging or NAT
will bypass that issue. Is there a simple guide for those setups so
the people who can use a simple configuration don't have to learn
enterprise routing first?
--
Les Mikesell
[email protected]
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
Openvpn-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openvpn-users
