Re: Progress on 2.1

----- Mail original -----
> De: "Achim Weber" <[email protected]>
> À: "Eric Oberlander" <[email protected]>, "IPCop devel" <[email protected]>, "Gilles
> Espinasse" <[email protected]>, "Olaf Westrik (ipcop-forum)" <[email protected]>
> 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 <[email protected]>
> > wrote:
> > 
> >> Thanks Achim
> >>
> >> Eric
> >>
> >>
> >> On 1 June 2013 12:17, Achim Weber <[email protected]> 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 <[email protected]> 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
> >>>>>> [email protected]
> >>>>>> 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
> >>>> [email protected]
> >>>> 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
> > [email protected]
> > 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
[email protected]
https://lists.sourceforge.net/lists/listinfo/ipcop-devel