From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Guardian 2.0 - Testing - 2.0-011
Date: Mon, 02 Mar 2015 19:54:09 +0100 [thread overview]
Message-ID: <1425322449.2564.35.camel@ipfire.org> (raw)
In-Reply-To: <CAA_nW+WsG62eKeTmx2zAWUQeHbS2w9JTz539PXh6Edw9BNs5Yg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1888 bytes --]
Hello Jim Becher,
> Hi all,
> Great work on adding Guardian.
>
>
> Here is my feedback on testing. System usage / process seems to be
> running well with not that much overhead.
>
>
Thanks for joining the guardian test team and sharing feedback and your
opinions with us.
>
>
> In looking at the log vs the web interface I have some feedback
> regarding web interface:
>
>
> Possible Bug: I was unable to delete a host from the web interface -
> screen cast is here showing the last Host not being removed when
> selecting the delete option: http://screencast.com/t/ccl8eGNlxcj
>
Looks really strange, I've tried but was not able to re-produce this
behaviour in any of my test environments. I also asked around a few
people which also are not affected by this problem.
Please try to execute the following command on your IPFire system:
"sudo -u nobody guardianctrl unblock x.x.x.x"
Also check for correct permissions which should be:
[root(a)ipfire ~]# ls -la /usr/local/bin/guardianctrl
-rwsr-s--x 1 root root 14857 Jan 18 11:25 /usr/local/bin/guardianctrl
>
> Suggestion: Would it be valuable to add the Date / time stamp in
> addition to the IP address.
>
I'm sorry, iptables does not store such information, so this is not
possible because of technical restrictions.
>
> Question: Will the list of blocked IP address paginate after a
> specific number
> Have been running for 24 hours and hit near 19 blocked hosts. This
> feature may already be there but I may not have enough blocked hosts.
>
No, there is no paginate process, all currently blocked addresses are
stored as list.
Best regards,
-Stefan
>
> Running Guardian 2.0-011 and IPFire 2.17 (i586) - Core Update 87
>
>
> Thanks
> Jim
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
parent reply other threads:[~2015-03-02 18:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAA_nW+WsG62eKeTmx2zAWUQeHbS2w9JTz539PXh6Edw9BNs5Yg@mail.gmail.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1425322449.2564.35.camel@ipfire.org \
--to=stefan.schantl@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox