ipcop-devel Mailing List for IPCop Firewall

2013/6/27 Eric Oberlander <eri...@gm...>:
> Hi Marcelo
>
> One of the texts in your files was blank:


#: urlfilter+restart+message
msgid "The URL filter must be restarted to activate the changed rules"
msgstr "Es necesario reiniciar el filtrado de URLs para activar las
reglas modificadas"

> Can you complete that for me?
>
> And I think this phrase may be wrong, can you confirm it is OK, or correct
> it?

#: log+username
msgid "Log username"
msgstr "Incluir los nombres de usuario en el log"

that is meaning some like "Include the username in the log" what would
good for a check-box if apply.

> The phrase is asking in a shortened form "Do you want to log the usernames,
> yes or no?" and not "Username of the log"


A note about words like "blacklist" or maybe "log".

In Castilian Spanish, "black list" must be translated "lista negra",
while among LA Spanish spoken people "blacklist" is enough and more
accurate. The same applies to "log" and "bitácora". So with a lot of
other words. At the end, being the U.S. backyard had to bring some
advantage, isn't it? ;p

Both strings was already fixed through the web app.
Thank you Eric!

Greetings
Marcelo



-- 
   Marcelo Zunino

Hi Marcelo

One of the texts in your files was blank:

#: urlfilter+restart+message
msgid "The URL filter must be restarted to activate the changed rules"
msgstr ""

Can you complete that for me?

And I think this phrase may be wrong, can you confirm it is OK, or correct
it?
#: log+username
msgid "Log username"
msgstr "Nombre de usuario del log"

The phrase is asking in a shortened form "Do you want to log the usernames,
yes or no?" and not "Username of the log"

My apologies if I have misunderstood.

Eric




On 27 June 2013 11:14, Eric Oberlander <eri...@gm...> wrote:

> Thanks Marcelo
>
> I'll add your translated phrases to the Database.
>
> Cheers
>
> Eric
>
>
> On 26 June 2013 19:50, Marcelo Zunino <mar...@gm...> wrote:
>
>> re-send cause bounced. > 40K
>>
>> The "attached" file can be found here http://bit.ly/10VMv8b (112K)
>>
>>
>> Greetings,
>> Marcelo.
>>
>>
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: Marcelo Zunino <mar...@gm...>
>> Date: 2013/6/26
>> Subject: Latino-American Span 1834/1954
>> To: ipc...@li...
>>
>>
>> Hello,
>>
>>
>> Facing to next release 2.1 I'm hurry to finish LA Spanish translation
>> tasks.
>> As shown in the IPCop Translations Database site, 120 chains remain
>> still untranslated.
>>
>> Attached tar file explodes next 4 files:
>> full_ipcop_la.po
>> full_ipcop_la.csv
>> delta_ipcop_la.po
>> delta_ipcop_la.csv
>>
>> containing full or delta only translated strings respectively in both
>> csv and po files.
>>
>> Regards,
>> Marcelo.
>>
>>
>> --
>>    Marcelo Zunino
>>
>>
>> --
>>    Marcelo Zunino
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Windows:
>>
>> Build for Windows Store.
>>
>> http://p.sf.net/sfu/windows-dev2dev
>> _______________________________________________
>> IPCop-devel mailing list
>> IPC...@li...
>> https://lists.sourceforge.net/lists/listinfo/ipcop-devel
>>
>
>

Thanks Marcelo

I'll add your translated phrases to the Database.

Cheers

Eric


On 26 June 2013 19:50, Marcelo Zunino <mar...@gm...> wrote:

> re-send cause bounced. > 40K
>
> The "attached" file can be found here http://bit.ly/10VMv8b (112K)
>
>
> Greetings,
> Marcelo.
>
>
>
>
>
> ---------- Forwarded message ----------
> From: Marcelo Zunino <mar...@gm...>
> Date: 2013/6/26
> Subject: Latino-American Span 1834/1954
> To: ipc...@li...
>
>
> Hello,
>
>
> Facing to next release 2.1 I'm hurry to finish LA Spanish translation
> tasks.
> As shown in the IPCop Translations Database site, 120 chains remain
> still untranslated.
>
> Attached tar file explodes next 4 files:
> full_ipcop_la.po
> full_ipcop_la.csv
> delta_ipcop_la.po
> delta_ipcop_la.csv
>
> containing full or delta only translated strings respectively in both
> csv and po files.
>
> Regards,
> Marcelo.
>
>
> --
>    Marcelo Zunino
>
>
> --
>    Marcelo Zunino
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> IPCop-devel mailing list
> IPC...@li...
> https://lists.sourceforge.net/lists/listinfo/ipcop-devel
>

