IPFire 2.13 - Testers wanted!

Help on building IPFire & Feature Requests
User avatar
Arne.F
Core Developer
Core Developer
Posts: 8522
Joined: May 7th, 2006, 8:57 am
Location: BS <-> NDH
Contact:

Re: IPFire 2.13 - Testers wanted!

Post by Arne.F » February 11th, 2013, 12:17 pm

Where can I find a backup? My own backup already contains the new version.

Backup is in /var/ipfire/backup/core...

But keep in mind that the grub is completly new, don't restore the backup, this will not boot because the kernel was changed.

There are only two entries after installation of the Update to 2.13 and a third with the pae kernel if pae is supported. The saved value was set to pae kernel. You should also use the pae if your board support it because some security features are only present in this kernel.

We suggest to not change the "default saved" in the grub.conf because we use this on kernel updates or feature changes add new pae-kernel.

If you want to force a kernel remotely change the save value to the new kernel
with "grub-set-default x" before you reboot.
Arne

Support the project on the donation!

Image

Image

Image
PS: I will not answer support questions via email and ignore IPFire related messages on my non IPFire.org mail addresses.

bluezone
Posts: 20
Joined: September 27th, 2011, 4:17 pm

Re: IPFire 2.13 - Testers wanted!

Post by bluezone » February 11th, 2013, 1:11 pm

Okay, this is getting strange.  On a wild hair, I changed the udev.conf file to info instead of err for logging by udev.  Now, when I reboot, it seems to be finding both the green and red interfaces reliably under Hyper-V.  Is there something different in the way it finds hardware based on the logging option?

User avatar
larsen
Posts: 426
Joined: May 4th, 2012, 9:36 am

Re: IPFire 2.13 - Testers wanted!

Post by larsen » February 11th, 2013, 1:38 pm

@Arne: thx!

I only need some files from /etc so no worry about grub.conf. However, is there a way to find out if my machine supports PAE without test-booting the PAE kernel?

User avatar
Arne.F
Core Developer
Core Developer
Posts: 8522
Joined: May 7th, 2006, 8:57 am
Location: BS <-> NDH
Contact:

Re: IPFire 2.13 - Testers wanted!

Post by Arne.F » February 11th, 2013, 4:37 pm

The core2.13 setup does this for you.
The default will only set to pae if the cpu support it.

The cpu support flags can read from /proc/cpuinfo
Arne

Support the project on the donation!

Image

Image

Image
PS: I will not answer support questions via email and ignore IPFire related messages on my non IPFire.org mail addresses.

User avatar
Arne.F
Core Developer
Core Developer
Posts: 8522
Joined: May 7th, 2006, 8:57 am
Location: BS <-> NDH
Contact:

Re: IPFire 2.13 - Testers wanted!

Post by Arne.F » February 11th, 2013, 4:41 pm

Okay, this is getting strange.  On a wild hair, I changed the udev.conf file to info instead of err for logging by udev.  Now, when I reboot, it seems to be finding both the green and red interfaces reliably under Hyper-V.  Is there something different in the way it finds hardware based on the logging option?

should not... It is only a bit slower because he has to write the log entries.
Arne

Support the project on the donation!

Image

Image

Image
PS: I will not answer support questions via email and ignore IPFire related messages on my non IPFire.org mail addresses.

User avatar
larsen
Posts: 426
Joined: May 4th, 2012, 9:36 am

Re: IPFire 2.13 - Testers wanted!

Post by larsen » February 11th, 2013, 5:21 pm

Arne.F wrote:The cpu support flags can read from /proc/cpuinfo


Thx! Got it:
grep pae /proc/cpuinfo

User avatar
Huginn
Posts: 30
Joined: October 18th, 2012, 12:00 pm
Location: /Absurdistan/Budapest

Re: IPFire 2.13 - Testers wanted!

Post by Huginn » February 11th, 2013, 9:17 pm

IPFire 2.13 - RC2 is out. (When?) How can I upgrade the RC1 to this version? I need only some time, to get the Pakfire lists are refreshed at your server?
Image

User avatar
larsen
Posts: 426
Joined: May 4th, 2012, 9:36 am

Re: IPFire 2.13 - Testers wanted!

Post by larsen » February 11th, 2013, 10:28 pm


User avatar
Huginn
Posts: 30
Joined: October 18th, 2012, 12:00 pm
Location: /Absurdistan/Budapest

Re: IPFire 2.13 - Testers wanted!

Post by Huginn » February 11th, 2013, 10:37 pm

I seen that. That's how I upgrade from 2.11 to 2.13-RC1 few day ago... But how I can upgrade IPFire from RC1 to RC2? :-]
Image

User avatar
larsen
Posts: 426
Joined: May 4th, 2012, 9:36 am

Re: IPFire 2.13 - Testers wanted!

Post by larsen » February 11th, 2013, 10:56 pm

Same way =)

User avatar
Huginn
Posts: 30
Joined: October 18th, 2012, 12:00 pm
Location: /Absurdistan/Budapest

Re: IPFire 2.13 - Testers wanted!

Post by Huginn » February 11th, 2013, 11:17 pm

Hm... Because the "pakfire update/upgrade" command by itself isn't enough. Thanks! :-]
Last edited by Huginn on February 11th, 2013, 11:26 pm, edited 1 time in total.
Image

axel2078
Posts: 294
Joined: January 30th, 2013, 3:53 am
Location: IL, USA

IPFire 2.13 - Testers wanted!

Post by axel2078 » February 12th, 2013, 1:05 am

dani wrote:IDS Log and Content Filter Log not working, Thanks  :-[


It doesn't work for me in 2.11 either.
Image

User avatar
Arne.F
Core Developer
Core Developer
Posts: 8522
Joined: May 7th, 2006, 8:57 am
Location: BS <-> NDH
Contact:

Re: IPFire 2.13 - Testers wanted!

Post by Arne.F » February 12th, 2013, 8:41 am

It doesn't work for me in 2.11 either.

Have you enabled IDS and Content Filter with log. If not there is nothing to display.
Arne

Support the project on the donation!

Image

Image

Image
PS: I will not answer support questions via email and ignore IPFire related messages on my non IPFire.org mail addresses.

zeero
Posts: 13
Joined: October 18th, 2011, 2:57 pm

Re: QOS & codel

Post by zeero » February 12th, 2013, 2:52 pm

MichaelTremer wrote:Hey Zee,

thanks for helping testing. Indeed your situation should improve when you are using CoDel. However, this looks more like the buffers on your ISP's site are full. For DSL this is sitting in the DSLAM.

When you are sending out an ICMP Echo Request for example the reply packet is sent to you, but when it reaches the DSLAM it gets queued, because the DSLAM throttles your connection.

This is a more general problem called "Bufferbloat" and can be fixed with CoDel for example, but not on your site. The ISP is the one who has to fix that.

A solution would be to throttle your internet connection to ~90% so the buffers on the ISP's site won't ever fill up.

Michael


Thanks for including codel support in IPFire  ;D
After further testing I am seeing definite improvements with codel. Two questions: should the "txqueuelen" in advanced settings be reduced from 30 packets? Secondly, I understand my modem may also face the same issues with Bufferbloat, are you aware of any ADSL modem vendors that provide codel support or smaller buffers?

Cheers
Zee

User avatar
Arne.F
Core Developer
Core Developer
Posts: 8522
Joined: May 7th, 2006, 8:57 am
Location: BS <-> NDH
Contact:

Re: IPFire 2.13 - Testers wanted!

Post by Arne.F » February 13th, 2013, 5:55 pm

should the "txqueuelen" in advanced settings be reduced from 30 packets?

No. This is left from QoS without codel... Thanks for the hint.
Arne

Support the project on the donation!

Image

Image

Image
PS: I will not answer support questions via email and ignore IPFire related messages on my non IPFire.org mail addresses.

Post Reply