ipcop-devel Mailing List for IPCop Firewall

On 24 September 2011 14:00, G.W. Haywood <ip...@ju...> wrote:
> Hi there,
>
> On Fri, 23 Sep 2011, Announcement mailinglist for the IPCop project. wrote:
>
>> ... IPCop v2.0.0 is released. ...
>
> laptop:/media/cdrom# ls -lrt
> total 46111
> -r--r--r-- 1 root root     1422 Sep 23 13:45 README.txt
> -r--r--r-- 1 root root 47188939 Sep 23 13:45 ipcop-2.0.0.tar.gz
> -r--r--r-- 1 root root    17992 Sep 23 13:45 COPYING
> dr-xr-xr-x 1 root root     2048 Sep 23 13:45 images
> dr-xr-xr-x 1 root root     2048 Sep 23 13:45 dosutils
> dr-xr-xr-x 1 root root     2048 Sep 23 13:45 doc
> dr-xr-xr-x 1 root root     2048 Sep 23 13:45 boot
> laptop:/media/cdrom# head README.txt
> IPCop - The Bad Packets Stop Here (2.0.0)
> ------------------------------------------
>
> Installation
> ------------
>
> Please read the IPCop Installation PDF before installing the firewall.
> This document is located in the \doc directory on the cdrom.  It will
> guide you through the installation process and will help you make the
> necessary decisions during the installation process.
> laptop:/media/cdrom# cd doc
> laptop:/media/cdrom/doc# ls -lrt
> total 8
> -r--r--r-- 1 root root 4485 Sep 23 13:45 README-netboot.i486
> -r--r--r-- 1 root root 3202 Sep 23 13:45 IPCop-2.0.0-packages-list.i486.txt
> laptop:/media/cdrom/doc#


I see that Olaf has recently changed the text in SVN to refer to the
online Installation Manual instead.

The Installation Manual is a 'work in progress', and needs a lot more
work. In particular, new screenshots are needed of the new network
install, and the alternative methods of installation need
documentation. I left these for other as I know little about them.

Eric

G'day Robert,

On Wednesday 28 September 2011 18:40:56 Robert Ladyman wrote:
 <snip>
>
> Glen, do you run multiple (i.e. more than just green+red) networks:
> I'd like to check the settings from a 1.4 box without having to rig
> one here. If so, could you forward me the contents of your /dhcp
> /ethernet, /red and possibly (if there are any others) /orange etc.?
>
  Have emailed you /var/ipcop/ files off-list.
Ta,
Glen

<snippity snip>
> Good one Robert, I will wait.  I've wasted most of today (Sunday here)
> making and trying to correct stupid errors.
>  The trusty v1.4.21 can stay in production for a bit longer
> BTW. A conversion from a v1.4 backup to something that v2.0 can accept
> is not going to be trivial as there is NOT a direct 1 to 1 translation
> of settings.  

Glen, do you run multiple (i.e. more than just green+red) networks: I'd like 
to check the settings from a 1.4 box without having to rig one here. If so, 
could you forward me the contents of your /dhcp /ethernet, /red and possibly 
(if there are any others) /orange etc.?

You should be able to:

