171 lines
3.3 KiB
HTML
171 lines
3.3 KiB
HTML
<HTML
|
|
><HEAD
|
|
><TITLE
|
|
>Planning</TITLE
|
|
><META
|
|
NAME="GENERATOR"
|
|
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
|
|
"><LINK
|
|
REL="HOME"
|
|
TITLE="VPN HOWTO"
|
|
HREF="index.html"><LINK
|
|
REL="UP"
|
|
TITLE="Implementation"
|
|
HREF="implemenetation.html"><LINK
|
|
REL="PREVIOUS"
|
|
TITLE="Implementation"
|
|
HREF="implemenetation.html"><LINK
|
|
REL="NEXT"
|
|
TITLE="Gather the tools
|
|
"
|
|
HREF="x375.html"></HEAD
|
|
><BODY
|
|
CLASS="sect1"
|
|
BGCOLOR="#FFFFFF"
|
|
TEXT="#000000"
|
|
LINK="#0000FF"
|
|
VLINK="#840084"
|
|
ALINK="#0000FF"
|
|
><DIV
|
|
CLASS="NAVHEADER"
|
|
><TABLE
|
|
SUMMARY="Header navigation table"
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TH
|
|
COLSPAN="3"
|
|
ALIGN="center"
|
|
>VPN HOWTO</TH
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="left"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="implemenetation.html"
|
|
ACCESSKEY="P"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="80%"
|
|
ALIGN="center"
|
|
VALIGN="bottom"
|
|
>Chapter 5. Implementation</TD
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="right"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="x375.html"
|
|
ACCESSKEY="N"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"></DIV
|
|
><DIV
|
|
CLASS="sect1"
|
|
><H1
|
|
CLASS="sect1"
|
|
><A
|
|
NAME="AEN370">5.1. Planning</H1
|
|
><P
|
|
> Let's imagine that we have a company, called mycompany.com. At our head
|
|
office, we are using the 192.168.0.0 reserved network, breaking the
|
|
class B into 256 class C networks to allow routing. We have just set up
|
|
two small remote offices, and want to add them to our network. We also
|
|
want to allow employees who work from home to be able to use their DSL
|
|
and cable modem connections instead of making them use dialup. To
|
|
start, we need to plan things out a little.
|
|
</P
|
|
><P
|
|
> I decide that I want to give each remote office a class C network range
|
|
to allow them to expand as necessary. So, I reserve the 192.168.10.0
|
|
and 192.168.11.0 nets. I also decide that for home users, I've got
|
|
enough numbers that I don't need to masquerade them on the VPN server
|
|
side. Each client gets it's own internal IP. So, I need to reserve
|
|
another class C for that, say 192.168.40.0. The only thing that I must
|
|
now do is to add these ranges to my router. Let's imagine that our
|
|
company owns a small Cisco (192.168.254.254) that handles all of the
|
|
traffic through our OC1. Just set routes on the Cisco such that traffic
|
|
headed to these reserved nets goes to our VPN server (192.168.40.254).
|
|
I put the VPN server into the home user's net for reasons that should
|
|
become clear later. We'll name the external interface of the server
|
|
vpn.mycompany.com, and the internal vpn-internal.mycompany.com.
|
|
</P
|
|
><P
|
|
> As for external numbers, we don't need to know them explicitly. You
|
|
should have your own numbers, supplied by your ISP.
|
|
</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="NAVFOOTER"
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"><TABLE
|
|
SUMMARY="Footer navigation table"
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="implemenetation.html"
|
|
ACCESSKEY="P"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="index.html"
|
|
ACCESSKEY="H"
|
|
>Home</A
|
|
></TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="x375.html"
|
|
ACCESSKEY="N"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
>Implementation</TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="implemenetation.html"
|
|
ACCESSKEY="U"
|
|
>Up</A
|
|
></TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
>Gather the tools</TD
|
|
></TR
|
|
></TABLE
|
|
></DIV
|
|
></BODY
|
|
></HTML
|
|
> |