re-send cause bounced. > 40K

The "attached" file can be found here http://bit.ly/10VMv8b (112K)


Greetings,
Marcelo.





---------- Forwarded message ----------
From: Marcelo Zunino <mar...@gm...>
Date: 2013/6/26
Subject: Latino-American Span 1834/1954
To: ipc...@li...


Hello,


Facing to next release 2.1 I'm hurry to finish LA Spanish translation tasks.
As shown in the IPCop Translations Database site, 120 chains remain
still untranslated.

Attached tar file explodes next 4 files:
full_ipcop_la.po
full_ipcop_la.csv
delta_ipcop_la.po
delta_ipcop_la.csv

containing full or delta only translated strings respectively in both
csv and po files.

Regards,
Marcelo.


--
   Marcelo Zunino


-- 
   Marcelo Zunino

----- Mail original -----
> De: "Achim Weber" <dot...@gm...>
> À: "Eric Oberlander" <eri...@gm...>, "IPCop devel" <ipc...@li...>, "Gilles
> Espinasse" <g....@fr...>, "Olaf Westrik (ipcop-forum)" <wei...@ip...>
> Envoyé: Mardi 25 Juin 2013 09:15:08
> Objet: Re: [IPCop-devel] Progress on 2.1
> 
> I think the biggest missing part is the linux kernel upgrade to 3.4. 
> Other than that are only minor stuff (maybe small package upgrade etc.). I think
> the linux kernel is the only show stopper a.t.m...
> 
> IIRC Gilles has done the upgrade locally but didn't commit it yet!?
> 
> @Gilles can you commit your changes? If I'm wrong and the upgrade still needs to
> be done, I would take the challenge if no one else steps in (may need some help
> at some point how to configure new/changed linux config options).
> 
> Achim
> 
Sorry, I had not enought free time since some weeks. 
I will try to do that this week (actually recompiling with 3.4.50)
I have too a few other netfilter* upgrade related to 3.4 kernel.

The other points I remember are:
- NetAddr-IP upgrade, the version we use is no more available for download. While looking there, I find that we use the pure perl code (PP*) while using the .so should be faster. I made the change on include files and some others related to the upgrade but I haven't tested yet running with the new selected files list.

- openswan: upgrade to 2.6.39 and dropt debian patches as nothing new appear.
 Need to revert the ipsec verify move from perl to python
 https://github.com/xelerance/Openswan/commit/42a64529a904697972a914a250d65a329cc037eb
 Another solution may emerge later.

Gilles 




> 
> 
> > How is progress? What's left to do before we can release 2.1?
> > 
> > Eric
> > 
> > 
> > 
> > On 1 June 2013 14:08, Eric Oberlander <eri...@gm...>
> > wrote:
> > 
> >> Thanks Achim
> >>
> >> Eric
> >>
> >>
> >> On 1 June 2013 12:17, Achim Weber <dot...@gm...> wrote:
> >>
> >>> Hi Eric
> >>>
> >>> it is working again, there was a file missing in rootfiles...
> >>>
> >>> Achim
> >>>
> >>>
> >>>> 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
> >>>>>>
> >>>>
> >>>>
> >>>>
> >>> ------------------------------------------------------------------------------
> >>>> Get 100% visibility into Java/.NET code with AppDynamics Lite
> >>>> It's a free troubleshooting tool designed for production
> >>>> Get down to code-level detail for bottlenecks, with <2%
> >>>> overhead.
> >>>> Download for free and get started troubleshooting in minutes.
> >>>> http://p.sf.net/sfu/appdyn_d2d_ap2
> >>>> _______________________________________________
> >>>> IPCop-devel mailing list
> >>>> IPC...@li...
> >>>> https://lists.sourceforge.net/lists/listinfo/ipcop-devel
> >>>
> >>>
> >>
> > 
> > 
> > 
> > ------------------------------------------------------------------------------
> > This SF.net email is sponsored by Windows:
> > 
> > Build for Windows Store.
> > 
> > http://p.sf.net/sfu/windows-dev2dev
> > 
> > 
> > 
> > _______________________________________________
> > IPCop-devel mailing list
> > IPC...@li...
> > https://lists.sourceforge.net/lists/listinfo/ipcop-devel
> > 
> 
> 

I think the biggest missing part is the linux kernel upgrade to 3.4. Other than
that are only minor stuff (maybe small package upgrade etc.). I think the linux
kernel is the only show stopper a.t.m...

IIRC Gilles has done the upgrade locally but didn't commit it yet!?

