ipcop-devel Mailing List for IPCop Firewall

Hi Gilles,
Gilles Espinasse schrieb:
> - open the resulting 2 files inside log_i486/03_ipcop/{Device-SerialPort,comgt}
> - change the prefix + by # or nothing for each file name in the list you want to
> include in iso
> - then replace 5.10.1 by PERLVER and i486-linux by MACHINE-linux inside the two
> files
> - copy the modified files in config/rootfiles/common with package name and no
> version number
> - rebuild the iso with the new files using again ./make.sh build
thank you very much! Very good explained in detail, and works great!
BTW. if you're interested here's a lfs for flashrom:
http://www.gknw.net/test/ipcop/flashrom

thanks, Gün.

----- Original Message ----- 
From: "Guenter" <li...@gk...>
To: <ipc...@li...>
Sent: Friday, February 26, 2010 2:40 AM
Subject: Re: [IPCop-devel] [2.0] release of v1.9.12, SVN #4247


...
> Now I get strange breakage within linux-atm:

Both linux-atm and udev compilation issues are fixed now

For linux-atm, script does not support more than make -j 2, so I hardcode -j
1

For udev, there was a possible timing race because a patch change
configure.ac
Using autoreconf fix that.

Gilles

Selon Guenter <li...@gk...>:

> Hi,
> I want to play a bit with two new packages, so added lfs files for these:
> http://www.gknw.net/test/ipcop/Device-SerialPort
> http://www.gknw.net/test/ipcop/comgt
> and also patched make.sh:
> --- make.sh.orig        2010-02-17 16:40:15.000000000 +0100
> +++ make.sh     2010-02-26 14:54:52.000000000 +0100
> @@ -1812,6 +1812,7 @@
>         chroot_make Net-SSLeay
>         chroot_make XML-Parser
>         chroot_make XML-Simple
> +       chroot_make Device-SerialPort
>         # end of CPAN
>         chroot_make ntp
>         chroot_make openldap
> @@ -1833,6 +1834,7 @@
>         chroot_make vlan
>         chroot_make wireless_tools
>         chroot_make 3c5x9setup
> +       chroot_make comgt
>  } # End of ipcop_build()
>
that is fine but you have too to indicate wich files you want to include in iso
from the list of files installed by the new package.

> both do not appear in the installation I did from the generated ISO ...
>
> any idea what I missed ?
>
> thanks, Gün.
>
- open the resulting 2 files inside log_i486/03_ipcop/{Device-SerialPort,comgt}
- change the prefix + by # or nothing for each file name in the list you want to
include in iso
- then replace 5.10.1 by PERLVER and i486-linux by MACHINE-linux inside the two
files
- copy the modified files in config/rootfiles/common with package name and no
version number
- rebuild the iso with the new files using again ./make.sh build

Gilles

Gilles

Guenter wrote:

> BTW. the 1.9.12 iso is now significantly smaller than previous versions:
> -rw-r--r-- 1 root root 53737472 2010-01-14 02:54 
> ipcop-1.9.11-install-cd.i486.iso
> -rw-r--r-- 1 root root 47546368 2010-02-26 11:36 
> ipcop-1.9.12-install-cd.i486.iso
> -rw-r--r-- 1 root root 52322304 2009-09-22 00:38 
> ipcop-1.9.8-install-cd.i486.iso
> -rw-r--r-- 1 root root 52697088 2010-01-14 00:52 
> ipcop-1.9.9-install-cd.i486.iso

Starting .12 the building of floppy images (which end up in the ISO) is
disabled by default.


Olaf

Guenter wrote:

> any idea what I missed ?

All documented:
http://sourceforge.net/apps/trac/ipcop/wiki/HowToCompileAdditionalCode#Addingremovingapackage


Olaf

Hi,
I want to play a bit with two new packages, so added lfs files for these:
http://www.gknw.net/test/ipcop/Device-SerialPort
http://www.gknw.net/test/ipcop/comgt
and also patched make.sh:
--- make.sh.orig        2010-02-17 16:40:15.000000000 +0100
+++ make.sh     2010-02-26 14:54:52.000000000 +0100
@@ -1812,6 +1812,7 @@
        chroot_make Net-SSLeay
        chroot_make XML-Parser
        chroot_make XML-Simple
+       chroot_make Device-SerialPort
        # end of CPAN
        chroot_make ntp
        chroot_make openldap
