Re: Correct way to transfer V1.4 rules to V2.0?

Michael Rasmussen <[email protected]>
Newsgroups gmane.comp.security.ipcop.devel
Message-ID <[email protected]>
On Sat, 24 Sep 2011 11:24:53 -0400
"[email protected]" <[email protected]> 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
--------------------------------------------------------------

------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/ipcop-devel
signature.asc (application/pgp-signature, 198 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk5+68QACgkQVErYVePoCReF6ACfb21rYhT/MY7t3+VS8WxodtdI
iVQAnRh7kbuvTrSoV3a6ScCvwVqMH2sf
=EfWi
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.