@Gilles can you commit your changes? If I'm wrong and the upgrade still needs to
be done, I would take the challenge if no one else steps in (may need some help
at some point how to configure new/changed linux config options).

Achim



> How is progress? What's left to do before we can release 2.1?
> 
> Eric
> 
> 
> 
> On 1 June 2013 14:08, Eric Oberlander <eri...@gm...> wrote:
> 
>> Thanks Achim
>>
>> Eric
>>
>>
>> On 1 June 2013 12:17, Achim Weber <dot...@gm...> wrote:
>>
>>> Hi Eric
>>>
>>> it is working again, there was a file missing in rootfiles...
>>>
>>> Achim
>>>
>>>
>>>> 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
>>>>>>
>>>>
>>>>
>>>>
>>> ------------------------------------------------------------------------------
>>>> Get 100% visibility into Java/.NET code with AppDynamics Lite
>>>> It's a free troubleshooting tool designed for production
>>>> Get down to code-level detail for bottlenecks, with <2% overhead.
>>>> Download for free and get started troubleshooting in minutes.
>>>> http://p.sf.net/sfu/appdyn_d2d_ap2
>>>> _______________________________________________
>>>> IPCop-devel mailing list
>>>> IPC...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/ipcop-devel
>>>
>>>
>>
> 
> 
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
> 
> Build for Windows Store.
> 
> http://p.sf.net/sfu/windows-dev2dev
> 
> 
> 
> _______________________________________________
> IPCop-devel mailing list
> IPC...@li...
> https://lists.sourceforge.net/lists/listinfo/ipcop-devel
> 

How is progress? What's left to do before we can release 2.1?

Eric



On 1 June 2013 14:08, Eric Oberlander <eri...@gm...> wrote:

> Thanks Achim
>
> Eric
>
>
> On 1 June 2013 12:17, Achim Weber <dot...@gm...> wrote:
>
>> Hi Eric
>>
>> it is working again, there was a file missing in rootfiles...
>>
>> Achim
>>
>>
>> > 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
>> > > >
>> >
>> >
>> >
>> ------------------------------------------------------------------------------
>> > Get 100% visibility into Java/.NET code with AppDynamics Lite
>> > It's a free troubleshooting tool designed for production
>> > Get down to code-level detail for bottlenecks, with <2% overhead.
>> > Download for free and get started troubleshooting in minutes.
>> > http://p.sf.net/sfu/appdyn_d2d_ap2
>> > _______________________________________________
>> > IPCop-devel mailing list
>> > IPC...@li...
>> > https://lists.sourceforge.net/lists/listinfo/ipcop-devel
>>
>>
>

