Hello followers,
at first I have to thanks to all of you which have joined the guardian 2.0 testing team. I've got a lot of positive feedback but also has been noticed about several tiny issues.
I've uploaded an updated test version to http://people.ipfire.org/~stevee/guardian-2.0/.
The installation / update works in the same way as described in the planet post: http://planet.ipfire.org/post/introducing-guardian-2-0-for-ipfire
IMPORTANT: Please create a backup of your files stored in "/var/ipfire/guardian/", otherwise the will be overwritten by the update!
Changelog:
* Matthias Fischer detected some small problems in the "guardian.cgi" and provided some patches for them. http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=19d6abcce57... http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=0a6c3cb8964... http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=82208c83c70...
* Blago Culjak informed me about problems on starting guardian and displaying it's status in the web interface. This behaviour only happens when the legacy version of guardian has been un-installed and not just replaced by the guardian. In the updated version contains the required file which is used by various IPFire scripts to detect if an addon is installed or not.
* The CLI switch "-d" called "debug mode" has been replaced by "-f" to launch guardian and run it in the foreground. http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=a58bd674863...
* Some new code has been added to prevent from starting multiple instances of guardian. http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=9d44c0d9952...
Best regards,
-Stefan
That's better. I was wondering what was happening when I started Guardian 2 and it didn't show as started. Thanks.
On Sat, Feb 28, 2015 at 8:50 AM, Stefan Schantl stefan.schantl@ipfire.org wrote:
Hello followers,
at first I have to thanks to all of you which have joined the guardian 2.0 testing team. I've got a lot of positive feedback but also has been noticed about several tiny issues.
I've uploaded an updated test version to http://people.ipfire.org/~stevee/guardian-2.0/.
The installation / update works in the same way as described in the planet post: http://planet.ipfire.org/post/introducing-guardian-2-0-for-ipfire
IMPORTANT: Please create a backup of your files stored in "/var/ipfire/guardian/", otherwise the will be overwritten by the update!
Changelog:
- Matthias Fischer detected some small problems in the "guardian.cgi"
and provided some patches for them.
http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=19d6abcce57... http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=0a6c3cb8964... http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=82208c83c70...
- Blago Culjak informed me about problems on starting guardian and
displaying it's status in the web interface. This behaviour only happens when the legacy version of guardian has been un-installed and not just replaced by the guardian. In the updated version contains the required file which is used by various IPFire scripts to detect if an addon is installed or not.
- The CLI switch "-d" called "debug mode" has been replaced by "-f" to
launch guardian and run it in the foreground.
http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=a58bd674863...
- Some new code has been added to prevent from starting multiple
instances of guardian.
http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=9d44c0d9952...
Best regards,
-Stefan
Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
Hello Stefan, I have updated, now seems fine. Will do even more testing in days to come.
I have two suggestions, one for community, other is for features in new version:
1. I think that you should rename Guardian 2.0 to Intrusion Prevention. Lots of people don't know (outside Linux world) about this package, but they do know Intrusion Preventon, what stands for. This is unique feature of IPFire, and should be considered like that. Ofcourse, give credit to orginal Guardian. This is entirly up to Michael and Project leaders, but I think this is great feature, that must be better promoted.
Hey, IPFire has Guardian 2.0. What the hell is that?
or
Hey, IPFire has Intrusion Prevention. Ooo,nice...
See what I mean?
2. Stefan, I have asked you, and I will try again. Can we make guardian even more better then just Intrusion Prevention? Can you block bad IP's that are destined from our network? Please have a look at the thread on forum. http://forum.ipfire.org/viewtopic.php?f=52&t=12639
Regards
Subject: Guardian 2.0 Testversion 011 From: stefan.schantl@ipfire.org To: development@lists.ipfire.org Date: Sat, 28 Feb 2015 14:50:35 +0100
Hello followers,
at first I have to thanks to all of you which have joined the guardian 2.0 testing team. I've got a lot of positive feedback but also has been noticed about several tiny issues.
I've uploaded an updated test version to http://people.ipfire.org/~stevee/guardian-2.0/.
The installation / update works in the same way as described in the planet post: http://planet.ipfire.org/post/introducing-guardian-2-0-for-ipfire
IMPORTANT: Please create a backup of your files stored in "/var/ipfire/guardian/", otherwise the will be overwritten by the update!
Changelog:
* Matthias Fischer detected some small problems in the "guardian.cgi" and provided some patches for them. http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=19d6abcce57... http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=0a6c3cb8964... http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=82208c83c70...
* Blago Culjak informed me about problems on starting guardian and displaying it's status in the web interface. This behaviour only happens when the legacy version of guardian has been un-installed and not just replaced by the guardian. In the updated version contains the required file which is used by various IPFire scripts to detect if an addon is installed or not.
* The CLI switch "-d" called "debug mode" has been replaced by "-f" to launch guardian and run it in the foreground. http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=a58bd674863...
* Some new code has been added to prevent from starting multiple instances of guardian. http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=9d44c0d9952...
Best regards,
-Stefan
_______________________________________________ Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
Hello Blago Culjak,
Hello Stefan, I have updated, now seems fine. Will do even more testing in days to come.
I have two suggestions, one for community, other is for features in new version:
- I think that you should rename Guardian 2.0 to Intrusion
Prevention. Lots of people don't know (outside Linux world) about this package, but they do know Intrusion Preventon, what stands for. This is unique feature of IPFire, and should be considered like that. Ofcourse, give credit to orginal Guardian. This is entirly up to Michael and Project leaders, but I think this is great feature, that must be better promoted.
Hey, IPFire has Guardian 2.0. What the hell is that?
or
Hey, IPFire has Intrusion Prevention. Ooo,nice...
See what I mean?
The decision was to keep the old name to give tribute to this really great piece of software. The legacy version of guardian has been introduced more than a decade ago. So I think the term "guardian" is well known in the certain group of people which currently are using (or have used) one of the various free and open firewall solutions out there. Renaming the software to a different name will break those recognition.
I don't agree in using a name like "IPS" or a similar one would help anybody in the decision to use the software or not, nor to promote it.
- Stefan, I have asked you, and I will try again. Can we make
guardian even more better then just Intrusion Prevention? Can you block bad IP's that are destined from our network? Please have a look at the thread on forum. http://forum.ipfire.org/viewtopic.php?f=52&t=12639
This is not really a guardian related issue, it affects the intrusion detection system. Snort is currently not configured to monitor the traffic inside the network zones or between them.
This will be one of the next points on my personal "todo-list" and guardian 2.0 was just on of the first steps of extending IDS/IPS on IPFire.
Best regards,
-Stefan
Regards
Subject: Guardian 2.0 Testversion 011 From: stefan.schantl@ipfire.org To: development@lists.ipfire.org Date: Sat, 28 Feb 2015 14:50:35 +0100
Hello followers,
at first I have to thanks to all of you which have joined the guardian 2.0 testing team. I've got a lot of positive feedback but also has been noticed about several tiny issues.
I've uploaded an updated test version to http://people.ipfire.org/~stevee/guardian-2.0/.
The installation / update works in the same way as described in the planet post: http://planet.ipfire.org/post/introducing-guardian-2-0-for-ipfire
IMPORTANT: Please create a backup of your files stored in "/var/ipfire/guardian/", otherwise the will be overwritten by the update!
Changelog:
- Matthias Fischer detected some small problems in the "guardian.cgi"
and provided some patches for them. http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=19d6abcce57... http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=0a6c3cb8964... http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=82208c83c70...
- Blago Culjak informed me about problems on starting guardian and
displaying it's status in the web interface. This behaviour only happens when the legacy version of guardian has been un-installed and not just replaced by the guardian. In the updated version contains the required file which is used by various IPFire scripts to detect if an addon is installed or not.
- The CLI switch "-d" called "debug mode" has been replaced by "-f" to
launch guardian and run it in the foreground. http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=a58bd674863...
- Some new code has been added to prevent from starting multiple
instances of guardian. http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=9d44c0d9952...
Best regards,
-Stefan
_______________________________________________ Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
Hello again,
as promised I recently have upload an updated testversion for guardian 2.0. As usual it can be obtained from http://people.ipfire.org/~stevee/guardian-2.0/
The installation / update works in the same way as described in the planet post: http://planet.ipfire.org/post/introducing-guardian-2-0-for-ipfire
IMPORTANT: You MUST NOT install/update the new version as long as you are using IPFire 2 - Core 89 or an older version!
Please also create a backup of your files stored in "/var/ipfire/guardian/", otherwise the will be overwritten by the update!
Changelog:
* This version only contains updated language and system files for core update 90 and upcomming releases.
Best regards,
-Stefan
Hello followers,
at first I have to thanks to all of you which have joined the guardian 2.0 testing team. I've got a lot of positive feedback but also has been noticed about several tiny issues.
I've uploaded an updated test version to http://people.ipfire.org/~stevee/guardian-2.0/.
The installation / update works in the same way as described in the planet post: http://planet.ipfire.org/post/introducing-guardian-2-0-for-ipfire
IMPORTANT: Please create a backup of your files stored in "/var/ipfire/guardian/", otherwise the will be overwritten by the update!
Changelog:
- Matthias Fischer detected some small problems in the "guardian.cgi"
and provided some patches for them. http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=19d6abcce57... http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=0a6c3cb8964... http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=82208c83c70...
- Blago Culjak informed me about problems on starting guardian and
displaying it's status in the web interface. This behaviour only happens when the legacy version of guardian has been un-installed and not just replaced by the guardian. In the updated version contains the required file which is used by various IPFire scripts to detect if an addon is installed or not.
- The CLI switch "-d" called "debug mode" has been replaced by "-f" to
launch guardian and run it in the foreground. http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=a58bd674863...
- Some new code has been added to prevent from starting multiple
instances of guardian. http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=9d44c0d9952...
Best regards,
-Stefan
Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
Hello again,
as promised I recently have uploaded a new test version of guardian 2.0.
It mainly contains updated language and system files to pay attention to the latest development efforts of IPFire core update 90.
As usual the new version can be downloaded from http://people.ipfire.org/~stevee/guardian-2.0/
The installation / update works in the same way as described in the planet post: http://planet.ipfire.org/post/introducing-guardian-2-0-for-ipfire
IMPORTANT: You MUST NOT install/update to the new version if you are using IPFire 2 - Core 89 or an older version!
Please also create a backup of your files stored in "/var/ipfire/guardian/", otherwise the will be overwritten by the update!
Best regards,
-Stefan
Hello followers,
at first I have to thanks to all of you which have joined the guardian 2.0 testing team. I've got a lot of positive feedback but also has been noticed about several tiny issues.
I've uploaded an updated test version to http://people.ipfire.org/~stevee/guardian-2.0/.
The installation / update works in the same way as described in the planet post: http://planet.ipfire.org/post/introducing-guardian-2-0-for-ipfire
IMPORTANT: Please create a backup of your files stored in "/var/ipfire/guardian/", otherwise the will be overwritten by the update!
Changelog:
- Matthias Fischer detected some small problems in the "guardian.cgi"
and provided some patches for them. http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=19d6abcce57... http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=0a6c3cb8964... http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=82208c83c70...
- Blago Culjak informed me about problems on starting guardian and
displaying it's status in the web interface. This behaviour only happens when the legacy version of guardian has been un-installed and not just replaced by the guardian. In the updated version contains the required file which is used by various IPFire scripts to detect if an addon is installed or not.
- The CLI switch "-d" called "debug mode" has been replaced by "-f" to
launch guardian and run it in the foreground. http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=a58bd674863...
- Some new code has been added to prevent from starting multiple
instances of guardian. http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=9d44c0d9952...
Best regards,
-Stefan
Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
Hello again,
as promised I recently have uploaded a new test version of guardian 2.0 (012).
It mainly contains updated language and system files to pay attention to the latest development efforts of IPFire core update 90.
As usual the new version can be downloaded from http://people.ipfire.org/~stevee/guardian-2.0/
The installation / update works in the same way as described in the planet post: http://planet.ipfire.org/post/introducing-guardian-2-0-for-ipfire
IMPORTANT: You MUST NOT install/update to the new version if you are using IPFire 2 - Core 89 or an older version!
Please also create a backup of your files stored in "/var/ipfire/guardian/", otherwise the will be overwritten by the update!
Best regards,
-Stefan
Hello followers,
at first I have to thanks to all of you which have joined the guardian 2.0 testing team. I've got a lot of positive feedback but also has been noticed about several tiny issues.
I've uploaded an updated test version to http://people.ipfire.org/~stevee/guardian-2.0/.
The installation / update works in the same way as described in the planet post: http://planet.ipfire.org/post/introducing-guardian-2-0-for-ipfire
IMPORTANT: Please create a backup of your files stored in "/var/ipfire/guardian/", otherwise the will be overwritten by the update!
Changelog:
- Matthias Fischer detected some small problems in the "guardian.cgi"
and provided some patches for them. http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=19d6abcce57... http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=0a6c3cb8964... http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=82208c83c70...
- Blago Culjak informed me about problems on starting guardian and
displaying it's status in the web interface. This behaviour only happens when the legacy version of guardian has been un-installed and not just replaced by the guardian. In the updated version contains the required file which is used by various IPFire scripts to detect if an addon is installed or not.
- The CLI switch "-d" called "debug mode" has been replaced by "-f" to
launch guardian and run it in the foreground. http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=a58bd674863...
- Some new code has been added to prevent from starting multiple
instances of guardian. http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=9d44c0d9952...
Best regards,
-Stefan
Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
Hi Stefan,
thx for updateing Guardian2. I use Core89 but the installversion 012 is done with internal error by update the cache lang - do you need more information? | #update-lang-cache
update-lang-cache Can't locate Locale/Codes/Country.pm in @INC (@INC contains: /usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi /usr/lib/perl5/site_perl/5.12.3 /usr/lib/perl5/5.12.3/i586-linux-thread-multi /usr/lib/perl5/5.12.3 .) at /var/ipfire/general-functions.pl line 20. BEGIN failed--compilation aborted at /var/ipfire/general-functions.pl line 20. Compilation failed in require at //var/ipfire/lang.pl line 12. Compilation failed in require at -e line 1.
| |The WUI say:|
||
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, root@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Apache/2.2.27 (Unix) mod_ssl/2.2.27 OpenSSL/1.0.1m PHP/5.3.27 Server at 192.168.XYZ.XYZ Port 444
||
||
On 10.05.2015 10:08, Stefan Schantl wrote:
Hello again,
as promised I recently have uploaded a new test version of guardian 2.0 (012).
It mainly contains updated language and system files to pay attention to the latest development efforts of IPFire core update 90.
As usual the new version can be downloaded from http://people.ipfire.org/~stevee/guardian-2.0/
The installation / update works in the same way as described in the planet post: http://planet.ipfire.org/post/introducing-guardian-2-0-for-ipfire
IMPORTANT: You MUST NOT install/update to the new version if you are using IPFire 2 - Core 89 or an older version!
Please also create a backup of your files stored in "/var/ipfire/guardian/", otherwise the will be overwritten by the update!
Best regards,
-Stefan
Hello followers,
at first I have to thanks to all of you which have joined the guardian 2.0 testing team. I've got a lot of positive feedback but also has been noticed about several tiny issues.
I've uploaded an updated test version to http://people.ipfire.org/~stevee/guardian-2.0/.
The installation / update works in the same way as described in the planet post: http://planet.ipfire.org/post/introducing-guardian-2-0-for-ipfire
IMPORTANT: Please create a backup of your files stored in "/var/ipfire/guardian/", otherwise the will be overwritten by the update!
Changelog:
- Matthias Fischer detected some small problems in the "guardian.cgi"
and provided some patches for them. http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=19d6abcce57... http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=0a6c3cb8964... http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=82208c83c70...
- Blago Culjak informed me about problems on starting guardian and
displaying it's status in the web interface. This behaviour only happens when the legacy version of guardian has been un-installed and not just replaced by the guardian. In the updated version contains the required file which is used by various IPFire scripts to detect if an addon is installed or not.
- The CLI switch "-d" called "debug mode" has been replaced by "-f" to
launch guardian and run it in the foreground. http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=a58bd674863...
- Some new code has been added to prevent from starting multiple
instances of guardian. http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=9d44c0d9952...
Best regards,
-Stefan
Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
Hi 5p9,
when you have installed the guardian 2.0 - 012 version on your IPFire system with core update 89 you have brick your system.
IMPORTANT: You MUST NOT install/update to the new version if you are using IPFire 2 - Core 89 or an older version!
If you still have access to it, downgrade guardian to version 011 or upgrade the system to core 90 and reinstall guardian 012 afterwards otherwise it will be really hard to get your system working again.
Best regards,
-Stefan
Hi Stefan,
thx for updateing Guardian2. I use Core89 but the installversion 012 is done with internal error by update the cache lang - do you need more information?
#update-lang-cache
update-lang-cache Can't locate Locale/Codes/Country.pm in @INC (@INC contains: /usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi /usr/lib/perl5/site_perl/5.12.3 /usr/lib/perl5/5.12.3/i586-linux-thread-multi /usr/lib/perl5/5.12.3 .) at /var/ipfire/general-functions.pl line 20. BEGIN failed--compilation aborted at /var/ipfire/general-functions.pl line 20. Compilation failed in require at //var/ipfire/lang.pl line 12. Compilation failed in require at -e line 1.
The WUI say:
Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, root@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log. Apache/2.2.27 (Unix) mod_ssl/2.2.27 OpenSSL/1.0.1m PHP/5.3.27 Server at 192.168.XYZ.XYZ Port 444
On 10.05.2015 10:08, Stefan Schantl wrote:
Hello again,
as promised I recently have uploaded a new test version of guardian 2.0 (012).
It mainly contains updated language and system files to pay attention to the latest development efforts of IPFire core update 90.
As usual the new version can be downloaded from http://people.ipfire.org/~stevee/guardian-2.0/
The installation / update works in the same way as described in the planet post: http://planet.ipfire.org/post/introducing-guardian-2-0-for-ipfire
IMPORTANT: You MUST NOT install/update to the new version if you are using IPFire 2 - Core 89 or an older version!
Please also create a backup of your files stored in "/var/ipfire/guardian/", otherwise the will be overwritten by the update!
Best regards,
-Stefan
Hello followers,
at first I have to thanks to all of you which have joined the guardian 2.0 testing team. I've got a lot of positive feedback but also has been noticed about several tiny issues.
I've uploaded an updated test version to http://people.ipfire.org/~stevee/guardian-2.0/.
The installation / update works in the same way as described in the planet post: http://planet.ipfire.org/post/introducing-guardian-2-0-for-ipfire
IMPORTANT: Please create a backup of your files stored in "/var/ipfire/guardian/", otherwise the will be overwritten by the update!
Changelog:
- Matthias Fischer detected some small problems in the "guardian.cgi"
and provided some patches for them. http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=19d6abcce57... http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=0a6c3cb8964... http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=82208c83c70...
- Blago Culjak informed me about problems on starting guardian and
displaying it's status in the web interface. This behaviour only happens when the legacy version of guardian has been un-installed and not just replaced by the guardian. In the updated version contains the required file which is used by various IPFire scripts to detect if an addon is installed or not.
- The CLI switch "-d" called "debug mode" has been replaced by "-f" to
launch guardian and run it in the foreground. http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=a58bd674863...
- Some new code has been added to prevent from starting multiple
instances of guardian. http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=commit;h=9d44c0d9952...
Best regards,
-Stefan
Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
Hi,
after downgrade 11er Version and update-lang-cache run my System normal.
And Guardian2 looks like good! Thx for your Work Stefan...very nice.
BG, 5p9
Am 12.05.2015 um 21:19 schrieb Stefan Schantl:
Hi 5p9,
when you have installed the guardian 2.0 - 012 version on your IPFire system with core update 89 you have brick your system.
IMPORTANT: You MUST NOT install/update to the new version if you are using IPFire 2 - Core 89 or an older version!
If you still have access to it, downgrade guardian to version 011 or upgrade the system to core 90 and reinstall guardian 012 afterwards otherwise it will be really hard to get your system working again.
Best regards,
-Stefan
Hi Stefan,
thx for updateing Guardian2. I use Core89 but the installversion 012 is done with internal error by update the cache lang - do you need more information?
#update-lang-cache
update-lang-cache Can't locate Locale/Codes/Country.pm in @INC (@INC contains: /usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi /usr/lib/perl5/site_perl/5.12.3 /usr/lib/perl5/5.12.3/i586-linux-thread-multi /usr/lib/perl5/5.12.3 .) at /var/ipfire/general-functions.pl line 20. BEGIN failed--compilation aborted at /var/ipfire/general-functions.pl line 20. Compilation failed in require at //var/ipfire/lang.pl line 12. Compilation failed in require at -e line 1.
The WUI say:
Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, root@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log. Apache/2.2.27 (Unix) mod_ssl/2.2.27 OpenSSL/1.0.1m PHP/5.3.27 Server at 192.168.XYZ.XYZ Port 444
On 10.05.2015 10:08, Stefan Schantl wrote:
Hello again,
as promised I recently have uploaded a new test version of guardian 2.0 (012).
It mainly contains updated language and system files to pay attention to the latest development efforts of IPFire core update 90.
As usual the new version can be downloaded from http://people.ipfire.org/~stevee/guardian-2.0/
The installation / update works in the same way as described in the planet post: http://planet.ipfire.org/post/introducing-guardian-2-0-for-ipfire
IMPORTANT: You MUST NOT install/update to the new version if you are
using IPFire 2 - Core 89 or an older version!
Please also create a backup of your files stored in "/var/ipfire/guardian/", otherwise the will be overwritten by the update!
Best regards,
-Stefan
Hi@all,
i have a question. My Fire has became the final Core-Update 90 (stable) and guardian 2 have now display-lang-bugs in the cgi.
Must i wait to a newest Version of guardian 2 or can i do the steps he told us?
As usual the new version can be downloaded from http://people.ipfire.org/~stevee/guardian-2.0/
The installation / update works in the same way as described in the planet post: http://planet.ipfire.org/post/introducing-guardian-2-0-for-ipfire
BG, 5p9
On 29.05.2015 00:32, 5p9 wrote:
Hi@all,
Hi!
i have a question. My Fire has became the final Core-Update 90 (stable) and guardian 2 have now display-lang-bugs in the cgi.
I think this is normal - and happened before - since the Guardian 2.0-language strings seem to be not fully implemented in the language files shipped with the new Core update.
Must i wait to a newest Version of guardian 2 or can i do the steps he told us?
I think you could either reinstall - which could lend to strings missing in other places so I would NOT recommend this - or simply copy the attached files to '/var/ipfire/addon-lang' and update the language cache starting "/usr/local/bin/update-lang-cache" from console. I hope I didn't miss a string. For me its looking good, no missing strings after updating.
This gives me the chance to repeat my proposal/feature request from here: https://forum.ipfire.org/viewtopic.php?f=4&t=13524&p=84922&sid=3...
Using the '/var/ipfire/addon-lang'-directory for those addons would make things perhaps a bit easier.
Jm2C - Regards Matthias
P.S.: Besides - update to Core 90 went ok by now, no probems detected. Good job - thanks! ;-)
Hi Fischer,
thx for help! :)
I think this is normal - and happened before - since the Guardian 2.0-language strings seem to be not fully implemented in the language files shipped with the new Core update.
i think this, too.
I think you could either reinstall - which could lend to strings missing in other places so I would NOT recommend this - or simply copy the attached files
Okay thx for this answer. I'll test and report it.
This gives me the chance to repeat my proposal/feature request from here:
https://forum.ipfire.org/viewtopic.php?f=4&t=13524&p=84922&sid=3... I know, I can remember me. Does that in a bugreport or wishlist?
Great job to "Core-Update90" IPFire-Team! GEOIPBlock rockt :D
5p9
Am 29.05.2015 um 01:28 schrieb Matthias Fischer:
On 29.05.2015 00:32, 5p9 wrote:
Hi@all,
Hi!
i have a question. My Fire has became the final Core-Update 90 (stable) and guardian 2 have now display-lang-bugs in the cgi.
I think this is normal - and happened before - since the Guardian 2.0-language strings seem to be not fully implemented in the language files shipped with the new Core update.
Must i wait to a newest Version of guardian 2 or can i do the steps he told us?
I think you could either reinstall - which could lend to strings missing in other places so I would NOT recommend this - or simply copy the attached files to '/var/ipfire/addon-lang' and update the language cache starting "/usr/local/bin/update-lang-cache" from console. I hope I didn't miss a string. For me its looking good, no missing strings after updating.
This gives me the chance to repeat my proposal/feature request from here: https://forum.ipfire.org/viewtopic.php?f=4&t=13524&p=84922&sid=3...
Using the '/var/ipfire/addon-lang'-directory for those addons would make things perhaps a bit easier.
Jm2C - Regards Matthias
P.S.: Besides - update to Core 90 went ok by now, no probems detected. Good job - thanks! ;-)