IPCop Firewall

(Replying to myself...I know bad form.)

On Mon, 2012-04-23 at 00:44 -0400, Kanwar Ranbir Sandhu wrote:
> So, how the shit do I fix this?  Can I do a HD install and convert it to
> a flash install after wards?

I just found this:

/usr/local/sbin/installflash.sh

I looked through it.  It doesn't appear to do much, but then I don't
know what's involved in a flash install for the 2.0 series.

From what I can see in /etc/rc.d/rc.sysinit, the existence of /etc/FLASH
will kick off a series of events that tune the system for running on
flash based storage.

Would I need to do anything else, or is running the script enough? 

Regards,

Ranbir
-- 
Kanwar Ranbir Sandhu
Linux 3.3.2-1.fc16.x86_64 x86_64 GNU/Linux 
01:01:39 up 16:05, 5 users, load average: 1.69, 0.94, 0.42

Same boat. No problems installing "HD" mode on the Intel SSD though. 

- Jonathan

On Apr 22, 2012, at 9:44 PM, "Kanwar Ranbir Sandhu" <m3freak@...> wrote:

> Hi Everyone,
> 
> I've tried doing a flash install of ipcop 2.0.3 to a 32 GB compact flash
> drive and in a KVM using a 32 GB LVM as the "HD".  Although the install
> appears to complete without issue, the system NEVER boots.  All I get is
> "boot error".
> 
> I'd keep trying, but failure 16 taught me there's better things to do in
> life.  :P
> 
> So, how the shit do I fix this?  Can I do a HD install and convert it to
> a flash install after wards?
> 
> Regards,
> 
> Ranbir
> -- 
> Kanwar Ranbir Sandhu
> Linux 3.3.2-1.fc16.x86_64 x86_64 GNU/Linux 
> 00:44:12 up 15:48, 5 users, load average: 0.00, 0.01, 0.16 
> 
> ------------------------------------------------------------------------------
> For Developers, A Lot Can Happen In A Second.
> Boundary is the first to Know...and Tell You.
> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> http://p.sf.net/sfu/Boundary-d2dvs2
> _______________________________________________
> IPCop-user mailing list
> IPCop-user@...
> https://lists.sourceforge.net/lists/listinfo/ipcop-user

Do a normal install, login, run 'installflash.sh'.  I think that's all I 
did and I have a flash install running on a 16GB compact flash in an 
NTA-3500.

Jim


Jonathan Mergy wrote:
> Same boat. No problems installing "HD" mode on the Intel SSD though.
>
> - Jonathan
>
> On Apr 22, 2012, at 9:44 PM, "Kanwar Ranbir Sandhu"<m3freak@...>  wrote:
>
>    
>> Hi Everyone,
>>
>> I've tried doing a flash install of ipcop 2.0.3 to a 32 GB compact flash
>> drive and in a KVM using a 32 GB LVM as the "HD".  Although the install
>> appears to complete without issue, the system NEVER boots.  All I get is
>> "boot error".
>>
>> I'd keep trying, but failure 16 taught me there's better things to do in
>> life.  :P
>>
>> So, how the shit do I fix this?  Can I do a HD install and convert it to
>> a flash install after wards?
>>
>> Regards,
>>
>> Ranbir
>> -- 
>> Kanwar Ranbir Sandhu
>> Linux 3.3.2-1.fc16.x86_64 x86_64 GNU/Linux
>> 00:44:12 up 15:48, 5 users, load average: 0.00, 0.01, 0.16
>>
>> ------------------------------------------------------------------------------
>> For Developers, A Lot Can Happen In A Second.
>> Boundary is the first to Know...and Tell You.
>> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
>> http://p.sf.net/sfu/Boundary-d2dvs2
>> _______________________________________________
>> IPCop-user mailing list
>> IPCop-user@...
>> https://lists.sourceforge.net/lists/listinfo/ipcop-user
>>      
>
> ------------------------------------------------------------------------------
> For Developers, A Lot Can Happen In A Second.
> Boundary is the first to Know...and Tell You.
> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> http://p.sf.net/sfu/Boundary-d2dvs2
> _______________________________________________
> IPCop-user mailing list
> IPCop-user@...
> https://lists.sourceforge.net/lists/listinfo/ipcop-user
>
>    

-- 
----------------------------------------------------------------------------
Words to live by for all of us http://medjugorje.hr/en/

    The motto for the Office of Homeland Insecurity should be changed to
                     "Omnia sed Realis Officia"

On Sun, 2012-04-22 at 23:22 -0700, Jim Jowski wrote:
> Do a normal install, login, run 'installflash.sh'.  I think that's all I 
> did and I have a flash install running on a 16GB compact flash in an 
> NTA-3500.

When I did that, I got a bunch of errors about missing files and
directories.  They were all related to files/dirs in /var/log.

I'm guessing the installflash.sh script won't complete correctly until
ipcop does its first log rotation.

I should try forcing a rotation and THEN run the installflash.sh script.

Regards,

Ranbir

-- 
Kanwar Ranbir Sandhu
Linux 3.3.2-1.fc16.x86_64 x86_64 GNU/Linux 
10:13:26 up 1 day, 1:17, 5 users, load average: 0.00, 0.04, 0.09

On Mon, 2012-04-23 at 10:13 -0400, Kanwar Ranbir Sandhu wrote:
> I should try forcing a rotation and THEN run the installflash.sh script.

I poked around a bit on the HD based ipcop 2.0.4 box I have had running
for the last four to five days.  Some of the dirs the installflash.sh
dir is looking for do not exist.  For example, there is
no /var/log_compressed dir.

Here are the relevant lines from the script (wrapped):

tar -czf /var/log_compressed/log.tgz
--exclude=/var/log/cache/* /var/log/*

tar -czf /var/log_compressed/spool.tgz -C /var/spool cron

Does /var/log_compressed get created eventually, or can I run the script
and ignore the errors?

Regards,

Ranbir
-- 
Kanwar Ranbir Sandhu
Linux 3.3.2-1.fc16.x86_64 x86_64 GNU/Linux 
10:51:13 up 1 day, 1:55, 5 users, load average: 0.00, 0.01, 0.05

use with dd.exe it's good for IPCop usb boot.
...
...
.......................................
kyawzwathant@...

5c151ded9d436d83dcca631251fb90dd




On Mon, Apr 23, 2012 at 9:21 PM, Kanwar Ranbir Sandhu <
m3freak@...> wrote:

> On Mon, 2012-04-23 at 10:13 -0400, Kanwar Ranbir Sandhu wrote:
> > I should try forcing a rotation and THEN run the installflash.sh script.
>
> I poked around a bit on the HD based ipcop 2.0.4 box I have had running
> for the last four to five days.  Some of the dirs the installflash.sh
> dir is looking for do not exist.  For example, there is
> no /var/log_compressed dir.
>
> Here are the relevant lines from the script (wrapped):
>
> tar -czf /var/log_compressed/log.tgz
> --exclude=/var/log/cache/* /var/log/*
>
> tar -czf /var/log_compressed/spool.tgz -C /var/spool cron
>
> Does /var/log_compressed get created eventually, or can I run the script
> and ignore the errors?
>
> Regards,
>
> Ranbir
> --
> Kanwar Ranbir Sandhu
> Linux 3.3.2-1.fc16.x86_64 x86_64 GNU/Linux
> 10:51:13 up 1 day, 1:55, 5 users, load average: 0.00, 0.01, 0.05
>
>
>
>
> ------------------------------------------------------------------------------
> For Developers, A Lot Can Happen In A Second.
> Boundary is the first to Know...and Tell You.
> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> http://p.sf.net/sfu/Boundary-d2dvs2
> _______________________________________________
> IPCop-user mailing list
> IPCop-user@...
> https://lists.sourceforge.net/lists/listinfo/ipcop-user
>

Kanwar Ranbir Sandhu wrote:
> On Mon, 2012-04-23 at 10:13 -0400, Kanwar Ranbir Sandhu wrote:
>    
>> I should try forcing a rotation and THEN run the installflash.sh script.
>>      
> I poked around a bit on the HD based ipcop 2.0.4 box I have had running
> for the last four to five days.  Some of the dirs the installflash.sh
> dir is looking for do not exist.  For example, there is
> no /var/log_compressed dir.
>
> Here are the relevant lines from the script (wrapped):
>
> tar -czf /var/log_compressed/log.tgz
> --exclude=/var/log/cache/* /var/log/*
>
> tar -czf /var/log_compressed/spool.tgz -C /var/spool cron
>
> Does /var/log_compressed get created eventually, or can I run the script
> and ignore the errors?
>
> Regards,
>
> Ranbir
>    
Run the script.  I ran it right after the install and reboot.

Jim

-- 
----------------------------------------------------------------------------
Words to live by for all of us http://medjugorje.hr/en/

    The motto for the Office of Homeland Insecurity should be changed to
                     "Omnia sed Realis Officia"

On Mon, 2012-04-23 at 08:46 -0700, Jim Jowski wrote:
    
> Run the script.  I ran it right after the install and reboot.

Booting the now "flashized" install (2.0.3) generates a number of
errors:

Decompressing Flash ... rm: cannot remove '/var/log': Device or resource
busy
tar (child): /var/log_compressed/spool.tgz: Cannot open: No such file or
directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
Rotating logs ... error: stat of /var/log/messages failed: No such file
or directory

Regards,

Ranbir
-- 
Kanwar Ranbir Sandhu
Linux 3.3.2-1.fc16.x86_64 x86_64 GNU/Linux 
11:53:54 up 1 day, 2:57, 5 users, load average: 0.04, 0.13, 0.10

Anyone planning on running ipcop with a flash install should look at the 
version 1.4 installation manual, section C.  It talks about the why and 
how to do this.  I think a reinstall using this as a guide will fix most 
problems.

Jim

-- 
----------------------------------------------------------------------------
Words to live by for all of us http://medjugorje.hr/en/

    The motto for the Office of Homeland Insecurity should be changed to
                     "Omnia sed Realis Officia"

Jim Jowski wrote:
> Anyone planning on running ipcop with a flash install should look at the
> version 1.4 installation manual, section C.  It talks about the why and
> how to do this.  I think a reinstall using this as a guide will fix most
> problems.
>
> Jim
>
  But it's apples and oranges. To make a flash install for 1.4 you use 
mkflash on a running hd install to spit out images from 512MB to 4GB and 
then image them to flash drives external to the running system. It does 
NOT work the same way in 2.x.x which ideally the choice is made during 
install. The installflash in the system does not appear to be complete 
at a a glance, correct me if I am wrong. In a HD install, root is small 
and /var/log is big, in a flash install, root is big to fill out unused 
space and /var/log_compressed is usually quite small as is the /boot 
partition. I do not see where the script renames /var/log to 
/var/log_compressed much less resizes anything.
-- 
Dave Studeman
http:/www.raqcop.com

On Tue, 2012-04-24 at 05:02 -0700, David W Studeman wrote:
>   But it's apples and oranges. To make a flash install for 1.4 you use 
> mkflash on a running hd install to spit out images from 512MB to 4GB and 
> then image them to flash drives external to the running system. It does 
> NOT work the same way in 2.x.x which ideally the choice is made during 
> install.

Yes, completely true.

> The installflash in the system does not appear to be complete 
> at a a glance, correct me if I am wrong. In a HD install, root is small 
> and /var/log is big, in a flash install, root is big to fill out unused 
> space and /var/log_compressed is usually quite small as is the /boot 
> partition. I do not see where the script renames /var/log to 
> /var/log_compressed much less resizes anything.

The flash install in 2.0.3 is completely broken.  It wouldn't boot on a
VIA EPIA 5000 (which worked fine for ipcop 1.4 series), and it wouldn't
boot as a KVM.  Running the flash install script on a HD install doesn't
work either.

I'd be interested to hear if anyone has managed to get a 2.0.3 system
running from the start as a flash install, without any errors.

Regards,

Ranbir
-- 
Kanwar Ranbir Sandhu
Linux 3.3.2-1.fc16.x86_64 x86_64 GNU/Linux 
08:29:04 up 1 day, 23:33, 3 users, load average: 0.02, 0.05, 0.05

On 2012-04-24 14:29, Kanwar Ranbir Sandhu wrote:

> I'd be interested to hear if anyone has managed to get a 2.0.3 system
> running from the start as a flash install, without any errors.

No errors and no problems.


Olaf

On Tue, 24 Apr 2012, Kanwar Ranbir Sandhu wrote:

> On Tue, 2012-04-24 at 05:02 -0700, David W Studeman wrote:
>>   But it's apples and oranges. To make a flash install for 1.4 you use
>> mkflash on a running hd install to spit out images from 512MB to 4GB and
>> then image them to flash drives external to the running system. It does
>> NOT work the same way in 2.x.x which ideally the choice is made during
>> install.
>
> Yes, completely true.
>
>> The installflash in the system does not appear to be complete
>> at a a glance, correct me if I am wrong. In a HD install, root is small
>> and /var/log is big, in a flash install, root is big to fill out unused
>> space and /var/log_compressed is usually quite small as is the /boot
>> partition. I do not see where the script renames /var/log to
>> /var/log_compressed much less resizes anything.
>
> The flash install in 2.0.3 is completely broken.  It wouldn't boot on a
> VIA EPIA 5000 (which worked fine for ipcop 1.4 series), and it wouldn't
> boot as a KVM.  Running the flash install script on a HD install doesn't
> work either.
>
> I'd be interested to hear if anyone has managed to get a 2.0.3 system
> running from the start as a flash install, without any errors.

The old flash install method as mentioned above no longer works. The new 
way to do it is to PXE boot the install process on the target device and 
choose flash install during the install. You must set up DHCPD to give the 
target an address, a "next server" which has the PXE linux kernel image 
available via tftp and then make the ipcop-2.0.3.tar.gz file available via 
http/ftp. This means that you must have a system on your network that is a 
dhcp server, tftp server and web server.

Mike Beirne 
beirne@...

On Tue, 2012-04-24 at 08:11 -0500, Michael G. Beirne wrote:
> The old flash install method as mentioned above no longer works. The new 
> way to do it is to PXE boot the install process on the target device and 
> choose flash install during the install. You must set up DHCPD to give the 
> target an address, a "next server" which has the PXE linux kernel image 
> available via tftp and then make the ipcop-2.0.3.tar.gz file available via 
> http/ftp. This means that you must have a system on your network that is a 
> dhcp server, tftp server and web server.

Ok, easy enough.  Does that mean doing a flash install from a USB key is
not possible?  All of my failed flash installs have been from a USB key.

Regards,

Ranbir
-- 
Kanwar Ranbir Sandhu
Linux 3.3.2-1.fc16.x86_64 x86_64 GNU/Linux 
09:31:38 up 2 days, 35 min, 3 users, load average: 0.00, 0.01, 0.05

On Tue, 2012-04-24 at 15:08 +0200, Olaf wrote:
> On 2012-04-24 14:29, Kanwar Ranbir Sandhu wrote:
> 
> > I'd be interested to hear if anyone has managed to get a 2.0.3 system
> > running from the start as a flash install, without any errors.
> 
> No errors and no problems.

Ok, that gives me hope.  I have to say though, I KNOW I'm not doing
anything wrong during the install.

Thanks for the reply!

Regards,

Ranbir
-- 
Kanwar Ranbir Sandhu
Linux 3.3.2-1.fc16.x86_64 x86_64 GNU/Linux 
09:35:04 up 2 days, 39 min, 3 users, load average: 0.00, 0.01, 0.05

On Tuesday 24 April 2012 14:11:08 Michael G. Beirne wrote:

> The old flash install method as mentioned above no longer works. The new
> way to do it is to PXE boot the install process on the target device and
> choose flash install during the install. You must set up DHCPD to give the
> target an address, a "next server" which has the PXE linux kernel image
> available via tftp and then make the ipcop-2.0.3.tar.gz file available via
> http/ftp. This means that you must have a system on your network that is a
> dhcp server, tftp server and web server.
>
> Mike Beirne
> beirne@...
>
Hi,
 that is quite a big ask for the average Joe NOT using this in a commercial 
environment,but to protect his family network with something small, green, 
fast and reliable. Especially if the family stuff is windoze based
-- 
TTFN
   Caparo.

On Tue, 2012-04-24 at 14:39 +0100, Caparo wrote:
> >
> Hi,
>  that is quite a big ask for the average Joe NOT using this in a commercial 
> environment,but to protect his family network with something small, green, 
> fast and reliable. Especially if the family stuff is windoze based

I'm having a hard time believing this, too.  Luckily for me, I can
accommodate this at home (I have the knowledge and skills).

Maybe there's been a misunderstanding.  If there hasn't, the
documentation should be updated to clearly state all flash installs MUST
be done over PXE.

Regards,

Ranbir

-- 
Kanwar Ranbir Sandhu
Linux 3.3.2-1.fc16.x86_64 x86_64 GNU/Linux 
10:11:27 up 2 days, 1:15, 3 users, load average: 0.02, 0.06, 0.05

----- Mail original -----
> De: "Kanwar Ranbir Sandhu" <m3freak@...>
> À: ipcop-user@...
> Envoyé: Mardi 24 Avril 2012 16:11:32
> Objet: Re: [IPCop-user] 2.0.3 flash install doesn't boot
> 
> On Tue, 2012-04-24 at 14:39 +0100, Caparo wrote:
> > >
> > Hi,
> >  that is quite a big ask for the average Joe NOT using this in a
> >  commercial environment,but to protect his family network with something small, green,
> > fast and reliable. Especially if the family stuff is windoze based
> 
> I'm having a hard time believing this, too.  Luckily for me, I can
> accommodate this at home (I have the knowledge and skills).
> 
> Maybe there's been a misunderstanding.  If there hasn't, the
> documentation should be updated to clearly state all flash installs
> MUST be done over PXE.
> 
> Regards,
> 
> Ranbir
> 
There is no reason flash install MUST be done over PXE.
The reason PXE work is that the easiest way for us developer to test the install so it is the most tested way to install.

Independently of the method to install (cd/pxe/usb), result should be the same.

A bug may have slip on usb install.
Or a bios may play some bad trick (change the letter/add a device before the disk) when an usb key is detected.

Gilles

On Tue, 2012-04-24 at 08:11 -0500, Michael G. Beirne wrote:
> The old flash install method as mentioned above no longer works. The
> new 
> way to do it is to PXE boot the install process on the target device
> and 
> choose flash install during the install. You must set up DHCPD to give
> the 
> target an address, a "next server" which has the PXE linux kernel
> image 
> available via tftp and then make the ipcop-2.0.3.tar.gz file available
> via 
> http/ftp. This means that you must have a system on your network that
> is a 
> dhcp server, tftp server and web server. 

Where do I get the "ipcop-2.0.3.tar.gz" file from? I don't see it in the
list list of downloads here:

http://sourceforge.net/projects/ipcop/files/IPCop/IPCop%202.0.3/

Regards,

Ranbir
-- 
Kanwar Ranbir Sandhu
Linux 3.3.2-1.fc16.x86_64 x86_64 GNU/Linux 
17:27:51 up 2 days, 8:31, 5 users, load average: 0.05, 0.09, 0.06

Kanwar Ranbir Sandhu wrote:
> On Tue, 2012-04-24 at 08:11 -0500, Michael G. Beirne wrote:
>    
>> The old flash install method as mentioned above no longer works. The
>> new
>> way to do it is to PXE boot the install process on the target device
>> and
>> choose flash install during the install. You must set up DHCPD to give
>> the
>> target an address, a "next server" which has the PXE linux kernel
>> image
>> available via tftp and then make the ipcop-2.0.3.tar.gz file available
>> via
>> http/ftp. This means that you must have a system on your network that
>> is a
>> dhcp server, tftp server and web server.
>>      
> Where do I get the "ipcop-2.0.3.tar.gz" file from? I don't see it in the
> list list of downloads here:
>
> http://sourceforge.net/projects/ipcop/files/IPCop/IPCop%202.0.3/
>
> Regards,
>
> Ranbir
>    
When you burn the iso to a CD or mount the iso image; ipcop-2.0.3.tar.gz 
is at the root level.  If I'm not mistaken, ipcop-2.0.3.tar.gz is also 
in the USB img file.

What concerns me about this whole thread now is that some of us are 
thinking that a flash device is the target of the install and others may 
be thinking that the install is being done from a flash device.  I think 
these are two different animals.  I used the iso image to do the install 
to a compact flash.  When I first tried using a USB stick, the install 
program (setup) complained that there was no /dev/cdrom and wouldn't 
install.  The USB stick install issue is or should be a separate thread.

Jim

-- 
----------------------------------------------------------------------------
Words to live by for all of us http://medjugorje.hr/en/

    The motto for the Office of Homeland Insecurity should be changed to
                     "Omnia sed Realis Officia"

On Tue, 2012-04-24 at 14:51 -0700, Jim Jowski wrote:    
> When you burn the iso to a CD or mount the iso image; ipcop-2.0.3.tar.gz 
> is at the root level.  If I'm not mistaken, ipcop-2.0.3.tar.gz is also 
> in the USB img file.

Damn - I didn't think to look there.  Thanks for the pointer.

> What concerns me about this whole thread now is that some of us are 
> thinking that a flash device is the target of the install and others may 
> be thinking that the install is being done from a flash device.  I think 
> these are two different animals.  I used the iso image to do the install 
> to a compact flash.  When I first tried using a USB stick, the install 
> program (setup) complained that there was no /dev/cdrom and wouldn't 
> install.  The USB stick install issue is or should be a separate thread.

Just to clarify what I had problems with and what I meant when I started
this thread:

- wrote ipcop-2.0.3-install-usb-zip.i486.img to USB key
- plugged the USB key into my VIA EPIA 5000 based system in which the 
  "HD" is a 32 GB CF card
- started the install and chose "flash" instead of "hdd"
- install finished with no apparent problem
- rebooted the system, but the boot failed

So, I'm using a flash device to install from, and a flash device to
install to.   The thread title came from the fact that the "flash"
install option didn't work.

Regards,

Ranbir

Kanwar wrote:-

> - wrote ipcop-2.0.3-install-usb-zip.i486.img to USB key
> - plugged the USB key into my VIA EPIA 5000 based system in which the 
>   "HD" is a 32 GB CF card
> - started the install and chose "flash" instead of "hdd"
> - install finished with no apparent problem
> - rebooted the system, but the boot failed
> 
> So, I'm using a flash device to install from, and a flash device to
> install to.   The thread title came from the fact that the "flash"
> install option didn't work.

I have not tried this but I can see it leading to problems particularly if the 'boot from' device is removed as the drive letters may change on re-booting. If it was me I would try and reduce the complexity and change the 'boot from' media.

Interesting thread as I want to do this when time permits.

regards,
Brian

On Tue, 2012-04-24 at 09:35 -0400, Kanwar Ranbir Sandhu wrote:
> On Tue, 2012-04-24 at 15:08 +0200, Olaf wrote:
> > On 2012-04-24 14:29, Kanwar Ranbir Sandhu wrote:
> > 
> > > I'd be interested to hear if anyone has managed to get a 2.0.3 system
> > > running from the start as a flash install, without any errors.
> > 
> > No errors and no problems.
> 
> Ok, that gives me hope.  I have to say though, I KNOW I'm not doing
> anything wrong during the install.
> 

I give up.  Booting the target machine via PXE and choosing "flash" for
the install results in a system that refuses to boot.  I've tried on two
different physical boxes and several virtual (KVM), each type with
different install images - the flash install always gives me a "boot
error".  If I choose HDD, the systems boot without ANY problems.

How the shit are you guys doing your installs?  Is there a step-by-step
somewhere to convert a HD based install to flash?

Ranbir

Kanwar Ranbir Sandhu wrote:
> On Tue, 2012-04-24 at 09:35 -0400, Kanwar Ranbir Sandhu wrote:
>    
>> On Tue, 2012-04-24 at 15:08 +0200, Olaf wrote:
>>      
>>> On 2012-04-24 14:29, Kanwar Ranbir Sandhu wrote:
>>>
>>>        
>>>> I'd be interested to hear if anyone has managed to get a 2.0.3 system
>>>> running from the start as a flash install, without any errors.
>>>>          
>>> No errors and no problems.
>>>        
>> Ok, that gives me hope.  I have to say though, I KNOW I'm not doing
>> anything wrong during the install.
>>
>>      
> I give up.  Booting the target machine via PXE and choosing "flash" for
> the install results in a system that refuses to boot.  I've tried on two
> different physical boxes and several virtual (KVM), each type with
> different install images - the flash install always gives me a "boot
> error".  If I choose HDD, the systems boot without ANY problems.
>
> How the shit are you guys doing your installs?  Is there a step-by-step
> somewhere to convert a HD based install to flash?
>
> Ranbir
>
>    
Don't give up yet.  I think I now remember how I fixed the same problem 
you're having.  My first attempts used the 2.0.3-install.img that I put 
on a USB stick.  I got the same "Boot Error" message.  This is what I 
think I had to do to get it to work.  Take the compact flash you're 
trying to install to and wipe the partition table clean using 'dd'.  
Check the man page but it'll be similar to 'dd if=/dev/zero 
of=/dev/your_compact_flash bs=512'. After that you can use 'fdisk' to 
verify that you cleaned it. Then you do a new install with the CD 
version of 2.0.3.  (I did it this way and it worked.)  With any luck at 
all you'll get to install to a flash device and after you set it up; 
you'll reboot successfully.

Hope this helps,
Jim

-- 
----------------------------------------------------------------------------
Words to live by for all of us http://medjugorje.hr/en/

    The motto for the Office of Homeland Insecurity should be changed to
                     "Omnia sed Realis Officia"

On 05/04/2012 10:31 AM, Jim Jowski wrote:
>
>
> Kanwar Ranbir Sandhu wrote:
>> On Tue, 2012-04-24 at 09:35 -0400, Kanwar Ranbir Sandhu wrote:
>>
>>> On Tue, 2012-04-24 at 15:08 +0200, Olaf wrote:
>>>
>>>> On 2012-04-24 14:29, Kanwar Ranbir Sandhu wrote:
>>>>
>>>>
>>>>> I'd be interested to hear if anyone has managed to get a 2.0.3 system
>>>>> running from the start as a flash install, without any errors.
>>>>>
>>>> No errors and no problems.
>>>>
>>> Ok, that gives me hope.  I have to say though, I KNOW I'm not doing
>>> anything wrong during the install.
>>>
>>>
>> I give up.  Booting the target machine via PXE and choosing "flash" for
>> the install results in a system that refuses to boot.  I've tried on two
>> different physical boxes and several virtual (KVM), each type with
>> different install images - the flash install always gives me a "boot
>> error".  If I choose HDD, the systems boot without ANY problems.
>>
>> How the shit are you guys doing your installs?  Is there a step-by-step
>> somewhere to convert a HD based install to flash?
>>
>> Ranbir
>>
>>
> Don't give up yet.  I think I now remember how I fixed the same problem
> you're having.  My first attempts used the 2.0.3-install.img that I put
> on a USB stick.  I got the same "Boot Error" message.  This is what I
> think I had to do to get it to work.  Take the compact flash you're
> trying to install to and wipe the partition table clean using 'dd'.
> Check the man page but it'll be similar to 'dd if=/dev/zero
> of=/dev/your_compact_flash bs=512'. After that you can use 'fdisk' to
> verify that you cleaned it. Then you do a new install with the CD
> version of 2.0.3.  (I did it this way and it worked.)  With any luck at
> all you'll get to install to a flash device and after you set it up;
> you'll reboot successfully.
>
> Hope this helps,
> Jim
>

It seems to me that the problem happens when using PXE boot with a flash 
install. It'd be interesting to see though if wiping the first sector on 
the drive (MBR and partition table) somehow remedies the problem.

-- 
-Eric 'shubes'

g.esp@... wrote:
>
>
> ----- Mail original -----
>> De: "Kanwar Ranbir Sandhu"<m3freak@...>
>> À: ipcop-user@...
>> Envoyé: Mardi 24 Avril 2012 16:11:32
>> Objet: Re: [IPCop-user] 2.0.3 flash install doesn't boot
>>
>> On Tue, 2012-04-24 at 14:39 +0100, Caparo wrote:
>>>>
>>> Hi,
>>>   that is quite a big ask for the average Joe NOT using this in a
>>>   commercial environment,but to protect his family network with something small, green,
>>> fast and reliable. Especially if the family stuff is windoze based
>>
>> I'm having a hard time believing this, too.  Luckily for me, I can
>> accommodate this at home (I have the knowledge and skills).
>>
>> Maybe there's been a misunderstanding.  If there hasn't, the
>> documentation should be updated to clearly state all flash installs
>> MUST be done over PXE.
>>
>> Regards,
>>
>> Ranbir
>>
> There is no reason flash install MUST be done over PXE.
> The reason PXE work is that the easiest way for us developer to test the install so it is the most tested way to install.
>
> Independently of the method to install (cd/pxe/usb), result should be the same.
>
> A bug may have slip on usb install.
> Or a bios may play some bad trick (change the letter/add a device before the disk) when an usb key is detected.
>
> Gilles

I was going to say that some of us used flash installs a plenty and 
never used PXE. To clarify some of the myths propagated here in this 
thread, you can do a flash install on any install whether using flash or 
spinning drives, cd keyboard and mouse to install etc using any install 
method. Of course you, Gilles know that some of us using strange semi-pc 
hardware cannot use pxe nor any conventional method to get IPCop onto it 
directly. Yep, the biosless headless x86 Cobalts.

  Fortunately, IPCop when installing, writes the partition name in the 
fstab, not drive letter. This makes it rather trivial to use VMWare or 
Virtual Box to install directly to a flash or other drive connected by 
usb to the flash drive and have it boot since it goes by label, not 
drive letter node (sda,sdb etc). Once in the actual machine, rerun setup 
for the network and go. Usb backups can be easily used on future 
VMWare/Virtual Box installs. A fresh install with a usb backup key takes 
about 20 seconds. Want flash raid? No problem! Use two usb slaved drives 
with VMWare/Virtual box and choose raid, this choice is made before the 
choice of flash during install.

For those that do not know, raid in IPCop is raid 1 mirrored.
-- 
Dave Studeman
http:/www.raqcop.com

On Fri, 2012-05-04 at 19:31 -0700, David W Studeman wrote:
> I was going to say that some of us used flash installs a plenty and 
> never used PXE. To clarify some of the myths propagated here in this 
> thread, you can do a flash install on any install whether using flash or 
> spinning drives, cd keyboard and mouse to install etc using any install 
> method. Of course you, 

The last time I tried a PXE boot flash type install, I actually
installed to a HD. I got the same "boot error" message.

>   Fortunately, IPCop when installing, writes the partition name in the 
> fstab, not drive letter. This makes it rather trivial to use VMWare or 
> Virtual Box to install directly to a flash or other drive connected by 
> usb to the flash drive and have it boot since it goes by label, not 
> drive letter node (sda,sdb etc). Once in the actual machine, rerun setup 
> for the network and go. Usb backups can be easily used on future 
> VMWare/Virtual Box installs. A fresh install with a usb backup key takes 
> about 20 seconds.

I tried that too - same error.  I know, I must be stupid.  :(

FYI: I've also compared checksums, which were fine.  I was hoping my
copy of ipcop was just corrupt and that corruption was the source of my
problems.  It would have certainly been easier to understand.

> Want flash raid? No problem! Use two usb slaved drives 
> with VMWare/Virtual box and choose raid, this choice is made before the 
> choice of flash during install.
> 
> For those that do not know, raid in IPCop is raid 1 mirrored.

I was wondering if ipcop supported RAID.  That's some good info.

Regards,

Ranbir
-- 
Kanwar Ranbir Sandhu
Linux 3.3.2-1.fc16.x86_64 x86_64 GNU/Linux 
09:17:33 up 11 days, 10:23, 3 users, load average: 0.02, 0.22, 0.49

On Fri, 2012-05-04 at 10:31 -0700, Jim Jowski wrote:    
> Don't give up yet.  I think I now remember how I fixed the same problem 
> you're having.  My first attempts used the 2.0.3-install.img that I put 
> on a USB stick.  I got the same "Boot Error" message.  This is what I 
> think I had to do to get it to work.  Take the compact flash you're 
> trying to install to and wipe the partition table clean using 'dd'.  
> Check the man page but it'll be similar to 'dd if=/dev/zero 
> of=/dev/your_compact_flash bs=512'. After that you can use 'fdisk' to 
> verify that you cleaned it. Then you do a new install with the CD 
> version of 2.0.3.  (I did it this way and it worked.)  With any luck at 
> all you'll get to install to a flash device and after you set it up; 
> you'll reboot successfully.

Thanks for the advice, but I've already tried the MBR wipe and it didn't
help! :(

However, I have good news: I finally got a flash install to boot!  I
used a virtual machine (KVM) and a brand new transcend 8 GB CF card as
the storage.  I booted the install from the latest ipcop ISO.

At the boot screen, I made one change.  Instead of just firing up the
install by hitting return, I used the "nodma" option.  I did the install
as usual by choosing "flash".  I also noticed the installation took
longer than normal.

I held my breath when I rebooted the KVM.  When I didn't see the error
and instead got the IPCop boot screen, I almost fell out of my chair.

I'd like to try another install with a brand new KVM to see if the nodma
option is really the key.  But, I'm too scared to wipe my now working
install.

I never thought I'd have so many problems getting ipcop 2.0 up and
running.  Thanks to everyone for your patience and help!

Regards,

Ranbir

-- 
Kanwar Ranbir Sandhu
Linux 3.3.2-1.fc16.x86_64 x86_64 GNU/Linux 
11:18:17 up 11 days, 12:24, 4 users, load average: 2.01, 0.76, 0.58

> Following up thread of same name (2012-05-06)
>
> I had the same problem installing from ATA CD to a USB flash (8Gb)
>
> I re-installed a harddisk and booted ok.
>
> I then reinstalled using the flash option and the system booted 
> without problems
>
> The USB flash storage was NOT new - I think I had installed either 
> CentOS or Endian on it before.
>
> Hope this helps
>
> D