But seriously: please keep calm, nobody said we will never support it
We currently working on a V4 version with full PI/AMD K6 support, but it will definitley not included in 4.000 because of some lib dependences. Please check regular the announcement forum for news and release dates for a PI/K6 enabled V4.
It's good to hear that K6's will be supported, I was just about to post on the hackers forum "how can I slipstream my own kernel into ASL"
Dumb question: I am running ASL 3.2 up2date'ing it's little heart out, will I reboot one day and find it won't get back on its feet? Or is everyone talking about ASL v4?
Dumb Question #2: When v4 is ready to support K6-2's will I need to reconfigure my whole system, or can it just upgrade, also will my existing home liscence grandfathered over or do I need to get another?
PS[:D]on't forget the little guy astaro it's the linux way to be efficient as possible and with my 3 computer network my K6-2 200MHz is 90-99% too much CPU already.
Due to some strange behavior of my old ASL 3.2 instalation I decided to upgrade our company ASL box to version 4.107. Eventhough it is not recomanded to use Beta versions in working production enviroment I made it on purposse to see the difference.
Since 3 days I had no problem with NICs, so new NIC kernel drivers are working OK. Users are working without any problem. Restore of configuration from 3.218 worked as it gets!
With version 3.2 I had in the night when logs were written, quite some problems and I always got up to 7 mails about process taking to much memory. Now those mails are gone, eventhough nothing changed on network.
At the end I have to say that version 4.107 is working for me without problem at full rate and can be easily used.
thx for your reports! However there is a Up2Date available (4.108, 6.8 MBytes) - in contrast to our last announcement we need this Up2Date to replace the kernel with a new one:
REMARKS
* Required previous version is 4.107 * Existing configuration will not be changed * Firewall will reboot!
NEW/CHANGED/IMPROVED - new kernel with routing cache hash fix (CAN-2003-0244)
No, the current thread concerns ASL 4.107 and 4.108, which both are BETA. And yes; it supports several types of processors that the current 4.x release doesn't.
I just discovered that if I enable QoS for an interface and, say, three rules exists and are enabled, the rules will not show up in "Current quality of service rules" before I've disabled/re-enabled one of the rules.
Is this by design or is it a bug (f***, I hate using that expression ;-)?
I just discovered that if I enable QoS for an interface and, say, three rules exists and are enabled, the rules will not show up in "Current quality of service rules" before I've disabled/re-enabled one of the rules.
Is this by design or is it a bug (f***, I hate using that expression ;-)?