scp -C -P 222 -r root@the-ip-address:/var/ipcop/dhcp/*  /some-local-dir



-- 
Robert Ladyman
File-Away Limited
3 Ralston Business Centre, Newtyle, Blairgowrie
Perthshire  PH12 8TL SCOTLAND
Tel: +44 (0) 1828 898 158
Mobile: +44 (0) 7732 771 649
http://www.file-away.co.uk

============================================
Registered Office: 32 Church Street, Newtyle, Blairgowrie
Perthshire, PH12 8TZ SCOTLAND
Registered in Scotland, Company Number SC222086

> On Sunday 25 September 2011 20:46:20 Robert Ladyman wrote:
> > I'm not proposing from backup to 2.0, but from existing 1.4 settings
> > to 2.0, which will be a LOT easier.
> 
> That's it, Robert. 1.4 settings that can be read into a v2.0 install
> would be magic.  My understanding is that once a v2.0 box is
> configured, then the backup/restore functions will work as intended - I
> hope. :-)
> G.

Progress report:-

Currently, the scripts (not finished all the settings yet) I have are working 
with a local copy of 1.4 /var/ipcop/* files and a local copy of 2.0 
/var/ipcop/*. For instance:-

python   faconvert.py  -f  ../1point4/   -t   ../2point0/ 

uses the 1.4 settings from (-f)  directory "1point4" and updates the settings 
files in (-t) "2point0"

you can copy the IPCOP settings files from the old and new machines by:

scp -r -P 222 root@someipaddress:/var/ipcop/*  /some/local/dir

and with ... -P 8022 for version 2 boxes (to a different directory, of 
course).

This is quite handy as you can preserve settings on a central box, but it's 
perhaps not as easy as restoring from a backup. I suspect that you could:-

* Copy a set of default version 2 files to your 1.4 box
* Run the script
* Copy off the version 2 files to a virtual machine running version 2
* Use that virtual machine to create a (V2) backup
* Install using that (V2) backup

The issue that might be a sticking point is the embedding of MAC addresses and 
card types in the /var/ipcop/ethernet/ settings which might not match your new 
machine. I'll have a think about that: perhaps a switch for 'going to be using 
this hardware' or not or you might have to set up a vanilla version 2 box and 
then copy over the files (that way, the vanilla install will have the correct 
hardware configuration).

I have not tried this python script with a Windows machine yet: you would need 
to have python installed for it to work. On linux it's a no-brainer (and 
probably on Macs, too).

Alternatively, you can run the python code on the old (1.4) box against a copy 
of the new settings files for version 2 that you've copied to it, for update, 
as 1.4 has python on board. The existing 1.4 files will be untouched. I cannot 
find python on the 2.0 box - I assume it's not there (is that so?).

Regards,

-- 
Robert Ladyman
File-Away Limited
3 Ralston Business Centre, Newtyle, Blairgowrie
Perthshire  PH12 8TL SCOTLAND
Tel: +44 (0) 1828 898 158
Mobile: +44 (0) 7732 771 649
http://www.file-away.co.uk

============================================
Registered Office: 32 Church Street, Newtyle, Blairgowrie
Perthshire, PH12 8TZ SCOTLAND
Registered in Scotland, Company Number SC222086

Feature Requests item #3414215, was opened at 2011-09-26 23:44
Message generated for change (Tracker Item Submitted) made by sebastiann
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428519&aid=3414215&group_id=40604

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: Next release
Status: Open
Priority: 5
Private: No
Submitted By: sebastian nielsen (sebastiann)
Assigned to: Nobody/Anonymous (nobody)
Summary: Option to disallow IpCop to use "upstream proxy" for its own

Initial Comment:
A problem I have noticed with ipcop is that if I specify a upstream proxy in IpCop proxy gui, Ipcop will also use that proxy for its own services, for example DynDNS and updates. Sometimes this is not desirable, for example if the upstream proxy is supposed for only them behind ipcop, not ipcop itself.

A suggestion is one of these:

1: Provide a checkbox: "IpCop also needs to use this upstream proxy", if checked, ipcop will use the upstream proxy specified, if unchecked, ipcop will not use a upstream proxy at all.
2: Provide 2 similar sections containing the boxes for "upstream proxy", "upstream proxy username" and "upstream proxy password", one section called "Upstream proxy for users behind IpCop" and one section called "Upstream proxy for IpCop itself".


For the now, I have to grep to find all script files containing references to upstream proxy settings and comment out the whole sections that apply upstream proxy settings for when ipcop itself does things over the internet.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428519&aid=3414215&group_id=40604

Hi!

> I've had firewalls with over 50 rules for port forwarding (about
> 10 port forwards for 5+ machines). If you then include access
> restrictions for each of those you easily get 100s per firewall.

As for access restrictions, you can create an address group (Firewall -> Address
Groups) of standard addresses and custom addresses (Firewall -> Addresses) and
use this address group in every port forwarding rule.
Too you can copy every rule which will preset the rule creator for a new rule
with the values of the copied rule.

Achim

Due to massive and repeated spamming of the ticketing system on 
SourceForge, which SF still does not have any effective measures 
against, the ticketing system is 'off' and will not be taking any new 
tickets.


I'm gonna start looking for alternatives elsewehere for bug tracking. 
Stay tuned.


Olaf

On Sunday 25 September 2011 20:46:20 Robert Ladyman wrote:

> I'm not proposing from backup to 2.0, but from existing 1.4 settings
> to 2.0, which will be a LOT easier.

That's it, Robert. 1.4 settings that can be read into a v2.0 install 
would be magic.  My understanding is that once a v2.0 box is 
configured, then the backup/restore functions will work as intended - I 
hope. :-)
G.

> On Sunday 25 September 2011 19:48:59 Robert Ladyman wrote:
> <big snip>
> 
> > I've a few to do as well, but I'll have a look at writing a
> > conversion script if you can wait a day or two.
> 
> Good one Robert, I will wait.  I've wasted most of today (Sunday here)
> making and trying to correct stupid errors.
>  The trusty v1.4.21 can stay in production for a bit longer
> BTW. A conversion from a v1.4 backup to something that v2.0 can accept
> is not going to be trivial as there is NOT a direct 1 to 1 translation
> of settings.  Here's hoping you can do it.
> Thanks in antic,
> Glen
> 
I'm not proposing from backup to 2.0, but from existing 1.4 settings to 2.0, 
which will be a LOT easier. 


-- 
Robert Ladyman
File-Away Limited
3 Ralston Business Centre, Newtyle, Blairgowrie
Perthshire  PH12 8TL SCOTLAND
Tel: +44 (0) 1828 898 158
Mobile: +44 (0) 7732 771 649
http://www.file-away.co.uk

============================================
Registered Office: 32 Church Street, Newtyle, Blairgowrie
Perthshire, PH12 8TZ SCOTLAND
Registered in Scotland, Company Number SC222086

On Sunday 25 September 2011 19:48:59 Robert Ladyman wrote:
<big snip>
> I've a few to do as well, but I'll have a look at writing a
> conversion script if you can wait a day or two.

Good one Robert, I will wait.  I've wasted most of today (Sunday here) 
making and trying to correct stupid errors.
 The trusty v1.4.21 can stay in production for a bit longer
BTW. A conversion from a v1.4 backup to something that v2.0 can accept 
is not going to be trivial as there is NOT a direct 1 to 1 translation 
of settings.  Here's hoping you can do it.
Thanks in antic,
Glen

> On Sun, Sep 25, 2011 at 09:33:29AM +0100, Steve wrote:
> > Cant be that hard to print them and re enter ?
> 
> May be not hard, but time consuming, boring, and very likely to
> introduce mistakes.
> 
> I've had firewalls with over 50 rules for port forwarding (about
> 10 port forwards for 5+ machines). If you then include access
> restrictions for each of those you easily get 100s per firewall.
> 
> We look after about 15 firewalls, so that is potentially 1000s of
> rules to enter. Entering those manually will mean mistakes.
> 
> Dealing with boring and time consuming data transformation is an
> excellant job for a computer. A simple sed or awk script should
> able to transform a comma separated file format.
> 

I've a few to do as well, but I'll have a look at writing a conversion script 
if you can wait a day or two.


-- 
Robert Ladyman
File-Away Limited
3 Ralston Business Centre, Newtyle, Blairgowrie
Perthshire  PH12 8TL SCOTLAND
Tel: +44 (0) 1828 898 158
Mobile: +44 (0) 7732 771 649
http://www.file-away.co.uk

============================================
Registered Office: 32 Church Street, Newtyle, Blairgowrie
Perthshire, PH12 8TZ SCOTLAND
Registered in Scotland, Company Number SC222086

 

Ah. So not a few rules for a handful of machines on a single ipcop then!

 

 

 

-------Original Message------- 

 

From: John Edwards 

Date: 25/09/2011 10:09:58 

To: Steve 

Cc: IPCOP devel 

Subject: Re: [IPCop-devel] Correct way to transfer V1.4 rules to V2.0? 

 

On Sun, Sep 25, 2011 at 09:33:29AM +0100, Steve wrote: 

> 

> Cant be that hard to print them and re enter ? 

 

May be not hard, but time consuming, boring, and very likely to 

introduce mistakes. 

 

I've had firewalls with over 50 rules for port forwarding (about 

10 port forwards for 5+ machines). If you then include access 

restrictions for each of those you easily get 100s per firewall. 

 

We look after about 15 firewalls, so that is potentially 1000s of 

rules to enter. Entering those manually will mean mistakes. 

 

Dealing with boring and time consuming data transformation is an 

excellent job for a computer. A simple sed or awk script should 

able to transform a comma separated file format. 

 

 

-- 

#---------------------------------------------------------# 

| John Edwards Email: jo...@co... | 

#---------------------------------------------------------# 

 

On Sun, Sep 25, 2011 at 09:33:29AM +0100, Steve wrote:
> 
> Cant be that hard to print them and re enter ?

May be not hard, but time consuming, boring, and very likely to
introduce mistakes.

I've had firewalls with over 50 rules for port forwarding (about
10 port forwards for 5+ machines). If you then include access
restrictions for each of those you easily get 100s per firewall.

We look after about 15 firewalls, so that is potentially 1000s of
rules to enter. Entering those manually will mean mistakes. 

Dealing with boring and time consuming data transformation is an
excellant job for a computer. A simple sed or awk script should
able to transform a comma separated file format.


-- 
#---------------------------------------------------------#
|    John Edwards   Email: jo...@co...    |
#---------------------------------------------------------#

On Sat, 24 Sep 2011 11:24:53 -0400
"ft...@mi..." <ft...@mi...> wrote:

> I've got a lot of rules on my V1.4 box that I'm not looking forward to 
> recreating on a V2.0 install.  Is there a good way to transfer rules to 
> a new V2.0 install?
> 
According to manual you should be able to make a backup onto either
floppy or USB and the use that at the beginning of the install process.
Only limitation is that your 2.0 must be installed on identical
hardware and platform.
http://www.ipcop.org/2.0.0/en/install/html/booting-restore.html

How much is restored though, I am not sure of.

-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael <at> rasmussen <dot> cc
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E
mir <at> datanom <dot> net
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C
mir <at> miras <dot> org
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917
--------------------------------------------------------------

Cant be that hard to print them and re enter ?

You will probably find some obsolete ones anyway. 

 

 

 

 

-------Original Message------- 

 

From: Glen Cunningham 

Date: 25/09/2011 09:25:44 

To: ipc...@li... 

Subject: Re: [IPCop-devel] Correct way to transfer V1.4 rules to V2.0? 

 

G'day "ftarz', 

 

On Sunday 25 September 2011 01:24:53 ft...@mi... wrote: 

> I've got a lot of rules on my V1.4 box that I'm not looking forward 

> to recreating on a V2.0 install. Is there a good way to transfer 

> rules to a new V2.0 install? 

> 

It does not look like you are going to be inundated with replies. For 

me the lack of a restore from V1.4 backup is a real show stopper. 

Manually recreating everthing is a right PITA particularly as there is 

not a direct v1.4 -> v2.0 correlation. 

 

Cheers and sympathy, 

Glen 

 

 

-----------------------------------------------------------------------------
 

All of the data generated in your IT infrastructure is seriously valuable. 

Why? It contains a definitive record of application performance, security 

threats, fraudulent activity, and more. Splunk takes this data and makes 

sense of it. IT sense. And common sense. 

http://p.sf.net/sfu/splunk-d2dcopy2 

_______________________________________________ 

IPCop-devel mailing list 

IPC...@li... 

https://lists.sourceforge.net/lists/listinfo/ipcop-devel 

 

G'day "ftarz',

On Sunday 25 September 2011 01:24:53 ft...@mi... wrote:
> I've got a lot of rules on my V1.4 box that I'm not looking forward
> to recreating on a V2.0 install.  Is there a good way to transfer
> rules to a new V2.0 install?
>
  It does not look like you are going to be inundated with replies.  For 
me the lack of a restore from V1.4 backup is a real show stopper.  
Manually recreating everthing is a right PITA particularly as there is 
not a direct v1.4 -> v2.0 correlation.
  
Cheers and sympathy,
Glen

I've got a lot of rules on my V1.4 box that I'm not looking forward to 
recreating on a V2.0 install.  Is there a good way to transfer rules to 
a new V2.0 install?

Hi there,

On Fri, 23 Sep 2011, Announcement mailinglist for the IPCop project. wrote:

> ... IPCop v2.0.0 is released. ...

laptop:/media/cdrom# ls -lrt
total 46111
-r--r--r-- 1 root root     1422 Sep 23 13:45 README.txt
-r--r--r-- 1 root root 47188939 Sep 23 13:45 ipcop-2.0.0.tar.gz
-r--r--r-- 1 root root    17992 Sep 23 13:45 COPYING
dr-xr-xr-x 1 root root     2048 Sep 23 13:45 images
dr-xr-xr-x 1 root root     2048 Sep 23 13:45 dosutils
dr-xr-xr-x 1 root root     2048 Sep 23 13:45 doc
dr-xr-xr-x 1 root root     2048 Sep 23 13:45 boot
laptop:/media/cdrom# head README.txt
IPCop - The Bad Packets Stop Here (2.0.0)
------------------------------------------

Installation
------------

Please read the IPCop Installation PDF before installing the firewall.
This document is located in the \doc directory on the cdrom.  It will
guide you through the installation process and will help you make the
necessary decisions during the installation process.
laptop:/media/cdrom# cd doc
laptop:/media/cdrom/doc# ls -lrt
total 8
-r--r--r-- 1 root root 4485 Sep 23 13:45 README-netboot.i486
-r--r--r-- 1 root root 3202 Sep 23 13:45 IPCop-2.0.0-packages-list.i486.txt
laptop:/media/cdrom/doc#


--

73,
Ged.

Congratulations!!

GREAT JOB!

Thanks guys

 

 

 

 

-------Original Message------- 

 

From: Olaf 

Date: 23/09/2011 15:12:10 

To: ipc...@li...; IPCop devel; IPCop users 

Subject: [IPCop-devel] [2.0] release of IPCop v2.0.0 

 

Dear all, 

 

 

I'll make this as short as possible. IPCop v2.0.0 is released. 

Thanks to those who have given valuable input during the development cycle. 

Special thanks to Mario, never giving up and always prepared to run yet 

another test, I guess by now he is able to install IPCop blind-folded, 

also special thanks to Tom, always giving feedback and ideas. 

 

 

Enjoy... 

 

Olaf 

 

=================================== 

 

IPCop 2.0.0 is released 

 

v2.0.0 can be installed using the installation images or as an update 

from version 1.9.20. 

 

For those familiar with earlier IPCop versions, IPCop v2 is different. 

Read the manuals to get an overview. 

Online English installation manual: 

http://www.ipcop.org/2.0.0/en/install/html 

Online German installation manual: 

http://www.ipcop.org/2.0.0/de/install/html 

The installation manuals are 'work in progress' and not yet complete. 

 

Online English admin manual: http://www.ipcop.org/2.0.0/en/admin/html 

Online German admin manual: http://www.ipcop.org/2.0.0/de/admin/html 

 

 

Noteworthy: 

- the GUI uses 8443 instead of 445. 

- SSH uses 8022 instead of 222. 

- access to IPCop and to the Internet from internal networks (aka 

Green, Blue, Orange) is very much different. Spend some time with the 

various options you will find under "Firewall Settings" and the online 

admin manual. 

- Danish, Dutch, English, French, German, Greek, Italian, 

Latino-American Spanish, 

Russian, Spanish and Turkish translations are complete, 

other languages are work in progress. 

- backups from 1.4-series can not be used. 

- addons made for the 1.4-series will not work. 

 

 

Updates 

add370e02b70f3b65c5f6c3dffa64a97 ipcop-2.0.0-update.i486.tgz.gpg 

 

Installation 

0128c026dc00d3039355880683fad9bf ipcop-2.0.0-install-cd.i486.ISO 

7ed2fb9e034a866057489d9debd94f17 ipcop-2.0.0-install-netboot.i486.tgz 

e51cd651a7ee92c5f83ee4161784b3fe ipcop-2.0.0-install-usb-fdd.i486.img.gz 

d94985ebf9ce839c2a44c51e6e078871 ipcop-2.0.0-install-usb-hdd.i486.img.gz 

386098f63ddf05dfeab0dc1380e3aba6 ipcop-2.0.0-install-usb-zip.i486.img.gz 

 

 

-----------------------------------------------------------------------------
 

All of the data generated in your IT infrastructure is seriously valuable. 

Why? It contains a definitive record of application performance, security 

threats, fraudulent activity, and more. Splunk takes this data and makes 

sense of it. IT sense. And common sense. 

http://p.sf.net/sfu/splunk-d2dcopy2 

_______________________________________________ 

IPCop-devel mailing list 

IPC...@li... 

https://lists.sourceforge.net/lists/listinfo/ipcop-devel 

 

On Fri, Sep 23, 2011 at 7:11 AM, Olaf <mai...@ba...> wrote:

>
> I'll make this as short as possible. IPCop v2.0.0 is released.
> Thanks to those who have given valuable input during the development cycle.
> Special thanks to Mario, never giving up and always prepared to run yet
> another test, I guess by now he is able to install IPCop blind-folded,
> also special thanks to Tom, always giving feedback and ideas.
>
>
It's awesome. Congratulation!

Thanks.
Bao

>
> Enjoy...
>
> Olaf
>
> ===================================
>
> IPCop 2.0.0 is released
>
> v2.0.0 can be installed using the installation images or as an update
> from version 1.9.20.
>
> For those familiar with earlier IPCop versions, IPCop v2 is different.
> Read the manuals to get an overview.
> Online English installation manual:
> http://www.ipcop.org/2.0.0/en/install/html
> Online German installation manual:
> http://www.ipcop.org/2.0.0/de/install/html
> The installation manuals are 'work in progress' and not yet complete.
>
> Online English admin manual: http://www.ipcop.org/2.0.0/en/admin/html
> Online German admin manual: http://www.ipcop.org/2.0.0/de/admin/html
>
>
> Noteworthy:
> - the GUI uses 8443 instead of 445.
> - SSH uses 8022 instead of 222.
> - access to IPCop and to the internet from internal networks (aka
> Green, Blue, Orange) is very much different. Spend some time with the
> various options you will find under "Firewall Settings" and the online
> admin manual.
> - Danish, Dutch, English, French, German, Greek, Italian,
> Latino-American Spanish,
> Russian, Spanish and Turkish translations are complete,
> other languages are work in progress.
> - backups from 1.4-series can not be used.
> - addons made for the 1.4-series will not work.
>
>
> Updates
> add370e02b70f3b65c5f6c3dffa64a97  ipcop-2.0.0-update.i486.tgz.gpg
>
> Installation
> 0128c026dc00d3039355880683fad9bf  ipcop-2.0.0-install-cd.i486.iso
> 7ed2fb9e034a866057489d9debd94f17  ipcop-2.0.0-install-netboot.i486.tgz
> e51cd651a7ee92c5f83ee4161784b3fe  ipcop-2.0.0-install-usb-fdd.i486.img.gz
> d94985ebf9ce839c2a44c51e6e078871  ipcop-2.0.0-install-usb-hdd.i486.img.gz
> 386098f63ddf05dfeab0dc1380e3aba6  ipcop-2.0.0-install-usb-zip.i486.img.gz
>
>
>
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2dcopy2
> _______________________________________________
> IPCop-devel mailing list
> IPC...@li...
> https://lists.sourceforge.net/lists/listinfo/ipcop-devel
>



-- 
Best Regards.
Bao C. Ha
Hacom - Embedded Systems and Appliances
http://www.hacom.net
voice: (714) 564-9932

Dear all,


I'll make this as short as possible. IPCop v2.0.0 is released.
Thanks to those who have given valuable input during the development cycle.
Special thanks to Mario, never giving up and always prepared to run yet 
another test, I guess by now he is able to install IPCop blind-folded, 
also special thanks to Tom, always giving feedback and ideas.


Enjoy...

Olaf

===================================

IPCop 2.0.0 is released

v2.0.0 can be installed using the installation images or as an update 
from version 1.9.20.

For those familiar with earlier IPCop versions, IPCop v2 is different.
Read the manuals to get an overview.
Online English installation manual: 
http://www.ipcop.org/2.0.0/en/install/html
Online German installation manual: 
http://www.ipcop.org/2.0.0/de/install/html
The installation manuals are 'work in progress' and not yet complete.

Online English admin manual: http://www.ipcop.org/2.0.0/en/admin/html
Online German admin manual: http://www.ipcop.org/2.0.0/de/admin/html


Noteworthy:
- the GUI uses 8443 instead of 445.
- SSH uses 8022 instead of 222.
- access to IPCop and to the internet from internal networks (aka
Green, Blue, Orange) is very much different. Spend some time with the
various options you will find under "Firewall Settings" and the online
admin manual.
- Danish, Dutch, English, French, German, Greek, Italian, 
Latino-American Spanish,
Russian, Spanish and Turkish translations are complete,
other languages are work in progress.
- backups from 1.4-series can not be used.
- addons made for the 1.4-series will not work.


Updates
add370e02b70f3b65c5f6c3dffa64a97  ipcop-2.0.0-update.i486.tgz.gpg

Installation
0128c026dc00d3039355880683fad9bf  ipcop-2.0.0-install-cd.i486.iso
7ed2fb9e034a866057489d9debd94f17  ipcop-2.0.0-install-netboot.i486.tgz
e51cd651a7ee92c5f83ee4161784b3fe  ipcop-2.0.0-install-usb-fdd.i486.img.gz
d94985ebf9ce839c2a44c51e6e078871  ipcop-2.0.0-install-usb-hdd.i486.img.gz
386098f63ddf05dfeab0dc1380e3aba6  ipcop-2.0.0-install-usb-zip.i486.img.gz

Hi there,

On Thu, 22 Sep 2011 Marcelo Zunino wrote:

> Sometimes already fixed words or expressions return to unfixed
> condition without notice. In fact there has been also occurred on some
> expressions translated since very long time ago.
>
> Things like that are not so serious ...

With the greatest respect, I disagree.  They are a very useful
indication of poor project management.

> To avoid boredom here we could set up a google group or elsewhere to
> continue the topic there if applied.

It would be very useful to see the activity on either the users or
development list.  Probably the development list would be better.

--

73,
Ged.

Many thanks for all the hard work (to all who have been working on it).

RJL


> On 2011-08-21 22:02, Olaf Westrik wrote:
> > Still missing for 2.0.0 is an update facility for IPsec configuration to
> > smoothen the migration from 1.4 to 2.0.0.
> > Other than that only bugfixes (should there be any in 1.9.20), critical
> > updates and language modifications. Anything else will have to wait
> > until after 2.0.0 is released.
> 
> after about 4 weeks of testing -rc1 (v1.9.20), I will release IPCop
> v2.0.0 tomorrow (23 September 2011).
> 
> There have been some modifications since -rc1, but IMHO those have all
> seen enough successful tests so I will skip -rc2.
> 
> 
> Olaf
> 
> ---------------------------------------------------------------------------
> --- All the data continuously generated in your IT infrastructure contains
>  a definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
> _______________________________________________
> IPCop-devel mailing list
> IPC...@li...
> https://lists.sourceforge.net/lists/listinfo/ipcop-devel
> 

-- 
Robert Ladyman
File-Away Limited
3 Ralston Business Centre, Newtyle, Blairgowrie
Perthshire  PH12 8TL SCOTLAND
Tel: +44 (0) 1828 898 158
Mobile: +44 (0) 7732 771 649
http://www.file-away.co.uk

============================================
Registered Office: 32 Church Street, Newtyle, Blairgowrie
Perthshire, PH12 8TZ SCOTLAND
Registered in Scotland, Company Number SC222086

On 2011-08-21 22:02, Olaf Westrik wrote:


> Still missing for 2.0.0 is an update facility for IPsec configuration to
> smoothen the migration from 1.4 to 2.0.0.
> Other than that only bugfixes (should there be any in 1.9.20), critical
> updates and language modifications. Anything else will have to wait
> until after 2.0.0 is released.

after about 4 weeks of testing -rc1 (v1.9.20), I will release IPCop 
v2.0.0 tomorrow (23 September 2011).

There have been some modifications since -rc1, but IMHO those have all 
seen enough successful tests so I will skip -rc2.


Olaf