@@ -1833,6 +1834,7 @@
        chroot_make vlan
        chroot_make wireless_tools
        chroot_make 3c5x9setup
+       chroot_make comgt
 } # End of ipcop_build()

although the packages report to build fine, and also the binaries appear
below build_i486:
find build_i486/ comgt | grep comgt

build_i486/ipcop/etc/comgt
build_i486/ipcop/etc/comgt/operator
build_i486/ipcop/etc/comgt/command
build_i486/ipcop/etc/comgt/sigmon
build_i486/ipcop/etc/comgt/README
build_i486/ipcop/etc/comgt/dump
build_i486/ipcop/usr/share/man/man1/comgt.1
build_i486/ipcop/usr/local/bin/comgt

find build_i486/ SerialPort* | grep SerialPort

build_i486/ipcop/usr/share/man/man3/Device::SerialPort.3
build_i486/ipcop/usr/lib/perl5/site_perl/5.10.1/i486-linux/Device/SerialPort.pm
build_i486/ipcop/usr/lib/perl5/site_perl/5.10.1/i486-linux/auto/Device/SerialPort
build_i486/ipcop/usr/lib/perl5/site_perl/5.10.1/i486-linux/auto/Device/SerialPort/.packlist
build_i486/ipcop/usr/lib/perl5/site_perl/5.10.1/i486-linux/auto/Device/SerialPort/SerialPort.so
build_i486/ipcop/usr/lib/perl5/site_perl/5.10.1/i486-linux/auto/Device/SerialPort/SerialPort.bs

both do not appear in the installation I did from the generated ISO ...

any idea what I missed ?

thanks, Gün.

Hi Gilles,
Gilles Espinasse schrieb:
> ----- Original Message ----- 
> From: "Guenter" <li...@gk...>
> To: <ipc...@li...>
> Sent: Friday, February 26, 2010 2:40 AM
> Subject: Re: [IPCop-devel] [2.0] release of v1.9.12, SVN #4247

>> Now I get strange breakage within linux-atm:
>>
>> gcc -DHAVE_CONFIG_H -I. -I../..     -I../../src/include -Os
>> -fomit-frame-pointer -march=i486 -mtune=pentium -pipe -Wall -Wshadow
>> -Wpointer-arith -Wwrite-strings -Wstrict-prototypes -MT ql_l.o -MD -MP
>> -MF .deps/ql_l.Tpo -c -o ql_l.o ql_l.c
>> ql_l.l:11:18: error: ql_y.h: No such file or directory
>> updating ql_y.h
> 
> 
> This happen sometime to me, very irregular like a failure with udev-146
> (with PARALLELISM=1 in .config)
> I even try to restart build with no success, and try another time with
> success.
> So it should be a race somewhere.
> I have commited the make fix recently include in LFS. Not sure at all it fix
> this issue.
> That's hard to understand why it sometime fail and sometime work.

yes, indeed. I did not even fetch from SVN, but only build this morning 
again without any changes, and all worked smoothly ....
when I wrote above I checked about 10 times again and again, and always 
got flex failures - though it were two different errors which alternated 
...; my machine is a dual-core with 64-bit OS which might be reason ...
I got similar whoes in the past when I dicovered that gnu-make sometimes 
struggled about dependencies because of timestamps beeing 1 sec in 
future (or at least make thought this).
If I face such issue again I will first try with PARALLELISM=1 ...

BTW. the 1.9.12 iso is now significantly smaller than previous versions:
-rw-r--r-- 1 root root 53737472 2010-01-14 02:54 
ipcop-1.9.11-install-cd.i486.iso
-rw-r--r-- 1 root root 47546368 2010-02-26 11:36 
ipcop-1.9.12-install-cd.i486.iso
-rw-r--r-- 1 root root 52322304 2009-09-22 00:38 
ipcop-1.9.8-install-cd.i486.iso
-rw-r--r-- 1 root root 52697088 2010-01-14 00:52 
ipcop-1.9.9-install-cd.i486.iso

any reason which might explain this? or another build failure on my 
machine? from what I see the 1.9.11 on SF is even bigger than mine ...

thanks, Gün.

----- Original Message ----- 
From: "Guenter" <li...@gk...>
To: <ipc...@li...>
Sent: Friday, February 26, 2010 2:40 AM
Subject: Re: [IPCop-devel] [2.0] release of v1.9.12, SVN #4247


>Hi Olaf,
>Am 16.02.2010 08:48, schrieb Olaf Westrik:
>> 1.9.12 is available as an update to 1.9.11.
>>
...
> Now I get strange breakage within linux-atm:
>
> gcc -DHAVE_CONFIG_H -I. -I../..     -I../../src/include -Os
> -fomit-frame-pointer -march=i486 -mtune=pentium -pipe -Wall -Wshadow
> -Wpointer-arith -Wwrite-strings -Wstrict-prototypes -MT ql_l.o -MD -MP
> -MF .deps/ql_l.Tpo -c -o ql_l.o ql_l.c
> ql_l.l:11:18: error: ql_y.h: No such file or directory
> updating ql_y.h


This happen sometime to me, very irregular like a failure with udev-146
(with PARALLELISM=1 in .config)
I even try to restart build with no success, and try another time with
success.
So it should be a race somewhere.
I have commited the make fix recently include in LFS. Not sure at all it fix
this issue.
That's hard to understand why it sometime fail and sometime work.

Gilles

Hi Olaf,
Am 16.02.2010 08:48, schrieb Olaf Westrik:
> 1.9.12 is available as an update to 1.9.11.
>
> The release of v2 is coming closer, but we are not there yet.
> 2 major problems still exist: IPsec roadwarrior and heavy CPU usage of
> traffic accounting.
> Planned future modifications include changes in kernel (2.6.27 ->
> 2.6.32), toolchain (gcc, glibc, etc.), and anything else that comes along.
due to a couple of issues with building 1.9.12 where I saw things got 
compile, but didnt went into the ISO, and finally after installation 
Ipcop still reported 1.9.11 I decided to do a 'make.sh clean' (blerk).
Now I get strange breakage within linux-atm:

gcc -DHAVE_CONFIG_H -I. -I../..     -I../../src/include -Os 
-fomit-frame-pointer -march=i486 -mtune=pentium -pipe -Wall -Wshadow 
-Wpointer-arith -Wwrite-strings -Wstrict-prototypes -MT ql_l.o -MD -MP 
-MF .deps/ql_l.Tpo -c -o ql_l.o ql_l.c
ql_l.l:11:18: error: ql_y.h: No such file or directory
updating ql_y.h
ql_l.l: In function 'yylex':
ql_l.l:45: error: 'TOK_BREAK' undeclared (first use in this function)
ql_l.l:45: error: (Each undeclared identifier is reported only once
ql_l.l:45: error: for each function it appears in.)
ql_l.l:46: error: 'TOK_CASE' undeclared (first use in this function)
ql_l.l:47: error: 'TOK_DEF' undeclared (first use in this function)
ql_l.l:48: error: 'TOK_DEFAULT' undeclared (first use in this function)
ql_l.l:49: error: 'TOK_LENGTH' undeclared (first use in this function)
ql_l.l:50: error: 'TOK_MULTI' undeclared (first use in this function)
ql_l.l:51: error: 'TOK_RECOVER' undeclared (first use in this function)
ql_l.l:52: error: 'TOK_ABORT' undeclared (first use in this function)
ql_l.l:53: error: 'yylval' undeclared (first use in this function)
ql_l.l:54: error: 'TOK_ID' undeclared (first use in this function)
ql_l.l:58: error: 'TOK_INCLUDE' undeclared (first use in this function)
ql_l.l:61: error: 'TOK_STRING' undeclared (first use in this function)
make[4]: *** [ql_l.o] Error 1
make[4]: *** Waiting for unfinished jobs....
make[4]: Leaving directory `/usr/src/linux-atm-2.5.1/src/qgen'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/usr/src/linux-atm-2.5.1/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/usr/src/linux-atm-2.5.1'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/usr/src/linux-atm-2.5.1'
make: *** [/usr/src/log_i486/03_ipcop/linux-atm-2.5.1] Error 2

any idea what goes here wrong, and how to fix it? This is SVN #4247.
Seems to me as if some flex magic now breaks ....

greets, Gün.

Hi Gilles,
Am 25.02.2010 11:36, schrieb Gilles Espinasse:
> Far more than an afternoon...
> But with latest 2.6.27 build and acpi=off selected after install, I still had
> the issue on power down.
>
> Tested too with Mandriva 2010 (kernel 2.6.31) and had the same 'power down'
> issue.
> Then I think the bios may be the issue.
> Motherboard is a Asus P2B and was with bios 1006 (from 1998).
>
> Upgraded the bios to lasted 1014 beta and now machine really stop on shutdown.
>
> So if the machine stop on a 2.4 kernel but not on a 2.6 kernel, trying to update
> an old bios (if update is available) is the right thing.
> Probably an advice to follow for any bios older than year 2000.
> 2000 has been the limit to switch acpi off (but some bios have a wrong date so date is not 100% reliable)

one good thing could be to enable the msr kernel module (msr.ko.gz is 
only 2297 bytes with 2.6.x kernel, and 1464 bytes with 2.4.x kernel); 
then we can use flashrom:
http://www.flashrom.org/

here's a binary with kernel mods for both 2.6.x and 2.4.x:
http://www.gknw.net/test/ipcop/ipcop-flashrom-r893.tar.gz
(installer is not yet finished, but should at least work for install)

Gün.

On Wed February 24 2010 23:32:52 Tapani Tarvainen wrote:

> Nice. Here's a tip for those who prefer emacs:
> you can use ssh from within emacs in another machine
> by opening a file with syntax like this:
>
> /sshx:root@ipcop#222:/etc/rc.d/rc.firewall.local
>

Likewise, for those of us who cannot deal with the omnibus that is emacs, in 
recent versions of vim:

localsystem:~$ vim scp://user@ipcopsystem:222//path/to/file

works.  There are some interesting behaviors since vim copies the file to the 
local system to edit and copies it back upon save. 

-- Brandon

Very old but I find the solution today

----- Original Message -----
From: "Olaf Westrik" <wei...@ip...>
To: "Gilles Espinasse" <g....@fr...>
Cc: "IPCOP devel" <ipc...@li...>

> Sent: Saturday, November 29, 2008 12:02 PM
> Subject: Re: [IPCop-devel] Reading module corresponding to a network interface

>> Gilles Espinasse wrote:
>>
>> > I find too that this test machine does not halt (display Power down message
>> > only).
>> > This is because of the acpi usage, now default on grub.
>> > Maybe we could parse the bios with dmidecode to look at the bios date?
>>
>> Does that machine power down without acpi?
>>
>>
> Will test this afternoon.
> On 2.4 kernel, no stop with acpi kernel, normal stop with acpi=off

Far more than an afternoon...
But with latest 2.6.27 build and acpi=off selected after install, I still had
the issue on power down.

Tested too with Mandriva 2010 (kernel 2.6.31) and had the same 'power down'
issue.
Then I think the bios may be the issue.
Motherboard is a Asus P2B and was with bios 1006 (from 1998).

Upgraded the bios to lasted 1014 beta and now machine really stop on shutdown.

So if the machine stop on a 2.4 kernel but not on a 2.6 kernel, trying to update
an old bios (if update is available) is the right thing.
Probably an advice to follow for any bios older than year 2000.
2000 has been the limit to switch acpi off (but some bios have a wrong date so date is not 100% reliable)

Gilles

Gunther,

there's a reason we're building vim with tiny feature set -- all 
configurations *should* be done from within the web interface.  Editing config 
files directly may break things.  That's why vim is there as a last resort 
tool and as such it's not meant to include all the features that provide a 
comfortable environment.  Our vim provides enough features to edit a file 
should you absolutely need to.

Also, we're trying to keep the size of ipcop minimal.

IvanK.




On Thursday 25 February 2010 00:59:17 Guenter wrote:
> Hi,
> every time I'm on Ipcop and doing some editing I really miss the usual
> status line which shows me the cursor position (line, column) ...
> here's a patch which compiles vim with the statusline feature:
> 
> --- lfs/vim.orig        2009-09-16 03:19:39.000000000 +0200
> +++ lfs/vim     2010-02-24 13:02:10.000000000 +0100
> @@ -88,15 +88,18 @@
>         @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar jxf $(DIR_DL)/$(DL_FILE)
> 
>         cd $(DIR_APP) && patch -Np1 -i $(DIR_DL)/$(PATCH1)
> +       cd $(DIR_APP) && echo '#define FEAT_STL_OPT' >> src/feature.h
> +       cd $(DIR_APP) && echo '#define FEAT_CMDL_INFO' >> src/feature.h
>         cd $(DIR_APP) && echo '#define SYS_VIMRC_FILE "/etc/vimrc"' >>
> src/feature.h
>         cd $(DIR_APP) && ./configure    --prefix=/usr \
> -                                       --with-features=tiny \
> +                                       --with-features=small \
>                                         --disable-gpm \
>                                         --enable-multibyte
>         cd $(DIR_APP) && make -j $(PARALLELISM)
>         cd $(DIR_APP) && make install
>         ln -sf vim /usr/bin/vi
>         echo "set nocompatible" >  /root/.vimrc
> +       echo "set ruler"        >> /root/.vimrc
>         echo "set bs=2"         >> /root/.vimrc
> 
>         @rm -rf $(DIR_APP)
> 
> would be nice if we could change this with 1.9.x ...
> this results in ~50kb bigger vim binary; probably it can be done even
> with less if we keep --with-features=tiny and add some other defines,
> but I have not further checked.
> 
> Gün.
> 
> 
> 
> ---------------------------------------------------------------------------
> --- Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> IPCop-devel mailing list
> IPC...@li...
> https://lists.sourceforge.net/lists/listinfo/ipcop-devel
> 

On Wed, Feb 24, 2010 at 11:59:17PM +0100, Guenter (li...@gk...) wrote:

> Hi,
> every time I'm on Ipcop and doing some editing I really miss the usual
> status line which shows me the cursor position (line, column) ...
> here's a patch which compiles vim with the statusline feature:

Nice. Here's a tip for those who prefer emacs:
you can use ssh from within emacs in another machine
by opening a file with syntax like this:

/sshx:root@ipcop#222:/etc/rc.d/rc.firewall.local

That way you get all the features of your local emacs
without having to install anything extra on the firewall.

-- 
Tapani Tarvainen

Hi,
every time I'm on Ipcop and doing some editing I really miss the usual
status line which shows me the cursor position (line, column) ...
here's a patch which compiles vim with the statusline feature:

--- lfs/vim.orig        2009-09-16 03:19:39.000000000 +0200
+++ lfs/vim     2010-02-24 13:02:10.000000000 +0100
@@ -88,15 +88,18 @@
        @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar jxf $(DIR_DL)/$(DL_FILE)

        cd $(DIR_APP) && patch -Np1 -i $(DIR_DL)/$(PATCH1)
+       cd $(DIR_APP) && echo '#define FEAT_STL_OPT' >> src/feature.h
+       cd $(DIR_APP) && echo '#define FEAT_CMDL_INFO' >> src/feature.h
        cd $(DIR_APP) && echo '#define SYS_VIMRC_FILE "/etc/vimrc"' >>
src/feature.h
        cd $(DIR_APP) && ./configure    --prefix=/usr \
-                                       --with-features=tiny \
+                                       --with-features=small \
                                        --disable-gpm \
                                        --enable-multibyte
        cd $(DIR_APP) && make -j $(PARALLELISM)
        cd $(DIR_APP) && make install
        ln -sf vim /usr/bin/vi
        echo "set nocompatible" >  /root/.vimrc
+       echo "set ruler"        >> /root/.vimrc
        echo "set bs=2"         >> /root/.vimrc

        @rm -rf $(DIR_APP)

would be nice if we could change this with 1.9.x ...
this results in ~50kb bigger vim binary; probably it can be done even
with less if we keep --with-features=tiny and add some other defines,
but I have not further checked.

Gün.

Gilles Espinasse wrote:
> insmod can't be used as it does not support compressed modules
> 
> root@scsi:~ # insmod /lib/modules/2.6.27-3/kernel/drivers/net/dummy.ko.gz
> insmod: error inserting
> '/lib/modules/2.6.27-3/kernel/drivers/net/dummy.ko.gz': -1 Invalid module
> format
> 
> root@scsi:~ # modprobe -v dummy
> insmod /lib/modules/2.6.27-3/kernel/drivers/net/dummy.ko.gz
> 
> modprobe is a bit misleading (insmod there is just a string displayed, not a
> call to insmod)
> 
> in contrary rmmod work with a compressed module
> root@scsi:~ # rmmod -v /lib/modules/2.6.27-3/kernel/drivers/net/dummy.ko.gz
> rmmod dummy, wait=no
> 
> But modprobe -r should be enought
> 
> On busybox, only modprobe is compiled.

OK, let us remove insmod/rmmod.


Olaf

insmod can't be used as it does not support compressed modules

root@scsi:~ # insmod /lib/modules/2.6.27-3/kernel/drivers/net/dummy.ko.gz
insmod: error inserting
'/lib/modules/2.6.27-3/kernel/drivers/net/dummy.ko.gz': -1 Invalid module
format

root@scsi:~ # modprobe -v dummy
insmod /lib/modules/2.6.27-3/kernel/drivers/net/dummy.ko.gz

modprobe is a bit misleading (insmod there is just a string displayed, not a
call to insmod)

in contrary rmmod work with a compressed module
root@scsi:~ # rmmod -v /lib/modules/2.6.27-3/kernel/drivers/net/dummy.ko.gz
rmmod dummy, wait=no

But modprobe -r should be enought

On busybox, only modprobe is compiled.

Gilles

Gilles Espinasse wrote:
> Selon ow...@us...:
> 
>> Revision: 4259
>>           http://ipcop.svn.sourceforge.net/ipcop/?rev=4259&view=rev
>> Author:   owes
>> Date:     2010-02-18 14:00:50 +0000 (Thu, 18 Feb 2010)
>>
>> Log Message:
>> -----------
>> Upgrade dnsmasq to 2.52
>>
> I think you need to stop before opening the tar.gz and start dnsmasq after the
> upgrade.
> Or a lock will make the replacement of /usr/sbin/dnsmasq to fail.

Yes, not tested yet, but I think we will need that.


Olaf

Selon ow...@us...:

> Revision: 4259
>           http://ipcop.svn.sourceforge.net/ipcop/?rev=4259&view=rev
> Author:   owes
> Date:     2010-02-18 14:00:50 +0000 (Thu, 18 Feb 2010)
>
> Log Message:
> -----------
> Upgrade dnsmasq to 2.52
>
I think you need to stop before opening the tar.gz and start dnsmasq after the
upgrade.
Or a lock will make the replacement of /usr/sbin/dnsmasq to fail.

See
http://ipcop.cvs.sourceforge.net/viewvc/ipcop/ipcop/updates/1.4.19/setup?revision=1.1.2.17&view=markup&pathrev=IPCOP_v1_4_0

Gilles

Olaf Westrik wrote:

> Dear all,
> 
> 
> 1.9.12 is available as an update to 1.9.11.
> 
> The release of v2 is coming closer, but we are not there yet.
> 2 major problems still exist: IPsec roadwarrior and heavy CPU usage of
> traffic accounting.
> Planned future modifications include changes in kernel (2.6.27 ->
> 2.6.32), toolchain (gcc, glibc, etc.), and anything else that comes along.
> 
> 
> Happy testing
> 
> Olaf
> 

The 2.6.32 kernel will further improve cellular data beyond what we 
backpatched already in addition to other kernel improvements.

As a side note for Cobalt users, the newer kernels have the possibility to 
embed arguments if felt necessary which would override the arguments the 
Cobalt Rom sends out. I haven't found a situation yet where it is needed but 
it's nice to have the option. 
-- 
Dave
http://www.raqcop.com

Bugs item #2952918, was opened at 2010-02-16 18:53
Message generated for change (Tracker Item Submitted) made by elektronxyz
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428516&aid=2952918&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: Build
Group: V2 beta
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Volker Richter (elektronxyz)
Assigned to: Nobody/Anonymous (nobody)
Summary: Link to lsof broken + md5sums wrong

Initial Comment:
Hello,

I tried to build the current trunk version from the svn sources (svn 4248).

I discovered that  the link to download lsof is broken. 
You can change it to:
http://gd.tuwien.ac.at/utils/admin-tools/lsof

Furthermore, the md5sums of popt as well as ql2400_fw.bin and ql2500_fw.bin from the binary-firmware-all 
packages have been changed.

Thanks for your great work 

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

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

Dear all,


1.9.12 is available as an update to 1.9.11.

The release of v2 is coming closer, but we are not there yet.
2 major problems still exist: IPsec roadwarrior and heavy CPU usage of
traffic accounting.
Planned future modifications include changes in kernel (2.6.27 ->
2.6.32), toolchain (gcc, glibc, etc.), and anything else that comes along.


Happy testing

Olaf

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


IPCop 1.9.12 is released

v1.9.12 is an UPDATE only, *NO* installation files.
To install from scratch you will need to install 1.9.11 first and then
upgrade to 1.9.12.

v1.9.12 is a BETA version, *DO NOT* use in a productive environment.

Some things will work, for example cleaning your harddisk on installation.
Some things may work.
Some things will not work.

There may be updates to later versions, but it is possible that a full
installation is required to use newer versions.


If you want to help, you can do so by testing and reporting any issues
you should find. Reports should go to the ipcop-devel mailing list.
Make sure that reports are verbose! also specify the exact version you
have been testing, either 1.9.12 or SVN version number if you are building
IPCop by yourself.
A simple "xyz does not work" will get you nowhere! and is more than likely
to be ignored.


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

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.
- Dutch and German translations are complete
- other translations are incomplete
- (online) manual is not yet complete but large sections are available
and worth reading.


v1.9.12 is a BETA version, *DO NOT* use in a productive environment.


http://sourceforge.net/projects/ipcop/files/IPCop%20Test%20Versions/IPCop%201.9.11


Updates
c0eba28e755020337523634f37d55f52  ipcop-1.9.12-update.i486.tgz.gpg

Bugs item #2952550, was opened at 2010-02-15 21:24
Message generated for change (Tracker Item Submitted) made by 
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428516&aid=2952550&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: Web Proxy
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: hroberts89436 ()
Assigned to: Nobody/Anonymous (nobody)
Summary: Blue to Green Connection

Initial Comment:
How can I enable all ports between blue and green?  If I have a wireless laptop, I would like it to be able to connect to all items on the green server.  Should I just move the WAP to the green side as well If that is the case what is the Blue used for?  I was thinking it was just the wireless connection to the green side of things.  My setup is currently with a WAP outside of the IPCOP system connected directly to one of the ports of the AT&T Modem.  This provides "free" Internet to anyone who wants it, and then was using the blue connection for internal to my stuff.


If this is not possible currently can it be added in a later build as an option just for my type of setup?

Thanks for the help on this.

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

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

Guenter wrote:

>> 1.9.11 PXE installed without a problem on my Alix 2D13n No sign of
>> the 'Bootloader installation error' seen by Guenter.
> woah, feared something like that already :)
> what size / brand is your CF card ? CHS or LBA mode set in bios setup?
> mine is a 512MB Transcend Industrial ...

Here is my disk info:

CompactFlash ATA device
        Model Number:       SanDisk SDCFX3-004G                     
        Serial Number:      116913F1109O4304
        Firmware Revision:  HDX 4.32
Standards:
        Supported: 4 
        Likely used: 4
Configuration:
        Logical         max     current
        cylinders       7964    7964
        heads           16      16
        sectors/track   63      63
        --
        CHS current addressable sectors:    8027712
        LBA    user addressable sectors:    8027712
        Logical/Physical Sector size:           512 bytes
        device size with M = 1024*1024:        3919 MBytes
        device size with M = 1000*1000:        4110 MBytes (4 GB)
        cache/buffer size  = 1 KBytes (type=DualPort)
Capabilities:
        LBA  IORDY(may be)(cannot be disabled)
        Standby timer values: spec'd by Vendor
        R/W multiple sector transfer: Max = 4   Current = 0
        DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 (?)
             Cycle time: min=120ns recommended=120ns
        PIO: pio0 pio1 pio2 pio3 pio4 
             Cycle time: no flow control=120ns  IORDY flow control=120ns
Commands/features:
        Enabled Supported:
                Write cache
           *    CFA feature set
           *    CFA advanced modes: pio5 *pio6 

> as it appears I probably need a newer revision of the Alix board since
> my wireless N cards also do not work (both TL-WN961N and TL-WN861N);
> while my G cards work fine (TL-WN660G and Compex-WLM54G) ...

I gave up trying to get the stock AW-NE766 wireless adaptor that is 
fitter to an EEEPC working and replaced it with an Intel 3945ABG which 
worked first time. There seems to be problems getting a suitable driver 
for some boards. There is a compatibility list here:

http://linux-wless.passys.nl/

which you may find useful although none of your boards seem to be listed 
there.

Bob

Hi Bob,
Bob Brewer schrieb:
> 1.9.11 PXE installed without a problem on my Alix 2D13n No sign of the 
> 'Bootloader installation error' seen by Guenter.
woah, feared something like that already :)
what size / brand is your CF card ? CHS or LBA mode set in bios setup?
mine is a 512MB Transcend Industrial ...
as it appears I probably need a newer revision of the Alix board since 
my wireless N cards also do not work (both TL-WN961N and TL-WN861N); 
while my G cards work fine (TL-WN660G and Compex-WLM54G) ...

Gün.