ipcop-devel Mailing List for IPCop Firewall

Hi Eric

I will check this. May take some days, I'm busy a.t.m...

I assume there is a file missing in rootfiles. Do you have an error
in /var/log/httpd/error_log?

Achim


> Achim
> 
> I've noticed that I'm getting a "Could not open available updates file."
> message on the home page, which looks like another perl file operation
> error.
> 
> Possibly thrown by these lines in general-function.pl
>    unless (open(FILE, '>/var/ipcop/patches/available.xml')) {
>         die "Could not open updates available XML file.";
> 
> Could be very big problem...
> 
> Eric *
> *
> 
> 
> On 23 May 2013 15:11, Achim Weber <dot...@gm...> wrote:
> 
> > Hi Gilles!
> >
> > > I slowed probably the process a lot with my suggestion to use the 3.4
> > kernel. I haven't found time to progress faster.
> > > Any issue compiling external driver for 3.4 should be fixed now as
> > sangoma released wanpipe-7.0.x
> > > The big jump in the release number from 3.5.28 mean nothing for the
> > code, only a sync with the windows driver version number.
> > > I haven't yet compiled that crap code.
> > >
> > > I am compiling those days ipcop with kernel 3.4.37 and I have seen
> > 3.4.38 should arrive soon.
> > >
> > > I haven't had the time to test the install a lot with 3.4 and tune the
> > kernel config.
> >
> > May you can commit the kernel 3.4 upgrade stuff you already have and
> > others can
> > test+modify it?!
> >
> > IIRC I read somewhere kernel 3.0 should be EOL oct 2013. So we really
> > should
> > upgrade to 3.4 for 2.1.x.
> >
> >
> > > Probably we should update perl to debian wheezy (5.14.2.20..) or in a
> > bit more than one year, our old perl will not be maintained anymore.
> >
> > I'm currently upgrading Perl to Debian Wheezy (5.14.2-x). I have tweaked
> > lfs/perl like described in LFS 7.1 and both toolchain and base are
> > compiling
> > fine. The Perl rootfile is already changed but needs some testing if
> > something
> > is missing.
> > Too the old Perl 5.10.1 is 'rm -f ...' in update-2.1.0-setup (needs
> > testing).
> > The update-rootfiles probably needs some more (new) Perl files, have to
> > check
> > this. Only want to have the regular Perl rootfile working before working
> > on the
> > update rootfile.
> >
> > Is there anything else I have to tweak/look into?
> >
> > best regards,
> > Achim
> >
> > PS:
> > Want to push 2.1.1 forward...
> >
> >
> > ------------------------------------------------------------------------------
> > Try New Relic Now & We'll Send You this Cool Shirt
> > New Relic is the only SaaS-based application performance monitoring service
> > that delivers powerful full stack analytics. Optimize and monitor your
> > browser, app, & servers with just a few lines of code. Try New Relic
> > and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
> > _______________________________________________
> > IPCop-devel mailing list
> > IPC...@li...
> > https://lists.sourceforge.net/lists/listinfo/ipcop-devel
> >

Achim

I've noticed that I'm getting a "Could not open available updates file."
message on the home page, which looks like another perl file operation
error.

Possibly thrown by these lines in general-function.pl
   unless (open(FILE, '>/var/ipcop/patches/available.xml')) {
        die "Could not open updates available XML file.";

Could be very big problem...

Eric *
*


On 23 May 2013 15:11, Achim Weber <dot...@gm...> wrote:

> Hi Gilles!
>
> > I slowed probably the process a lot with my suggestion to use the 3.4
> kernel. I haven't found time to progress faster.
> > Any issue compiling external driver for 3.4 should be fixed now as
> sangoma released wanpipe-7.0.x
> > The big jump in the release number from 3.5.28 mean nothing for the
> code, only a sync with the windows driver version number.
> > I haven't yet compiled that crap code.
> >
> > I am compiling those days ipcop with kernel 3.4.37 and I have seen
> 3.4.38 should arrive soon.
> >
> > I haven't had the time to test the install a lot with 3.4 and tune the
> kernel config.
>
> May you can commit the kernel 3.4 upgrade stuff you already have and
> others can
> test+modify it?!
>
> IIRC I read somewhere kernel 3.0 should be EOL oct 2013. So we really
> should
> upgrade to 3.4 for 2.1.x.
>
>
> > Probably we should update perl to debian wheezy (5.14.2.20..) or in a
> bit more than one year, our old perl will not be maintained anymore.
>
> I'm currently upgrading Perl to Debian Wheezy (5.14.2-x). I have tweaked
> lfs/perl like described in LFS 7.1 and both toolchain and base are
> compiling
> fine. The Perl rootfile is already changed but needs some testing if
> something
> is missing.
> Too the old Perl 5.10.1 is 'rm -f ...' in update-2.1.0-setup (needs
> testing).
> The update-rootfiles probably needs some more (new) Perl files, have to
> check
> this. Only want to have the regular Perl rootfile working before working
> on the
> update rootfile.
>
> Is there anything else I have to tweak/look into?
>
> best regards,
> Achim
>
> PS:
> Want to push 2.1.1 forward...
>
>
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
> _______________________________________________
> IPCop-devel mailing list
> IPC...@li...
> https://lists.sourceforge.net/lists/listinfo/ipcop-devel
>

Ports forwarding to from aliased external ip address to a internal ip
address stopped working.

Lines 6 7 and 8 all stopped working. The IP referenced in 7 and 8 is
correct and was the same with 6. Also interesting is when corrected it
doesn't show IP it shows host name. ns2.agweb.net = 173.14.76.234

I clicked on edit for 6 and in the edit window it showed a different ip
address than the .234. The external aliased ip address is wrong and
different than the previous window.  If i correct it here and save then the
port forwarding works as expected.

screenshots available upon request


-fastfish

Hi Gilles!

> I slowed probably the process a lot with my suggestion to use the 3.4 kernel. I haven't found time to progress faster.
> Any issue compiling external driver for 3.4 should be fixed now as sangoma released wanpipe-7.0.x
> The big jump in the release number from 3.5.28 mean nothing for the code, only a sync with the windows driver version number.
> I haven't yet compiled that crap code.
> 
> I am compiling those days ipcop with kernel 3.4.37 and I have seen 3.4.38 should arrive soon.
> 
> I haven't had the time to test the install a lot with 3.4 and tune the kernel config.

May you can commit the kernel 3.4 upgrade stuff you already have and others can
test+modify it?!

IIRC I read somewhere kernel 3.0 should be EOL oct 2013. So we really should
upgrade to 3.4 for 2.1.x.


> Probably we should update perl to debian wheezy (5.14.2.20..) or in a bit more than one year, our old perl will not be maintained anymore.

I'm currently upgrading Perl to Debian Wheezy (5.14.2-x). I have tweaked
lfs/perl like described in LFS 7.1 and both toolchain and base are compiling
fine. The Perl rootfile is already changed but needs some testing if something
is missing.
Too the old Perl 5.10.1 is 'rm -f ...' in update-2.1.0-setup (needs testing).
The update-rootfiles probably needs some more (new) Perl files, have to check
this. Only want to have the regular Perl rootfile working before working on the
update rootfile.

Is there anything else I have to tweak/look into?

best regards,
Achim

PS:
Want to push 2.1.1 forward...

Bugs item #3613786, was opened at 2013-05-23 03:49
Message generated for change (Tracker Item Submitted) made by jwarnier
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428516&aid=3613786&group_id=40604

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Jerome Warnier (jwarnier)
Assigned to: Nobody/Anonymous (nobody)
Summary: IPCop Commercial support page update

Initial Comment:
Could you please move the BeezNest company from Luxemburg to Belgium, and remove the reference to Esch-sur-Alzette (only keeping Brussels).

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

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

> ccache_clean should only be required for very special corner cases :
> - if the lib linked to gcc are changed but not resulting gcc md5sum
> - a design bug with headers when new headers files are added and previous compilation did not use those headers.
> http://www.mail-archive.com/cc...@li.../msg00920.html

I wanted to be sure I don't run into some side effects with broken ccache or old
toolchain.

As for the issue, I did commit a fix for my test scenario (upload host cert). I
saw some more code with those move()/copy() without explicit return value
evaluation. I will change this code as-well within the next days.

Achim

----- Mail original -----
> De: "Achim Weber" <dot...@gm...>
> À: "Eric Oberlander" <eri...@gm...>
> Cc: "Olaf Westrik" <wei...@ip...>, "IPCOP devel" <ipc...@li...>
> Envoyé: Mardi 21 Mai 2013 08:50:29
> Objet: Re: [IPCop-devel] Perl File::Copy / Upload host cert is broken somehow
> 
> Hi all!
> 
> I found it, the issue came with #6907. It seems the newer openssl behaves
> different to the older ones. The return code 512 doesn't come from move() but
> from the openssl call some lines before the move().
> 
Thank for debugging that.

> I will look into it how the ipsec.cgi has to be changed. It will be easy now.
> We will see...
> 
> Achim
> 
> PS:
> Did another 15 builds, everytime with ccache_clean + toolchain now...
>

ccache_clean should only be required for very special corner cases :
- if the lib linked to gcc are changed but not resulting gcc md5sum
- a design bug with headers when new headers files are added and previous compilation did not use those headers.
http://www.mail-archive.com/cc...@li.../msg00920.html

I migrated one machine (32bits from debian v6 (squeeze) to v7 (wheezy).
After that first build experience, I could see :
- a very big amount of warning during gcc pass1 (due to gcc-4.7 compiling gcc-4.4.5)
- bash-4.2 should have the same bug we suffer during ./make.sh execution sometime.
The issue in that build attempt is that toolchain gettext was silently not compiled, build was sucessfull but msgfmt was missing everywhere.

Gilles

Hi all!

I found it, the issue came with #6907. It seems the newer openssl behaves
different to the older ones. The return code 512 doesn't come from move() but
from the openssl call some lines before the move().

I will look into it how the ipsec.cgi has to be changed. It will be easy now.
We will see...

Achim

PS: 
Did another 15 builds, everytime with ccache_clean + toolchain now...


> I confirm that I get the same error :(
> 
> Eric
> 
> 
> On 17 May 2013 20:02, Achim Weber <dot...@gm...> wrote:
> 
> > Hi Eric
> >
> > > I haven't used a VPN before, but I'm willing to give it a try, if you
> > want
> > > to contact me off list.
> >
> > No need to really setup a VPN.
> >
> > Just follow those steps:
> > 1) Button "Generate Root/Host Certificates" (vpnca.cgi)
> > 2) Enable IPsec on RED and/or BLUE, Option "Restart net-to-net...",
> > Button [Save] (ipsec.cgi)
> > 3a) [Add] Connection (ipsec.cgi)
> > 3b) Option Net-to-Net, [Add]
> > 3c) Enter:
> >         - Name: Test
> >         - Remote Host/IP: 1.1.1.1
> >         - Remote subnet: 192.168.0.0/255.255.255.0
> >         Below in section "Authentication":
> >         - Option "Upload a certificate" and Upload the example host cert
> > which
> >           is attached to this email
> >         -> button [Save]
> > When I do this I get the error message from my screenshot.
> >
> >
> > > I'm running 2.1.1 built on an Ubuntu 12.04 box. Installed as an update
> > > using SVN 7038.
> >
> > Ok, if you don't get the error when following the above steps I will
> > install
> > another build machine with a different distro.
> >
> > Thanks,
> > Achim

I confirm that I get the same error :(

Eric


On 17 May 2013 20:02, Achim Weber <dot...@gm...> wrote:

> Hi Eric
>
> > I haven't used a VPN before, but I'm willing to give it a try, if you
> want
> > to contact me off list.
>
> No need to really setup a VPN.
>
> Just follow those steps:
> 1) Button "Generate Root/Host Certificates" (vpnca.cgi)
> 2) Enable IPsec on RED and/or BLUE, Option "Restart net-to-net...",
> Button [Save] (ipsec.cgi)
> 3a) [Add] Connection (ipsec.cgi)
> 3b) Option Net-to-Net, [Add]
> 3c) Enter:
>         - Name: Test
>         - Remote Host/IP: 1.1.1.1
>         - Remote subnet: 192.168.0.0/255.255.255.0
>         Below in section "Authentication":
>         - Option "Upload a certificate" and Upload the example host cert
> which
>           is attached to this email
>         -> button [Save]
> When I do this I get the error message from my screenshot.
>
>
> > I'm running 2.1.1 built on an Ubuntu 12.04 box. Installed as an update
> > using SVN 7038.
>
> Ok, if you don't get the error when following the above steps I will
> install
> another build machine with a different distro.
>
> Thanks,
> Achim

Hi Eric

> I haven't used a VPN before, but I'm willing to give it a try, if you want
> to contact me off list.

