From: <eob...@us...> - 2009-01-04 15:58:27
|
Revision: 2276 http://ipcop.svn.sourceforge.net/ipcop/?rev=2276&view=rev Author: eoberlander Date: 2009-01-04 15:58:23 +0000 (Sun, 04 Jan 2009) Log Message: ----------- Forward changes from v1.4 branch, rename files etc. Modified Paths: -------------- IPCopDoc/trunk/en/admin/images/gui.png IPCopDoc/trunk/en/admin/images/passwords.png IPCopDoc/trunk/en/admin/images/shutdown.png IPCopDoc/trunk/en/admin/images/ssh.png IPCopDoc/trunk/en/admin/xml/home.xml Removed Paths: ------------- IPCopDoc/trunk/en/admin/images/home.png IPCopDoc/trunk/en/admin/images/updates.png Modified: IPCopDoc/trunk/en/admin/images/gui.png =================================================================== (Binary files differ) Deleted: IPCopDoc/trunk/en/admin/images/home.png =================================================================== (Binary files differ) Modified: IPCopDoc/trunk/en/admin/images/passwords.png =================================================================== (Binary files differ) Modified: IPCopDoc/trunk/en/admin/images/shutdown.png =================================================================== (Binary files differ) Modified: IPCopDoc/trunk/en/admin/images/ssh.png =================================================================== (Binary files differ) Deleted: IPCopDoc/trunk/en/admin/images/updates.png =================================================================== (Binary files differ) Modified: IPCopDoc/trunk/en/admin/xml/home.xml =================================================================== --- IPCopDoc/trunk/en/admin/xml/home.xml 2009-01-03 10:05:19 UTC (rev 2275) +++ IPCopDoc/trunk/en/admin/xml/home.xml 2009-01-04 15:58:23 UTC (rev 2276) @@ -13,11 +13,11 @@ <screenshot> <mediaobject> <imageobject role="fo"> - <imagedata fileref="&imagepath;home.&imageext;" format="PNG" + <imagedata fileref="&imagepath;home1.&imageext;" format="PNG" contentwidth="14cm"/> </imageobject> <imageobject role="html"> - <imagedata fileref="&imagepath;home.&imageext;" format="PNG" align="center"/> + <imagedata fileref="&imagepath;home1.&imageext;" format="PNG" align="center"/> </imageobject> <textobject> <phrase>Home Page</phrase> @@ -116,11 +116,11 @@ <screenshot> <mediaobject> <imageobject role="fo"> - <imagedata fileref="&imagepath;home.&imageext;" format="PNG" + <imagedata fileref="&imagepath;home1.&imageext;" format="PNG" contentwidth="14cm"/> </imageobject> <imageobject role="html"> - <imagedata fileref="&imagepath;home.&imageext;" format="PNG" align="center"/> + <imagedata fileref="&imagepath;home1.&imageext;" format="PNG" align="center"/> </imageobject> <textobject> <phrase>Home Page, Ethernet Connection</phrase> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <eob...@us...> - 2009-03-15 14:42:20
|
Revision: 2570 http://ipcop.svn.sourceforge.net/ipcop/?rev=2570&view=rev Author: eoberlander Date: 2009-03-15 14:42:05 +0000 (Sun, 15 Mar 2009) Log Message: ----------- Update screenshots and text to reflect changes to cgis. Modified Paths: -------------- IPCopDoc/trunk/en/admin/images/services.png IPCopDoc/trunk/en/admin/images/shutdown.png IPCopDoc/trunk/en/admin/xml/info.xml IPCopDoc/trunk/en/admin/xml/system.xml Modified: IPCopDoc/trunk/en/admin/images/services.png =================================================================== (Binary files differ) Modified: IPCopDoc/trunk/en/admin/images/shutdown.png =================================================================== (Binary files differ) Modified: IPCopDoc/trunk/en/admin/xml/info.xml =================================================================== --- IPCopDoc/trunk/en/admin/xml/info.xml 2009-03-14 15:56:31 UTC (rev 2569) +++ IPCopDoc/trunk/en/admin/xml/info.xml 2009-03-15 14:42:05 UTC (rev 2570) @@ -181,6 +181,34 @@ </para> </sect3> + <sect3 id="info-system-status-raid"> + <title>RAID Status (optional)</title> + <para> + <guilabel>RAID Status</guilabel> - This displays + information on the RAID devices on your + IPCop server, if fitted. + </para> + <para> + <screenshot> + <mediaobject> + <imageobject role="fo"> + <imagedata fileref="&imagepath;info-raid.&imageext;" + format="PNG" + contentwidth="14cm"/> + </imageobject> + <imageobject role="html"> + <imagedata fileref="&imagepath;info-raid.&imageext;" + format="PNG" + align="center"/> + </imageobject> + <textobject> + <phrase>RAID Status</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + </sect3> + <sect3 id="info-system-status-uptime"> <title>Uptime and users</title> <para> Modified: IPCopDoc/trunk/en/admin/xml/system.xml =================================================================== --- IPCopDoc/trunk/en/admin/xml/system.xml 2009-03-14 15:56:31 UTC (rev 2569) +++ IPCopDoc/trunk/en/admin/xml/system.xml 2009-03-15 14:42:05 UTC (rev 2570) @@ -920,23 +920,5 @@ or halt the IPCop server. </para> </sect3> - <sect3 id="shutdown_reboot_schedule"> - <title> - Schedule IPCop reboots - </title> - <para> - The ability to schedule reboots or shutdowns was added in version - 1.4.10. A cronjob is added to root's <command>crontab</command>. - To schedule IPCop to reboot once a day on a regular schedule, - select the time from the drop down menu; check the day (or days) - you require; select <guibutton>Reboot</guibutton> or - <guibutton>Shutdown</guibutton>; and press the - <guibutton>Save</guibutton> button. - </para> - <para> - To remove a schedule, clear (uncheck) all the checkboxes - and press the <guibutton>Save</guibutton> button. - </para> - </sect3> </sect2> </sect1> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <eob...@us...> - 2009-03-21 14:56:10
|
Revision: 2615 http://ipcop.svn.sourceforge.net/ipcop/?rev=2615&view=rev Author: eoberlander Date: 2009-03-21 14:56:05 +0000 (Sat, 21 Mar 2009) Log Message: ----------- Add section for Scheduler page, with screenshots. Modified Paths: -------------- IPCopDoc/trunk/en/admin/xml/system.xml Added Paths: ----------- IPCopDoc/trunk/en/admin/images/scheduler-add.png IPCopDoc/trunk/en/admin/images/scheduler-list.png Added: IPCopDoc/trunk/en/admin/images/scheduler-add.png =================================================================== (Binary files differ) Property changes on: IPCopDoc/trunk/en/admin/images/scheduler-add.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: IPCopDoc/trunk/en/admin/images/scheduler-list.png =================================================================== (Binary files differ) Property changes on: IPCopDoc/trunk/en/admin/images/scheduler-list.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Modified: IPCopDoc/trunk/en/admin/xml/system.xml =================================================================== --- IPCopDoc/trunk/en/admin/xml/system.xml 2009-03-21 14:54:23 UTC (rev 2614) +++ IPCopDoc/trunk/en/admin/xml/system.xml 2009-03-21 14:56:05 UTC (rev 2615) @@ -23,6 +23,12 @@ </para> </listitem> <listitem> + <para><link linkend="scheduler"><guimenuitem>Scheduler</guimenuitem></link> — + Allows you to schedule reboot, shutdown, connection and + disconnection events on IPCop. + </para> + </listitem> + <listitem> <para><link linkend="updates"><guimenuitem>Updates</guimenuitem></link> — Allows you to query and apply fixes to IPCop. </para> @@ -62,6 +68,83 @@ </listitem> </itemizedlist> </para> + <sect2 id="scheduler"> + <title> + Scheduler + </title> + <para> + This page has two sections: + </para> + <orderedlist> + <listitem> + <para> + The first box allows you to Add or Edit a Scheduled Event. + </para> + </listitem> + <listitem> + <para> + The second box lists the Scheduled Events. + </para> + </listitem> + </orderedlist> + <figure id="v190.system.010" > + <title>Add a Scheduler Action screen</title> + <mediaobject> + <imageobject role="fo"> + <imagedata fileref="&imagepath;scheduler-add.&imageext;" format="PNG" + contentwidth="14cm"/> + </imageobject> + <imageobject role="html"> + <imagedata fileref="&imagepath;scheduler-add.&imageext;" format="PNG" align="center"/> + </imageobject> + <textobject> + <phrase>Add a Scheduler Action Box</phrase> + </textobject> + </mediaobject> + </figure> + <para> + Select an <guilabel>Action</guilabel>, a <guilabel>Time</guilabel> + and a <guilabel>Day</guilabel>, and then press the + <guibutton>Add</guibutton> button to add a new event to the Scheduler. + This will move the entry to the next section, and list it + as enabled. + </para> + <para> + Select an Action from Reconnect, Connect, Disconnect, Reboot or Shutdown. + </para> + <para> + Optionally, you can include a <guilabel>Remark</guilabel> to describe + the event. + </para> + <figure id="v190.system.011" > + <title>Scheduled Actions section</title> + <mediaobject> + <imageobject role="fo"> + <imagedata fileref="&imagepath;scheduler-list.&imageext;" format="PNG" + contentwidth="14cm"/> + </imageobject> + <imageobject role="html"> + <imagedata fileref="&imagepath;scheduler-list.&imageext;" format="PNG" align="center"/> + </imageobject> + <textobject> + <phrase>Scheduled Actions Box</phrase> + </textobject> + </mediaobject> + </figure> + <para> + The <guilabel>Scheduled Actions</guilabel> section lists the current + events. To remove one, click the <quote>Trash Can</quote> + icon. To edit one, click the <quote>Yellow Pencil</quote> icon. + </para> + <para> + To enable or disable an event, click on the + <quote>Enabled</quote> icon (to the left of the Yellow Pencil) + for the particular entry you want to enable or disable. + The icon changes to an empty box when an event is + disabled. Click the checkbox to enable it again. + </para> + </sect2> + <sect2 id="updates"> <title> Updates This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <eob...@us...> - 2009-03-22 17:51:24
|
Revision: 2626 http://ipcop.svn.sourceforge.net/ipcop/?rev=2626&view=rev Author: eoberlander Date: 2009-03-22 17:51:15 +0000 (Sun, 22 Mar 2009) Log Message: ----------- Rearrange Logs section. Some content still required... Modified Paths: -------------- IPCopDoc/trunk/en/admin/images/log-settings.png IPCopDoc/trunk/en/admin/xml/logs.xml Modified: IPCopDoc/trunk/en/admin/images/log-settings.png =================================================================== (Binary files differ) Modified: IPCopDoc/trunk/en/admin/xml/logs.xml =================================================================== --- IPCopDoc/trunk/en/admin/xml/logs.xml 2009-03-22 16:59:50 UTC (rev 2625) +++ IPCopDoc/trunk/en/admin/xml/logs.xml 2009-03-22 17:51:15 UTC (rev 2626) @@ -8,11 +8,56 @@ <!-- $Id$ --> <sect1 id="logs"> <title>Logs Menu</title> + <para> + This group of web pages presents you with information + from the logs on your IPCop server. + To get to these web pages, select + <guimenu>Logs</guimenu> from the tab bar at the top of the screen. + The following choices will appear in a dropdown menu: + <itemizedlist> + <listitem> + <para> + <link linkend="log-settings"> + <guimenuitem>Log Settings</guimenuitem></link> + </para> + </listitem> + <listitem> + <para> + <link linkend="log-summary"> + <guimenuitem>Log Summary</guimenuitem></link> + </para> + </listitem> + <listitem> + <para> + <link linkend="section-logs-proxy"> + <guimenuitem>Proxy Logs</guimenuitem></link> + </para> + </listitem> + <listitem> + <para> + <link linkend ="section-logs-firewall"> + <guimenuitem>Firewall Logs</guimenuitem></link> + </para> + </listitem> + <listitem> + <para> + <link linkend="section-logs-ids"> + <guimenuitem>IDS Logs</guimenuitem></link> + </para> + </listitem> + <listitem> + <para> + <link linkend="logs-system"> + <guimenuitem>System Logs</guimenuitem></link> + </para> + </listitem> + </itemizedlist> + </para> <sect2 id="log_intro"> <title>Introduction</title> <para> - The Logs AW Consists of five or six sub-pages - + The Logs web pages consist of five or six sub-pages - <guisubmenu>Log Settings</guisubmenu>, <guisubmenu>Log Summary</guisubmenu>, <guisubmenu>Proxy Logs</guisubmenu>, @@ -25,16 +70,16 @@ Dropdown <guilabel>Month:</guilabel> and <guilabel>Day:</guilabel> lists in the <guilabel>Settings:</guilabel> - area of the AW are provided to allow - you to select Logs information for preceding days and + area of the webpage are provided to allow + you to select log information for preceding days and months. Each time that you select a new combination of <guilabel>Month:</guilabel> and <guilabel>Day:</guilabel>, you must also click the <guibutton>Update</guibutton> - button before the Logs information + button before the log information will be updated. When you first select a sub-page, the - Logs information displayed will be that for the + log information displayed will be that for the current date. </para> <para> @@ -43,8 +88,8 @@ <guilabel>>></guilabel> button moves a day forward. </para> <para> - The Logs information appears as a list in the - main section of the window (usually labeled + The Log information appears as a list in the + main section of the window (usually labelled <guilabel>Log:</guilabel>). If that list is too long to fit into a reasonably sized window, only the latest Logs @@ -59,7 +104,7 @@ Pressing the <guibutton>Export</guibutton> button downloads a text-format file (<filename>log.dat</filename>), containing the - information from the current Logs AW page, from the + information from the current Logs webpage, from the IPCop server to your computer. Depending on how your computer is set up, pressing the <guibutton>Export</guibutton> @@ -81,7 +126,7 @@ Section to be written... </para> <para> - <figure id="v140.logs.001"> + <figure id="v190.logs.001"> <title>Log Settings</title> <mediaobject> <imageobject role="fo"> @@ -95,7 +140,7 @@ align="center"/> </imageobject> <textobject> - <phrase>Log Settings AW</phrase> + <phrase>Log Settings Webpage</phrase> </textobject> </mediaobject> </figure> @@ -110,7 +155,7 @@ Section to be written... </para> <para> - <figure id="v140.logs.002"> + <figure id="v190.logs.002"> <title>Log Summary Output</title> <mediaobject> <imageobject role="fo"> @@ -124,7 +169,7 @@ align="center"/> </imageobject> <textobject> - <phrase>Log Summary AW</phrase> + <phrase>Log Summary Webpage</phrase> </textobject> </mediaobject> </figure> @@ -204,7 +249,7 @@ </itemizedlist> <para> - For this page, the Logs information appearing in + For this page, the Log information appearing in the <guilabel>Log:</guilabel> section of the window consists of: </para> @@ -231,7 +276,7 @@ </para> </note> <para> - <figure id="v140.logs.003"> + <figure id="v190.logs.003"> <title>Proxy Log Output</title> <mediaobject> <imageobject role="fo"> @@ -297,7 +342,7 @@ and ownership. </para> <para> - <figure id="v140.logs.004"> + <figure id="v190.logs.004"> <title>Firewall Log Output</title> <mediaobject> <imageobject role="fo"> @@ -389,7 +434,7 @@ </listitem> </itemizedlist> <para> - <figure id="v140.logs.005"> + <figure id="v190.logs.005"> <title>IDS Log Output</title> <mediaobject> <imageobject role="fo"> @@ -437,20 +482,9 @@ of dialup modem links. </para> </listitem> <listitem> - <para><guilabel>RED</guilabel> - traffic sent - over the interface that is providing the PPP - interface for IPCop. This includes the data - strings sent to, and received from modems and - other network interfaces<!-- Is the latter - true? -->. This can be a very useful resource - in troubleshooting "failure to connect" - situations.</para> - </listitem> - <listitem> <para> - <guilabel>DNS</guilabel> - shows a log of - activity for dnsmasq, the domain name - service utility. + <guilabel>Cron</guilabel> - provides a record + of activity of the fcron daemon. </para> </listitem> <listitem> @@ -462,22 +496,20 @@ </listitem> <listitem> <para> - <guilabel>SSH</guilabel> - provides a record - of users who have logged in to, and out of the - IPCop server over a network via the SSH - interface. + <guilabel>DNS</guilabel> - shows a log of + activity for dnsmasq, the domain name + service utility. </para> </listitem> <listitem> - <para> - <guilabel>NTP</guilabel> - shows a log of - activity for the ntpd Server function. + <para><guilabel>IPSec</guilabel> - is a record + of activity of IPSec - a VPN software module used by IPCop. </para> </listitem> <listitem> <para> - <guilabel>Cron</guilabel> - provides a record - of activity of the cron daemon. + <guilabel>Kernel</guilabel> - is a record of + kernel activity in the IPCop server. </para> </listitem> <listitem> @@ -491,17 +523,41 @@ </listitem> <listitem> <para> - <guilabel>Kernel</guilabel> - is a record of - kernel activity in the IPCop server. + <guilabel>NTP</guilabel> - shows a log of + activity for the ntpd Server function. </para> </listitem> <listitem> - <para><guilabel>IPSec</guilabel> - is a record - of activity of IPSec - the VPN software module used by IPCop. + <para><guilabel>OpenVPN</guilabel> - is a record + of activity of OpenVPN - a VPN software module used by IPCop. </para> </listitem> <listitem> + <para><guilabel>RED</guilabel> - traffic sent + over the interface that is providing the PPP + interface for IPCop. This includes the data + strings sent to, and received from modems and + other network interfaces<!-- Is the latter + true? -->. This can be a very useful resource + in troubleshooting "failure to connect" + situations.</para> + </listitem> + <listitem> <para> + <guilabel>Snort</guilabel> - shows a log of + activity for Snort, the Intrusion Detection System. + </para> + </listitem> + <listitem> + <para> + <guilabel>SSH</guilabel> - provides a record + of users who have logged in to, and out of the + IPCop server over a network via the SSH + interface. + </para> + </listitem> + <listitem> + <para> <guilabel>Update transcript</guilabel> - is a log of the results of any updates applied to the IPCop software via the @@ -509,15 +565,9 @@ <guimenuitem>Update</guimenuitem> window. </para> </listitem> - <listitem> - <para> - <guilabel>Snort</guilabel> - shows a log of - activity for Snort, the Intrusion Detection System. - </para> - </listitem> </itemizedlist> <para> - <figure id="v140.logs.006"> + <figure id="v190.logs.006"> <title>System Log Output</title> <mediaobject> <imageobject role="fo"> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <eob...@us...> - 2009-03-28 19:49:56
|
Revision: 2646 http://ipcop.svn.sourceforge.net/ipcop/?rev=2646&view=rev Author: eoberlander Date: 2009-03-28 19:49:52 +0000 (Sat, 28 Mar 2009) Log Message: ----------- Update DHCP section. Modified Paths: -------------- IPCopDoc/trunk/en/admin/images/blueaccess.png IPCopDoc/trunk/en/admin/images/dhcp-dynamic.png IPCopDoc/trunk/en/admin/images/dhcp.png IPCopDoc/trunk/en/admin/images/time.png IPCopDoc/trunk/en/admin/images/time2.png IPCopDoc/trunk/en/admin/xml/info.xml IPCopDoc/trunk/en/admin/xml/services.xml Modified: IPCopDoc/trunk/en/admin/images/blueaccess.png =================================================================== (Binary files differ) Modified: IPCopDoc/trunk/en/admin/images/dhcp-dynamic.png =================================================================== (Binary files differ) Modified: IPCopDoc/trunk/en/admin/images/dhcp.png =================================================================== (Binary files differ) Modified: IPCopDoc/trunk/en/admin/images/time.png =================================================================== (Binary files differ) Modified: IPCopDoc/trunk/en/admin/images/time2.png =================================================================== (Binary files differ) Modified: IPCopDoc/trunk/en/admin/xml/info.xml =================================================================== --- IPCopDoc/trunk/en/admin/xml/info.xml 2009-03-28 19:32:25 UTC (rev 2645) +++ IPCopDoc/trunk/en/admin/xml/info.xml 2009-03-28 19:49:52 UTC (rev 2646) @@ -410,7 +410,7 @@ <title>Current Dynamic Leases</title> <para> Displays the contents of the - <filename>/var/state/dhcp/dhcpd.leases</filename> + <filename>/var/run/dnsmasq/dnsmasq.leases</filename> file if DHCP is enabled. The current dynamic leases are listed, with hostnames if available, and expiry dates. </para> Modified: IPCopDoc/trunk/en/admin/xml/services.xml =================================================================== --- IPCopDoc/trunk/en/admin/xml/services.xml 2009-03-28 19:32:25 UTC (rev 2645) +++ IPCopDoc/trunk/en/admin/xml/services.xml 2009-03-28 19:49:52 UTC (rev 2646) @@ -14,13 +14,36 @@ </para><para> These are: <itemizedlist> - <listitem><para><link linkend="services_webproxy">Proxy</link> (Web Proxy Server)</para></listitem> - <listitem><para><link linkend="services_dhcp">DHCP Server</link></para></listitem> - <listitem><para><link linkend="services_dyndns">Dynamic DNS Management</link></para></listitem> - <listitem><para><link linkend="services_hosts">Edit Hosts</link> (Local DNS Server)</para></listitem> - <listitem><para><link linkend="services_time">Time Server</link></para></listitem> - <listitem><para><link linkend="services_shaping">Traffic Shaping</link></para></listitem> - <listitem><para><link linkend="services_ids">Intrusion Detection System</link></para></listitem> + <listitem> + <para><link linkend="services_webproxy"><guimenuitem>Proxy</guimenuitem></link> + (Web Proxy Server) + </para> + </listitem> + <listitem> + <para><link linkend="services_dhcp"><guimenuitem>DHCP Server</guimenuitem></link> + </para> + </listitem> + <listitem> + <para><link linkend="services_dyndns"><guimenuitem>Dynamic DNS Management</guimenuitem></link> + </para> + </listitem> + <listitem> + <para><link linkend="services_hosts"><guimenuitem>Edit Hosts</guimenuitem></link> + (Local DNS Server) + </para> + </listitem> + <listitem> + <para><link linkend="services_time"><guimenuitem>Time Server</guimenuitem></link> + </para> + </listitem> + <listitem> + <para><link linkend="services_shaping"><guimenuitem>Traffic Shaping</guimenuitem></link> + </para> + </listitem> + <listitem> + <para><link linkend="services_ids"><guimenuitem>Intrusion Detection System</guimenuitem></link> + </para> + </listitem> </itemizedlist> In a larger network it is likely that these services will be provided by dedicated servers and should be disabled here. @@ -59,7 +82,7 @@ </screenshot> </para><para> You can choose if you want to proxy requests from your Green (private) network - and/or your Blue (wireless) network. Just tick the relevant boxes. + and/or your Blue (wireless) network (if fitted). Just tick the relevant boxes. </para> <formalpara> <title><guilabel>Log enabled</guilabel></title> @@ -190,7 +213,7 @@ </para> <para> You can choose if you want to provide this service to your Green (private) network - and/or your Blue (wireless) network. Just tick the relevant box. + and/or your Blue (wireless) network (if installed). Just tick the relevant box. </para><para> For a full explanation of DHCP you may want to read Linux Magazine's <ulink url="http://www.linux-mag.com/2000-04/networknirvana_01.html"> @@ -221,8 +244,8 @@ <title><guilabel>Start Address</guilabel> (optional)</title> <para> You can specify the lowest and highest addresses that the server will hand out to - other requestors. The default is to hand out all the addresses within the subnet you set - up when you installed IPCop. If you have machines on your network that do not use + other requestors. + If you have machines on your network that do not use DHCP, and have their IP addresses set manually, you should set the start and end address so that the server will not hand out any of these manual IPs. </para> @@ -247,17 +270,6 @@ </para> </note> <formalpara> - <title><guilabel>Base IP for fixed lease creation</guilabel> (optional)</title> - <para> - The ability to add fixed leases from the list of dynamic - leases was added in v1.4.12. - </para> - </formalpara> - <para> - You can specify an IP Address which will be used as the base - from which new fixed leases will be incremented. - </para> - <formalpara> <title><guilabel>Default lease time</guilabel></title> <para> This can be left at its default value unless you @@ -274,21 +286,6 @@ </para> </formalpara> <formalpara> - <title><guilabel>Maximum lease time</guilabel></title> - <para> - This can be left at its default value unless you - need to specify your own value. - The maximum lease time is the time interval during - which the DHCP server will always honor client - renewal requests for their current IP addresses. - After the maximum lease time, client IP addresses - may be changed by the server. - If the dynamic IP address range has changed, the - server will hand out an IP address in the new - dynamic range. - </para> - </formalpara> - <formalpara> <title><guilabel>Domain name suffix</guilabel> (optional)</title> <para> There should not be a leading period in this box. @@ -382,6 +379,7 @@ When you press <guibutton>Save</guibutton>, the change is acted upon. </para> </sect3> +<!-- section now redundant? <sect3 id="dhcp_options"> <title>Additional DHCP Options</title> <para> @@ -500,6 +498,7 @@ </para> </note> </sect3> +--> <sect3 id="add_dhcp_lease"> <title>Fixed Leases</title> <para> @@ -651,7 +650,7 @@ <para> If DHCP is enabled, this section lists the dynamic leases contained in the - <filename>/var/state/dhcp/dhcpd.leases</filename> file. + <filename>/var/run/dnsmasq/dnsmasq.leases</filename> file. The IP Address, MAC Address, hostname (if available) and lease expiry time of each record are shown, sorted by IP Address. @@ -667,7 +666,7 @@ section, if needed. </para> <para> - <figure id="v140.services.004"> + <figure id="v190.services.004"> <title>Current dynamic leases</title> <mediaobject> <imageobject role="fo"> @@ -687,14 +686,6 @@ </figure> </para> <para> - A new method of adding fixed leases from the list of dynamic - leases was added in v1.4.12. Used in conjunction with the - <emphasis>Base IP for fixed lease creation</emphasis> field, you - can select one or more checkboxes, and click the - <guibutton>Create fixed leases</guibutton> button to quickly add - a number of devices to the fixed lease list. - </para> - <para> Lease times that have already expired are <quote>struck through</quote>. </para> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <eob...@us...> - 2009-04-13 18:40:30
|
Revision: 2708 http://ipcop.svn.sourceforge.net/ipcop/?rev=2708&view=rev Author: eoberlander Date: 2009-04-13 18:40:24 +0000 (Mon, 13 Apr 2009) Log Message: ----------- Start to update VPN section. Modified Paths: -------------- IPCopDoc/trunk/en/admin/images/vpn-ca1.png IPCopDoc/trunk/en/admin/xml/vpns.xml Added Paths: ----------- IPCopDoc/trunk/en/admin/images/vpn-ca2.png IPCopDoc/trunk/en/admin/images/vpn-ca3.png Modified: IPCopDoc/trunk/en/admin/images/vpn-ca1.png =================================================================== (Binary files differ) Added: IPCopDoc/trunk/en/admin/images/vpn-ca2.png =================================================================== (Binary files differ) Property changes on: IPCopDoc/trunk/en/admin/images/vpn-ca2.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: IPCopDoc/trunk/en/admin/images/vpn-ca3.png =================================================================== (Binary files differ) Property changes on: IPCopDoc/trunk/en/admin/images/vpn-ca3.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Modified: IPCopDoc/trunk/en/admin/xml/vpns.xml =================================================================== --- IPCopDoc/trunk/en/admin/xml/vpns.xml 2009-04-13 12:56:39 UTC (rev 2707) +++ IPCopDoc/trunk/en/admin/xml/vpns.xml 2009-04-13 18:40:24 UTC (rev 2708) @@ -10,6 +10,35 @@ <title> VPNs Menu </title> + <para> + The VPNs Menu contains webpages which control Virtual Private Networks + which allow IPCop to connect two (or more) networks directly to each + other over another network, such as the Internet. + To get to these web pages, select + <guimenu>VPNs</guimenu> from the tab bar at the top of the screen. + The following choices will appear in a dropdown menu: + <itemizedlist> + <listitem> + <para> + <link linkend="vpn-ipsec"> + <guimenuitem>IPsec</guimenuitem></link> + </para> + </listitem> + <listitem> + <para> + <link linkend="vpn-openvpn"> + <guimenuitem>OpenVPN</guimenuitem></link> + </para> + </listitem> + <listitem> + <para> + <link linkend="vpn-ca"> + <guimenuitem>Certificate Authorities</guimenuitem></link> + </para> + </listitem> + </itemizedlist> + </para> + <sect2 id="vpn-intro"> <title> Virtual Private Networks (VPNs) @@ -21,19 +50,19 @@ from prying eyes. Similarly, a single computer can also connect to another network using the same facilities. - One of the protocols used to create VPNs is known as IPSec. + One of the protocols used to create VPNs is known as IPsec. </para> <para> IPCop can easily establish VPNs between other IPCop servers. IPCop can also inter-operate with just about any - VPN product that supports IPSec and standard encryption + VPN product that supports IPsec and standard encryption technologies such as 3DES. VPN connections in IPCop are defined as Net-to-Net or Host-to-Net. This is 100% optional, so you may safely ignore this section if you do not wish to make use of this feature. </para> <para> - Most modern operating systems have support for IPSec. + Most modern operating systems have support for IPsec. This includes Windows, Macintosh OSX, Linux and most Unix variants. Unfortunately, the tools needed to provide this support vary @@ -43,11 +72,11 @@ <title>Net-to-Net</title> <para> Net-to-net VPNs link two or more private networks across the - Internet, by creating an IPSec <quote>tunnel</quote>. + Internet, by creating an IPsec <quote>tunnel</quote>. In a net-to-net VPN, at least one of the networks involved must be connected to the Internet with an IPCop firewall. The other network can be connected to an IPCop firewall, or - another IPSec enabled router or firewall. + another IPsec enabled router or firewall. These router/firewalls have public IP addresses assigned by an ISP and are most likely to be using Network Address Translation, hence the term Net-to-Net. @@ -70,6 +99,185 @@ </para> </sect3> </sect2> + + <sect2 id="vpn-ipsec"> + <title> + IPsec Configuration Administrative Web Page + </title> + <para> + Content to be written... + </para> + </sect2> + + <sect2 id="vpn-openvpn"> + <title> + OpenVPN Configuration Administrative Web Page + </title> + <para> + Content to be written... + </para> + </sect2> + + <sect2 id="vpn-ca"> + <title> + Certificate Authorities Administrative Web Page + </title> + <para> + Content to be written... + </para> + + <sect3 id="gen-ca-cert"> + <title>Generating Root and Host Certificates</title> + <para> + <figure id="v190.vpn.031"> + <title>Certificate Authorities window: Initial View</title> + <mediaobject> + <imageobject role="fo"> + <imagedata fileref="&imagepath;vpn-ca1.&imageext;" format="PNG" + contentwidth="14cm"/> + </imageobject> + <imageobject role="html"> + <imagedata fileref="&imagepath;vpn-ca1.&imageext;" format="PNG" align="center"/> + </imageobject> + <textobject> + <phrase>Initial View</phrase> + </textobject> + </mediaobject> + </figure> + </para> + <para> + To create an IPCop's Certificate Authority or CA, enter your + CA's name in the + <guilabel>CA Name</guilabel> box. + The name should be different than the IPCop machine's + host name to avoid confusion. + For example, <userinput>ipcopca</userinput> for the CA and + <userinput>ipcop</userinput> for the hostname. + Then click on the + <guibutton>Generate Root/Host Certificates</guibutton> + button. + </para> + <para> + The <guilabel>Generate Root/Host Certificates</guilabel> + will appear. + Fill out the form and both a X.509 root and host certificate will be + generated. + </para> + <para> + <figure id="v190.vpn.032"> + <title>Generate Root/Host Certificates window</title> + <mediaobject> + <imageobject role="fo"> + <imagedata fileref="&imagepath;vpn-ca2.&imageext;" format="PNG" + contentwidth="14cm"/> + </imageobject> + <imageobject role="html"> + <imagedata fileref="&imagepath;vpn-ca2.&imageext;" format="PNG" align="center"/> + </imageobject> + <textobject> + <phrase>Generate a Certificate</phrase> + </textobject> + </mediaobject> + </figure> + </para> + <formalpara> + <title><guilabel>Organization Name</guilabel></title> + <para> + The organization name you want used in the certificate. + For example, if your VPN is tying together schools in a school + district, you may want to use something like + <userinput>Some School District.</userinput> + </para> + </formalpara> + <formalpara> + <title><guilabel>IPCop's Hostname</guilabel></title> + <para> + This should be the fully qualified domain name of your IPCop. + If you are using a + <link linkend="services_dyndns">dynamic DNS service</link>, + use it. + </para> + </formalpara> + <formalpara> + <title><guilabel>Your E-mail Address</guilabel></title> + <para> + Your E-mail address, so that folks can get hold of you. + </para> + </formalpara> + <para> + The next three fields; department, city and state or province. + You can leave them out if you wish. + </para> + <formalpara> + <title><guilabel>Your Department</guilabel> - optional</title> + <para> + This is the department or suborganization name. + Continuing the school district example, this could be + <userinput>My Elementary School</userinput>. + </para> + </formalpara> + <formalpara> + <title><guilabel>City</guilabel> - optional</title> + <para> + The city or mailing address for your machine. + </para> + </formalpara> + <formalpara> + <title><guilabel>State or Province</guilabel> - optional</title> + <para> + The state or province associated with the mailing address. + </para> + </formalpara> + <formalpara> + <title><guilabel>Country</guilabel></title> + <para> + This pull down selection menu contains every ISO recognized + country name. + Use it to select the country associated with the certificate. + </para> + </formalpara> + <formalpara> + <title><guilabel>Subject Alt Name</guilabel></title> + <para> + Description required... + </para> + </formalpara> + <para> + After completing the form, click on the + <guibutton>Generate Root/Host Certificates</guibutton> + button to generate the certificates. + </para> + <para> + <figure id="v190.vpn.033"> + <title>Certificate Authorities window: with Certificates</title> + <mediaobject> + <imageobject role="fo"> + <imagedata fileref="&imagepath;vpn-ca3.&imageext;" format="PNG" + contentwidth="14cm"/> + </imageobject> + <imageobject role="html"> + <imagedata fileref="&imagepath;vpn-ca3.&imageext;" format="PNG" align="center"/> + </imageobject> + <textobject> + <phrase>Certificate Management</phrase> + </textobject> + </mediaobject> + </figure> + </para> + <para> + If desired, you can generate several root and host certificates on a + single IPCop, and then export them to PKCS12 format files, encrypted + with a password. + You can then email them as attachments to your other sites. + Using the + <guilabel>Upload PKCS12 file</guilabel> + portion of this web page, you can upload and decrypt the certificates + on a local IPCop machine. + </para> + </sect3> + </sect2> + +<!-- <sect2 id="authentication_intro"> <title>Methods of Authentication</title> <para> @@ -97,7 +305,7 @@ It can be used to test connectivity of a VPN and to become familiar with the procedure of establishing a VPN connection. Experienced users may wish to progress straight to - <link linkend="create_CA_cert">generating a certificate of + <link linkend="gen-ca-cert">generating a certificate of authority</link> before trying to configure a roadwarrior or a net-to-net VPN connection. </para> @@ -265,115 +473,6 @@ The VPN connection type page will appear. </link> </para> - <sect3 id="create_CA_cert"> - <title>Creating IPCop's Certificates</title> - <para> - <figure id="v140.vpn.007"> - <title>VPN Certificate Authorities window: Initial View</title> - <mediaobject> - <imageobject role="fo"> - <imagedata fileref="&imagepath;vpn-ca1.&imageext;" format="PNG" - contentwidth="14cm"/> - </imageobject> - <imageobject role="html"> - <imagedata fileref="&imagepath;vpn-ca1.&imageext;" format="PNG" align="center"/> - </imageobject> - <textobject> - <phrase>VPN Certificate Authorities</phrase> - </textobject> - </mediaobject> - </figure> - </para> - <para> - To create an IPCop's Certificate Authority or CA, enter your - CA's name in the - <guilabel>CA Name</guilabel> box. - The name should be different than the IPCop machine's - host name to avoid confusion. - For example, <userinput>ipcopca</userinput> for the CA and - <userinput>ipcop</userinput> for the hostname. - Then click on the - <guibutton>Generate Root/Host Certificates</guibutton> - button. - </para> - <para> - The <guilabel>Generate Root/Host Certificates</guilabel> - will appear. - Fill out the form and both a X.509 root and host certificate will be - generated. - </para> - <formalpara> - <title><guilabel>Organization Name</guilabel></title> - <para> - The organization name you want used in the certificate. - For example, if your VPN is tying together schools in a school - district, you may want to use something like - <quote>Some School District.</quote> - </para> - </formalpara> - <formalpara> - <title><guilabel>IPCop's Hostname</guilabel></title> - <para> - This should be the fully qualified domain name of your IPCop. - If you are using a - <link linkend="services_dyndns">dynamic DNS service,</link> - use it. - </para> - </formalpara> - <formalpara> - <title><guilabel>Your E-mail Address</guilabel></title> - <para> - Your E-mail address, so that folks can get hold of you. - </para> - </formalpara> - <para> - The next three fields; department, city and state or province. - You can leave them out if you wish. - </para> - <formalpara> - <title><guilabel>Your Department</guilabel></title> - <para> - This is the department or suborganization name. - Continuing the school district example, this could be - <userinput>XX Elementary School.</userinput> - </para> - </formalpara> - <formalpara> - <title><guilabel>City</guilabel></title> - <para> - The city or mailing address for your machine. - </para> - </formalpara> - <formalpara> - <title><guilabel>State or Province</guilabel></title> - <para> - The state or province associated with the mailing address. - </para> - </formalpara> - <formalpara> - <title><guilabel>Country</guilabel></title> - <para> - This pull down selection menu contains every ISO recognized - country name. - Use it to select the country associated with the certificate. - </para> - </formalpara> - <para> - After completing the form, click on the - <guibutton>Generate Root/Host Certificates</guibutton> - button to generate the certificates. - </para> - <para> - If desired, you can generate several root and host certificates on a - single IPCop, and then export them to PKCS12 format files, encrypted - with a password. - You can then email them as attachments to your other sites. - Using the - <guilabel>Upload PKCS12 file</guilabel> - portion of this web page, you can upload and decrypt the certificates - on a local IPCop machine. - </para> - </sect3> <sect3 id="vpn-connection-type"> <title> @@ -511,7 +610,7 @@ to restart the VPN if its IP address changes. There are several scripts available on the IPCop news groups that will do this for you. - </para> + </para> </formalpara> <formalpara> <title><guilabel>Remote subnet</guilabel></title> @@ -745,4 +844,5 @@ </sect3> </sect2> +--> </sect1> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <eob...@us...> - 2009-04-30 19:38:36
|
Revision: 2756 http://ipcop.svn.sourceforge.net/ipcop/?rev=2756&view=rev Author: eoberlander Date: 2009-04-30 19:38:27 +0000 (Thu, 30 Apr 2009) Log Message: ----------- Update section on Backup. Modified Paths: -------------- IPCopDoc/trunk/en/admin/images/backup.png IPCopDoc/trunk/en/admin/xml/system.xml Removed Paths: ------------- IPCopDoc/trunk/en/admin/images/backup2.png Modified: IPCopDoc/trunk/en/admin/images/backup.png =================================================================== (Binary files differ) Deleted: IPCopDoc/trunk/en/admin/images/backup2.png =================================================================== (Binary files differ) Modified: IPCopDoc/trunk/en/admin/xml/system.xml =================================================================== --- IPCopDoc/trunk/en/admin/xml/system.xml 2009-04-30 19:36:39 UTC (rev 2755) +++ IPCopDoc/trunk/en/admin/xml/system.xml 2009-04-30 19:38:27 UTC (rev 2756) @@ -803,66 +803,19 @@ </para> </sect3> </sect2> + <sect2 id="backup"> <title> Backup Web Page </title> - <sect3 id="backup_v1411"> - <title> - v1.4.11 - </title> - <para> - The Backup Web Page was overhauled in v1.4.11, and the changes - include: - </para> - <itemizedlist> - <listitem> - <para> - The new backup supports USB keys. - </para> - </listitem> - <listitem> - <para> - Unencrypted backups were removed for security reasons. - </para> - </listitem> - <listitem> - <para> - Export of <filename>backup.key</filename> - </para> - <para> - Key is encrypted with a 'backup' password needed - for reinstallation, hostname is included in the exported - key file. - </para> - </listitem> - <listitem> - <para> - <filename>backup.dat</filename> now includes the hostname - and timestamp of the backup. - </para> - <para> - Before reinstalling, remove the timestamp from the filename - you want to use for the restore. - </para> - <para> - A comment field is available for each backup. The comment - will be restored on backup upload (if available). - </para> - </listitem> - <listitem> - <para> - Floppy backup - </para> - <para> - Display size used. - Check that backup is not too big. - Display errors for bad floppy, missing disk etc. - </para> - </listitem> - </itemizedlist> - <figure id="v140.system.005"> - <title>Backup</title> + <para> + This web page allows you to backup your system's settings, + either to a floppy disk (if you have one installed), or to a file. + The files can be saved to the harddrive, or to a USB stick, and + exported and restored via this page. + </para> + <figure id="v200.system.005"> + <title>Backup screen</title> <mediaobject> <imageobject role="fo"> <imagedata fileref="&imagepath;backup.&imageext;" format="PNG" @@ -872,11 +825,11 @@ <imagedata fileref="&imagepath;backup.&imageext;" format="PNG" align="center"/> </imageobject> <textobject> - <phrase>Backup</phrase> + <phrase>Backup screen</phrase> </textobject> </mediaobject> </figure> - </sect3> + <sect3 id="backup_to_floppy"> <title>Backup to Floppy</title> <para> @@ -895,11 +848,6 @@ Your configuration will be written to the floppy and verified. </para> - </sect3> - <sect3 id="backup_info"> - <title> - Information - </title> <para> All error messages and any information generated during a backup will appear at the foot of the panel. @@ -928,10 +876,10 @@ </sect3> <sect3 id="backup_key_export"> <title> - Export backup key + Backup Encryption Key </title> <para> - To use the new Web Backup Key Export, do the following: + To use the Web Backup Key Export feature, do the following: </para> <procedure> <step> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <eob...@us...> - 2009-05-03 08:37:42
|
Revision: 2775 http://ipcop.svn.sourceforge.net/ipcop/?rev=2775&view=rev Author: eoberlander Date: 2009-05-03 08:37:39 +0000 (Sun, 03 May 2009) Log Message: ----------- Review text in Update section, and add new screenshots. Modified Paths: -------------- IPCopDoc/trunk/en/admin/xml/system.xml Added Paths: ----------- IPCopDoc/trunk/en/admin/images/updates-available.png IPCopDoc/trunk/en/admin/images/updates-installed.png Added: IPCopDoc/trunk/en/admin/images/updates-available.png =================================================================== (Binary files differ) Property changes on: IPCopDoc/trunk/en/admin/images/updates-available.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: IPCopDoc/trunk/en/admin/images/updates-installed.png =================================================================== (Binary files differ) Property changes on: IPCopDoc/trunk/en/admin/images/updates-installed.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Modified: IPCopDoc/trunk/en/admin/xml/system.xml =================================================================== --- IPCopDoc/trunk/en/admin/xml/system.xml 2009-05-03 08:05:09 UTC (rev 2774) +++ IPCopDoc/trunk/en/admin/xml/system.xml 2009-05-03 08:37:39 UTC (rev 2775) @@ -155,18 +155,18 @@ <orderedlist> <listitem> <para> - The first box shows a list of available updates and links to - enable you to download and apply patches. You can also - select a kernel type to save space when disk space is low. + The first box shows a list of available updates with links to + enable you to download and apply patches. </para> </listitem> <listitem> <para> - A second box lists the updates that have been installed. + The second box lists the updates that have been installed. </para> </listitem> </orderedlist> - <screenshot> + <figure id="v190.system.012" > + <title>Available Updates Box</title> <mediaobject> <imageobject role="fo"> <imagedata fileref="&imagepath;updates-available.&imageext;" format="PNG" @@ -179,7 +179,7 @@ <phrase>Available Updates Box</phrase> </textobject> </mediaobject> - </screenshot> + </figure> <para> Every time you connect to the Internet IPCop will check for any new updates that may be available. You may also manually check for updates @@ -190,11 +190,9 @@ <para> Clicking on the <guibutton>Download</guibutton> button will download the <filename>.tgz.gpg</filename> file directly onto the IPCop system. - (A bug in the 1.4.20 update broke this feature, which is why you still - have to manually install the 1.4.21 update). </para> <para> - The earlier manual method requires you to download the + The alternative, manual method, requires you to download the <filename>.tgz.gpg</filename> file onto your client PC with a web browser, not directly onto IPCop. Once you have downloaded the file, in the <emphasis role="strong">Upload</emphasis> [the] @@ -203,6 +201,7 @@ client PC, the <guibutton>Upload</guibutton> button then uploads the <filename>.tgz.gpg</filename> file to IPCop and applies the changes. </para> +<!-- no longer applies to v2.0 <para> Kernel updates are sometimes split into two parts to accommodate lack of free space on disks. @@ -236,8 +235,9 @@ <filename>/var/log</filename>. The <guibutton>Clear cache (squid)</guibutton> button is provided for this purpose. - </para> - <screenshot> + </para> --> + <figure id="v190.system.013" > + <title>Installed Updates Box</title> <mediaobject> <imageobject role="fo"> <imagedata fileref="&imagepath;updates-installed.&imageext;" format="PNG" @@ -250,16 +250,34 @@ <phrase>Installed Updates Box</phrase> </textobject> </mediaobject> - </screenshot> + </figure> <note> <para> - Only IPCop official patches will actually install on your + Only IPCop official patches (which have been + <command>gpg</command> signed) will actually install on your IPCop server. Some updates may require you to reboot your IPCop server, so please read <emphasis role="strong">all</emphasis> patch information thoroughly before applying the update. </para> </note> + <note> + <title>Troubleshooting</title> + <para> + If you get an error message <quote>This is not an authorised + update</quote>, check if your IPCop server's clock is in + the past, as <command>gpg</command> will think the signature + date is in the future, and will stop with an error. + </para> + <para> + Check the log file <filename>/var/log/httpd/error_log</filename> + to confirm. + </para> + <para> + IPCop is often run on old hardware, and the battery can go flat, + causing the system clock to fail. + </para> + </note> </sect2> <sect2 id="passwords"> <title> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <eob...@us...> - 2009-05-05 11:27:08
|
Revision: 2795 http://ipcop.svn.sourceforge.net/ipcop/?rev=2795&view=rev Author: eoberlander Date: 2009-05-05 11:27:03 +0000 (Tue, 05 May 2009) Log Message: ----------- Remove section on IDS, and references to IDS, from 2.0 Admin Manual. Modified Paths: -------------- IPCopDoc/trunk/en/admin/images/info-inodes.png IPCopDoc/trunk/en/admin/images/infodisk.png IPCopDoc/trunk/en/admin/images/infokern.png IPCopDoc/trunk/en/admin/images/services.png IPCopDoc/trunk/en/admin/xml/home.xml IPCopDoc/trunk/en/admin/xml/introduction.xml IPCopDoc/trunk/en/admin/xml/logs.xml IPCopDoc/trunk/en/admin/xml/preface.xml IPCopDoc/trunk/en/admin/xml/services.xml Modified: IPCopDoc/trunk/en/admin/images/info-inodes.png =================================================================== (Binary files differ) Modified: IPCopDoc/trunk/en/admin/images/infodisk.png =================================================================== (Binary files differ) Modified: IPCopDoc/trunk/en/admin/images/infokern.png =================================================================== (Binary files differ) Modified: IPCopDoc/trunk/en/admin/images/services.png =================================================================== (Binary files differ) Modified: IPCopDoc/trunk/en/admin/xml/home.xml =================================================================== --- IPCopDoc/trunk/en/admin/xml/home.xml 2009-05-05 10:30:49 UTC (rev 2794) +++ IPCopDoc/trunk/en/admin/xml/home.xml 2009-05-05 11:27:03 UTC (rev 2795) @@ -94,7 +94,7 @@ Configuration/Administration of your IPCop server's Virtual Private Network settings and options.</para></listitem> <listitem><para><guimenuitem>Logs:</guimenuitem> - View all your IPCop server's logs (firewall, IDS, + View all your IPCop server's logs (firewall, proxy, etc.)</para></listitem> </itemizedlist> Modified: IPCopDoc/trunk/en/admin/xml/introduction.xml =================================================================== --- IPCopDoc/trunk/en/admin/xml/introduction.xml 2009-05-05 10:30:49 UTC (rev 2794) +++ IPCopDoc/trunk/en/admin/xml/introduction.xml 2009-05-05 11:27:03 UTC (rev 2795) @@ -74,8 +74,8 @@ </para> <para> Now, after almost two and a half years, the first major overhaul of IPCop has been released. - With it, a lot of cool things have been added; quad network support, intrusion detection on - all networks and a slick new interface, to name a few. + With it, a lot of cool things have been added; quad network support + and a slick new interface, to name a few. </para> <para> And so again, Welcome to IPCop! @@ -194,11 +194,6 @@ </listitem> <listitem> <para> - Intrusion Detection for ALL networks (RED, ORANGE, BLUE and GREEN) - </para> - </listitem> - <listitem> - <para> Virtual Private Network (VPN) to allow multiple sites to act as single large network. </para> </listitem> Modified: IPCopDoc/trunk/en/admin/xml/logs.xml =================================================================== --- IPCopDoc/trunk/en/admin/xml/logs.xml 2009-05-05 10:30:49 UTC (rev 2794) +++ IPCopDoc/trunk/en/admin/xml/logs.xml 2009-05-05 11:27:03 UTC (rev 2795) @@ -41,12 +41,6 @@ </listitem> <listitem> <para> - <link linkend="section-logs-ids"> - <guimenuitem>IDS Logs</guimenuitem></link> - </para> - </listitem> - <listitem> - <para> <link linkend="logs-system"> <guimenuitem>System Logs</guimenuitem></link> </para> @@ -57,12 +51,11 @@ <sect2 id="log_intro"> <title>Introduction</title> <para> - The Logs web pages consist of five or six sub-pages - + The Logs web pages consist of five sub-pages - <guisubmenu>Log Settings</guisubmenu>, <guisubmenu>Log Summary</guisubmenu>, <guisubmenu>Proxy Logs</guisubmenu>, - <guisubmenu>Firewall Logs</guisubmenu>, - <guisubmenu>IDS Logs</guisubmenu> (if enabled) and + <guisubmenu>Firewall Logs</guisubmenu> and <guisubmenu>System Logs</guisubmenu>. These share a common set of interface features to select the log information to be displayed, and to @@ -363,98 +356,6 @@ </para> </sect2> - <sect2 id="section-logs-ids"> - <title> - Intrusion Detection System Log Page - </title> - <para> - This page shows incidents detected by the IPCop - Intrusion Detection System (IDS). The IDS system is - inactive after first installation of IPCop, and may be - activated (and deactivated) through a specific - administration page (<guimenu>Services</guimenu> > - <guimenu>Intrusion Detection</guimenu>). - </para> - <para> - The controls on this page are the basic - <guilabel>Month</guilabel>, - <guilabel>Day</guilabel>, - <guilabel><<</guilabel> (Day before), - <guilabel>>></guilabel> (Day after), - <guibutton>Update</guibutton> and - <guibutton>Export</guibutton> buttons that - are described in detail at the beginning of this - Section. These allow you to examine the IDS Logs for a - specific day. These Logs consist of a number of items - for each detected incident: - </para> - - <itemizedlist> - <listitem> - <para>The <guilabel>Date:</guilabel> and time of - the incident.</para> - </listitem> - <listitem> - <para><guilabel>Name:</guilabel> - a description - of the incident.</para> - </listitem> - <listitem> - <para><guilabel>Priority:</guilabel> (if - available). This is the severity of the incident, - graded as 1 ("bad"), 2 ("not too bad"), & 3 - ("possibly bad").</para> - </listitem> - <listitem> - <para><guilabel>Type:</guilabel> - a general - description of the incident (if available).</para> - </listitem> - <listitem> - <para><guilabel>IP Info:</guilabel> - the IP - identities (address & port) of the source and - target involved in the incident. Each IP address - is a hyperlink, which you can use to perform a DNS - lookup for that IP address and obtain any - available information about its registration and - ownership.</para> - </listitem> - <listitem> - <para><guilabel>References:</guilabel> - - hyperlinked URLs to any available sources of - information for this type of incident.</para> - </listitem> - <listitem> - <para><guilabel>SID:</guilabel> - the Snort ID - number (if available). "Snort" is the software - module used by IPCop to provide the IDS function, - and SID is the ID code used by the Snort module to - identify a particular pattern of attack. This - parameter is hyperlinked to a web page carrying - the relevant entry on the Snort database of - intrusion signatures.</para> - </listitem> - </itemizedlist> - <para> - <figure id="v190.logs.005"> - <title>IDS Log Output</title> - <mediaobject> - <imageobject role="fo"> - <imagedata fileref= - "&imagepath;idslog.&imageext;" format="PNG" - contentwidth="14cm"/> - </imageobject> - <imageobject role="html"> - <imagedata fileref= - "&imagepath;idslog.&imageext;" format="PNG" - align="center"/> - </imageobject> - <textobject> - <phrase>IDS Log</phrase> - </textobject> - </mediaobject> - </figure> - </para> - </sect2> - <sect2 id="logs-system"> <title> System Log Page @@ -544,12 +445,6 @@ </listitem> <listitem> <para> - <guilabel>Snort</guilabel> - shows a log of - activity for Snort, the Intrusion Detection System. - </para> - </listitem> - <listitem> - <para> <guilabel>SSH</guilabel> - provides a record of users who have logged in to, and out of the IPCop server over a network via the SSH Modified: IPCopDoc/trunk/en/admin/xml/preface.xml =================================================================== --- IPCopDoc/trunk/en/admin/xml/preface.xml 2009-05-05 10:30:49 UTC (rev 2794) +++ IPCopDoc/trunk/en/admin/xml/preface.xml 2009-05-05 11:27:03 UTC (rev 2795) @@ -7,7 +7,7 @@ > <preface id="preface"> <title>Preface</title> - <sect1 id="rightsndiscaimers"> + <sect1 id="rightsndisclaimers"> <title>Rights and Disclaimers</title> <para>IPCop is Copyright the IPCop Linux Group.</para> <para>IPCop Linux is published under the GNU General Public License. For more @@ -81,4 +81,4 @@ </ulink> </para> </sect1> -</preface> \ No newline at end of file +</preface> Modified: IPCopDoc/trunk/en/admin/xml/services.xml =================================================================== --- IPCopDoc/trunk/en/admin/xml/services.xml 2009-05-05 10:30:49 UTC (rev 2794) +++ IPCopDoc/trunk/en/admin/xml/services.xml 2009-05-05 11:27:03 UTC (rev 2795) @@ -40,13 +40,9 @@ <para><link linkend="services_shaping"><guimenuitem>Traffic Shaping</guimenuitem></link> </para> </listitem> - <listitem> - <para><link linkend="services_ids"><guimenuitem>Intrusion Detection System</guimenuitem></link> - </para> - </listitem> </itemizedlist> - In a larger network it is likely that these services will be provided by dedicated - servers and should be disabled here. + In a larger network it is likely that some of these services will be + provided by dedicated servers and should be disabled here. </para> <sect2 id="services_webproxy"> <title>Web Proxy Administrative Web Page</title> @@ -982,12 +978,12 @@ </para> <para> Follow their instructions on how to use country zones (for example - 0.us.pool.ntp.org) rather than the global zone (0.pool.ntp.org), to further + <userinput>0.us.pool.ntp.org</userinput>) rather than the global zone (<userinput>0.pool.ntp.org</userinput>), to further improve efficiency. </para> <para> In January 2008 the IPCop vendor pool became available. Please - use 0.ipcop.pool.ntp.org 1.ipcop.pool.ntp.org or 2.ipcop.pool.ntp.org + use <userinput>0.ipcop.pool.ntp.org 1.ipcop.pool.ntp.org</userinput> or <userinput>2.ipcop.pool.ntp.org</userinput> instead of the previous default zone names. </para> <para> @@ -1122,76 +1118,5 @@ Depending on your usage, you will undoubtedly want to rearrange your choices of high, medium and low priority traffic. </para> - </sect2><sect2 id="services_ids"> - <title>Intrusion Detection System Administrative Web Page</title> - <para> - IPCop contains a powerful intrusion detection system, Snort, which analyses the contents - of packets received by the firewall and searches for known signatures of malicious activity. - </para><para> - Snort is a passive system which requires management by the - User. You need to monitor the logs, and interpret the - information. Snort only logs suspicious activity, so if - you need an active system, consider - <filename>snort_inline</filename> or the - <filename>guardian</filename> addon. - </para><para> - You should also note that Snort is memory hungry, with - newer versions using about 80Mb per interface. This - depends in part on the ruleset used, and can be reduced - by selection of the rules used. - </para><para> - <figure id="v140.services.011"> - <title>Intrusion Detection Settings</title> - <mediaobject> - <imageobject role="fo"> - <imagedata fileref="&imagepath;ids.&imageext;" format="PNG" contentwidth="14cm"/> - </imageobject> - <imageobject role="html"> - <imagedata fileref="&imagepath;ids.&imageext;" format="PNG" align="center"/> - </imageobject> - <textobject> - <phrase>IDS Web Page</phrase> - </textobject> - </mediaobject> - </figure> - </para><para> - IPCop can monitor packets on the Green, Blue, Orange and Red interfaces. Just tick the relevant - boxes and click the <guilabel>Save</guilabel> button. - </para> - <sect3 id="services_ids_update"> - <title>Snort rules update</title> - <para> - A standard installation of IPCop comes with a set - of Snort's default rules. As more attacks are - discovered, the rules Snort uses to recognize them - will be updated. To utilize Sourcefire VRT Certified - rules you need to register on Snort's website - <ulink url="http://www.snort.org/">www.snort.org</ulink> - and obtain an <quote>Oink Code</quote>. - </para> - <para> - Select the correct radio button, add your Oink Code - and click the <guilabel>Save</guilabel> button - <emphasis>before</emphasis> - your first attempt to download a ruleset. - </para> - <para> - Then, click the - <guilabel>Refresh update list</guilabel> button, - followed by the - <guilabel>Download new ruleset</guilabel> button, - and finally click - <guilabel>Apply now</guilabel>. - </para> - <para> - After a successful operation the date and time will - be displayed beside each button. - </para> - <para> - The final button - - <guilabel>Read last ruleset installation log</guilabel> - - will display the last installation log. - </para> - </sect3> </sect2> </sect1> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <eob...@us...> - 2009-05-11 11:01:19
|
Revision: 2834 http://ipcop.svn.sourceforge.net/ipcop/?rev=2834&view=rev Author: eoberlander Date: 2009-05-11 11:01:10 +0000 (Mon, 11 May 2009) Log Message: ----------- Add style.css for 2.0 Admin Manual on IPCop website. Added Paths: ----------- IPCopDoc/trunk/en/admin/html/ IPCopDoc/trunk/en/admin/html/style.css Added: IPCopDoc/trunk/en/admin/html/style.css =================================================================== --- IPCopDoc/trunk/en/admin/html/style.css (rev 0) +++ IPCopDoc/trunk/en/admin/html/style.css 2009-05-11 11:01:10 UTC (rev 2834) @@ -0,0 +1,52 @@ +/* + style.css - a CSS stylesheet for use with HTML output produced by + tldp-xsl stylesheets. Written by Emma Jane Hogbin. Comments + added by David Horton. +*/ + + +body { + +/* + Style the HMTL <body> tag with a sans-serif font and 5% margin to + make text easier to read in a web browser. +*/ + + font-family: sans-serif; + margin: 5%; +} + + +pre { + +/* + Style <pre> tags with a light gray background and a small indention. + HTML <pre> tags are used to represent Docbook XML tags like + <programlisting> and <screen> +*/ + + background: #E0E0E0; + margin: 0 5%; + padding: 5px; +} + + +/* Add any desired customizations below. */ + +.guisubmenu, .guimenu, .guimenuitem { + font-style: italic; +} + + +.guibutton { + font-weight: bold; + background-color: #F0F0F0; +} + +.guilabel { + background-color: #F0F0F0; +} + +.figure { + font-size: 75%; +} Property changes on: IPCopDoc/trunk/en/admin/html/style.css ___________________________________________________________________ Added: svn:executable + * This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <eob...@us...> - 2009-05-29 18:39:11
|
Revision: 2951 http://ipcop.svn.sourceforge.net/ipcop/?rev=2951&view=rev Author: eoberlander Date: 2009-05-29 18:39:07 +0000 (Fri, 29 May 2009) Log Message: ----------- Review Proxy section, and add new screenshots, split through text. This is a first draft. Modified Paths: -------------- IPCopDoc/trunk/en/admin/images/home1.png IPCopDoc/trunk/en/admin/images/proxy.png IPCopDoc/trunk/en/admin/xml/services.xml Added Paths: ----------- IPCopDoc/trunk/en/admin/images/proxy1.png IPCopDoc/trunk/en/admin/images/proxy2.png IPCopDoc/trunk/en/admin/images/proxy3.png IPCopDoc/trunk/en/admin/images/proxy4.png IPCopDoc/trunk/en/admin/images/proxy5.png IPCopDoc/trunk/en/admin/images/proxy6.png Modified: IPCopDoc/trunk/en/admin/images/home1.png =================================================================== (Binary files differ) Modified: IPCopDoc/trunk/en/admin/images/proxy.png =================================================================== (Binary files differ) Added: IPCopDoc/trunk/en/admin/images/proxy1.png =================================================================== (Binary files differ) Property changes on: IPCopDoc/trunk/en/admin/images/proxy1.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: IPCopDoc/trunk/en/admin/images/proxy2.png =================================================================== (Binary files differ) Property changes on: IPCopDoc/trunk/en/admin/images/proxy2.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: IPCopDoc/trunk/en/admin/images/proxy3.png =================================================================== (Binary files differ) Property changes on: IPCopDoc/trunk/en/admin/images/proxy3.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: IPCopDoc/trunk/en/admin/images/proxy4.png =================================================================== (Binary files differ) Property changes on: IPCopDoc/trunk/en/admin/images/proxy4.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: IPCopDoc/trunk/en/admin/images/proxy5.png =================================================================== (Binary files differ) Property changes on: IPCopDoc/trunk/en/admin/images/proxy5.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: IPCopDoc/trunk/en/admin/images/proxy6.png =================================================================== (Binary files differ) Property changes on: IPCopDoc/trunk/en/admin/images/proxy6.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Modified: IPCopDoc/trunk/en/admin/xml/services.xml =================================================================== --- IPCopDoc/trunk/en/admin/xml/services.xml 2009-05-29 13:52:00 UTC (rev 2950) +++ IPCopDoc/trunk/en/admin/xml/services.xml 2009-05-29 18:39:07 UTC (rev 2951) @@ -44,6 +44,7 @@ In a larger network it is likely that some of these services will be provided by dedicated servers and should be disabled here. </para> + <sect2 id="services-webproxy"> <title>Web Proxy Administrative Web Page</title> <para> @@ -60,8 +61,29 @@ is also possible to run the proxy in <quote>transparent</quote> mode. In this case the browsers need no special configuration and the firewall automatically redirects all traffic on port 80, the standard HTTP port, to the proxy server. - </para><para> - <screenshot> + </para> + + <sect3 id="services-webproxy-commonsettings"> + <title>Common settings</title> + <para> + You can choose if you want to proxy requests from your Green + (private) network and/or your Blue (wireless) network (if + fitted). Just tick the relevant boxes. + </para> + </sect3> + <sect3 id="services-webproxy-upstream"> + <title>Upstream proxy</title> + <para> + If your ISP requires you to use their cache for web access then + you should specify the hostname and port in the + <guibutton>Upstream proxy</guibutton> text box. If your + ISP's proxy requires a username and password then enter + them in the <guibutton>Upstream username</guibutton> and + <guibutton>Upstream password</guibutton> boxes. + </para> + <para> + <figure id="v2.services.001"> + <title>Web proxy - Common settings & Upstream proxy Sections</title> <mediaobject> <imageobject role="fo"> <imagedata fileref="&imagepath;proxy.&imageext;" @@ -75,117 +97,373 @@ <phrase>HTTP Proxy Web Page</phrase> </textobject> </mediaobject> - </screenshot> - </para><para> - You can choose if you want to proxy requests from your Green (private) network - and/or your Blue (wireless) network (if fitted). Just tick the relevant boxes. - </para> - <formalpara> - <title><guilabel>Log enabled</guilabel></title> - <para> - If you choose to enable the proxy then you can also - log web accesses by ticking the - <guibutton>Log Enabled</guibutton> box. Accesses made - through the proxy can be seen by clicking the Proxy - Logs choice of the Logs menu. + </figure> </para> - </formalpara> - <para> - If your ISP requires you to use their cache for web access then you should specify the hostname and port - in the <guibutton>Upstream proxy</guibutton> text box. If your ISP's proxy requires a user name - and password then enter them in the <guibutton>Upstream username</guibutton> and - <guibutton>Upstream password</guibutton> boxes. - </para> - <formalpara> - <title><guilabel>Your extension_methods - list</guilabel></title> + </sect3> + <sect3 id="services-webproxy-logsettings"> + <title>Log Settings</title> + <formalpara> + <title><guilabel>Log enabled</guilabel></title> + <para> + If you choose to enable the proxy, then you can also log + web accesses by ticking the + <guibutton>Log Enabled</guibutton> checkbox. + </para> + </formalpara> <para> - Squid only knows about standard HTTP request methods. - Unknown methods are denied, unless you add them to the - <filename>extension_methods</filename> list. - You can add up to 20 additional "extension" - methods here. + Accesses made through the proxy can be seen by visiting the + <link linkend="logs-proxy">Proxy Logs</link> webpage. </para> - </formalpara> - <para> - For example, <ulink url="http://subversion.tigris.org/">subversion</ulink> - uses some non-standard methods that squid blocks. - To allow subversion to work through IPCop's transparent proxy, - you will have to add <filename>REPORT</filename> - <filename>MKACTIVITY</filename> <filename>CHECKOUT</filename> and - <filename>MERGE</filename> to the - <filename>extension_methods</filename> list. - </para> - <formalpara> - <title><guilabel>Disallow local proxying on blue/green - networks</guilabel></title> + <formalpara> + <title><guilabel>Log query terms</guilabel></title> + <para> + Content to be written... + </para> + </formalpara> + <formalpara> + <title><guilabel>Log useragents</guilabel></title> + <para> + Content to be written... + </para> + </formalpara> + </sect3> + <sect3 id="services-webproxy-cacheman"> + <title>Cache management</title> <para> - Check this option to disable proxying to green and - blue networks (if blue is available). This closes a - possible hole between Green and Blue if they are run - in <quote>transparent</quote> mode. + You can choose how much disk space should be used for caching + web pages in the Cache Management section. You can also set the + size of the smallest object to be cached, normally 0, and the + largest, 4096KB. </para> - </formalpara> - <formalpara> - <title><guilabel>or specify a list of destinations - which are not to be proxied</guilabel></title> <para> - This gives somewhat more flexibility, allowing you to - define which destination networks are to be DENIED - through the proxy. You can specify a network (or - networks) with an IP Address and Netmask, for example: - <filename>192.168.3.0/255.255.255.0</filename> + For privacy reasons, the proxy will not cache pages received via + https, or other pages where a username and password are + submitted via the URL. </para> - </formalpara> - <formalpara id="cache_management"> - <title>Cache Management</title> <para> - You can choose how much disk space should be used for caching web pages in the Cache Management section. - You can also set the size of the smallest object to be cached, normally 0, and the largest, 4096KB. - For privacy reasons, the proxy will not cache pages received via https, or other pages - where a username and password are submitted via the URL. + <figure id="v2.services.002"> + <title>Web proxy - Log settings & Cache management Sections</title> + <mediaobject> + <imageobject role="fo"> + <imagedata fileref="&imagepath;proxy1.&imageext;" + format="PNG" + contentwidth="14cm"/> + </imageobject> + <imageobject role="html"> + <imagedata fileref="&imagepath;proxy1.&imageext;" format="PNG" align="center"/> + </imageobject> + <textobject> + <phrase>HTTP Web Proxy Page</phrase> + </textobject> + </mediaobject> + </figure> </para> - </formalpara> - <formalpara> - <title><guilabel>Repair cache</guilabel></title> + <warning> + <para> + Caching can take up a lot of space on your hard drive. + If you use a large cache, then the minimum size hard drive + listed in the IPCop documentation will + <emphasis>not</emphasis> be large enough. + </para> + <para> + The larger the cache you choose, the more memory is required + by the proxy server to manage the cache. If you are running + IPCop on a machine with low memory do not choose a large + cache. + </para> + </warning> + </sect3> + <sect3 id="services-webproxy-destports"> + <title>Destination ports</title> + <formalpara> + <title><guilabel>Allowed standard ports (one per line)</guilabel></title> + <para> + Content to be written... + </para> + </formalpara> + <formalpara> + <title><guilabel>Allowed SSL ports (one per line)</guilabel></title> + <para> + Content to be written... + </para> + </formalpara> <para> - You can repair the proxy cache by clicking the - <guibutton>Repair cache</guibutton> button. + <figure id="v2.services.003"> + <title>Web proxy - Destination ports Section</title> + <mediaobject> + <imageobject role="fo"> + <imagedata fileref="&imagepath;proxy2.&imageext;" + format="PNG" + contentwidth="14cm"/> + </imageobject> + <imageobject role="html"> + <imagedata fileref="&imagepath;proxy2.&imageext;" format="PNG" align="center"/> + </imageobject> + <textobject> + <phrase>HTTP Web Proxy Page</phrase> + </textobject> + </mediaobject> + </figure> </para> - </formalpara> - <formalpara> - <title><guilabel>Clear cache</guilabel></title> + </sect3> + <sect3 id="services-webproxy-network"> + <title>Network based access control</title> + <formalpara> + <title><guilabel>Allowed subnets (one per line)</guilabel></title> + <para> + Content to be written... + </para> + </formalpara> + <formalpara> + <title><guilabel>Disable internal proxy access</guilabel></title> + <para> + Check this box to disable internal proxy access. + </para> + </formalpara> + <formalpara> + <title><guilabel>Disable internal proxy access to Green from other subnets</guilabel></title> + <para> + Check this box to disable internal proxy access to Green + from other subnets. + </para> + </formalpara> + <formalpara> + <title><guilabel>Disable internal proxy access to Blue from other subnets</guilabel></title> + <para> + Check this box to disable internal proxy access to Blue + from other subnets. + </para> + </formalpara> + <formalpara> + <title><guilabel>Unrestricted IP addresses (one per line)</guilabel> (optional)</title> + <para> + Content to be written... + </para> + </formalpara> + <formalpara> + <title><guilabel>Unrestricted MAC addresses (one per line)</guilabel> (optional)</title> + <para> + Content to be written... + </para> + </formalpara> + <formalpara> + <title><guilabel>Banned IP addresses (one per line)</guilabel> (optional)</title> + <para> + Content to be written... + </para> + </formalpara> + <formalpara> + <title><guilabel>Banned MAC addresses (one per line)</guilabel> (optional)</title> + <para> + Content to be written... + </para> + </formalpara> <para> - You can flush all pages out of the proxy cache at any - time by clicking the - <guibutton>Clear cache</guibutton> button. + <figure id="v2.services.004"> + <title>Web proxy - Network based access control Section</title> + <mediaobject> + <imageobject role="fo"> + <imagedata fileref="&imagepath;proxy3.&imageext;" + format="PNG" + contentwidth="14cm"/> + </imageobject> + <imageobject role="html"> + <imagedata fileref="&imagepath;proxy3.&imageext;" format="PNG" align="center"/> + </imageobject> + <textobject> + <phrase>HTTP Web Proxy Page</phrase> + </textobject> + </mediaobject> + </figure> </para> - </formalpara> - <formalpara id="transfer_limits"> + </sect3> + <sect3 id="services-webproxy-time"> + <title>Time Restrictions</title> + <formalpara> + <title><guilabel>Access</guilabel></title> + <para> + Content to be written... + </para> + </formalpara> + </sect3> + <sect3 id="services-webproxy-transferlimits"> <title>Transfer limits</title> <para> - The web proxy can also be used to control how your users access the web. The only control accessible via the - web interface is the maximum size of data received from and sent to the web. You can use this to - prevent your users - downloading large files and slowing Internet access for - everyone else. Set the two fields to 0, the default, to - remove all restrictions. + The web proxy can also be used to control how your Users access + the web. One control accessible via the web interface is the + maximum size of data received from and sent to the web. You can + use this to prevent your Users downloading large files and + slowing Internet access for everyone else. Set the + <guilabel>Max download size (KB)</guilabel> and + <guilabel>Max upload size (KB)</guilabel> fields to 0, + the default, to remove all restrictions. </para> - </formalpara> - <formalpara> - <title><guilabel>Save</guilabel></title> + </sect3> + <sect3 id="services-webproxy-throttling"> + <title>Download Throttling</title> <para> - To save any changes, press the - <guibutton>Save</guibutton> button. + Content required... </para> - </formalpara> - <warning><para> - Caching can take up a lot of space on your hard drive. If you use a large cache, then the - minimum size hard drive listed in the IPCop documentation will not be large enough.</para><para> - The larger the cache you choose the more memory is required by the proxy server to manage the cache. If - you are running IPCop on a machine with low memory do not choose a large cache.</para> - </warning> - </sect2><sect2 id="services-dhcp"> + <para> + <figure id="v2.services.005"> + <title>Web proxy - Time restrictions, Transfer limits & Download throttling Sections</title> + <mediaobject> + <imageobject role="fo"> + <imagedata fileref="&imagepath;proxy4.&imageext;" + format="PNG" + contentwidth="14cm"/> + </imageobject> + <imageobject role="html"> + <imagedata fileref="&imagepath;proxy4.&imageext;" format="PNG" align="center"/> + </imageobject> + <textobject> + <phrase>HTTP Web Proxy Page</phrase> + </textobject> + </mediaobject> + </figure> + </para> + </sect3> + <sect3 id="services-webproxy-mime"> + <title>MIME type filter</title> + <formalpara> + <title><guilabel>Enabled</guilabel></title> + <para> + Content to be written... + </para> + </formalpara> + <formalpara> + <title><guilabel>Block these MIME types (one per line)</guilabel> (optional)</title> + <para> + Content to be written... + </para> + </formalpara> + </sect3> + <sect3 id="services-webproxy-browser"> + <title>Web browser</title> + <formalpara> + <title><guilabel>Enable browser check</guilabel></title> + <para> + Check this box if you want to enable browser checking. + </para> + </formalpara> + <formalpara> + <title><guilabel>Allowed clients for web access</guilabel></title> + <para> + Check the appropriate box(es) for permitted clients. + </para> + </formalpara> + <para> + <figure id="v2.services.006"> + <title>Web proxy - MIME type filter & Web browser Sections</title> + <mediaobject> + <imageobject role="fo"> + <imagedata fileref="&imagepath;proxy5.&imageext;" + format="PNG" + contentwidth="14cm"/> + </imageobject> + <imageobject role="html"> + <imagedata fileref="&imagepath;proxy5.&imageext;" format="PNG" align="center"/> + </imageobject> + <textobject> + <phrase>HTTP Web Proxy Page</phrase> + </textobject> + </mediaobject> + </figure> + </para> + </sect3> + <sect3 id="services-webproxy-privacy"> + <title>Privacy</title> + <formalpara> + <title><guilabel>Fake useragent submitted to external sites</guilabel> (optional)</title> + <para> + Content to be written... + </para> + </formalpara> + <formalpara> + <title><guilabel>Fake referer submitted to external sites</guilabel> (optional)</title> + <para> + Content to be written... + </para> + </formalpara> + </sect3> + <sect3 id="services-webproxy-authentication"> + <title>Authentication method</title> + <formalpara> + <title><guilabel>None</guilabel> (default)</title> + <para> + Content to be written... + </para> + </formalpara> + <formalpara> + <title><guilabel>Local</guilabel></title> + <para> + Content to be written... + </para> + </formalpara> + <formalpara> + <title><guilabel>identd</guilabel></title> + <para> + Content to be written... + </para> + </formalpara> + <formalpara> + <title><guilabel>LDAP</guilabel></title> + <para> + Content to be written... + </para> + </formalpara> + <formalpara> + <title><guilabel>Windows</guilabel></title> + <para> + Content to be written... + </para> + </formalpara> + <formalpara> + <title><guilabel>RADIUS</guilabel></title> + <para> + Content to be written... + </para> + </formalpara> + </sect3> + <sect3 id="services-webproxy-clearcache"> + <title>Clear Cache/Save</title> + <formalpara> + <title><guilabel>Clear cache</guilabel></title> + <para> + You can flush all pages out of the proxy cache at any + time by clicking the + <guibutton>Clear cache</guibutton> button. + </para> + </formalpara> + <formalpara> + <title><guilabel>Save</guilabel></title> + <para> + After making any changes, press the + <guibutton>Save</guibutton> button to apply them. + </para> + </formalpara> + <para> + <figure id="v2.services.007"> + <title>Web proxy - Privacy & Authentication Method Sections</title> + <mediaobject> + <imageobject role="fo"> + <imagedata fileref="&imagepath;proxy6.&imageext;" + format="PNG" + contentwidth="14cm"/> + </imageobject> + <imageobject role="html"> + <imagedata fileref="&imagepath;proxy6.&imageext;" format="PNG" align="center"/> + </imageobject> + <textobject> + <phrase>HTTP Web Proxy Page</phrase> + </textobject> + </mediaobject> + </figure> + </para> + </sect3> + </sect2> + + <sect2 id="services-dhcp"> <title>DHCP Administrative Web Page</title> <para> DHCP (Dynamic Host Configuration Protocol) allows you to control the network configuration of all your computers This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <ow...@us...> - 2009-05-30 07:26:24
|
Revision: 2954 http://ipcop.svn.sourceforge.net/ipcop/?rev=2954&view=rev Author: owes Date: 2009-05-30 07:25:37 +0000 (Sat, 30 May 2009) Log Message: ----------- Add screenshot for DHCP client (RED=DHCP). Add some texts in the Status sections. Modified Paths: -------------- IPCopDoc/trunk/en/admin/xml/info.xml Added Paths: ----------- IPCopDoc/trunk/en/admin/images/net-dhcpc.png Added: IPCopDoc/trunk/en/admin/images/net-dhcpc.png =================================================================== (Binary files differ) Property changes on: IPCopDoc/trunk/en/admin/images/net-dhcpc.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Modified: IPCopDoc/trunk/en/admin/xml/info.xml =================================================================== --- IPCopDoc/trunk/en/admin/xml/info.xml 2009-05-29 21:50:58 UTC (rev 2953) +++ IPCopDoc/trunk/en/admin/xml/info.xml 2009-05-30 07:25:37 UTC (rev 2954) @@ -378,7 +378,8 @@ <sect2 id="status-network"> <title>Network Status</title> <para> - Content to be written... + This section displays information on the network interfaces and networking + within your IPCop server. </para> <sect3 id="status-network-interfaces"> @@ -408,9 +409,40 @@ </mediaobject> </screenshot> </para> + </sect3> + + <sect3 id="status-network-dhcpc"> + <title>Current DHCP Client Status</title> <para> - Content to be checked... + Displays the status of the DHCP client if your RED interface + is DHCP. The current gateway, DNS server(s), IP address of + DHCP server, lease time and lease expiry time are shown. </para> + <para> + <screenshot> + <mediaobject> + <imageobject role="fo"> + <imagedata fileref="&imagepath;net-dhcpc.&imageext;" + format="PNG" + contentwidth="14cm"/> + </imageobject> + <imageobject role="html"> + <imagedata fileref="&imagepath;net-dhcpc.&imageext;" + format="PNG" + align="center"/> + </imageobject> + <textobject> + <phrase>Current DHCP Client Status</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + <note> + <para> + This section will <emphasis>only</emphasis> be visible + if your RED interface is DHCP. + </para> + </note> </sect3> <sect3 id="status-network-dhcp"> @@ -422,9 +454,6 @@ listed, with hostnames if available, and expiry dates. </para> <para> - Leases that have expired are scored through. - </para> - <para> <screenshot> <mediaobject> <imageobject role="fo"> @@ -456,7 +485,7 @@ <sect3 id="status-network-routing"> <title>Routing Table Entries</title> <para> - Content to be written... + Displays the current routing table and default gateway. </para> <para> <screenshot> @@ -482,6 +511,9 @@ <sect3 id="status-network-arp"> <title>ARP Table Entries</title> <para> + Shows the current content of the ARP table. + </para> + <para> <screenshot> <mediaobject> <imageobject role="fo"> @@ -500,11 +532,7 @@ </mediaobject> </screenshot> </para> - <para> - Content to be written... - </para> </sect3> - </sect2> <sect2 id="status-graphs"> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <eob...@us...> - 2009-06-27 14:12:43
|
Revision: 3136 http://ipcop.svn.sourceforge.net/ipcop/?rev=3136&view=rev Author: eoberlander Date: 2009-06-27 12:29:29 +0000 (Sat, 27 Jun 2009) Log Message: ----------- Update screenshots and text for Web Proxy. Modified Paths: -------------- IPCopDoc/trunk/en/admin/images/proxy.png IPCopDoc/trunk/en/admin/images/proxy1.png IPCopDoc/trunk/en/admin/xml/services.xml Modified: IPCopDoc/trunk/en/admin/images/proxy.png =================================================================== (Binary files differ) Modified: IPCopDoc/trunk/en/admin/images/proxy1.png =================================================================== (Binary files differ) Modified: IPCopDoc/trunk/en/admin/xml/services.xml =================================================================== --- IPCopDoc/trunk/en/admin/xml/services.xml 2009-06-27 11:57:51 UTC (rev 3135) +++ IPCopDoc/trunk/en/admin/xml/services.xml 2009-06-27 12:29:29 UTC (rev 3136) @@ -63,6 +63,14 @@ the standard HTTP port, to the proxy server. </para> + <sect3 id="services-webproxy-settings"> + <title>Web proxy</title> + <para> + The first line in the <guilabel>Settings</guilabel> box + indicates if the proxy server is stopped or running. + </para> + </sect3> + <sect3 id="services-webproxy-commonsettings"> <title>Common settings</title> <para> @@ -81,24 +89,6 @@ them in the <guibutton>Upstream username</guibutton> and <guibutton>Upstream password</guibutton> boxes. </para> - <para> - <figure id="v2.services.001"> - <title>Web proxy - Common settings & Upstream proxy Sections</title> - <mediaobject> - <imageobject role="fo"> - <imagedata fileref="&imagepath;proxy.&imageext;" - format="PNG" - contentwidth="14cm"/> - </imageobject> - <imageobject role="html"> - <imagedata fileref="&imagepath;proxy.&imageext;" format="PNG" align="center"/> - </imageobject> - <textobject> - <phrase>HTTP Proxy Web Page</phrase> - </textobject> - </mediaobject> - </figure> - </para> </sect3> <sect3 id="services-webproxy-logsettings"> <title>Log Settings</title> @@ -126,6 +116,25 @@ Content to be written... </para> </formalpara> + <para> + <figure id="v2.services.001"> + <title>Web proxy - Common settings, Upstream proxy & + Log Settings Sections</title> + <mediaobject> + <imageobject role="fo"> + <imagedata fileref="&imagepath;proxy.&imageext;" + format="PNG" + contentwidth="14cm"/> + </imageobject> + <imageobject role="html"> + <imagedata fileref="&imagepath;proxy.&imageext;" format="PNG" align="center"/> + </imageobject> + <textobject> + <phrase>HTTP Proxy Web Page</phrase> + </textobject> + </mediaobject> + </figure> + </para> </sect3> <sect3 id="services-webproxy-cacheman"> <title>Cache management</title> @@ -142,7 +151,7 @@ </para> <para> <figure id="v2.services.002"> - <title>Web proxy - Log settings & Cache management Sections</title> + <title>Web proxy - Cache management Section</title> <mediaobject> <imageobject role="fo"> <imagedata fileref="&imagepath;proxy1.&imageext;" This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <eob...@us...> - 2009-07-11 13:02:28
|
Revision: 3213 http://ipcop.svn.sourceforge.net/ipcop/?rev=3213&view=rev Author: eoberlander Date: 2009-07-11 13:02:24 +0000 (Sat, 11 Jul 2009) Log Message: ----------- Update screenshots and text in DHCP section. Modified Paths: -------------- IPCopDoc/trunk/en/admin/images/dhcp.png IPCopDoc/trunk/en/admin/images/dhcp2.png IPCopDoc/trunk/en/admin/images/dhcp3.png IPCopDoc/trunk/en/admin/xml/services.xml Modified: IPCopDoc/trunk/en/admin/images/dhcp.png =================================================================== (Binary files differ) Modified: IPCopDoc/trunk/en/admin/images/dhcp2.png =================================================================== (Binary files differ) Modified: IPCopDoc/trunk/en/admin/images/dhcp3.png =================================================================== (Binary files differ) Modified: IPCopDoc/trunk/en/admin/xml/services.xml =================================================================== --- IPCopDoc/trunk/en/admin/xml/services.xml 2009-07-11 07:47:02 UTC (rev 3212) +++ IPCopDoc/trunk/en/admin/xml/services.xml 2009-07-11 13:02:24 UTC (rev 3213) @@ -480,7 +480,8 @@ and its DNS and WINS configuration will be set from the IPCop machine. To use this feature new machines must be set to obtain their network configuration automatically. </para><para> - <screenshot> + <figure id="v2.services.008"> + <title>DHCP settings</title> <mediaobject> <imageobject role="fo"> <imagedata fileref="&imagepath;dhcp.&imageext;" format="PNG" contentwidth="14cm"/> @@ -492,7 +493,7 @@ <phrase>DHCP Server Web Page</phrase> </textobject> </mediaobject> - </screenshot> + </figure> </para> <para> You can choose if you want to provide this service to your Green (private) network @@ -662,126 +663,6 @@ When you press <guibutton>Save</guibutton>, the change is acted upon. </para> </sect3> -<!-- section now redundant? - <sect3 id="dhcp_options"> - <title>Additional DHCP Options</title> - <para> - If you have any special parameters you want to distribute - to your network via the DHCP server, you add them here. - (This functionality was added in v1.4.6). - </para> - <para> - <figure id="v140.services.001"> - <title>Additional DHCP Options</title> - <mediaobject> - <imageobject role="fo"> - <imagedata fileref="&imagepath;dhcp2.&imageext;" format="PNG" contentwidth="14cm"/> - </imageobject> - <imageobject role="html"> - <imagedata fileref="&imagepath;dhcp2.&imageext;" format="PNG" align="center"/> - </imageobject> - <textobject> - <phrase>Additional DHCP Options screenshot</phrase> - </textobject> - </mediaobject> - </figure> - </para> - <para> - You can add additional DHCP Options here: - </para> - <formalpara> - <title><guilabel>Option name</guilabel></title> - <para> - You specify the name of the DHCP option here, - for example: - <filename>smtp-server</filename> or - <filename>tcp-keepalive-interval</filename>. - </para> - </formalpara> - <formalpara> - <title><guilabel>Option value</guilabel></title> - <para> - The value, appropriate to the option, goes here. - It could be a string, an integer, an IP Address, - or an on/off flag, depending on the option. - </para> - </formalpara> - <para> - Possible option formats are: boolean, integer 8, - integer 16, integer 32, signed integer 8, signed - integer 16, signed integer 32, unsigned integer 8, - unsigned integer 16, unsigned integer 32, ip-address, - text, string, array of ip-address. - </para> - <para> - The following formats were added in v1.4.12: array of - integer 8, array of integer 16, array of integer 32, - array of signed integer 8, array of signed integer 16, - array of signed integer 32, array of unsigned integer 8, - array of unsigned integer 16, array of unsigned integer 32. - </para> - <formalpara> - <title><guilabel>Option scope</guilabel> (optional)</title> - <para> - The scope of the option will be Global, - <emphasis>unless</emphasis> one of the interface - checkboxes is checked, in which case it will only - apply to that interface. - </para> - </formalpara> - <formalpara> - <title><guilabel>Enabled</guilabel></title> - <para> - Click on this check box to tell the DHCP - server to hand out this option. - If the entry is not enabled, it will be - stored in IPCop's files, but the DHCP - server will not issue the option. - </para> - </formalpara> - <formalpara> - <title><guilabel>Add</guilabel></title> - <para> - Click on this button to add the option. - </para> - </formalpara> - <formalpara> - <title><guilabel>List options</guilabel></title> - <para> - Click on this button to display a list of - options with possible values. - </para> - </formalpara> - <note> - <title>Adding custom DHCP options</title> - <para> - If the option you want is not included in the built-in list - of options, you can add your own custom definitions. The - syntax required is listed at the foot of the Options List. - </para> - <para> - For example, to add the ldap-server option (code 95) to the - list, firstly, - Add a DHCP Option with name: <filename>ldap-server</filename> - and value: <filename>code 95=string</filename> - (be sure to enter value correctly, 1 space between code and - 95 and no spaces around the = sign). - </para> - <para> - You should then see an entry with Option name: - <filename>ldap-server</filename>, Option value: - <filename>code 95=string</filename> and Option scope: - <filename>Definition</filename>. - </para> - <para> - Now you can add an ldap-server as you would with any built-in - DHCP option, with Option name: - <filename>ldap-server</filename> and Option value: - <filename>"ldap://some.server/dc=foo,dc=bar"</filename> - </para> - </note> - </sect3> ---> <sect3 id="add_dhcp_lease"> <title>Fixed Leases</title> <para> @@ -793,7 +674,7 @@ server to ask for their IP address and will take whatever we have configured for them. </para> <para> - <figure id="v140.services.002"> + <figure id="v2.services.009"> <title>Add a new fixed lease</title> <mediaobject> <imageobject role="fo"> @@ -812,6 +693,16 @@ You can specify the following fixed lease parameters: </para> <formalpara> + <title><guilabel>Enabled</guilabel></title> + <para> + Click on this check box to tell the DHCP + server to hand out this static lease. + If the entry is not enabled, it will be + stored in IPCop's files, but the DHCP + server will not issue this lease. + </para> + </formalpara> + <formalpara> <title><guilabel>MAC Address</guilabel></title> <para> The six octet/byte colon separated MAC address @@ -820,17 +711,18 @@ </formalpara> <warning> <para> - The format of the MAC address is xx:xx:xx:xx:xx:xx, - not xx-xx-xx-xx-xx-xx, as some machines show, i.e. - 00:e5:b0:00:02:d2. + The format of the MAC address is + <filename>xx:xx:xx:xx:xx:xx</filename>, not + <filename>xx-xx-xx-xx-xx-xx</filename>, as some machines show, + i.e. <filename>00:e5:b0:00:02:d2</filename> </para> </warning> - <para> +<!-- <para> It is possible to assign different fixed leases to the same device, provided the IP addresses are in different subnets. Duplicated addresses are highlighted in the - table in <emphasis>bold</emphasis> text. - </para> + table in <emphasis role='strong'>bold</emphasis> text. + </para> not yet... --> <formalpara> <title><guilabel>IP Address</guilabel></title> <para> @@ -841,16 +733,25 @@ dynamic address range. </para> </formalpara> - <para> +<!-- <para> It is possible to assign an IP Address outwith the local subnets to a device. The IP address will be highlighted in orange in the table. - </para> + </para> not yet... --> <formalpara> + <title><guilabel>Hostname or FQDN</guilabel> (optional)</title> + <para> + You can specify a hostname here that will always be allocated + to a device with a particular hardware address. + A hostname specified like this overrides any supplied by the + DHCP client on the machine. + </para> + </formalpara> + <formalpara> <title><guilabel>Remark</guilabel> (optional)</title> <para> If you want, you can include a string of text to identify the device - using the fixed lease. (This field was added in v1.4.4). + using the fixed lease. </para> </formalpara> <formalpara> @@ -873,16 +774,6 @@ path to it here. </para> </formalpara> - <formalpara> - <title><guilabel>Enabled</guilabel></title> - <para> - Click on this check box to tell the DHCP - server to hand out this static lease. - If the entry is not enabled, it will be - stored in IPCop's files, but the DHCP - server will not issue this lease. - </para> - </formalpara> </sect3> <sect3 id="current_lease_display"> <title><guilabel>Current fixed leases</guilabel></title> @@ -892,19 +783,19 @@ </para> <para> You can sort the display of the fixed leases by clicking - on the underlined headings <emphasis>MAC Address</emphasis> - or <emphasis>IP Address</emphasis>. Another click on the + on the underlined headings <guilabel>MAC Address</guilabel> + or <guilabel>IP Address</guilabel>. Another click on the heading will reverse the sort order. </para> <para> - <figure id="v140.services.003"> + <figure id="v2.services.010"> <title>List of fixed leases</title> <mediaobject> <imageobject role="fo"> - <imagedata fileref="&imagepath;dhcp3.&imageext;" format="PNG" contentwidth="14cm"/> + <imagedata fileref="&imagepath;dhcp2.&imageext;" format="PNG" contentwidth="14cm"/> </imageobject> <imageobject role="html"> - <imagedata fileref="&imagepath;dhcp3.&imageext;" format="PNG" align="center"/> + <imagedata fileref="&imagepath;dhcp2.&imageext;" format="PNG" align="center"/> </imageobject> <textobject> <phrase>Fixed lease screenshot</phrase> @@ -913,20 +804,20 @@ </figure> </para> <para> - To edit an existing lease, click on its - <guiicon>pencil</guiicon> icon. - The fixed leases values will be displayed - in the <emphasis>Edit an existing lease</emphasis> - section of the page. - The fixed lease being edited will be highlighted in yellow. - Click the <emphasis>Update</emphasis> - button to save any changes. + To enable or disable an entry - click on the + <quote>Enabled</quote> icon (the checkbox in the Action column) + for the particular item you want to enable or disable. + The icon changes to an empty box when a fixed lease is + disabled. Click on the checkbox to enable it again. </para> <para> - To remove an existing profile, click on its - <guiicon>trash can</guiicon> icon. - The lease will be removed. + To edit a lease click on its <guiicon>Pencil</guiicon> icon. + The entry's data will be displayed in the form above. Make your changes + and click the <guibutton>Update</guibutton> button. </para> + <para> + To delete an entry click on its <guiicon>Trash Can</guiicon> icon. + </para> </sect3> <sect3 id="current_dynamic_display"> <title><guilabel>Current dynamic leases</guilabel></title> @@ -949,7 +840,7 @@ section, if needed. </para> <para> - <figure id="v190.services.004"> + <figure id="v2.services.011"> <title>Current dynamic leases</title> <mediaobject> <imageobject role="fo"> @@ -968,11 +859,24 @@ </mediaobject> </figure> </para> + </sect3> + + <sect3 id="dhcp_options"> + <title>Additional DHCP options</title> <para> - Lease times that have already expired are - <quote>struck through</quote>. + If you have any special parameters you want to distribute to + your network via the DHCP server, then add them to the file + <filename>/var/ipcop/dhcp/dnsmasq.local</filename> + provided for user's use. + After you have modified the file, restart the DHCP server via + the web interface so your changes propagate to the network. </para> + <para> + Refer to the + <ulink url="http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html">dnsmasq manual</ulink>. + </para> </sect3> + <sect3 id="dhcp_errors"> <title><guilabel>Error messages</guilabel></title> <para> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <eob...@us...> - 2009-07-19 19:05:33
|
Revision: 3282 http://ipcop.svn.sourceforge.net/ipcop/?rev=3282&view=rev Author: eoberlander Date: 2009-07-19 19:05:30 +0000 (Sun, 19 Jul 2009) Log Message: ----------- Add placeholder image for interface policies section. Modified Paths: -------------- IPCopDoc/trunk/en/admin/xml/firewall.xml Added Paths: ----------- IPCopDoc/trunk/en/admin/images/firewall-policy.png Added: IPCopDoc/trunk/en/admin/images/firewall-policy.png =================================================================== (Binary files differ) Property changes on: IPCopDoc/trunk/en/admin/images/firewall-policy.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Modified: IPCopDoc/trunk/en/admin/xml/firewall.xml =================================================================== --- IPCopDoc/trunk/en/admin/xml/firewall.xml 2009-07-19 18:56:51 UTC (rev 3281) +++ IPCopDoc/trunk/en/admin/xml/firewall.xml 2009-07-19 19:05:30 UTC (rev 3282) @@ -199,10 +199,10 @@ <title>Interface policies</title> <mediaobject> <imageobject role="fo"> - <imagedata fileref="&imagepath;firewall02.&imageext;" format="PNG" contentwidth="14cm"/> + <imagedata fileref="&imagepath;firewall-policy.&imageext;" format="PNG" contentwidth="14cm"/> </imageobject> <imageobject role="html"> - <imagedata fileref="&imagepath;firewall02.&imageext;" format="PNG" align="center"/> + <imagedata fileref="&imagepath;firewall-policy.&imageext;" format="PNG" align="center"/> </imageobject> <textobject> <phrase>Interface policies screenshot</phrase> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <eob...@us...> - 2009-07-20 14:00:07
|
Revision: 3285 http://ipcop.svn.sourceforge.net/ipcop/?rev=3285&view=rev Author: eoberlander Date: 2009-07-20 13:59:57 +0000 (Mon, 20 Jul 2009) Log Message: ----------- Incorporate some suggestions. Modified Paths: -------------- IPCopDoc/trunk/en/admin/images/firewall-policy.png IPCopDoc/trunk/en/admin/xml/firewall.xml Modified: IPCopDoc/trunk/en/admin/images/firewall-policy.png =================================================================== (Binary files differ) Modified: IPCopDoc/trunk/en/admin/xml/firewall.xml =================================================================== --- IPCopDoc/trunk/en/admin/xml/firewall.xml 2009-07-20 13:30:34 UTC (rev 3284) +++ IPCopDoc/trunk/en/admin/xml/firewall.xml 2009-07-20 13:59:57 UTC (rev 3285) @@ -121,13 +121,27 @@ <sect2 id="firewall-settings"> <title>Firewall Settings Administrative Web Page</title> + <para> + The first section allows you to control administrative access + (via https and ssh) to specific networks + (Green, Blue, OpenVPN, IPsec) as available. + </para> + <sect3 id="firewall-settings-settings"> + <title>Settings</title> + <formalpara> + <title>Admin network</title> + <para> + Check the checkboxes beside each network interface you want + to open for administrative access. + </para> + </formalpara> <para> - The first section allows you to open administrative access - (via https and ssh) to specific networks - (Green, Blue, OpenVPN, IPsec) as available. + If you want ssh access, don't forget to enable it on the + <link linkend="system-ssh">SSH Access</link> + page. </para> <para> - If the MAC address is set, it is combined, so if you enable both + If a MAC address is set, it is combined, so if you enable both Green and Blue, <emphasis>and</emphasis> set a MAC address, this machine has administrative access from both Green and Blue. </para> @@ -182,19 +196,33 @@ </para> </formalpara> <para> - Check this box to to control the the display of interface colors on + Check this box to control the display of interface colors on <!-- add link when known --> link page. </para> <formalpara> - <title>Interface policies</title> + <title>Save</title> <para> - The second section shows the currently active interfaces and - their log and policy settings. + Press the <guibutton>Save</guibutton> button to save your settings. </para> </formalpara> + <formalpara> + <title>Reset</title> + <para> + Press the <guibutton>Reset</guibutton> button to revert + settings to their defaults. + </para> + </formalpara> + </sect3> + + <sect3 id="firewall-settings-policy"> + <title>Interface policies</title> <para> + The second section shows the currently active interfaces and + their log and policy settings. + </para> + <para> <figure id="v200.firewall.002"> <title>Interface policies</title> <mediaobject> @@ -285,7 +313,7 @@ <formalpara> <title>Blue Access</title> <para> - If enabled, only those clients that are on the + If Blue Access control is enabled, only those clients that are on the <link linkend="firewall-blue-access">Blue Access</link> list have access, depending on policy. </para> @@ -295,9 +323,12 @@ only use DHCP and can open IPsec and/or OpenVPN tunnels. </para> <para> - If Blue Access is <emphasis>not</emphasis> enabled, all + If Blue Access control is <emphasis>not</emphasis> enabled, all clients have access, depending on policy. </para> + <para> + This only applies if you have a Blue network interface installed. + </para> <formalpara> <title>Action</title> <para> @@ -305,18 +336,39 @@ edit a policy. </para> </formalpara> -<!-- + </sect3> + + <sect3 id="firewall-settings-defaults"> + <title>Default settings</title> <para> - Text + Green is the only Admin network interface enabled by default. </para> - <formalpara> - <title>Title</title> - <para> - Text - </para> - </formalpara> ---> - </sect2> + <para> + Red Interface has <quote>closed</quote> as default policy. + All other interfaces have <quote>open</quote>. + </para> + <para> + Red Interface has <quote>Drop</quote> as Deny Action. + All other interfaces have <quote>Reject</quote>. + </para> + <para> + Logging is active on all interfaces. + </para> + <para> + Blue Access control is active. + </para> + <para> + The difference with IPCop version 1.4 and version 2.0 is the Deny + Action. In 1.4 it was <quote>Drop</quote> on all interfaces. + </para> + <para> + An additional difference is that we no longer Accept all packets + that are sent to IPCop from internal interfaces, only packets for + services that we know about (DHCP, DNS, NTP, Proxy, IPsec, OpenVPN) + are accepted. + </para> + </sect3> + </sect2> <sect2 id="firewall-blue-access"> <title>Blue Access Administrative Web Page</title> @@ -513,6 +565,17 @@ Content to be written... </para> </sect2> +<!-- + <para> + Text + </para> + <formalpara> + <title>Title</title> + <para> + Text + </para> + </formalpara> +--> </sect1> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <eob...@us...> - 2009-07-20 20:10:26
|
Revision: 3288 http://ipcop.svn.sourceforge.net/ipcop/?rev=3288&view=rev Author: eoberlander Date: 2009-07-20 20:10:21 +0000 (Mon, 20 Jul 2009) Log Message: ----------- Review/update Blue Access section. Modified Paths: -------------- IPCopDoc/trunk/en/admin/xml/firewall.xml Added Paths: ----------- IPCopDoc/trunk/en/admin/images/blueaccess1.png IPCopDoc/trunk/en/admin/images/blueaccess2.png Added: IPCopDoc/trunk/en/admin/images/blueaccess1.png =================================================================== (Binary files differ) Property changes on: IPCopDoc/trunk/en/admin/images/blueaccess1.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: IPCopDoc/trunk/en/admin/images/blueaccess2.png =================================================================== (Binary files differ) Property changes on: IPCopDoc/trunk/en/admin/images/blueaccess2.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Modified: IPCopDoc/trunk/en/admin/xml/firewall.xml =================================================================== --- IPCopDoc/trunk/en/admin/xml/firewall.xml 2009-07-20 17:27:36 UTC (rev 3287) +++ IPCopDoc/trunk/en/admin/xml/firewall.xml 2009-07-20 20:10:21 UTC (rev 3288) @@ -379,8 +379,8 @@ <sect2 id="firewall-blue-access"> <title>Blue Access Administrative Web Page</title> <para> - This subsection allows you to configure which Wireless Access Points - on the Blue network can connect to IPCop. + This section allows you to configure a Wireless Access Point + on the Blue network connected to IPCop. This is 100% optional, so you may safely ignore this section if you do not wish to make use of this feature. </para> @@ -390,6 +390,9 @@ installed and configured a Blue network interface card. </para> </note> + + <sect3 id="firewall-blue-access-setup"> + <title>Setup</title> <para> To setup Blue Access do the following: </para> @@ -458,9 +461,19 @@ </para> </listitem> </orderedlist> + </sect3> + + <sect3 id="firewall-blue-access-add"> + <title>Adding a device</title> <para> - <figure id="v140.firewall.004"> - <title>Blue Access Settings</title> + In the <guilabel>Add Device</guilabel> section you input the + IP Address or the MAC Address of a wireless Access Point, or any + device on the Blue network that you want to connect to the + Internet through IPCop. + </para> + <para> + <figure id="v200.firewall.003"> + <title>Add device</title> <mediaobject> <imageobject role="fo"> <imagedata fileref="&imagepath;blueaccess.&imageext;" format="PNG" contentwidth="14cm"/> @@ -469,65 +482,116 @@ <imagedata fileref="&imagepath;blueaccess.&imageext;" format="PNG" align="center"/> </imageobject> <textobject> - <phrase>Blue Access Web Page</phrase> + <phrase>Add device section</phrase> </textobject> </mediaobject> </figure> </para> + <formalpara> + <title>IP Address (optional)</title> + <para> + You have to enter at least one IP <emphasis>or</emphasis> + one MAC Address per device, or both. + </para> + </formalpara> <para> - In the <guilabel>Add Device</guilabel> section you input the - IP Address or the MAC Address of a wireless Access Point, or any - device on the Blue network that you want to connect to the - Internet through IPCop. - </para> - <para> - You have to enter at least one MAC <emphasis>or</emphasis> one IP - Address per device. - </para> - <para> If you use DHCP on the Blue Network, and want to allow any device to connect and access the Red Network, you must add an entry for every IP address in your DHCP range to this list. Leave the MAC Address field empty when adding each IP Address. </para> + <formalpara> + <title>MAC Address (optional)</title> + <para> + Conversely, if you want to restrict access to known devices, add the + MAC address of each device, and leave the IP Address field empty. + That will allow listed devices to connect regardless of the DHCP + lease they receive. + </para> + </formalpara> + <formalpara> + <title>Remark (optional)</title> + <para> + If you want, you can include a string of text to describe or identify + the device. + </para> + </formalpara> + <formalpara> + <title>Add</title> + <para> + Once you have entered all the information, + press the <guibutton>Add</guibutton>. + This will move the entry to the next section, and list it + as enabled. + </para> + </formalpara> + </sect3> + + <sect3 id="firewall-blue-access-current"> + <title>Current devices</title> <para> - Conversely, if you want to restrict access to known devices, add the MAC - address of each device, and leave the IP Address field empty. That will - allow listed devices to connect regardless of the DHCP lease they receive. + The <guilabel>Devices on Blue</guilabel> section lists the current + entries. </para> <para> - Once you have entered all the information, click the - <guilabel>Enabled</guilabel> box and press - <guibutton>Add</guibutton>. - This will move the entry to the next section, and list it - as enabled. + <figure id="v200.firewall.004"> + <title>Devices on Blue</title> + <mediaobject> + <imageobject role="fo"> + <imagedata fileref="&imagepath;blueaccess1.&imageext;" format="PNG" contentwidth="14cm"/> + </imageobject> + <imageobject role="html"> + <imagedata fileref="&imagepath;blueaccess1.&imageext;" format="PNG" align="center"/> + </imageobject> + <textobject> + <phrase>Devices on Blue section</phrase> + </textobject> + </mediaobject> + </figure> </para> <para> - The <guilabel>Devices on Blue</guilabel> section lists the current - entries. To remove one, click the - <quote>Trash Can</quote> icon. + To remove an entry, click the + <emphasis>Trash Can</emphasis> icon. To edit one, click the - <quote>Yellow Pencil</quote> icon. + <emphasis>Yellow Pencil</emphasis> icon. </para> <para> - To enable or disable an entry, click on the - <quote>Enabled</quote> icon (to the left of the Yellow Pencil) - for the particular entry you want to enable or disable. - The icon changes to an empty box when a device is - disabled. Click the checkbox to enable it again. + To enable or disable a device - click on the checkbox in the Action + column for the particular machine you want to enable or disable. + The icon changes to an empty box when a device is disabled. + Click on the checkbox to enable it again. </para> <para> - If DHCP is enabled for the Blue network, the + If the DHCP server is enabled for the Blue network, the <guilabel>Current DHCP leases on Blue</guilabel> section will be displayed. </para> <para> - This provides a quick way of adding wireless devices to the list. - You just have to click on the <quote>Blue Pencil</quote> icon + <figure id="v200.firewall.005"> + <title>Current DHCP leases on Blue</title> + <mediaobject> + <imageobject role="fo"> + <imagedata fileref="&imagepath;blueaccess2.&imageext;" format="PNG" contentwidth="14cm"/> + </imageobject> + <imageobject role="html"> + <imagedata fileref="&imagepath;blueaccess2.&imageext;" format="PNG" align="center"/> + </imageobject> + <textobject> + <phrase>Current DHCP leases on Blue section</phrase> + </textobject> + </mediaobject> + </figure> + </para> + <para> + There is a quick way of adding machines to the device list. + You just have to click on the <emphasis>Blue Pencil Plus</emphasis> icon for a device to be added to the list of enabled devices. - You can then edit the entry, if necessary, by clicking on the - <quote>Yellow Pencil</quote> icon, as before. </para> + <para> + You can then edit the entry, if necessary, by clicking the + <emphasis>Yellow Pencil</emphasis> icon, as before. + </para> + </sect3> </sect2> <sect2 id="firewall-services"> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <eob...@us...> - 2009-07-23 13:32:40
|
Revision: 3299 http://ipcop.svn.sourceforge.net/ipcop/?rev=3299&view=rev Author: eoberlander Date: 2009-07-23 13:32:39 +0000 (Thu, 23 Jul 2009) Log Message: ----------- Initial review of DynDNS section, with new screenshots. Modified Paths: -------------- IPCopDoc/trunk/en/admin/images/dyndns.png IPCopDoc/trunk/en/admin/images/dyndns2.png IPCopDoc/trunk/en/admin/xml/services.xml Added Paths: ----------- IPCopDoc/trunk/en/admin/images/dyndns1.png Modified: IPCopDoc/trunk/en/admin/images/dyndns.png =================================================================== (Binary files differ) Added: IPCopDoc/trunk/en/admin/images/dyndns1.png =================================================================== (Binary files differ) Property changes on: IPCopDoc/trunk/en/admin/images/dyndns1.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Modified: IPCopDoc/trunk/en/admin/images/dyndns2.png =================================================================== (Binary files differ) Modified: IPCopDoc/trunk/en/admin/xml/services.xml =================================================================== --- IPCopDoc/trunk/en/admin/xml/services.xml 2009-07-23 09:00:25 UTC (rev 3298) +++ IPCopDoc/trunk/en/admin/xml/services.xml 2009-07-23 13:32:39 UTC (rev 3299) @@ -899,19 +899,29 @@ <sect2 id="services-dyndns"> <title>Dynamic DNS Administrative Web Page</title> <para> - Dynamic DNS (DYNDNS) allows you to make your server available to the Internet - even though it does not have a static IP address. + Dynamic DNS (DYNDNS) allows you to make your domain name available to the Internet + even though you do not have a static IP address. + </para> + <para> To use DYNDNS you must first register a subdomain with a DYNDNS provider. Then - whenever your server connects to the Internet and is given an IP address by your ISP + whenever IPCop connects to the Internet and is given an IP address by your ISP, it must inform the DYNDNS server of that IP address. - When a client machine wishes to connect to your server it will resolve the address + When a client machine wishes to connect to your domain it will resolve the address by going to the DYNDNS server, which will give it the latest value. If this is up to date - then the client will be able to contact your server (assuming your firewall rules allow this). + then the client will be able to contact you (assuming your firewall rules allow this). + </para> + <para> IPCop makes the process of keeping your DYNDNS address up to date easier by providing automatic updates for many of the DYNDNS providers. - </para><para> - <figure id="v140.services.005"> - <title>Dynamic DNS Settings</title> + </para> + <sect3 id="services-dyndns-settings"> + <title>Settings</title> + <para> + The first section has a couple of general settings. + </para> + <para> + <figure id="v200.services.031"> + <title>Dynamic DNS Settings</title> <mediaobject> <imageobject role="fo"> <imagedata fileref="&imagepath;dyndns.&imageext;" @@ -924,16 +934,85 @@ align="center"/> </imageobject> <textobject> - <phrase>Dynamic DNS Web Page</phrase> + <phrase>Dynamic DNS Settings section</phrase> </textobject> </mediaobject> </figure> </para> - <sect3 id="dyndnsadd"> + <formalpara> + <title>Dynamic DNS provider(s) will receive an IP address + for this IPCop from</title> + <para> + Choose 'The classical RED IP used by IPCop during + connection' if your IPCop box has a public IP or the + IP that you want to be reported. + If IPCop fails to detect your public IP choose + 'Guess the real public IP with help of an external + server'. + </para> + </formalpara> + <formalpara> + <title>Guess the real public IP with help of an external + server</title> + <para> + This option is mainly used if your IPCop is behind a router. + Do not use this option with Dial on Demand. + Your RED IP must be inside one of the three private networks + e.g. 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16. + </para> + </formalpara> + <formalpara> + <title>Minimize updates</title> + <para> + Avoid many updates to the dynamic DNS service by comparing + the IP registered with your service and the IP that IPCop + has detected. + As many dynamic DNS services do ban you if you update too often, + it is strongly recommended that you select this option. + </para> + </formalpara> + <para> + For IPCop's that are connected 24/7, a cronjob forces an update + once a week. + Another cronjob is set up to force an update once a month, + <emphasis>even if</emphasis> 'Minimize updates' is selected, + to avoid an account being declared 'dead'. + </para> + <formalpara> + <title><guilabel>Save</guilabel></title> + <para> + After making any changes, press the + <guibutton>Save</guibutton> button to apply them. + </para> + </formalpara> + </sect3> + + <sect3 id="services-dyndns-add"> <title>Add a host</title> <para> The following DYNDNS parameters can be set from the web interface: </para> + <para> + <figure id="v200.services.032"> + <title>Add a DYNDNS provider</title> + <mediaobject> + <imageobject role="fo"> + <imagedata fileref="&imagepath;dyndns1.&imageext;" + format="PNG" + contentwidth="14cm"/> + </imageobject> + <imageobject role="html"> + <imagedata fileref="&imagepath;dyndns1.&imageext;" + format="PNG" + align="center"/> + </imageobject> + <textobject> + <phrase>Add a DYNDNS provider section</phrase> + </textobject> + </mediaobject> + </figure> + </para> + <formalpara> <title><guilabel>Service</guilabel></title> <para> @@ -991,12 +1070,16 @@ reentering the data. </para> </formalpara> - </sect3><sect3 id="dyndnsedit"> + </sect3> + + <sect3 id="services-dyndns-current"> <title>Current hosts</title> <para> This section shows the DYNDNS entries you have currently configured. - </para><para> - <screenshot> + </para> + <para> + <figure id="v200.services.033"> + <title>Current hosts</title> <mediaobject> <imageobject role="fo"> <imagedata fileref="&imagepath;dyndns2.&imageext;" @@ -1009,25 +1092,32 @@ align="center"/> </imageobject> <textobject> - <phrase>Dynamic DNS Web Page</phrase> + <phrase>Current hosts section</phrase> </textobject> </mediaobject> - </screenshot> - </para><para> - To edit an entry click on its <guiicon>pencil</guiicon> icon. - The entry's data will be displayed in the form above. Make your changes - and click the <guibutton>Save</guibutton> button on the form. - </para><para> - You can also update the <guilabel>Behind a proxy</guilabel>, - <guilabel>Use wildcards</guilabel> and <guilabel>Enabled</guilabel> tick boxes directly - from the current hosts list entry. + </figure> </para> + <para> + A green entry indicates that the last update was OK, a blue entry indicates + it's inactive, and a red entry means a failed update. + </para> + <para> + To edit an entry click on its <emphasis>Yellow Pencil</emphasis> icon. + The entry's data will be displayed in the form above. Make your changes + and click the <guibutton>Save</guibutton> button on the form. + </para> + <para> + You can also toggle the <guilabel>Proxy</guilabel>, + <guilabel>Wildcards</guilabel> and <guilabel>Enabled</guilabel> checkboxes directly + from the current hosts list entry. + </para> </sect3> + <sect3 id="manual_update"> <title>Forcing a Manual Update</title> <para> You can force IPCop to refresh the information manually - by pressing <guibutton>Force Update</guibutton>, however, + by pressing the <guibutton>Instant Update</guibutton> button, however, it is best to only update when the IP address has actually changed, as dynamic DNS service providers don't like to handle updates that make no changes. @@ -1035,7 +1125,9 @@ be updated each time your IP changes. </para> </sect3> - </sect2><sect2 id="services-hosts"> + </sect2> + + <sect2 id="services-hosts"> <title>Edit Hosts Administrative Web Page</title> <para> As well as caching DNS information from the Internet, the DNS proxy on IPCop allows you This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <eob...@us...> - 2009-07-24 15:22:33
|
Revision: 3315 http://ipcop.svn.sourceforge.net/ipcop/?rev=3315&view=rev Author: eoberlander Date: 2009-07-24 14:34:52 +0000 (Fri, 24 Jul 2009) Log Message: ----------- Modifications to DynDNS section. Modified Paths: -------------- IPCopDoc/trunk/en/admin/images/dyndns1.png IPCopDoc/trunk/en/admin/images/dyndns2.png IPCopDoc/trunk/en/admin/xml/services.xml Modified: IPCopDoc/trunk/en/admin/images/dyndns1.png =================================================================== (Binary files differ) Modified: IPCopDoc/trunk/en/admin/images/dyndns2.png =================================================================== (Binary files differ) Modified: IPCopDoc/trunk/en/admin/xml/services.xml =================================================================== --- IPCopDoc/trunk/en/admin/xml/services.xml 2009-07-24 12:59:25 UTC (rev 3314) +++ IPCopDoc/trunk/en/admin/xml/services.xml 2009-07-24 14:34:52 UTC (rev 3315) @@ -972,11 +972,9 @@ </para> </formalpara> <para> - For IPCop's that are connected 24/7, a cronjob forces an update - once a week. - Another cronjob is set up to force an update once a month, - <emphasis>even if</emphasis> 'Minimize updates' is selected, - to avoid an account being declared 'dead'. + If your IPCop is connected 24/7, you can set up a Scheduled Event + to force an update to avoid your account being declared + 'dead'. See the section below. </para> <formalpara> <title><guilabel>Save</guilabel></title> @@ -990,9 +988,14 @@ <sect3 id="services-dyndns-add"> <title>Add a host</title> <para> - The following DYNDNS parameters can be set from the web interface: + The second section allows you to Add or Edit a host. </para> <para> + Select a DYNDNS provider from the drop down list, and + press the <guibutton>Add</guibutton> button. + The screen below will appear. + </para> + <para> <figure id="v200.services.032"> <title>Add a DYNDNS provider</title> <mediaobject> @@ -1016,10 +1019,10 @@ <formalpara> <title><guilabel>Service</guilabel></title> <para> - Choose a DYNDNS provider from the dropdown. - You should have already registered with that provider. + You should have already registered with this service. </para> </formalpara> +<!-- <formalpara> <title><guilabel>Behind a proxy</guilabel></title> <para> @@ -1028,46 +1031,57 @@ other services. </para> </formalpara> +redundant ? --> <formalpara> - <title><guilabel>Enable wildcards</guilabel></title> + <title>Enabled</title> <para> - Enable Wildcards will allow you to have all the subdomains of your dynamic - DNS hostname pointing to the same IP as your hostname (e.g. with this tick - box enabled, www.ipcop.dyndns.org will point to the same IP as ipcop.dyndns.org). - This tick box is useless with no-ip.com service, as they only allow this to be - activated or deactivated directly on their website. + If this is not ticked then IPCop will not update the + information on the DYNDNS server. + It will retain the information so you can re-enable + DYNDNS updates without re-entering the data. </para> </formalpara> <formalpara> - <title><guilabel>Hostname</guilabel></title> + <title>Enable wildcards</title> <para> + Enable Wildcards will allow you to have all the subdomains + of your dynamic DNS hostname pointing to the same IP as + your hostname (e.g. with this checkbox enabled, + www.ipcop.dyndns.org will point to the same IP as + ipcop.dyndns.org). + This checkbox doesn't work with the no-ip.com service, + as they only allow this to be activated or deactivated + directly on their website. + </para> + </formalpara> + <formalpara> + <title>Hostname</title> + <para> Enter the hostname you registered with your DYNDNS provider. </para> </formalpara> <formalpara> - <title><guilabel>Domain</guilabel></title> + <title>Domain</title> <para> Enter the domain name you registered with your DYNDNS provider. </para> </formalpara> <formalpara> - <title><guilabel>Username</guilabel></title> + <title>User Name</title> <para> - Enter the username you registered with your DYNDNS provider. + Enter the username/login name you registered with your DYNDNS provider. </para> </formalpara> <formalpara> - <title><guilabel>Password</guilabel></title> + <title>Password</title> <para> Enter the password for your username. </para> </formalpara> <formalpara> - <title><guilabel>Enabled</guilabel></title> + <title>Add</title> <para> - If this is not ticked then IPCop will not update the information on the DYNDNS - server. It will retain the information so you can re-enable DYNDNS updates without - reentering the data. + When you press the <guibutton>Add</guibutton> button the details are saved. </para> </formalpara> </sect3> @@ -1107,7 +1121,7 @@ and click the <guibutton>Save</guibutton> button on the form. </para> <para> - You can also toggle the <guilabel>Proxy</guilabel>, + You can also toggle the <guilabel>Wildcards</guilabel> and <guilabel>Enabled</guilabel> checkboxes directly from the current hosts list entry. </para> @@ -1124,6 +1138,21 @@ Once the host entries have been enabled your IP will automatically be updated each time your IP changes. </para> + </sect3> + + <sect3 id="services-dyndns-schedule"> + <title>Scheduling an Update</title> + <para> + To avoid your account being declared 'dead' + due to lack of activity, you can force IPCop to refresh + the information automatically by adding an event on the + <link linkend="system-scheduler">Scheduler</link> + page. + </para> + <para> + This mainly applies to IPCop's that run non-stop, and + don't change their IP very often. + </para> </sect3> </sect2> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <eob...@us...> - 2009-07-26 11:01:22
|
Revision: 3329 http://ipcop.svn.sourceforge.net/ipcop/?rev=3329&view=rev Author: eoberlander Date: 2009-07-26 11:01:15 +0000 (Sun, 26 Jul 2009) Log Message: ----------- Initial commit for Firewall Services section. Modified Paths: -------------- IPCopDoc/trunk/en/admin/xml/firewall.xml Added Paths: ----------- IPCopDoc/trunk/en/admin/images/firewall-add-service.png IPCopDoc/trunk/en/admin/images/firewall-custom-service.png IPCopDoc/trunk/en/admin/images/firewall-def-services.png Added: IPCopDoc/trunk/en/admin/images/firewall-add-service.png =================================================================== (Binary files differ) Property changes on: IPCopDoc/trunk/en/admin/images/firewall-add-service.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: IPCopDoc/trunk/en/admin/images/firewall-custom-service.png =================================================================== (Binary files differ) Property changes on: IPCopDoc/trunk/en/admin/images/firewall-custom-service.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: IPCopDoc/trunk/en/admin/images/firewall-def-services.png =================================================================== (Binary files differ) Property changes on: IPCopDoc/trunk/en/admin/images/firewall-def-services.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Modified: IPCopDoc/trunk/en/admin/xml/firewall.xml =================================================================== --- IPCopDoc/trunk/en/admin/xml/firewall.xml 2009-07-26 06:50:11 UTC (rev 3328) +++ IPCopDoc/trunk/en/admin/xml/firewall.xml 2009-07-26 11:01:15 UTC (rev 3329) @@ -597,15 +597,109 @@ <sect2 id="firewall-services"> <title>Services Administrative Web Page</title> <para> - Content to be written... + The IPCop Firewall is configured by using Services and/or + Service Groups. </para> + <para> + If you want to create a rule for a Service that is not present + in the list of Default Services, you will have to add it first. + </para> + <sect3 id="firewall-services-add"> + <title>Adding a service</title> + <para> + In first section you give the custom Service a descriptive name, + choose the Protocol and Ports (TCP and UDP only). + </para> + <para> + <figure id="v200.firewall.031"> + <title>Add a service</title> + <mediaobject> + <imageobject role="fo"> + <imagedata fileref="&imagepath;firewall-add-service.&imageext;" format="PNG" contentwidth="14cm"/> + </imageobject> + <imageobject role="html"> + <imagedata fileref="&imagepath;firewall-add-service.&imageext;" format="PNG" align="center"/> + </imageobject> + <textobject> + <phrase>Add a service section</phrase> + </textobject> + </mediaobject> + </figure> + </para> + <note> + <para> + Use the Invert option with great care, as this can create far + larger holes in your IPCop Firewall than you might expect! + </para> + </note> + </sect3> + + <sect3 id="firewall-services-custom"> + <title>Custom services</title> + <para> + The second section lists the custom services you have added. + </para> + <para> + <figure id="v200.firewall.032"> + <title>Custom services</title> + <mediaobject> + <imageobject role="fo"> + <imagedata fileref="&imagepath;firewall-custom-service.&imageext;" format="PNG" contentwidth="14cm"/> + </imageobject> + <imageobject role="html"> + <imagedata fileref="&imagepath;firewall-custom-service.&imageext;" format="PNG" align="center"/> + </imageobject> + <textobject> + <phrase>Custom services section</phrase> + </textobject> + </mediaobject> + </figure> + </para> + + + </sect3> + + <sect3 id="firewall-services-default"> + <title>Default services</title> + <para> + The third section lists the Default services. + </para> + <para> + <figure id="v200.firewall.033"> + <title>Default services</title> + <mediaobject> + <imageobject role="fo"> + <imagedata fileref="&imagepath;firewall-def-services.&imageext;" format="PNG" contentwidth="14cm"/> + </imageobject> + <imageobject role="html"> + <imagedata fileref="&imagepath;firewall-def-services.&imageext;" format="PNG" align="center"/> + </imageobject> + <textobject> + <phrase>Default services section</phrase> + </textobject> + </mediaobject> + </figure> + </para> + </sect3> </sect2> <sect2 id="firewall-servicegroups"> <title>Service Groups Administrative Web Page</title> <para> - Content to be written... + The IPCop Firewall is configured by using Services and/or + Service Groups. </para> + <para> + Service Groups give you the opportunity to combine several + Services into a Group. + After which you can create rule(s) which then combine all + Services in a single step. + </para> + <para> + A typical example is to create a DropNoLog Group which then + holds those Services that you know about and do not want to + fill up your Firewall log. + </para> </sect2> <sect2 id="firewall-addresses"> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <eob...@us...> - 2009-07-26 13:00:41
|
Revision: 3330 http://ipcop.svn.sourceforge.net/ipcop/?rev=3330&view=rev Author: eoberlander Date: 2009-07-26 13:00:34 +0000 (Sun, 26 Jul 2009) Log Message: ----------- Initial commit for Firewall Service Groups section. Modified Paths: -------------- IPCopDoc/trunk/en/admin/xml/firewall.xml Added Paths: ----------- IPCopDoc/trunk/en/admin/images/firewall-add-group.png IPCopDoc/trunk/en/admin/images/firewall-list-groups.png Added: IPCopDoc/trunk/en/admin/images/firewall-add-group.png =================================================================== (Binary files differ) Property changes on: IPCopDoc/trunk/en/admin/images/firewall-add-group.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: IPCopDoc/trunk/en/admin/images/firewall-list-groups.png =================================================================== (Binary files differ) Property changes on: IPCopDoc/trunk/en/admin/images/firewall-list-groups.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Modified: IPCopDoc/trunk/en/admin/xml/firewall.xml =================================================================== --- IPCopDoc/trunk/en/admin/xml/firewall.xml 2009-07-26 11:01:15 UTC (rev 3329) +++ IPCopDoc/trunk/en/admin/xml/firewall.xml 2009-07-26 13:00:34 UTC (rev 3330) @@ -655,8 +655,6 @@ </mediaobject> </figure> </para> - - </sect3> <sect3 id="firewall-services-default"> @@ -695,11 +693,65 @@ After which you can create rule(s) which then combine all Services in a single step. </para> - <para> - A typical example is to create a DropNoLog Group which then - holds those Services that you know about and do not want to - fill up your Firewall log. - </para> + <sect3 id="firewall-servicegroups-add"> + <title>Add service to Group</title> + <para> + In the first section you create a Service Group with a name and + add Default Services, or Custom Services if they have been + created. + Once a Group is created it can then be selected and added to + from the drop down menu. + </para> + <para> + <figure id="v200.firewall.041"> + <title>Service Groups</title> + <mediaobject> + <imageobject role="fo"> + <imagedata fileref="&imagepath;firewall-add-group.&imageext;" format="PNG" contentwidth="14cm"/> + </imageobject> + <imageobject role="html"> + <imagedata fileref="&imagepath;firewall-add-group.&imageext;" format="PNG" align="center"/> + </imageobject> + <textobject> + <phrase>Add service to group section</phrase> + </textobject> + </mediaobject> + </figure> + </para> + </sect3> + + <sect3 id="firewall-servicegroups-list"> + <title>Service Groups</title> + <para> + The second section lists the Service Groups you have created. + </para> + <para> + <figure id="v200.firewall.042"> + <title>Service Groups</title> + <mediaobject> + <imageobject role="fo"> + <imagedata fileref="&imagepath;firewall-list-groups.&imageext;" format="PNG" contentwidth="14cm"/> + </imageobject> + <imageobject role="html"> + <imagedata fileref="&imagepath;firewall-list-groups.&imageext;" format="PNG" align="center"/> + </imageobject> + <textobject> + <phrase>Service Group list</phrase> + </textobject> + </mediaobject> + </figure> + </para> + <para> + In the example above we have created a 'DropNoLog' + Group which holds some Services that we know about and do not + want to fill up our Firewall log with. + </para> + <para> + Dropping and not logging netbios-dgm (tcp+udp/138) and + netbios-ns (tcp+udp/137) avoids filling up the logs with + Netbios Broadcasts. + </para> + </sect3> </sect2> <sect2 id="firewall-addresses"> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <eob...@us...> - 2009-07-26 13:20:48
|
Revision: 3331 http://ipcop.svn.sourceforge.net/ipcop/?rev=3331&view=rev Author: eoberlander Date: 2009-07-26 13:20:40 +0000 (Sun, 26 Jul 2009) Log Message: ----------- Initial commit for IPTables section. Modified Paths: -------------- IPCopDoc/trunk/en/admin/xml/info.xml Added Paths: ----------- IPCopDoc/trunk/en/admin/images/iptables.png Added: IPCopDoc/trunk/en/admin/images/iptables.png =================================================================== (Binary files differ) Property changes on: IPCopDoc/trunk/en/admin/images/iptables.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Modified: IPCopDoc/trunk/en/admin/xml/info.xml =================================================================== --- IPCopDoc/trunk/en/admin/xml/info.xml 2009-07-26 13:00:34 UTC (rev 3330) +++ IPCopDoc/trunk/en/admin/xml/info.xml 2009-07-26 13:20:40 UTC (rev 3331) @@ -758,8 +758,33 @@ <sect2 id="status-iptables"> <title>IPTables Output</title> <para> - Content to be written... + This page shows output from IPTables, which can be filtered in + a number of ways. </para> + <para> + Select a filter from the drop down menu, or type the specific + name in the <guilabel>Chain</guilabel> field, and press the + <guibutton>Refresh</guibutton> button. + </para> + <para> + <screenshot> + <mediaobject> + <imageobject role="fo"> + <imagedata fileref="&imagepath;iptables.&imageext;" + format="PNG" + contentwidth="14cm"/> + </imageobject> + <imageobject role="html"> + <imagedata fileref="&imagepath;iptables.&imageext;" + format="PNG" + align="center"/> + </imageobject> + <textobject> + <phrase>IPTables screen output</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> </sect2> </sect1> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <eob...@us...> - 2009-07-28 18:11:00
|
Revision: 3343 http://ipcop.svn.sourceforge.net/ipcop/?rev=3343&view=rev Author: eoberlander Date: 2009-07-28 18:10:50 +0000 (Tue, 28 Jul 2009) Log Message: ----------- Initial content for Address section. Modified Paths: -------------- IPCopDoc/trunk/en/admin/images/firewall-add-address.png IPCopDoc/trunk/en/admin/images/firewall-def-networks.png IPCopDoc/trunk/en/admin/xml/firewall.xml Added Paths: ----------- IPCopDoc/trunk/en/admin/images/firewall-custom-address.png Modified: IPCopDoc/trunk/en/admin/images/firewall-add-address.png =================================================================== (Binary files differ) Added: IPCopDoc/trunk/en/admin/images/firewall-custom-address.png =================================================================== (Binary files differ) Property changes on: IPCopDoc/trunk/en/admin/images/firewall-custom-address.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Modified: IPCopDoc/trunk/en/admin/images/firewall-def-networks.png =================================================================== (Binary files differ) Modified: IPCopDoc/trunk/en/admin/xml/firewall.xml =================================================================== --- IPCopDoc/trunk/en/admin/xml/firewall.xml 2009-07-27 20:02:26 UTC (rev 3342) +++ IPCopDoc/trunk/en/admin/xml/firewall.xml 2009-07-28 18:10:50 UTC (rev 3343) @@ -520,7 +520,7 @@ <title>Add</title> <para> Once you have entered all the information, - press the <guibutton>Add</guibutton>. + press the <guibutton>Add</guibutton> button. This will move the entry to the next section, and list it as enabled. </para> @@ -704,7 +704,7 @@ </para> <para> <figure id="v200.firewall.041"> - <title>Service Groups</title> + <title>Add service to Group</title> <mediaobject> <imageobject role="fo"> <imagedata fileref="&imagepath;firewall-add-group.&imageext;" format="PNG" contentwidth="14cm"/> @@ -755,10 +755,137 @@ </sect2> <sect2 id="firewall-addresses"> - <title>Addresses Administrative Web Page</title> + <title>Address Settings Administrative Web Page</title> <para> - Content to be written... + You can assign names to IP Addresses, IP Networks and MAC Addresses. </para> + <para> + The advantage of using names is that when you have to change an + internal server's IP Address, or exchange a network card + (with a different MAC), there is only one place that needs + modification, and you do not have to change multiple outgoing + rules, pinholes and portforwards. + </para> + <sect3 id="firewall-addresses-add"> + <title>Add address</title> + <para> + In the first section you link a name to an address. + </para> + <para> + <figure id="v200.firewall.051"> + <title>Add address</title> + <mediaobject> + <imageobject role="fo"> + <imagedata fileref="&imagepath;firewall-add-address.&imageext;" format="PNG" contentwidth="14cm"/> + </imageobject> + <imageobject role="html"> + <imagedata fileref="&imagepath;firewall-add-address.&imageext;" format="PNG" align="center"/> + </imageobject> + <textobject> + <phrase>Add address section</phrase> + </textobject> + </mediaobject> + </figure> + </para> + <formalpara> + <title>Name</title> + <para> + Enter a name. + </para> + </formalpara> + <formalpara> + <title>Addressformat</title> + <para> + Select IP or MAC from the drop down menu. + </para> + </formalpara> + <formalpara> + <title>Address</title> + <para> + Enter the address. + </para> + </formalpara> + <note> + <para> + MAC Addresses can only be used as source in rules, + not as destination. + </para> + </note> + <formalpara> + <title>Netmask (optional)</title> + <para> + If the netmask field is left empty when defining an IP Address, + the mask 255.255.255.255 will be used. + </para> + </formalpara> + <formalpara> + <title>Add</title> + <para> + Once you have entered all the information, + press the <guibutton>Add</guibutton> button. + This will move the entry to the next section. + </para> + </formalpara> + <formalpara> + <title>Reset</title> + <para> + Press the <guibutton>Reset</guibutton> button to revert + settings to their defaults. + </para> + </formalpara> + </sect3> + + <sect3 id="firewall-addresses-custom"> + <title>Custom addresses</title> + <para> + The second section contains a list of your custom addresses. + </para> + <para> + <figure id="v200.firewall.052"> + <title>Custom address list</title> + <mediaobject> + <imageobject role="fo"> + <imagedata fileref="&imagepath;firewall-custom-address.&imageext;" format="PNG" contentwidth="14cm"/> + </imageobject> + <imageobject role="html"> + <imagedata fileref="&imagepath;firewall-custom-address.&imageext;" format="PNG" align="center"/> + </imageobject> + <textobject> + <phrase>Custom address section</phrase> + </textobject> + </mediaobject> + </figure> + </para> + <para> + To delete an entry, click the + <emphasis>Trash Can</emphasis> icon. + To edit one, click the + <emphasis>Yellow Pencil</emphasis> icon. + </para> + </sect3> + + <sect3 id="firewall-addresses-networks"> + <title>Default networks</title> + <para> + The third section contains networking information. + </para> + <para> + <figure id="v200.firewall.053"> + <title>Default networks list</title> + <mediaobject> + <imageobject role="fo"> + <imagedata fileref="&imagepath;firewall-def-networks.&imageext;" format="PNG" contentwidth="14cm"/> + </imageobject> + <imageobject role="html"> + <imagedata fileref="&imagepath;firewall-def-networks.&imageext;" format="PNG" align="center"/> + </imageobject> + <textobject> + <phrase>Default networks section</phrase> + </textobject> + </mediaobject> + </figure> + </para> + </sect3> </sect2> <sect2 id="firewall-addressgroups"> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <eob...@us...> - 2009-07-29 13:25:42
|
Revision: 3349 http://ipcop.svn.sourceforge.net/ipcop/?rev=3349&view=rev Author: eoberlander Date: 2009-07-29 13:25:33 +0000 (Wed, 29 Jul 2009) Log Message: ----------- Initial content for Address Groups section. Modified Paths: -------------- IPCopDoc/trunk/en/admin/xml/firewall.xml Added Paths: ----------- IPCopDoc/trunk/en/admin/images/firewall-add-addressgroup.png IPCopDoc/trunk/en/admin/images/firewall-list-addressgroups.png Added: IPCopDoc/trunk/en/admin/images/firewall-add-addressgroup.png =================================================================== (Binary files differ) Property changes on: IPCopDoc/trunk/en/admin/images/firewall-add-addressgroup.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: IPCopDoc/trunk/en/admin/images/firewall-list-addressgroups.png =================================================================== (Binary files differ) Property changes on: IPCopDoc/trunk/en/admin/images/firewall-list-addressgroups.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Modified: IPCopDoc/trunk/en/admin/xml/firewall.xml =================================================================== --- IPCopDoc/trunk/en/admin/xml/firewall.xml 2009-07-29 11:47:59 UTC (rev 3348) +++ IPCopDoc/trunk/en/admin/xml/firewall.xml 2009-07-29 13:25:33 UTC (rev 3349) @@ -769,7 +769,7 @@ <sect3 id="firewall-addresses-add"> <title>Add address</title> <para> - In the first section you link a name to an address. + In the first section you give an Address or Network a Name. </para> <para> <figure id="v200.firewall.051"> @@ -891,8 +891,91 @@ <sect2 id="firewall-addressgroups"> <title>Address Groups Administrative Web Page</title> <para> - Content to be written... + Default addresses (i.e. Green Network, Blue Network, etc.) and + addressnames can be combined into groups. </para> + <para> + In an address Group you could combine the Green and Blue + Networks and then allow a specific service for this group + with one rule. + </para> + <sect3 id="firewall-addressgroups-add"> + <title>Add address to Group</title> + <para> + In the first section you create an Address Group with a name and + add Default Networks, or Custom Addresses if they have been + created. + Once a Group is created it can then be selected and added to + from the drop down menu. + </para> + <para> + <figure id="v200.firewall.061"> + <title>Add address to Group</title> + <mediaobject> + <imageobject role="fo"> + <imagedata fileref="&imagepath;firewall-add-addressgroup.&imageext;" format="PNG" contentwidth="14cm"/> + </imageobject> + <imageobject role="html"> + <imagedata fileref="&imagepath;firewall-add-addressgroup.&imageext;" format="PNG" align="center"/> + </imageobject> + <textobject> + <phrase>Add address to group section</phrase> + </textobject> + </mediaobject> + </figure> + </para> + <para> + You can also combine + <link linkend="firewall-addresses">Address names</link> + into a group. + For example if you have multiple computers in Blue, but + only want to create a pinhole for two specific laptops. + </para> + <note> + <para> + Groups cannot be used as destination in a portforward. + </para> + </note> + </sect3> + + <sect3 id="firewall-addressgroups-list"> + <title>Address Groups</title> + <para> + The second section lists the Address Groups you have created. + </para> + <para> + In the example below we have combined the Green and Blue + Networks into one Group called GreenBlue. + </para> + <para> + <figure id="v200.firewall.062"> + <title>Address Groups list</title> + <mediaobject> + <imageobject role="fo"> + <imagedata fileref="&imagepath;firewall-list-addressgroups.&imageext;" format="PNG" contentwidth="14cm"/> + </imageobject> + <imageobject role="html"> + <imagedata fileref="&imagepath;firewall-list-addressgroups.&imageext;" format="PNG" align="center"/> + </imageobject> + <textobject> + <phrase>Address Groups section</phrase> + </textobject> + </mediaobject> + </figure> + </para> + <para> + To delete an entry, click the + <emphasis>Trash Can</emphasis> icon. + To edit one, click the + <emphasis>Yellow Pencil</emphasis> icon. + </para> + <para> + To enable or disable an entry - click on the checkbox + for the particular address(es) you want to enable or disable. + The icon changes to an empty box when an address is disabled. + Click on the checkbox to enable it again. + </para> + </sect3> </sect2> <sect2 id="firewall-interfaces"> @@ -909,9 +992,14 @@ </para> </sect2> <!-- + <note> <para> Text </para> + </note> + <para> + Text + </para> <formalpara> <title>Title</title> <para> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <eob...@us...> - 2009-07-29 18:34:31
|
Revision: 3356 http://ipcop.svn.sourceforge.net/ipcop/?rev=3356&view=rev Author: eoberlander Date: 2009-07-29 18:34:23 +0000 (Wed, 29 Jul 2009) Log Message: ----------- Initial content for Interfaces section. Modified Paths: -------------- IPCopDoc/trunk/en/admin/images/firewall-add-iface.png IPCopDoc/trunk/en/admin/xml/firewall.xml Modified: IPCopDoc/trunk/en/admin/images/firewall-add-iface.png =================================================================== (Binary files differ) Modified: IPCopDoc/trunk/en/admin/xml/firewall.xml =================================================================== --- IPCopDoc/trunk/en/admin/xml/firewall.xml 2009-07-29 18:15:59 UTC (rev 3355) +++ IPCopDoc/trunk/en/admin/xml/firewall.xml 2009-07-29 18:34:23 UTC (rev 3356) @@ -981,8 +981,114 @@ <sect2 id="firewall-interfaces"> <title>Interfaces Administrative Web Page</title> <para> - Content to be written... + There are special cases where interfaces are present beyond + the standard Green, Blue, Orange and Red interfaces. + After assigning a name to such an interface it is possible + to create firewall rules for those interfaces. </para> + <note> + <para> + Custom Interfaces are only available if + 'Advanced Mode' + is enabled on the + <link linkend="firewall-settings">Firewall Settings</link> + page. + </para> + </note> + <sect3 id="firewall-interfaces-add"> + <title>Add interface</title> + <para> + In the first section you give an Interface a Name. + </para> + <para> + <figure id="v200.firewall.071"> + <title>Add interface</title> + <mediaobject> + <imageobject role="fo"> + <imagedata fileref="&imagepath;firewall-add-iface.&imageext;" format="PNG" contentwidth="14cm"/> + </imageobject> + <imageobject role="html"> + <imagedata fileref="&imagepath;firewall-add-iface.&imageext;" format="PNG" align="center"/> + </imageobject> + <textobject> + <phrase>Add interface section</phrase> + </textobject> + </mediaobject> + </figure> + </para> + <formalpara> + <title>Name</title> + <para> + The name for your interface. Avoid using commas. + </para> + </formalpara> + <formalpara> + <title>Interface</title> + <para> + In this field you are limited to using upper and lowercase + letters, numbers, and a : (for an alias). + </para> + </formalpara> + <formalpara> + <title>Add</title> + <para> + Once you have entered all the information, + press the <guibutton>Add</guibutton> button. + This will move the entry to the next section. + </para> + </formalpara> + <formalpara> + <title>Reset</title> + <para> + Press the <guibutton>Reset</guibutton> button to revert + settings to their defaults. + </para> + </formalpara> + <note> + <para> + You will still need to assign drivers and IP + addresses manually. + </para> + </note> + </sect3> + + <sect3 id="firewall-interfaces-custom"> + <title>Custom interfaces</title> + <para> + Any custom interfaces you have created are listed in the + second section. + </para> + <para> + To delete a custom interface click the + <emphasis>Trash Can</emphasis> icon. + To edit one, click the + <emphasis>Yellow Pencil</emphasis> icon. + </para> + </sect3> + + <sect3 id="firewall-interfaces-list"> + <title>Default interface</title> + <para> + The default interfaces on your IPCop are shown in the + third section. + </para> + <para> + <figure id="v200.firewall.073"> + <title>Default interfaces</title> + <mediaobject> + <imageobject role="fo"> + <imagedata fileref="&imagepath;firewall-def-ifaces.&imageext;" format="PNG" contentwidth="14cm"/> + </imageobject> + <imageobject role="html"> + <imagedata fileref="&imagepath;firewall-def-ifaces.&imageext;" format="PNG" align="center"/> + </imageobject> + <textobject> + <phrase>Default interfaces section</phrase> + </textobject> + </mediaobject> + </figure> + </para> + </sect3> </sect2> <sect2 id="firewall-fwrules"> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |