ipcop-devel Mailing List for IPCop Firewall

Craig Robinson said the following on 29/07/2005 21:54:

> Any ideas/suggestions on this project will be appericated.

I've played around with linux on my xbox and was thinking of using it as 
a server but never got round to it.

They're fairly quiet so how a bout combining the work with running IPCop 
from compact flash?

Good luck!  Keep us up to date.

N

Although way out of my league you may be able to pinch some drivers
and kernel mods from the group at
http://www.xbox-linux.org/wiki/Main_Page

On 7/29/05, Craig Robinson <cn...@gm...> wrote:
> I am about to undertake a new project that consists of installing
> IPCop on a XBOX.  Linux installations on XBOX are "easy" and have been
> accomplished using a cross-installation with the PC.  The idea would
> be to use the XBOX, along with a USB NIC as an IPCOP machine.  This
> would allow the cost of an IPCop machine to be less than $200.00 for
> new parts.  The XBOX comes stock with one NIC on the motherboard, and
> 4 USB ports with a different type connector than the usual (the cable
> to convert is $6.00 or you can solder one in).
>=20
> There are a few reasons I am mailing the DEV community for IPCop.  Has
> this been tried before?  The only problem I see with install IPCop is
> the inital installation where IPCop scans your computer for NIC's.
> Also I'm not sure if the kernel supports USB NIC's.  There is also an
> issue of having the XBOX kernel patched.  All of these issues seem
> like they could be easily overcome with some input by the IPCop
> Development Team.
>=20
> Any ideas/suggestions on this project will be appericated.
>=20
> Craig Robinson
> cn...@gm...
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&opclick
> _______________________________________________
> IPCop-devel mailing list
> IPC...@li...
> https://lists.sourceforge.net/lists/listinfo/ipcop-devel
>=20


--=20
Jay Smith
ja...@gm...

-------------------------------------------------
Menopause: When the stork that brings babies is shot by drunken hunters.

I am about to undertake a new project that consists of installing
IPCop on a XBOX.  Linux installations on XBOX are "easy" and have been
accomplished using a cross-installation with the PC.  The idea would
be to use the XBOX, along with a USB NIC as an IPCOP machine.  This
would allow the cost of an IPCop machine to be less than $200.00 for
new parts.  The XBOX comes stock with one NIC on the motherboard, and
4 USB ports with a different type connector than the usual (the cable
to convert is $6.00 or you can solder one in).

There are a few reasons I am mailing the DEV community for IPCop.  Has
this been tried before?  The only problem I see with install IPCop is
the inital installation where IPCop scans your computer for NIC's.=20
Also I'm not sure if the kernel supports USB NIC's.  There is also an
issue of having the XBOX kernel patched.  All of these issues seem
like they could be easily overcome with some input by the IPCop
Development Team.

Any ideas/suggestions on this project will be appericated.

Craig Robinson
cn...@gm...

Hi everyone,

I'm using serveral ods.org adresses and now that I switched to IPcop, I found that adding ods.org support is dead easy. Adding "ods.org" to /home/httpd/cgi-bin/ddns.cgi is a matter of 60 seconds. Please support ods.org for future releases.

Regards,

Frederik
__________________________________________________________
Mit WEB.DE FreePhone mit hoechster Qualitaet ab 0 Ct./Min.
weltweit telefonieren! http://freephone.web.de/?mc=021201

On Thu, 2005-07-28 at 12:32 +0100, Dave Roberts wrote:
> Can't find it from Google or on linuxfromscratch.org.  Has anyone got a
> url?  Or can somebody send it to me?

Try:

http://ipcop.ath.cx/

No idea who runs it, but it's a good place to find all your missing
downloads.

-- 
 Robert Kerr

On Thu, Jul 28, 2005 at 12:32:59PM +0100, Dave Roberts wrote:
> Can't find it from Google or on linuxfromscratch.org.  Has anyone got a
> url?  Or can somebody send it to me?

Try Google again:
	http://www.google.co.uk/search?hl=en&q=shadow-4.0.7-uClibc-1.patch&btnG=Google+Search&meta=

And you'll find that the first result is an archived email that says 
why the file was created (for new version of shadow) and gives you the 
contents of file:
	http://linuxfromscratch.org/pipermail/patches/2005-January/002001.html

Google also finds another couple of emails that noted that the file 
has been removed:
	http://www.mail-archive.com/pa...@li.../msg00212.html
	http://www.mail-archive.com/pa...@li.../msg00213.html


Maybe the lfs files in CVS HEAD should be updated to use the newer 
version of shadow (4.0.11) as this patch is no longer required:
	ftp://ftp.pld.org.pl/software/shadow/


-- 
#---------------------------------------------------------#
|    John Edwards   Email: jo...@co...    |
|                                                         |
| A. Because it breaks the logical sequence of discussion |
| Q. Why is top posting bad ?                             |
#---------------------------------------------------------#

Can't find it from Google or on linuxfromscratch.org.  Has anyone got a
url?  Or can somebody send it to me?

Thanks,

Dave

> Selon "E.Zierler" <zo...@st...>:
>
>> > Selon "E.Zierler" <zo...@st...>:
>> >
>> [...]
>> >>
>> >> Now I have this situation again and I would find it VERY VERY usefu=
l
>> to
>> >> have a little more detailed information where one has to jump in an=
d
>> >> change things in order to compile in a few extra modules which are
>> >> required on certain machines.
>> >>
>> >> This can be a very short document, in fact a list of files where
>> things
>> >> need to be changed. Does something like this exist or does anyone
>> think
>> >> he/she could create such a document?
>> >>
>> > the simple way is
>> > - compile the entire distrib without changes
>> > - add a lfs/my_script (look at the others, configure VER,
>> THISAPP,DL_FILE,
>> > DL_FROM,DIR_APP,TARGET,$(DL_FILE)_md5 and the way to compile)
>> > - add a call to this script in make.sh : ipcopmake my_script
>> > - ./make.sh build until your script work
>> > - look at log/$(my_script_TARGET) for the list of file result of the
>> > compilation
>> > - copy the list of files in src/ROOTFILES.i386 and comment with # th=
e
>> > files you
>> > don't want to include in the ISO
>> > - ./make.sh build again and the supplementary files are include in
>> your
>> > ISO
>> >
>> > I may be more elaborate if you need to hack the installer for a
>> specific
>> > hardware.
>> >
>> > Gilles
>>
>> Hi once again, with help of this short tips from Gilles I have managed
>> to
>> successfully compile my hardware specific drivers and build a working
>> ISO file. However, I need to EXCLUDE for instance the promise_sata
>> module
>> and according to your advice I am supposed to comment out everything
>> that
>> I don't want in src/ROOTFILES.i386. When I check I see that this file
>> is already commented out.
>>
>> #lib/modules/2.4.29/kernel/drivers/scsi/sata_promise.o.gz
>> #lib/modules/2.4.29-smp/kernel/drivers/scsi/sata_promise.o.gz
>>
>> Hmm, so all I need to figure out is how to prevent certain modules to
>> be checked while booting. I'd be thankful for any hints!
>>
>> Regards,
>>  Erwin
>>
> Sometime a higher level of directory is include.
> This is the case of lib/modules/2.4.29/kernel
>
> The exact solution is when everything is compilated to :
> ./make.sh shell
> cd /usr/src/linux
> make menuconfig and remove compilation of SATA_PROMISE
> make oldconfig to remove some menuconfig comments
> track changes between /usr/src/linux/.config and kernel.config.i386
> report the changes in kernel.config.i386-smp and kernel.config.installe=
r
> remove the line in ROOTFILES.i386 (for documentation purpose only)
> recompile linux so remover
> log/{linux-ipcop,linux-ipcop-smp,linux-installer}
> (or recompile everything)
>
> This is a bit painfull. I play this game sometime during this WE.

It is ;-) But I guess I will get that working eventually.

> It may work a shorter way by directly removing the file you don't want =
in
> lfs/linux (and/or under build/lib/modules/2.4.29), so those files will =
not
> be include.

The art is to remove the modules thta you do not want at the right time!
I seem to have a talent getting them on the ISO file everytime anyway ;-)

> Why do you want to remove sata_promise?

Because the orignal driver from Promise supports my controller fully i.e.
it recognizes the 'real' configuration of the raid system. the sata_promi=
se
module shows me sda and sdb instead of a single disk (sda) - so no mirror=
!
And I have this controller/driver running on other Linuxes with success.

> I will commit changes for kernel 2.4.31 tonight.

I just did a fresh download of the cvs tree and now I get an error I neve=
r
have seen before:

cd /build/ipcop/build/usr/src/openswan-1.0.9 && patch -Np1 <
/build/ipcop/build/usr/src/src/patches/openswan-1.0.1-plutoctl.patch
cd /build/ipcop/build/usr/src/openswan-1.0.9 && patch -Np1 <
/build/ipcop/build/usr/src/src/patches/openswan-1.0.6-numif.patch

Seems those files are indeed missing. Any clue?

> Gilles
>

TIA,
 Erwin

PS.: sorry for being a pain in ... ...

At 09:24 AM 7/25/2005 +0100, Supporting Role Office wrote:
>Hi,
>
>We are running IPCop 1.4.6 and it's working just great but recently we
>tried to make a floppy backup (for the first time) and computer just 
>locked up, there was no
>response at all. No ping, no keyboard - nothing. We just could RESET it -
>that was only way to start it again.
>
>Without backup on floppy it's working OK - no problems.
>
>So we tried with 1.4.5, 1.4.4, 1.4.2 - the same thing
>
>But with 1.3.0 everything is OK
>
>We checked everything with Knoppix. Floppy disk is working fine and also 
>there are no problems with mainboard under any other OS (distribution)
>
>
>Now we believe that the problem is with SiS 661FX/963 chipset because on 
>mainboard with Intel chipset everything is working fine.
>
>
>
>Do you know anything about SiS issue ?
>
>ShuttleX with FS56 mainboard (http://www.shuttlecomputer.de/eu/fs56.htm)
>256DDR RAM
>PIV 2,6GHz
>
>
>Any ideas ?

I would hold the SiS chipset strongly suspect.  I had numerous intermittant
problems on a SiS chipset based system that I tried to run IPCop on.  The
main problem was a locking up of the distro during the boot process while
detecting the IDE drives/partitions.  Turning the PC off completely and
letting it sit for a while let things work when I tried it later, but it
still was not reliable.  I think this problem was due to an IDE driver
incompatibility with the onboard IDE controller.

Specs:
http://support.mpccorp.com/apps/syscomp.asp?ID=34&Categ=34
Micron Millenia M54Li
http://www.tacktech.com/pub/manuals/m54li.doc
SiS 85C550X chipset.
SMC 665 Super I/O chip
prominent chip on motherboard: SiS 5501

Other IPCop/SiS chipset problems that people have reported include:

[ 1098510 ] ide=nodma causes install to hang when partitioning on SiS CS
https://sourceforge.net/tracker/index.php?func=detail&aid=1098510&group_id=4
0604&atid=428516

[ 973674 ] sis 600 ide chipset support
https://sourceforge.net/tracker/index.php?func=detail&aid=973674&group_id=40
604&atid=428516

I've also run into compatibility problems between a Geovision GV-900
security camera capture card running on an ASRock P4S61 
(SiS 661FX chipset) motherboard (Pentium 4 board).
http://www.asrock.com.tw/support/Download/dl_p4S61.htm  The problem I
encountered was whenever the GV-900 PCI board was installed in the
motherboard, the system either would not boot in ACPI mode, and when in
booted in APM mode, the system became very 'choppy', i.e. it'd run in short
bursts with painful slowness between the bursts.

Finally, a P4 2.6 ghz box is almost certainly overkill for IPCop and an old
x86 intel-chipset system would likely be easier to get working.

-hk

I am not still ready to publish a v1.4.7 in test and this will be delayed
until Wednesday or Thursday.

Still some more tests and works to be done before to call you for testing.

Once it will be published, I will give you a bit more than one week for
testing and if everything is ok, official v1.4.7 will be released in the
first week of august.
I had too to collect the short log of the changes since v1.4.6.

Gilles

----- Original Message ----- 
From: "Achim Weber" <dot...@gm...>
To: <ipc...@li...>
Sent: Monday, July 25, 2005 7:54 PM
Subject: Re: [IPCop-devel] Exclude 'addon-lang' from backup


> >> > My backup set is 460K. Far from 1440K floppy capacity. No danger from
> >> > some translation files.
> >> > But yes addon should take care of this if they add some 'big' things
> > into
> >> > /var/ipcop  (like ssquidGuard blacklist) !
> >>
> >> If the addon-lang files are included in backup and you do not install
> >> the same addons again, you will have laying around those trash files.
> >>
> >> Achim
> >>
> > Add-on removal could remove his files.
> > During uninstall, warn to make a backup again.
>
> Jep, Addon uninstall scripts have to remove those files.
>
> But imagine this scenario:
> - Install fresh IPCop#1
> - install some addons
> - make backup#1 (disk), addon-lang is included in backup
> - install IPcop#2 with backup#1, the addon-lang files are restored and
>   laying around
> - no install of addons on ipcop#2
>
> Those trash files will not hurt but its not neat in my eyes.
> /var/ipcop/langs is excluded too.
>
> if you say we include addon-lang, no problem for me.
>
> Achim
>
>
You are right addon-lang need to be exclude from backup.

Gilles

>> > My backup set is 460K. Far from 1440K floppy capacity. No danger from
>> > some translation files.
>> > But yes addon should take care of this if they add some 'big' things
> into
>> > /var/ipcop  (like ssquidGuard blacklist) !
>>
>> If the addon-lang files are included in backup and you do not install
>> the same addons again, you will have laying around those trash files.
>>
>> Achim
>>
> Add-on removal could remove his files.
> During uninstall, warn to make a backup again.

Jep, Addon uninstall scripts have to remove those files.

But imagine this scenario:
- Install fresh IPCop#1
- install some addons
- make backup#1 (disk), addon-lang is included in backup
- install IPcop#2 with backup#1, the addon-lang files are restored and
  laying around
- no install of addons on ipcop#2

Those trash files will not hurt but its not neat in my eyes.
/var/ipcop/langs is excluded too.

if you say we include addon-lang, no problem for me.

Achim

> My backup set is 460K. Far from 1440K floppy capacity. No danger from
> some translation files.
> But yes addon should take care of this if they add some 'big' things into
> /var/ipcop  (like ssquidGuard blacklist) !

If the addon-lang files are included in backup and you do not install
the same addons again, you will have laying around those trash files.

Achim

Hello,

A project 'ipcop-like', may be some info to exchange with 
the author.


http://www.cybcon.com/~coert/linux/siso/index.html



Franck

Selon "E.Zierler" <zo...@st...>:

> > Selon "E.Zierler" <zo...@st...>:
> >
> [...]
> >>
> >> Now I have this situation again and I would find it VERY VERY useful=
 to
> >> have a little more detailed information where one has to jump in and
> >> change things in order to compile in a few extra modules which are
> >> required on certain machines.
> >>
> >> This can be a very short document, in fact a list of files where thi=
ngs
> >> need to be changed. Does something like this exist or does anyone th=
ink
> >> he/she could create such a document?
> >>
> > the simple way is
> > - compile the entire distrib without changes
> > - add a lfs/my_script (look at the others, configure VER, THISAPP,DL_=
FILE,
> > DL_FROM,DIR_APP,TARGET,$(DL_FILE)_md5 and the way to compile)
> > - add a call to this script in make.sh : ipcopmake my_script
> > - ./make.sh build until your script work
> > - look at log/$(my_script_TARGET) for the list of file result of the
> > compilation
> > - copy the list of files in src/ROOTFILES.i386 and comment with # the
> > files you
> > don't want to include in the ISO
> > - ./make.sh build again and the supplementary files are include in yo=
ur
> > ISO
> >
> > I may be more elaborate if you need to hack the installer for a speci=
fic
> > hardware.
> >
> > Gilles
>
> Hi once again, with help of this short tips from Gilles I have managed =
to
> successfully compile my hardware specific drivers and build a working
> ISO file. However, I need to EXCLUDE for instance the promise_sata modu=
le
> and according to your advice I am supposed to comment out everything th=
at
> I don't want in src/ROOTFILES.i386. When I check I see that this file
> is already commented out.
>
> #lib/modules/2.4.29/kernel/drivers/scsi/sata_promise.o.gz
> #lib/modules/2.4.29-smp/kernel/drivers/scsi/sata_promise.o.gz
>
> Hmm, so all I need to figure out is how to prevent certain modules to
> be checked while booting. I'd be thankful for any hints!
>
> Regards,
>  Erwin
>
Sometime a higher level of directory is include.
This is the case of lib/modules/2.4.29/kernel

The exact solution is when everything is compilated to :
./make.sh shell
cd /usr/src/linux
make menuconfig and remove compilation of SATA_PROMISE
make oldconfig to remove some menuconfig comments
track changes between /usr/src/linux/.config and kernel.config.i386
report the changes in kernel.config.i386-smp and kernel.config.installer
remove the line in ROOTFILES.i386 (for documentation purpose only)
recompile linux so remover log/{linux-ipcop,linux-ipcop-smp,linux-install=
er}
(or recompile everything)

This is a bit painfull. I play this game sometime during this WE.

It may work a shorter way by directly removing the file you don't want in
lfs/linux (and/or under build/lib/modules/2.4.29), so those files will no=
t be
include.

Why do you want to remove sata_promise?

I will commit changes for kernel 2.4.31 tonight.

Gilles

Le Lundi 25 Juillet 2005 14:44, Achim Weber a =E9crit :
> I think the new dir /var/ipcop/addon-lang should be excluded from backup!?
>
> http://cvs.sourceforge.net/viewcvs.py/ipcop/ipcop/config/cfgroot/backup-e=
xc
>lude?rev=3D1.3.2.1&view=3Dmarkup
>
> Achim
>

My backup set is 460K. Far from 1440K floppy capacity. No danger from
some translation files.
But yes addon should take care of this if they add some 'big' things into
/var/ipcop  (like ssquidGuard blacklist) !



=46ranck

I think the new dir /var/ipcop/addon-lang should be excluded from backup!?

http://cvs.sourceforge.net/viewcvs.py/ipcop/ipcop/config/cfgroot/backup-exclude?rev=1.3.2.1&view=markup

Achim

> Selon "E.Zierler" <zo...@st...>:
>
[...]
>>
>> Now I have this situation again and I would find it VERY VERY useful t=
o
>> have a little more detailed information where one has to jump in and
>> change things in order to compile in a few extra modules which are
>> required on certain machines.
>>
>> This can be a very short document, in fact a list of files where thing=
s
>> need to be changed. Does something like this exist or does anyone thin=
k
>> he/she could create such a document?
>>
> the simple way is
> - compile the entire distrib without changes
> - add a lfs/my_script (look at the others, configure VER, THISAPP,DL_FI=
LE,
> DL_FROM,DIR_APP,TARGET,$(DL_FILE)_md5 and the way to compile)
> - add a call to this script in make.sh : ipcopmake my_script
> - ./make.sh build until your script work
> - look at log/$(my_script_TARGET) for the list of file result of the
> compilation
> - copy the list of files in src/ROOTFILES.i386 and comment with # the
> files you
> don't want to include in the ISO
> - ./make.sh build again and the supplementary files are include in your
> ISO
>
> I may be more elaborate if you need to hack the installer for a specifi=
c
> hardware.
>
> Gilles

Hi once again, with help of this short tips from Gilles I have managed to
successfully compile my hardware specific drivers and build a working
ISO file. However, I need to EXCLUDE for instance the promise_sata module
and according to your advice I am supposed to comment out everything that
I don't want in src/ROOTFILES.i386. When I check I see that this file
is already commented out.

#lib/modules/2.4.29/kernel/drivers/scsi/sata_promise.o.gz
#lib/modules/2.4.29-smp/kernel/drivers/scsi/sata_promise.o.gz

Hmm, so all I need to figure out is how to prevent certain modules to
be checked while booting. I'd be thankful for any hints!

Regards,
 Erwin

Hello,


> What about "badblocks" ?

we didn't try badblocks command yet - just fdformat but floppies are without 
bb (checked under W98)

>
>> I can do whatever I want with this floppy under any other OS.
>
> Does that include booting this Shuttle box with a Linux CD distibution
> like Knoppix, and using that to test the floppy drive with different
> disks ?

Yes - we tried with Knopix 3.9, fdformat was working, we also tried to put 
some data on disk and it was also ok.


Strange thing is that backup is working with IPCop 1.3 and not with 1.4.x

Bartosz

On Mon, Jul 25, 2005 at 10:36:42AM +0100, Bartosz Morawiec - Supporting Role Ltd. wrote:
> John Edwards wrote:
>> The email to ipcop-user has not arrived here yet, have you made
>> sure that you are subscribed to that mailing list ? If you're
>> not subscribed then you have to wait until a moderator OKs the
>> email (to stop spam).
>> 
>> 
>> I assume you are doing a floppy backup via the web interface.
>> If then the real work is done by program:
>> /usr/local/bin/ipcopbackup
>> 
>> First thing to do is to run this program from the command.
>> 
>> If it still freezes then grab the source code for that program
>> and look at what it does. Then run through each of the major step
>> independently, especially the system commands for "dd" and "tar"
>> which wipe and write to the floppy disk.
>> 
>> Running "badblocks /dev/fd0" will test the floppy disk for defects.
>> 
>> Usual suspects are a bad disk or bad drive.

> I've sent an email on 14.07.2005 and it's on the list already for more than 
> week. And i'm subscribed.

Yes, you're right. It was posted from a different email address so I 
didn't spot it:
	http://sourceforge.net/mailarchive/forum.php?thread_id=7729372&forum_id=4957


> The problem is that even so easy operation as fdformat is not working :( it 
> freezes on 22%  with many floppy discs and floppy drives, cables etc. but 
> just under ipcop.

What about "badblocks" ?


> I can do whatever I want with this floppy under any other OS.

Does that include booting this Shuttle box with a Linux CD distibution 
like Knoppix, and using that to test the floppy drive with different 
disks ?


ps. It's generally a good idea to copy the mailing list on follow-up 
emails, so that other people get the extra information and know 
if/when/what fixed the problem.


-- 
#---------------------------------------------------------#
|    John Edwards   Email: jo...@co...    |
|                                                         |
| A. Because it breaks the logical sequence of discussion |
| Q. Why is top posting bad ?                             |
#---------------------------------------------------------#

Selon John Edwards <jo...@co...>:

> On Mon, Jul 25, 2005 at 09:24:10AM +0100, Supporting Role Office wrote:
> > Hi,
> >
> > We are running IPCop 1.4.6 and it's working just great but recently w=
e
> > tried to make a floppy backup (for the first time) and computer just
> > locked up, there was no
> > response at all. No ping, no keyboard - nothing. We just could RESET =
it -
> > that was only way to start it again.
> >
> > Without backup on floppy it's working OK - no problems.
> >
> > So we tried with 1.4.5, 1.4.4, 1.4.2 - the same thing
> >
> > But with 1.3.0 everything is OK
> >
> > We checked everything with Knoppix. Floppy disk is working fine and a=
lso
> > there are no problems with mainboard under any other OS (distribution=
)
> >
> >
> > Now we believe that the problem is with SiS 661FX/963 chipset because=
 on
> > mainboard with Intel chipset everything is working fine.
> >
> >
> >
> > Do you know anything about SiS issue ?
> >
> > ShuttleX with FS56 mainboard (http://www.shuttlecomputer.de/eu/fs56.h=
tm)
> > 256DDR RAM
> > PIV 2,6GHz
> >
> >
> > Any ideas ?
> >
> > We are writing here because on IPCOP User list we've got no response,=
 so
> > maybe this is the first email about this kind of problem.
>
> The email to ipcop-user has not arrived here yet, have you made
> sure that you are subscribed to that mailing list ? If you're
> not subscribed then you have to wait until a moderator OKs the
> email (to stop spam).
>
>
> I assume you are doing a floppy backup via the web interface.
> If then the real work is done by program:
> 	/usr/local/bin/ipcopbackup
>
> First thing to do is to run this program from the command.
>
> If it still freezes then grab the source code for that program
> and look at what it does. Then run through each of the major step
> independently, especially the system commands for "dd" and "tar"
> which wipe and write to the floppy disk.
>
> Running "badblocks /dev/fd0" will test the floppy disk for defects.
>
> Usual suspects are a bad disk or bad drive.
>
>
I know one bad case where ipcopbackup hang.
When the compressed files size excess the floppy size, the program fail b=
ut it
does not stop the whole machine.

This may happen if there is to many files added in /var/ipcop.

Gilles

On Mon, Jul 25, 2005 at 09:24:10AM +0100, Supporting Role Office wrote:
> Hi,
> 
> We are running IPCop 1.4.6 and it's working just great but recently we
> tried to make a floppy backup (for the first time) and computer just 
> locked up, there was no
> response at all. No ping, no keyboard - nothing. We just could RESET it -
> that was only way to start it again.
> 
> Without backup on floppy it's working OK - no problems.
> 
> So we tried with 1.4.5, 1.4.4, 1.4.2 - the same thing
> 
> But with 1.3.0 everything is OK
> 
> We checked everything with Knoppix. Floppy disk is working fine and also 
> there are no problems with mainboard under any other OS (distribution)
> 
> 
> Now we believe that the problem is with SiS 661FX/963 chipset because on 
> mainboard with Intel chipset everything is working fine.
> 
> 
> 
> Do you know anything about SiS issue ?
> 
> ShuttleX with FS56 mainboard (http://www.shuttlecomputer.de/eu/fs56.htm)
> 256DDR RAM
> PIV 2,6GHz
> 
> 
> Any ideas ?
> 
> We are writing here because on IPCOP User list we've got no response, so 
> maybe this is the first email about this kind of problem.

The email to ipcop-user has not arrived here yet, have you made 
sure that you are subscribed to that mailing list ? If you're 
not subscribed then you have to wait until a moderator OKs the 
email (to stop spam).


I assume you are doing a floppy backup via the web interface.
If then the real work is done by program:
	/usr/local/bin/ipcopbackup

First thing to do is to run this program from the command.

If it still freezes then grab the source code for that program 
and look at what it does. Then run through each of the major step 
independently, especially the system commands for "dd" and "tar" 
which wipe and write to the floppy disk.

Running "badblocks /dev/fd0" will test the floppy disk for defects.

Usual suspects are a bad disk or bad drive.


-- 
#---------------------------------------------------------#
|    John Edwards   Email: jo...@co...    |
|                                                         |
| A. Because it breaks the logical sequence of discussion |
| Q. Why is top posting bad ?                             |
#---------------------------------------------------------#

Hi,

We are running IPCop 1.4.6 and it's working just great but recently we
tried to make a floppy backup (for the first time) and computer just 
locked up, there was no
response at all. No ping, no keyboard - nothing. We just could RESET it -
that was only way to start it again.

Without backup on floppy it's working OK - no problems.

So we tried with 1.4.5, 1.4.4, 1.4.2 - the same thing

But with 1.3.0 everything is OK

We checked everything with Knoppix. Floppy disk is working fine and also 
there are no problems with mainboard under any other OS (distribution)


Now we believe that the problem is with SiS 661FX/963 chipset because on 
mainboard with Intel chipset everything is working fine.



Do you know anything about SiS issue ?

ShuttleX with FS56 mainboard (http://www.shuttlecomputer.de/eu/fs56.htm)
256DDR RAM
PIV 2,6GHz


Any ideas ?

We are writing here because on IPCOP User list we've got no response, so 
maybe this is the first email about this kind of problem.



Greetings
Bart

Hi,

I wrote the linetest-plugin for automatic fallback if dsl/RED fails.

Is there a mechanism available in more recent 1.5.0er which replaces
(hopefully) my plugin?

--- info ---
linetest replaces /var/ipcop/ethernet/settings and some other files if a
line is down.

Very interesting if a company uses ipcop as firewall between their
intranet and the internet (directly connected via ethernet ->router...).
If this line drops linetest replaces the complete network-config and
enables a modem-dialup/isdn...
--- /info ---

any suggestions?


Regards,

Michael

www.alquanto.de

Le Samedi 23 Juillet 2005 17:37, DEast a =E9crit :
> I have added code to the ddns,cgi and setddns.pl to
> include a dynamic service named "enom".  I have
> attached the two files, in case you guys are
> interested in adding it to upcoming releases.
>
> Glad to help.  It's a great project.
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com


Ok, good, I will include your provider. But please, for everybody:

1) avoid sending windows text (CR/LF)
2) prefers a diff -p patch
3) patch against latest version from cvs !
4) and use a precise subject in your message ;)
5) or post an RFE, which is harder to get lost !!!

Thank you
=46ranck