No need to really setup a VPN. 

Just follow those steps:
1) Button "Generate Root/Host Certificates" (vpnca.cgi)
2) Enable IPsec on RED and/or BLUE, Option "Restart net-to-net...",
Button [Save] (ipsec.cgi) 
3a) [Add] Connection (ipsec.cgi)
3b) Option Net-to-Net, [Add]
3c) Enter:
	- Name: Test
	- Remote Host/IP: 1.1.1.1
	- Remote subnet: 192.168.0.0/255.255.255.0
	Below in section "Authentication":
	- Option "Upload a certificate" and Upload the example host cert which
	  is attached to this email
	-> button [Save]
When I do this I get the error message from my screenshot.


> I'm running 2.1.1 built on an Ubuntu 12.04 box. Installed as an update
> using SVN 7038.

Ok, if you don't get the error when following the above steps I will install
another build machine with a different distro.

Thanks,
Achim

On 17 May 2013 18:20, Achim Weber <dot...@gm...> wrote:

> Hi Eric
>
> > Are the permissions on the /var/ipcop/ca or /var/ipcop/certs directories
> > unusual in any way? They are owned by nobody:nobody on my system.
>
> Everything looks ok to me:
> root@ipcop20:~ # ls -al /var/ipcop/ca/
> total 12
> drwxr-xr-x  2 nobody nobody 4096 May 16 23:14 .
> drwxr-xr-x 34 root   root   4096 May 16 23:11 ..
> -rw-r--r--  1 nobody nobody 1253 May 16 23:14 cacert.pem
> root@ipcop20:~ # ls -al /var/ipcop/certs/
> total 28
> drwxr-xr-x  2 nobody nobody 4096 May 16 23:16 .
> drwxr-xr-x 34 root   root   4096 May 16 23:11 ..
> -rw-r--r--  1 nobody nobody 1180 May 16 23:15 hostcert.pem
> -rw-r--r--  1 nobody nobody  887 May 16 23:15 hostkey.pem
> -rw-r--r--  1 nobody nobody    0 May 16 23:15 index.txt
> -rw-r--r--  1 nobody nobody   21 May 16 23:15 index.txt.attr
> -rw-r--r--  1 nobody nobody    2 May 16 23:15 serial
> -rw-r--r--  1 nobody nobody 1314 May 17 19:13 test3cert.pem
>
> And where the uploaded (tmp) cert file is moved from:
> root@ipcop20:~ # ls -al /tmp/
> total 8
> drwxrwxrwt  2 root root   60 May 17 19:13 .
> drwxrwxrwt 18 root root 4096 May 16 23:11 ..
> -rw-r--r--  1 root root  290 May 17 19:10 vnstat.xml
>
> Every time I did a fresh install, so no [broken] backups involved.
>
> Eric, are you able to create a Ipsec vpn connection with uploaded host cert
> with current SVN build? Whats your build machine/distro?
>
> Achim
>


I haven't used a VPN before, but I'm willing to give it a try, if you want
to contact me off list.

I'm running 2.1.1 built on an Ubuntu 12.04 box. Installed as an update
using SVN 7038.

Eric

Hi Eric

> Are the permissions on the /var/ipcop/ca or /var/ipcop/certs directories
> unusual in any way? They are owned by nobody:nobody on my system.

Everything looks ok to me:
root@ipcop20:~ # ls -al /var/ipcop/ca/
total 12
drwxr-xr-x  2 nobody nobody 4096 May 16 23:14 .
drwxr-xr-x 34 root   root   4096 May 16 23:11 ..
-rw-r--r--  1 nobody nobody 1253 May 16 23:14 cacert.pem
root@ipcop20:~ # ls -al /var/ipcop/certs/
total 28
drwxr-xr-x  2 nobody nobody 4096 May 16 23:16 .
drwxr-xr-x 34 root   root   4096 May 16 23:11 ..
-rw-r--r--  1 nobody nobody 1180 May 16 23:15 hostcert.pem
-rw-r--r--  1 nobody nobody  887 May 16 23:15 hostkey.pem
-rw-r--r--  1 nobody nobody    0 May 16 23:15 index.txt
-rw-r--r--  1 nobody nobody   21 May 16 23:15 index.txt.attr
-rw-r--r--  1 nobody nobody    2 May 16 23:15 serial
-rw-r--r--  1 nobody nobody 1314 May 17 19:13 test3cert.pem

And where the uploaded (tmp) cert file is moved from:
root@ipcop20:~ # ls -al /tmp/
total 8
drwxrwxrwt  2 root root   60 May 17 19:13 .
drwxrwxrwt 18 root root 4096 May 16 23:11 ..
-rw-r--r--  1 root root  290 May 17 19:10 vnstat.xml

Every time I did a fresh install, so no [broken] backups involved.

Eric, are you able to create a Ipsec vpn connection with uploaded host cert
with current SVN build? Whats your build machine/distro?

Achim

On 17 May 2013 08:24, Achim Weber <dot...@gm...> wrote:

> Hi!
>
> I noticed the Perl File::Copy is broken. In current 2.1.1 I'm no more able
> to
> upload a host cert when configuring an Ipsec vpn connection. I always get
> an
> errormessage "Certificate file move failed: ", see screenshot [1].
>
> The corresponding code is in ipsec.cgi line 718:
> ------------------------ Code start -----------------------------------
> move($filename, "/var/ipcop/certs/$cgiparams{'NAME'}cert.pem");
> if ($? ne 0) {
>     $errormessage = "$Lang::tr{'certificate file move failed'}: $!";
>     unlink ($filename);
>     goto VPNCONF_ERROR;
> }
> ------------------------ Code end -------------------------------------
> Here $? is always '512', normally move() should return with 1 or 0 [2].
> Also
> the file was successfully moved (or at least copied), I can see the file
> in /var/ipcop/certs/! And the reason $! is empty!
>
> It seams there is a system call inside move() which is failing(?) [3][4], I
> don't know.
>
> This issue is not present in 2.0.6 and it is not a local problem by my
> because
> those .iso's from Olaf are also showing the same behavior. I have tried to
> identify the SVN commit which broke it but was not successful. I have
> compiled
> around 15 different svn revs but didn't found it.
>
> Here are my results from the latest builds:
> Build order | SVN Rev   | Error avail.?
> ------------|-----------|---------------
>     1       | 6903      | Error avail.
>     2       | 6902      | Error avail.
>     3       | 6863      | OK, no Error
>     4       | 6864      | OK, no Error
>     5       | 6882      | OK, no Error
>     6       | 6883      | OK, no Error
>     7       | 6899      | OK, no Error
>     8       | 6900      | OK, no Error
>     9       | 6901      | OK, no Error
>    10       | 6902 again| OK, no Error now!
>    11       | 7031      | Error avail.
>
> I did always "svn up -r nnnn, make.sh clean, make.sh prefetch, make.sh
> build"
> between every build. Before the latest 7031 build I additionally did a
> "make.sh
> ccach_clean, make.sh toolchain" before the build.
>
> I'm very confused what to do now. Any Ideas?
>
> Buildmachine is an up-to-date Debian 6 (Squeeze). IIRC Olaf is also
> building
> on Debian 6?
>
> Achim
>
>
> [1] http://s1.directupload.net/images/130517/b279tmdq.png
> [2] http://perldoc.perl.org/File/Copy.html#RETURN
> [3] http://www.perlmonks.org/?node_id=818402
> [4] http://perldoc.perl.org/functions/system.html
>
>
>
Hi Achim

Are the permissions on the /var/ipcop/ca or /var/ipcop/certs directories
unusual in any way? They are owned by nobody:nobody on my system.

Eric

Hi!

I noticed the Perl File::Copy is broken. In current 2.1.1 I'm no more able to
upload a host cert when configuring an Ipsec vpn connection. I always get an
errormessage "Certificate file move failed: ", see screenshot [1].

The corresponding code is in ipsec.cgi line 718:
------------------------ Code start -----------------------------------
move($filename, "/var/ipcop/certs/$cgiparams{'NAME'}cert.pem");
if ($? ne 0) {
    $errormessage = "$Lang::tr{'certificate file move failed'}: $!"; 
    unlink ($filename); 
    goto VPNCONF_ERROR;
}
------------------------ Code end -------------------------------------
Here $? is always '512', normally move() should return with 1 or 0 [2]. Also
the file was successfully moved (or at least copied), I can see the file
in /var/ipcop/certs/! And the reason $! is empty!

It seams there is a system call inside move() which is failing(?) [3][4], I
don't know.

This issue is not present in 2.0.6 and it is not a local problem by my because
those .iso's from Olaf are also showing the same behavior. I have tried to
identify the SVN commit which broke it but was not successful. I have compiled
around 15 different svn revs but didn't found it. 

Here are my results from the latest builds:
Build order | SVN Rev   | Error avail.?
------------|-----------|---------------
    1       | 6903      | Error avail.
    2       | 6902      | Error avail.
    3       | 6863      | OK, no Error
    4       | 6864      | OK, no Error
    5       | 6882      | OK, no Error
    6       | 6883      | OK, no Error
    7       | 6899      | OK, no Error
    8       | 6900      | OK, no Error
    9       | 6901      | OK, no Error
   10       | 6902 again| OK, no Error now!
   11       | 7031      | Error avail.

I did always "svn up -r nnnn, make.sh clean, make.sh prefetch, make.sh build"
between every build. Before the latest 7031 build I additionally did a "make.sh
ccach_clean, make.sh toolchain" before the build.

I'm very confused what to do now. Any Ideas?

Buildmachine is an up-to-date Debian 6 (Squeeze). IIRC Olaf is also building
on Debian 6?

Achim


[1] http://s1.directupload.net/images/130517/b279tmdq.png
[2] http://perldoc.perl.org/File/Copy.html#RETURN
[3] http://www.perlmonks.org/?node_id=818402
[4] http://perldoc.perl.org/functions/system.html

Hi

I've uploaded a set of placeholder file for a Spanish version of the Admin
Manual to SVN, as a start. If you'd like checkout a Working Copy, you can
edit that and check how it builds using the command 'make LANGUAGES=es'

You may need to install bits of software on your build system, such as
xmlto or other necessary docbook files.

Regards

Eric



On 8 May 2013 11:03, Eric Oberlander <eri...@gm...> wrote:

> Hi
>
> Thanks for your kind offer of help. If you'd like to add it within the
> existing IPCop SVN framework on SourceForge that would be great. It offers
> the ability for help icons in the webGUI to be linked to the online manuals
> (currently on DE and EN are available). You can see the structure within
> the IPCopDoc branch on SVN:
>
> http://ipcop.svn.sourceforge.net/viewvc/ipcop/IPCopDoc/trunk/
>
> Currently there are three sub-directories, de, en and fr. An admin can add
> 'es', and populate it with the existing directories, xml files and images,
> probably from the 'en' tree, which is most up-to-date. You can then
> edit/translate/replace the existing xml and image files with your own
> versions and commit them to SVN as you go. There is a 'make' system in
> place to automagically create HTML and PDF fils from the xml files. It is
> important that you keep the file structure, section names and file names
> the same, so it just works. The HTML files can then be uploaded to the
> IPCop website.
>
> We can set about creating the 'es' document tree if you like, and you can
> then download your own Working Copy, but we'll need an Admin (I'm not an SF
> Admin) to give you rights to be able to commit to SVN.
>
> That's a start, I'm sure you will have more questions :)
>
> Eric
>
>
>
> On 7 May 2013 21:27, L.N. <le...@gm...> wrote:
>
>> Hi:
>>
>> I reviewed and completed the ES_es translation of the IPCop system itself
>> some time ago.
>>
>> Now, as part of a Master I'm studying, I want to translate the whole
>> documentation and complete the missed sections for the ES_es language. It
>> will be published in the Documentation area at SourceForge with the same
>> license you are using (GNU).
>>
>> I need instructions about it from the person in charge of translations
>> about which format you prefer, schemes, indexes, how to add screenshots,
>> how to publish, permisions, etc.
>>
>> I will probably add ES_es translation for the Copfilter project, as it's
>> widely used along with IPCop. It will depend on my timings. I prefer to
>> stick to IPCop and maintain it's documentation rather than make two "poor"
>> jobs or stop maintaining one of them.
>>
>> My intention is not only make the translation, but also fill the existing
>> gaps in the EN version and keep it up to date according to new versions of
>> the system.
>>
>> Hope you accept my project! Otherwise, sorry for the noise.
>>
>> Best regards.
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Learn Graph Databases - Download FREE O'Reilly Book
>> "Graph Databases" is the definitive new guide to graph databases and
>> their applications. This 200-page book is written by three acclaimed
>> leaders in the field. The early access version is available now.
>> Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
>> _______________________________________________
>> IPCop-devel mailing list
>> IPC...@li...
>> https://lists.sourceforge.net/lists/listinfo/ipcop-devel
>>
>>
>

Hi

Thanks for your kind offer of help. If you'd like to add it within the
existing IPCop SVN framework on SourceForge that would be great. It offers
the ability for help icons in the webGUI to be linked to the online manuals
(currently on DE and EN are available). You can see the structure within
the IPCopDoc branch on SVN:

http://ipcop.svn.sourceforge.net/viewvc/ipcop/IPCopDoc/trunk/

Currently there are three sub-directories, de, en and fr. An admin can add
'es', and populate it with the existing directories, xml files and images,
probably from the 'en' tree, which is most up-to-date. You can then
edit/translate/replace the existing xml and image files with your own
versions and commit them to SVN as you go. There is a 'make' system in
place to automagically create HTML and PDF fils from the xml files. It is
important that you keep the file structure, section names and file names
the same, so it just works. The HTML files can then be uploaded to the
IPCop website.

We can set about creating the 'es' document tree if you like, and you can
then download your own Working Copy, but we'll need an Admin (I'm not an SF
Admin) to give you rights to be able to commit to SVN.

That's a start, I'm sure you will have more questions :)

Eric



On 7 May 2013 21:27, L.N. <le...@gm...> wrote:

> Hi:
>
> I reviewed and completed the ES_es translation of the IPCop system itself
> some time ago.
>
> Now, as part of a Master I'm studying, I want to translate the whole
> documentation and complete the missed sections for the ES_es language. It
> will be published in the Documentation area at SourceForge with the same
> license you are using (GNU).
>
> I need instructions about it from the person in charge of translations
> about which format you prefer, schemes, indexes, how to add screenshots,
> how to publish, permisions, etc.
>
> I will probably add ES_es translation for the Copfilter project, as it's
> widely used along with IPCop. It will depend on my timings. I prefer to
> stick to IPCop and maintain it's documentation rather than make two "poor"
> jobs or stop maintaining one of them.
>
> My intention is not only make the translation, but also fill the existing
> gaps in the EN version and keep it up to date according to new versions of
> the system.
>
> Hope you accept my project! Otherwise, sorry for the noise.
>
> Best regards.
>
>
>
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and
> their applications. This 200-page book is written by three acclaimed
> leaders in the field. The early access version is available now.
> Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
> _______________________________________________
> IPCop-devel mailing list
> IPC...@li...
> https://lists.sourceforge.net/lists/listinfo/ipcop-devel
>
>

Hi:

I reviewed and completed the ES_es translation of the IPCop system itself
some time ago.

Now, as part of a Master I'm studying, I want to translate the whole
documentation and complete the missed sections for the ES_es language. It
will be published in the Documentation area at SourceForge with the same
license you are using (GNU).

I need instructions about it from the person in charge of translations
about which format you prefer, schemes, indexes, how to add screenshots,
how to publish, permisions, etc.

I will probably add ES_es translation for the Copfilter project, as it's
widely used along with IPCop. It will depend on my timings. I prefer to
stick to IPCop and maintain it's documentation rather than make two "poor"
jobs or stop maintaining one of them.

My intention is not only make the translation, but also fill the existing
gaps in the EN version and keep it up to date according to new versions of
the system.

Hope you accept my project! Otherwise, sorry for the noise.

Best regards.

Bugs item #3612430, was opened at 2013-05-01 11:14
Message generated for change (Tracker Item Submitted) made by 
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428516&aid=3612430&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: User Interface
Group: 2.0.0
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: https://www.google.com/accounts ()
Assigned to: Nobody/Anonymous (nobody)
Summary: Network metrics not displayed by /cgi-bin/netstatus.cgi

Initial Comment:
Network interface metrics displayed by ifconfig are not displayed by the /cgi-bin/netstatus.cgi (Status -> Network Status -> Interfaces)  web interface.

1) The value of the "dropped" metric in Status -> Network Status -> Interfaces is zero while ifconfig reports a non-zero value.  See attached screen shots.
2) ifconfig reports an "overruns" metric but a corresponding column does not exist in Status -> Network Status -> Interfaces.  See attached screen shots.

Regards
Adrian

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

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