Hi Tom,
On 12.06.2013 18:51, Tom Eichstaedt wrote:
> Am 11.06.2013 21:32, schrieb Guenter:
>> its a pity that you only post bugs to the list but no feature requests
>> :-(
>>
>> therefore I want to bring this to your attention:
>> http://sourceforge.net/p/ipcop/feature-requests/533/
>> its really a simple patch, but improves proxy logging a lot ...
>> please consider to add this to the next release.
>>
>> Günter.
> Hi Günter,
>
> see SVN rev. 6369: (Add username to proxy log view).
> http://marc.info/?l=ipcop-svn&m=132960208823118&w=2
>
> This works for me since 2012-02-18.
ah yes - looks very close to what I've hacked up;
so what's then the reason that this commit didnt make it into any 2.0.x 
release??

Günter.

Am 11.06.2013 21:32, schrieb Guenter:
> Hi all,
> its a pity that you only post bugs to the list but no feature requests :-(
>
> therefore I want to bring this to your attention:
> http://sourceforge.net/p/ipcop/feature-requests/533/
> its really a simple patch, but improves proxy logging a lot ...
> please consider to add this to the next release.
>
> Günter.
Hi Günter,

see SVN rev. 6369: (Add username to proxy log view).
http://marc.info/?l=ipcop-svn&m=132960208823118&w=2

This works for me since 2012-02-18.

Cheers Tom.

Hi all,
its a pity that you only post bugs to the list but no feature requests :-(

therefore I want to bring this to your attention:
http://sourceforge.net/p/ipcop/feature-requests/533/
its really a simple patch, but improves proxy logging a lot ...
please consider to add this to the next release.

Günter.

On 06/06/2013 04:43 AM, David W Studeman wrote:
> On 06/05/2013 10:43 PM, Achim Weber wrote:
>> Hi David
>>
>>>     Somewhere past r7050, the builds will no longer init on either a 586
>>> or 686 machine here. The kernel loads fine and then it hangs
>>> indefinitely at the init into runlevel 3, it is clear from the console
>>> that nothing in rc.sysinit ever happens. I'm trying to narrow it down. I
>>> am building 7051 after cleaning to see if it boots, 7050 definitely
>>> does. I'm thinking 7052 is where I'll run into trouble but we'll see in
>>> a few hours. For reference, the 586 is an AMD K6-2 and the 686 is a
>>> Pentium 3 Coppermine.
>>
>> Did you (re-)build a new toolchain?
>>
>> Achim
>>
>
> Doing that now.
>

For whatever reason, rebuilding the toolchain and doing a clean build 
left me with a bootable system this time. Previously the culprit was 
lack of executable files in /etc/rc.d and /etc/ppp which Eric pointed 
out in rc.d. Much ado over nothing on my part?

Thanks for the suggestion!

-- 
Dave Studeman
http://www.raqcop.com

On 06/06/2013 12:27 AM, Eric Oberlander wrote:
> Hi David
>
> I had a similar problem, and traced it to the permissions of some of the
> files in /etc/rc.d/
> Basically the files from the upgrade .tgz didn't have execute permissions.
>
> I had to login as root, remount the root partition and chmod +x the
> files affected (such as rc.sysinit) before I could boot again.
>
> I think the problem was caused when I did a partial rebuild, and used
> the upgrade tgz from that. The problem fixed itself after a make clean &
> build.
>
> HTH
>
> Eric
>
Mine was a clean install but it was a permissions issue in /etc/rc.d. 
Once I got it to boot, I also had to fix the permissions in /etc/ppp to 
get that particular box to dial the 3G Modem.


-- 
Dave Studeman
http://www.raqcop.com

On 06/05/2013 10:43 PM, Achim Weber wrote:
> Hi David
>
>>    Somewhere past r7050, the builds will no longer init on either a 586
>> or 686 machine here. The kernel loads fine and then it hangs
>> indefinitely at the init into runlevel 3, it is clear from the console
>> that nothing in rc.sysinit ever happens. I'm trying to narrow it down. I
>> am building 7051 after cleaning to see if it boots, 7050 definitely
>> does. I'm thinking 7052 is where I'll run into trouble but we'll see in
>> a few hours. For reference, the 586 is an AMD K6-2 and the 686 is a
>> Pentium 3 Coppermine.
>
> Did you (re-)build a new toolchain?
>
> Achim
>

Doing that now.

-- 
Dave Studeman
http://www.raqcop.com

Hi David

I had a similar problem, and traced it to the permissions of some of the
files in /etc/rc.d/
Basically the files from the upgrade .tgz didn't have execute permissions.

I had to login as root, remount the root partition and chmod +x the files
affected (such as rc.sysinit) before I could boot again.

I think the problem was caused when I did a partial rebuild, and used the
upgrade tgz from that. The problem fixed itself after a make clean & build.

HTH

Eric


On 6 June 2013 03:18, David W Studeman <da...@da...> wrote:

>   Somewhere past r7050, the builds will no longer init on either a 586
> or 686 machine here. The kernel loads fine and then it hangs
> indefinitely at the init into runlevel 3, it is clear from the console
> that nothing in rc.sysinit ever happens. I'm trying to narrow it down. I
> am building 7051 after cleaning to see if it boots, 7050 definitely
> does. I'm thinking 7052 is where I'll run into trouble but we'll see in
> a few hours. For reference, the 586 is an AMD K6-2 and the 686 is a
> Pentium 3 Coppermine.
> --
> Dave Studeman
> http://www.raqcop.com
>
>
>
> ------------------------------------------------------------------------------
> How ServiceNow helps IT people transform IT departments:
> 1. A cloud service to automate IT design, transition and operations
> 2. Dashboards that offer high-level views of enterprise services
> 3. A single system of record for all IT processes
> http://p.sf.net/sfu/servicenow-d2d-j
> _______________________________________________
> IPCop-devel mailing list
> IPC...@li...
> https://lists.sourceforge.net/lists/listinfo/ipcop-devel
>

Hi David

>   Somewhere past r7050, the builds will no longer init on either a 586 
> or 686 machine here. The kernel loads fine and then it hangs 
> indefinitely at the init into runlevel 3, it is clear from the console 
> that nothing in rc.sysinit ever happens. I'm trying to narrow it down. I 
> am building 7051 after cleaning to see if it boots, 7050 definitely 
> does. I'm thinking 7052 is where I'll run into trouble but we'll see in 
> a few hours. For reference, the 586 is an AMD K6-2 and the 686 is a 
> Pentium 3 Coppermine.

Did you (re-)build a new toolchain?

Achim

  Somewhere past r7050, the builds will no longer init on either a 586 
or 686 machine here. The kernel loads fine and then it hangs 
indefinitely at the init into runlevel 3, it is clear from the console 
that nothing in rc.sysinit ever happens. I'm trying to narrow it down. I 
am building 7051 after cleaning to see if it boots, 7050 definitely 
does. I'm thinking 7052 is where I'll run into trouble but we'll see in 
a few hours. For reference, the 586 is an AMD K6-2 and the 686 is a 
Pentium 3 Coppermine.
-- 
Dave Studeman
http://www.raqcop.com

---------- Forwarded message ----------
From: SourceForge.net <nor...@in...>
Date: 2013/6/5
Subject: SourceForge Project Upgrade - Code Repo Complete
To: no...@in...


Your svn repository in upgraded project ipcop is now ready for use.

Old repository url: http://ipcop.svn.sourceforge.net/svnroot/ipcop

New repository checkout command: svn checkout --username=riddles svn+ssh://
ri...@sv.../p/ipcop/svn/ ipcop-svn

You should do a checkout using the new repository location.  The old
repository is read-only now.

For more detailed instructions on migrating to your new repo, please see
https://sourceforge.net/p/forge/community-docs/Repository%20Upgrade%20FAQ/

--
SourceForge.net has sent this mailing to you as a registered user of
the SourceForge.net site to convey important information regarding
your SourceForge.net account or your use of SourceForge.net services.
If you have concerns about this mailing please contact our Support
team per: http://sourceforge.net/support

---------- Forwarded message ----------
From: SourceForge.net <nor...@in...>
Date: 2013/6/5
Subject: SourceForge Project Upgrade Notification
To: no...@in...


Dear SourceForge Project Developer,

As you probably know, we've been talking for several months about the
imminent upgrade of the SourceForge developer platform. A few weeks ago we
announced (http://sourceforge.net/blog/upgrades-april22/) that starting
April 22, we would be upgrading all projects that had not yet done so on
their own. That time has arrived.

We wanted to let you know that we've upgraded your project, IPCop Firewall,
to the new SourceForge developer platform. The next time you log in, things
will look a little different.

The new platform, codenamed "Allura", is a rewrite and redesign of the Open
Source development tool set. It provides tighter integration between the
various tools to give you a better developer experience. Allura is a
project in incubation at the Apache Software Foundation, where people from
many different companies are collaborating to make it even better. (
http://incubator.apache.org/allura/)

Your source code repositories are currently being migrated to the new
setup. You will receive another email when that import is complete. That
means that you and any other developers should do a fresh checkout using
the new repository location when it is ready (see the "code" tab). Please
be aware that large repositories may take a long time.

Have a look around your project, at http://sourceforge.net/projects/ipcop/,
and tell us what you think. Let us know if there's anything we can do to
make your SourceForge experience better. There's lots of ways to get in
touch. You can email us at com...@so..., on IRC at
#sourceforge on Freenode, on our Facebook page at
http://facebook.com/SourceForgeNet, on our Google Plus community at
https://plus.google.com/communities/108980648585760076156, or via Twitter
at @sourceforge.

--
SourceForge.net has sent this mailing to you as a registered user of the
SourceForge.net site to convey important information regarding your
SourceForge.net account or your use of SourceForge.net services. If you
have concerns about this mailing please contact our Support team per:
http://sourceforge.net/support

Thanks Achim

Eric


On 1 June 2013 12:17, Achim Weber <dot...@gm...> wrote:

> Hi Eric
>
> it is working again, there was a file missing in rootfiles...
>
> Achim
>
>
> > 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
> > > >
> >
> >
> >
> ------------------------------------------------------------------------------
> > Get 100% visibility into Java/.NET code with AppDynamics Lite
> > It's a free troubleshooting tool designed for production
> > Get down to code-level detail for bottlenecks, with <2% overhead.
> > Download for free and get started troubleshooting in minutes.
> > http://p.sf.net/sfu/appdyn_d2d_ap2
> > _______________________________________________
> > IPCop-devel mailing list
> > IPC...@li...
> > https://lists.sourceforge.net/lists/listinfo/ipcop-devel
>
>

Hi Eric

it is working again, there was a file missing in rootfiles...

Achim


> 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
> > >
> 
> 
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite
> It's a free troubleshooting tool designed for production
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://p.sf.net/sfu/appdyn_d2d_ap2
> _______________________________________________
> IPCop-devel mailing list
> IPC...@li...
> https://lists.sourceforge.net/lists/listinfo/ipcop-devel