From: <ow...@us...> - 2010-08-29 19:35:30
|
Revision: 4895 http://ipcop.svn.sourceforge.net/ipcop/?rev=4895&view=rev Author: owes Date: 2010-08-29 19:35:23 +0000 (Sun, 29 Aug 2010) Log Message: ----------- Rework first part(s) of the installation manual Modified Paths: -------------- IPCopDoc/trunk/en/install/xml/preparation.xml Modified: IPCopDoc/trunk/en/install/xml/preparation.xml =================================================================== --- IPCopDoc/trunk/en/install/xml/preparation.xml 2010-08-29 09:19:37 UTC (rev 4894) +++ IPCopDoc/trunk/en/install/xml/preparation.xml 2010-08-29 19:35:23 UTC (rev 4895) @@ -74,277 +74,184 @@ </para> </sect1> - <sect1 id="preparation-decide-configuration"> - <title>Decide On Your Configuration</title> - <sect2 id="preparation-network-interfaces"> - <title>Network Interfaces</title> - <para> - IPCop defines up to four network interfaces, RED, - GREEN, BLUE and ORANGE. - </para> - <sect3 id="red-interface"> - <title>RED Network Interface</title> - <para> - This network is the Internet or other untrusted - network. - IPCop's primary purpose is to protect the - GREEN, BLUE and ORANGE networks and their computers from - traffic originating on the RED network. - Your current connection method and hardware are - used to connect to this network. - </para> - </sect3> - <sect3 id="green-interface"> - <title>GREEN Network Interface</title> - <para> - This interface only connects to the computer(s) - that IPCop is protecting. - It is presumed to be local. - Traffic to it is routed though an Ethernet NIC on - the IPCop computer firewall. - </para> - </sect3> - <sect3 id="blue-interface"> - <title>BLUE Network Interface</title> - <para> - This optional network allows you to place - wireless devices on a separate network. - Computers on this network cannot get to the GREEN - network except tightly controlled <quote>pinholes</quote>, or via a VPN. - Traffic to this network is routed through an - Ethernet NIC. - </para> - </sect3> - <sect3 id="orange-interface"> - <title>ORANGE Network Interface</title> - <para> - This optional network allows you to place - publicly accessible servers on a separate network. - Computers on this network cannot get to the GREEN or BLUE - networks, except through tightly controlled - <quote>DMZ pinholes</quote>. - Traffic to this network is routed through an - Ethernet NIC. - </para> - </sect3> - <sect3> - <title>Network Interfaces</title> - <para> - Your firewall will need at least 1 Ethernet cable and network interface - card (NIC). - It may need up to 4 NICs, depending on the network configuration - you choose and your connection to the Internet. - </para> - <para> - All NICs must be different physical cards (or their equivalent if you - have multiport cards). - </para> - <para> - Ignoring for a moment the RED network, you will have to plug a - separate Ethernet NIC and cable into your firewall for each of the - GREEN, BLUE and/or ORANGE network. - The GREEN and RED networks are required. - The ORANGE and BLUE networks are optional. - The interface requirements for your RED network will vary depending - on your connection to the Internet. - The RED network may require an additional Ethernet card and cable. - </para> - <para> - <mediaobject id="fullconfig"> - <imageobject role="fo"> - <imagedata - fileref="&imagepath;01a-network.&imageext;" - format="JPG" - contentwidth="16cm"/> - </imageobject> - <imageobject role="html"> - <imagedata - fileref="&imagepath;01a-network.&imageext;" - format="JPG"/> - </imageobject> - <textobject> - <phrase>sample networks</phrase> - </textobject> - <caption> - <para> - RED, ORANGE, BLUE, GREEN Configuration - </para> - </caption> - </mediaobject> - </para> - <para> - The - <link linkend="fullconfig">RED, ORANGE, BLUE, GREEN - diagram</link> - shows that, other than the RED net, each of the networks - needs an Ethernet card. - If you are currently using an Ethernet connection to the - Internet, you will need a card for it, too. - The networks must have different network addresses. - </para> - <note> - <para> - Remember, the BLUE and ORANGE networks are - optional. - </para> - </note> - <table frame="all"> - <title>NIC Requirements</title> - <tgroup cols="5" align="left" colsep="1" rowsep="1"> - <colspec colname="Networks"/> - <colspec colname="Networks"/> - <colspec colname="Networks"/> - <colspec colname="modem"/> - <colspec colname="ISDN"/> - <colspec colname="USBADSL"/> - <colspec colname="eithernet"/> - <thead> - <row> - <entry>Connection</entry> - <entry>Modem</entry> - <entry>ISDN</entry> - <entry>USB ADSL</entry> - <entry>Ethernet</entry> - </row> - </thead> - <tbody> - <row> - <entry><emphasis role="bold">RED, GREEN</emphasis></entry> - <entry>1 NIC (G)</entry> - <entry>1 NIC (G)</entry> - <entry>1 NIC (G)</entry> - <entry>2 NICs (G,R)</entry> - </row> - <row> - <entry><emphasis role="bold">RED, BLUE, GREEN</emphasis></entry> - <entry>2 NICs (B,G)</entry> - <entry>2 NICs (B,G)</entry> - <entry>2 NICs (B,G)</entry> - <entry>3 NICs (B,G,R)</entry> - </row> - <row> - <entry><emphasis role="bold">RED, ORANGE, GREEN</emphasis></entry> - <entry>2 NICs (O,G)</entry> - <entry>2 NICs (O,G)</entry> - <entry>2 NICs (O,G)</entry> - <entry>3 NICs (O,G,R)</entry> - </row> - <row> - <entry><emphasis role="bold">RED, ORANGE, BLUE, GREEN</emphasis></entry> - <entry>3 NICs (O,B,G)</entry> - <entry>3 NICs (O,B,G)</entry> - <entry>3 NICs (O,B,G)</entry> - <entry>4 NICs (O,B,G,R)</entry> - </row> - </tbody> - </tgroup> - </table> - </sect3> - <sect3> - <title>Relative Security of IPCop Network Interfaces</title> - <para> - The security model of IPCop is that the GREEN network is fully - trusted and any requests from this network, whether initiated by a - user or by a machine infected with a virus, Trojan horse or other - <quote>malware</quote> is legitimate and allowed by IPCop. - </para> - <para> - A new feature of IPCop 2.0.0, allows to set policies for each network - interface. This makes it possible to allow only specific traffic to - RED and IPCop. - </para> - <para> - The order of trustworthiness of networks in order of increasing - trust is: - </para> - <para> - RED→ORANGE→BLUE→GREEN - </para> - </sect3> - </sect2> +<sect1 id="preparation-decide-configuration"> + <title>Decide On Your Configuration</title> + <para> + The base configuration is <link linkend="red-interface">RED</link> + /<link linkend="green-interface">GREEN</link> where IPCop protects a + single internal network from the Internet. + If you have a wireless access point then you can attach it to the + <link linkend="blue-interface">BLUE</link> network interface and + configure IPCop to restrict the access of machines on your wireless LAN. + If you have some servers that need to be accessible from the Internet + you can place them in an untrusted DMZ attached to the + <link linkend="orange-interface">ORANGE</link> network interface. + </para> + <para> + Although you can easily change the network interfaces later, it is + advisable to have a plan before you start installation. + </para> + <para> + <itemizedlist> + <listitem> + <para><link linkend="preparation-network-interfaces"><guimenuitem>Network Interfaces</guimenuitem></link> — + Description of IPCop network interfaces. + </para> + </listitem> + <listitem> + <para><link linkend="preparation-connecting-internet"><guimenuitem>RED connection</guimenuitem></link> — + How are you currently connecting to the Internet. + </para> + </listitem> + <listitem> + <para><link linkend="preparation-local-address"><guimenuitem>Network Address(es)</guimenuitem></link> — + Decide On Your Local Network Address(es). + </para> + </listitem> + </itemizedlist> + </para> + <sect2 id="preparation-network-interfaces"> + <title>Network Interfaces</title> + <para> + IPCop defines up to four network interfaces, RED, + GREEN, BLUE and ORANGE. + </para> + <sect3 id="red-interface"> + <title>RED Network Interface</title> + <para> + This network is the Internet or other untrusted network. + IPCop's primary purpose is to protect the + GREEN, BLUE and ORANGE networks and their computers from + traffic originating on the RED network. + Your current connection method and hardware are + used to connect to this network. + </para> + </sect3> + <sect3 id="green-interface"> + <title>GREEN Network Interface</title> + <para> + This network only connects to the computer(s) that IPCop is + protecting. It is presumed to be local. + Traffic to it is routed through an Ethernet NIC. + </para> + </sect3> + <sect3 id="blue-interface"> + <title>BLUE Network Interface</title> + <para> + This optional network allows you to place + wireless and/or wired devices on a separate network. + Computers on this network cannot get to the GREEN + network except via tightly controlled <quote>pinholes</quote>, + or via a VPN. + Traffic to this network is routed through an Ethernet NIC. + </para> + </sect3> + <sect3 id="orange-interface"> + <title>ORANGE Network Interface</title> + <para> + This optional network allows you to place publicly accessible + servers on a separate network. + Computers on this network cannot get to the GREEN or BLUE + networks, except through tightly controlled + <quote>pinholes</quote>. + Traffic to this network is routed through an Ethernet NIC. + </para> + </sect3> + <sect3> + <title>Network Interfaces</title> + <para> + Your firewall will need at least 1 Ethernet cable and network interface + card (NIC). + It may need up to 4 NICs, depending on the network configuration + you choose and your connection to the Internet. + </para> + <para> + All NICs must be different physical cards (or their equivalent if you + have multiport cards). + </para> + <para> + Ignoring for a moment the RED network, you will have to plug a + separate Ethernet NIC and cable into your firewall for each of the + GREEN, BLUE and/or ORANGE network. + The GREEN and RED networks are required. + The ORANGE and BLUE networks are optional. + The interface requirements for your RED network will vary depending + on your connection to the Internet. + The RED network may require an additional Ethernet card and cable. + </para> + <para> + <mediaobject id="fullconfig"> + <imageobject role="fo"> + <imagedata fileref="&imagepath;01a-network.&imageext;" format="JPG" contentwidth="16cm"/> + </imageobject> + <imageobject role="html"> + <imagedata fileref="&imagepath;01a-network.&imageext;" format="JPG"/> + </imageobject> + <textobject> + <phrase>sample networks</phrase> + </textobject> + <caption> + <para> + RED, ORANGE, BLUE, GREEN Configuration + </para> + </caption> + </mediaobject> + </para> + <para> + The + <link linkend="fullconfig">RED, ORANGE, BLUE, GREEN diagram</link> + shows that, other than the RED net, each of the networks + needs an Ethernet card. + If you are currently using an Ethernet connection to the + Internet, you will need a card for it, too. + The networks must have different network addresses. + </para> + <note> + <para> + Remember, the BLUE and ORANGE networks are optional. + </para> + </note> + </sect3> + <sect3> + <title>Relative Security of IPCop Network Interfaces</title> + <para> + The security model of IPCop is that the GREEN network is fully + trusted and any requests from this network, whether initiated by a + user or by a machine infected with a virus, Trojan horse or other + <quote>malware</quote> is legitimate and allowed by IPCop. + </para> + <para> + A new feature of IPCop 2.0.0, allows to set policies for each network + interface. This makes it possible to allow only specific traffic to + RED and IPCop. + </para> + <para> + The order of trustworthiness of networks in order of increasing + trust is: + </para> + <para> + RED→ORANGE→BLUE→GREEN + </para> + </sect3> + </sect2> - <sect2 id="preparation-network-config"> - <title>Network Configurations</title> - <para> - The base configuration is RED/GREEN where IPCop - protects a single internal network from the Internet. - If you have a wireless access point then you can attach - it to the BLUE NIC and configure IPCop to restrict the - access of machines on your wireless LAN. - If you have some servers that need to be accessible to the - Internet you can place them in an untrusted DMZ attached to - the ORANGE NIC. - You should decide which combination you want for your - site. + <sect2 id="preparation-connecting-internet"> + <title>Connecting to the Internet or External Network</title> + <para> + How are you currently connecting to the Internet, today? + </para> + <para> + If you are connected through an external broadband modem or + router, you probably will be connected via an Ethernet + network interface card or NIC. + In any case, a similar card must be in your IPCop PC. + If you are connected via an internal analog modem, + ISDN modem, or ADSL USB modem, this must be moved to + the IPCop PC. + If you are connected via an external dial up modem, you will have + to connect it to your IPCop PC. </para> - </sect2> - <sect2 id="preparation-network-config-types"> - <title>Network Configuration Types</title> <para> - Since the RED interface can connect either by modem - or by Ethernet, there are eight Network Configuration Types: - </para> - <itemizedlist> - <listitem> - <para> - GREEN (RED is modem/ISDN) - </para> - </listitem> - <listitem> - <para> - GREEN + RED (RED is Ethernet) - </para> - </listitem> - <listitem> - <para> - GREEN + ORANGE + RED (RED is Ethernet) - </para> - </listitem> - <listitem> - <para> - GREEN + ORANGE (RED is modem/ISDN) - </para> - </listitem> - <listitem> - <para> - GREEN + BLUE + RED (RED is Ethernet) - </para> - </listitem> - <listitem> - <para> - GREEN + BLUE (RED is modem/ISDN) - </para> - </listitem> - <listitem> - <para> - GREEN + BLUE + ORANGE + RED (RED is Ethernet) - </para> - </listitem> - <listitem> - <para> - GREEN + BLUE + ORANGE (RED is modem/ISDN) - </para> - </listitem> - </itemizedlist> - </sect2> - - <sect2 id="preparation-connecting-internet"> - <title>Connecting to the Internet or External Network</title> - <para> - How are you currently connecting to the Internet, today? - </para> - <para> - If you are connected through an external broadband modem or - router, you probably will be connected via an Ethernet - network interface card or NIC. - In any case, a similar card must be in your IPCop PC. - If you are connected via an internal analog modem, - ISDN modem, or ADSL USB modem, this must be moved to - the IPCop PC. - If you are connected via an external dial up modem, you will have - to connect it to your IPCop PC. - </para> - <para> This hardware will be used for your RED network interface. </para> <para> @@ -407,8 +314,7 @@ <prompt>C:\></prompt><userinput>winipcfg</userinput> </screen> entered from the command prompt. - On Windows NT and Windows 2000, - the command is + On Windows NT, 2000, XP, Windows 7, etc. the command is <screen format="linespecific"> <prompt>C:\></prompt><userinput>ipconfig /all</userinput> </screen> @@ -439,8 +345,8 @@ This is not the IP address provided by your ISP. Addresses on this interface will never appear on the Internet. - IPCop uses a technique called Port Address Translation, - PAT, to hide your GREEN machines from outside eyes. + IPCop uses a technique called Network Address Translation, + NAT, to hide your GREEN machines from outside eyes. To make sure there are no IP address conflicts, it is suggested that you choose one of the address ranges defined in This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <ow...@us...> - 2010-09-03 17:29:25
|
Revision: 4924 http://ipcop.svn.sourceforge.net/ipcop/?rev=4924&view=rev Author: owes Date: 2010-09-03 17:29:15 +0000 (Fri, 03 Sep 2010) Log Message: ----------- More changes for the preparation chapter Modified Paths: -------------- IPCopDoc/trunk/en/install/xml/preparation.xml Modified: IPCopDoc/trunk/en/install/xml/preparation.xml =================================================================== --- IPCopDoc/trunk/en/install/xml/preparation.xml 2010-09-03 17:07:42 UTC (rev 4923) +++ IPCopDoc/trunk/en/install/xml/preparation.xml 2010-09-03 17:29:15 UTC (rev 4924) @@ -28,7 +28,8 @@ </para> </caption> </mediaobject></para> - <sect1 id="preparation-architectures"> + +<sect1 id="preparation-architectures"> <title>Supported Architectures</title> <para> Starting with IPCop 2.0.0 multiple architectures are @@ -494,6 +495,10 @@ If you are installing from USB key, you may need to set some bios options. Turn off all types of boot, except your hard drive after installation completes. </para> + <para> + If you are installing from network (PXE), you may need to set some bios options. + Turn off all types of boot, except your hard drive after installation completes. + </para> </listitem> </itemizedlist> </sect1> @@ -502,11 +507,11 @@ <title>Decide Upon and Prepare the Installation Media</title> <para> Obtain installation files from - <ulink url="https://sourceforge.net/project/showfiles.php?group_id=40604"> + <ulink url="http://sourceforge.net/projects/ipcop/files/"> www.ipcop.org</ulink>. The size of image files is about 60 megabytes. You should check the - <ulink url="http://ipcop.sourceforge.net/modules.php?op=modload&name=FAQ&file=index&myfaq=yes&id_cat=3#q15"> + <ulink url="http://sourceforge.net/apps/mediawiki/ipcop/index.php?title=FAQInstallation#md5"> MD5 checksum</ulink> of the file you downloaded against the one on the IPCop web site before going any further. @@ -560,7 +565,7 @@ <entry>N</entry> </row> <row> - <entry align="left">PXE boot with CD</entry> + <entry align="left">netboot with CD</entry> <entry>Y</entry> <entry>N</entry> <entry>Y</entry> @@ -570,7 +575,7 @@ <entry>N</entry> </row> <row> - <entry align="left">PXE boot with USB key</entry> + <entry align="left">netboot with USB key</entry> <entry>N</entry> <entry>Y</entry> <entry>Y</entry> @@ -580,7 +585,7 @@ <entry>N</entry> </row> <row> - <entry align="left">PXE boot with FTP/Web Server</entry> + <entry align="left">netboot with FTP/Web Server</entry> <entry>N</entry> <entry>N</entry> <entry>Y</entry> @@ -610,7 +615,7 @@ <entry>N</entry> </row> <row> - <entry align="left">Bootable Floppy with FTP/Web Server </entry> + <entry align="left">Bootable Floppy with FTP/Web Server</entry> <entry>N</entry> <entry>N</entry> <entry>N</entry> @@ -635,6 +640,10 @@ </para> </note> + <para> + Most IPCop installation are done with CD or USB key, because it is + much easier compared to the other methods. + </para> <para> If the IPCop PC has a CD drive and its BIOS can boot from CD, you should use the <quote>Bootable CD</quote> media for the @@ -642,20 +651,36 @@ The CD drive can be removed after the installation. </para> <para> - If the IPCop PC has USB and can its BIOS can boot from USB key, + If the IPCop PC has USB and its BIOS can boot from USB key, the <quote>Bootable USB key</quote> media can be used. </para> <para> + If the IPCop PC can use netboot (PXE), the + <quote>netboot</quote> media can be used. Choose + <quote>netboot with CD</quote> if the IPCop PC has a CD, + <quote>netboot with USB key</quote> if the IPCop PC has USB or + <quote>netboot with FTP/Web Server</quote>. + </para> + <para> If the IPCop PC cannot boot from CD, but has both a floppy drive and a CD drive, the <quote>Bootable Floppy With CD</quote> can be used. Both the floppy drive and CD drive can be removed after the install. However, if you plan on using IPCop's backup and restore - facilities, you may want to keep the floppy disk in the + facilities, you may want to keep the floppy drive in the IPCop PC. </para> <para> + If the IPCop PC cannot boot from CD, but has both a + floppy drive and USB, the <quote>Bootable Floppy + With USB key</quote> can be used. + The floppy drive can be removed after the install. + However, if you plan on using IPCop's backup and restore + facilities, you may want to keep the floppy drive in the + IPCop PC. + </para> + <para> Finally, if the IPCop PC has only a floppy drive or you do not own a CD burner, the <quote>Bootable Floppy with FTP/Web Server</quote> must be used. @@ -665,8 +690,6 @@ IPCop PC. </para> - <para>TODO: describe the other methods. Sigh we have way too many options ;-)</para> - <sect2 id="preparation-creating-cd"> <title>Creating the CD</title> <para> @@ -690,86 +713,17 @@ </sect2> <sect2 id="preparation-creating-netboot"> - <title>Creating PXE (netboot)</title> + <title>Creating netboot (PXE)</title> <para> Text to be written. </para> </sect2> - <sect2 id="preparation-mounting-iso"> - <title>Mounting the ISO Image</title> - <para> - If you don't have a CD writer, have no fear. - You can still install IPCop, but you will have to go - through some extra work. - What has to be done depends upon the hardware and - operating systems you have available on other computers. - </para> - <sect3 id="mounting-iso-linux"> - <title>Linux</title> - <para> - If you have a Linux or Unix system, you can mount - the CD image, using the following commands: -<screen format="linespecific"> -<prompt># </prompt><userinput>losetup /dev/loop0 /path/to/IPCop/iso</userinput> -</screen> - where - <parameter class="command"> - /path/to/IPCop/iso - </parameter> - is the file name of IPCop's - <filename class="extension"> - iso - </filename> - file. - This links a <quote>loop back</quote> hardware - level device to the IPCop ISO file. -<screen format="linespecific"> -<prompt># </prompt><userinput>mount -r -t iso9660 /dev/loop0 /mnt/cdrom</userinput> -</screen> - This actually mounts the loop back hardware device on a *nix - file system. - The CD-ROM image will appear at - <filename class="directory"> - /mnt/cdrom</filename>. - NOTE: On most systems you must have root authority - or use the - <command> - sudo - </command> - command to mount file systems. - </para> - </sect3> - - <sect3 id="mounting-iso-windows"> - <title>Windows</title> - <para> - There are several utilities such as ISOBuster and - WinImage available on the Internet that can be - used to open the ISO image. - Download one of them, and follow their directions - to open the IPCop ISO file. - </para> - </sect3> - - <sect3 id="mounting-iso-macintosh"> - <title>Macintosh</title> - <para> - On Macintosh OS X, Apple's Disk Copy utility - will open the ISO image. - There does not seem to be a free or public domain - utility available to open IPCop's ISO images - on Mac systems before OS X. - However, many commercial CD-ROM burning programs - do have this capability. - If you have a CD burner, check the software that - came with it. - </para> - </sect3> - </sect2> - <sect2 id="preparation-creating-floppy"> <title>Creating Floppy Disks From Images</title> + <note><para> + This complete section needs a rewrite as we now have different floppy images! + </para></note> <para> If your IPCop PC has a CD-ROM, but your BIOS will not allow a CD-ROM boot, you will need to create a @@ -788,7 +742,7 @@ the floppies can be done from a terminal window with the dd command: <screen format="linespecific"> -<prompt># </prompt><userinput>dd if=/mnt/cdrom/images/boot-&ipcoprelease;.img of=/dev/fd0 bs=1k count=1440</userinput> +<prompt># </prompt><userinput>dd if=/mnt/cdrom/images/ipcop-&ipcoprelease;-boot.img of=/dev/fd0 bs=1k count=1440</userinput> </screen> Use the same command with <parameter class="command"> @@ -838,72 +792,57 @@ </sect3> </sect2> - <sect2 id="preparation-file-available"> - <title>Making The Installation File Available</title> - <para> - This step is only needed if you are installing from - bootable floppy and FTP/Web Server. - In the root directory - <filename class="directory"> - / - </filename> - of the ISO image there is a file named - <filename> - ipcop-1.4.0.tgz</filename>. - This file contains a compressed image of the IPCop - hard drive. - Copy this file to a machine that is running a web - server or FTP server. - Put it where the server can find it during install. - During the install, IPCop will log in to your FTP or - web server as anonymous. - Most servers do not allow anonymous users to access - files out of the server's hierarchy. - Even though a directory appears at the top level of - the server, such as - <filename class="directory"> - /pub - </filename> - they really are somewhere else, such as - <filename class="directory"> - /anonftp/pub</filename>. - </para> - <para> - If your IPCop PC uses SCSI disk drives then you also need to - copy the file - <filename>scsidrv-1.4.0.img</filename> - from the - <filename class="directory">/images</filename> - folder of the ISO image to this directory. - </para> - <para> - If you are creating your private network for the first - time, change the IP address of the server machine to - be on the private, GREEN, network, using a static - address. - You only need to do this for the duration of the install. - </para> - <para> - If your server machine is connected to the Internet, - remove the connection and physically connect your - IPCop PC and other machines together. - See TODO: FIXME - <!-- <link linkend="home-nets"> - Appendix A</link>,--> - for a discussion of your choices. - If you are using 192.168.1.1 for the IPCop PC, - 192.168.1.2 is a good address for the server. - Set the server up with a static IP address, temporarily. - You will need to reboot any Windows PC if you change - its IP address. - </para> - <para> - Verify that the IPCop installation file is available - via the FTP command or entering its URL from a browser, - even if you have to do it from the server machine. - You can cancel the download or close your browser once - you are sure the URL works. - </para> - </sect2> - </sect1> + <sect2 id="preparation-file-available"> + <title>Making The Installation File Available</title> + <para> + This step is only needed if you are installing via + netboot or from bootable floppy and are using FTP/Web Server. + In the root directory + <filename class="directory">/</filename> + of the ISO image there is a file named + <filename>ipcop-&ipcoprelease;.tar.gz</filename>. + This file contains a compressed image of the IPCop + hard drive. + Copy this file to a machine that is running a web + server or FTP server. + Put it where the server can find it during install. + During the install, IPCop will log in to your FTP or + web server as anonymous. + Most servers do not allow anonymous users to access + files out of the server's hierarchy. + Even though a directory appears at the top level of + the server, such as + <filename class="directory">/pub</filename> + they really are somewhere else, such as + <filename class="directory">/anonftp/pub</filename>. + </para> + <para> + If you are creating your private network for the first + time, change the IP address of the server machine to + be on the private, GREEN, network, using a static + address. + You only need to do this for the duration of the install. + </para> + <para> + If your server machine is connected to the Internet, + remove the connection and physically connect your + IPCop PC and other machines together. + See TODO: FIXME + <!-- <link linkend="home-nets"> Appendix A</link>,--> + for a discussion of your choices. + If you are using 192.168.1.1 for the IPCop PC, + 192.168.1.2 is a good address for the server. + Set the server up with a static IP address, temporarily. + You will need to reboot any Windows PC if you change + its IP address. + </para> + <para> + Verify that the IPCop installation file is available + via the FTP command or entering its URL from a browser, + even if you have to do it from the server machine. + You can cancel the download or close your browser once + you are sure the URL works. + </para> + </sect2> +</sect1> </chapter> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <ow...@us...> - 2011-09-21 05:18:33
|
Revision: 5860 http://ipcop.svn.sourceforge.net/ipcop/?rev=5860&view=rev Author: owes Date: 2011-09-21 05:18:26 +0000 (Wed, 21 Sep 2011) Log Message: ----------- Update installation doc for archs and upgrades. Modified Paths: -------------- IPCopDoc/trunk/en/install/xml/preparation.xml Modified: IPCopDoc/trunk/en/install/xml/preparation.xml =================================================================== --- IPCopDoc/trunk/en/install/xml/preparation.xml 2011-09-21 05:05:40 UTC (rev 5859) +++ IPCopDoc/trunk/en/install/xml/preparation.xml 2011-09-21 05:18:26 UTC (rev 5860) @@ -32,13 +32,9 @@ <sect1 id="preparation-architectures"> <title>Supported Architectures</title> <para> - Starting with IPCop 2.0.0 multiple architectures are - supported: + IPCop 2.0.0 supports x86 architecture only. Still under development are: <itemizedlist> <listitem> - <para>x86</para> - </listitem> - <listitem> <para>Power PC</para> </listitem> <listitem> @@ -47,33 +43,30 @@ </itemizedlist> </para> </sect1> - <sect1 id="preparation-upgrade-ipcop"> - <title>Upgrading from IPCop 1.2.0 or Greater</title> - <para> - Starting with IPCop 1.3.0, you can upgrade your IPCop PC - from IPCop 1.2.0 or later and save your configuration. - Use the web interface to log in to your IPCop PC and - take a backup on a floppy, using the Backup Administrative - web page. - If you don't know how to do this, please read the IPCop - Administration Manual section entitled - <ulink - url="http://www.ipcop.org/1.4.0/en/admin/html/system.html#backup"> - System->Backup AW</ulink>. - During installation you will be asked whether you wish - to restore your settings from a backup floppy. - Insert the backup floppy in your floppy disk drive and - respond, <quote>Restore</quote>. +<sect1 id="preparation-upgrade-ipcop"> + <title>Upgrading from older IPCop versions</title> + <para> + Versions 1.9.9 and newer can be upgraded. + Use the web interface to log in to your IPCop and + take a backup on a floppy, USB key or downloaded files using the + Backup Administrative web page. + If you don't know how to do this, please read the IPCop + Administration Manual section entitled + <ulink url="http://www.ipcop.org/2.0.0/en/admin/html/system-backup.html"> + System->Backup AW</ulink>. + During installation you will be asked whether you wish + to restore your settings from a backup floppy or USB key. <note> - <title>Restore from 1.4.23 or later only!</title> + <title>Restore from IPCop 1.4.21 or older</title> <para> - IPCop &ipcoprelease; will only accept backups from version - 1.4.23 or later. If you are using an earlier version, you - will need to upgrade to version 1.4.23. + There is no upgrade path from IPCop 1.x to IPCop &ipcoprelease;. + Migration of individual pieces is described in + <ulink url="http://sourceforge.net/apps/mediawiki/ipcop/index.php?title=HowTos"> + HowTos.</ulink> </para> </note> - </para> - </sect1> + </para> +</sect1> <sect1 id="preparation-decide-configuration"> <title>Decide On Your Configuration</title> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <ow...@us...> - 2011-10-08 20:45:36
|
Revision: 5917 http://ipcop.svn.sourceforge.net/ipcop/?rev=5917&view=rev Author: owes Date: 2011-10-08 20:45:26 +0000 (Sat, 08 Oct 2011) Log Message: ----------- Fix link to RFC1918 Modified Paths: -------------- IPCopDoc/trunk/en/install/xml/preparation.xml Modified: IPCopDoc/trunk/en/install/xml/preparation.xml =================================================================== --- IPCopDoc/trunk/en/install/xml/preparation.xml 2011-10-08 15:05:20 UTC (rev 5916) +++ IPCopDoc/trunk/en/install/xml/preparation.xml 2011-10-08 20:45:26 UTC (rev 5917) @@ -344,7 +344,7 @@ To make sure there are no IP address conflicts, it is suggested that you choose one of the address ranges defined in - <ulink url="ftp://ftp.isi.edu/in-notes/rfc1918.txt"> + <ulink url="http://www.rfc-editor.org/rfc/rfc1918.txt"> RFC1918 </ulink> as private (non-routable) addresses. This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |