public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Bob Brewer <ipfire-devel@grantura.co.uk>
To: development@lists.ipfire.org
Subject: Re: IPCop Banish Addon for IPFire
Date: Tue, 08 Jan 2019 16:42:22 +0000	[thread overview]
Message-ID: <q12jte$2m6$1@tuscan3.grantura.co.uk> (raw)
In-Reply-To: <ef52e446-75ab-d9f8-7fa4-e13fcb3a77fb@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2726 bytes --]

Matthias Fischer wrote:


> But still I can't add any entries. Page reloads, list stays empty. GUI
> stays empty and 'iptables' chains, too. Rule(s) seem(s) to be deleted
> right before/after adding!?
> 
> Here I tried to add '50.22.0.0/15:
> ...
> 22:08:56	banish	: Remove Banish rules
> 22:08:56	banish	: Removing Banished entries
> 22:08:56	banish	: Load Banish rules
> 22:08:56	banish	: Adding Banished entries to DROP
> 22:08:56	banish	: Regel hinzugefügt: 50.22.0.0/15
> 22:08:56	banish	: Remove Banish rules
> 22:08:56	banish	: Removing Banished entries
> 22:08:56	banish	: Load Banish rules
> 22:08:56	banish	: Adding Banished entries to DROP
> 22:08:56	banish	: Regel gelöscht:
> ...
> 
> For entries to add, must the testmachine be online!?
> 
It would seem so, my test box is connected with a static ip to the orange 
interface of my main IPFire box. The DNS is set to my ISPs DNS.

I tried reloading the rules with the red interface disconnected and iptables 
complains "iptables v1.6.2: host/network `xxx.yy.zz' not found" when trying 
to write rules for a FQDN. Presumably iptables needs an operating DNS to 
generate the rules. Other IP Address and CIDRs seem to load OK though.
Re-connecting the red interface restored functionality. 
> 
>> 
>>> 3. $Lang::tr{'apply'} - used in 'BanishGeo.cgi' line 232 - is missing in
>>> the language-files.
>>> 
>> This is a problem with the original banish distribution files. Maybe
>> there was a translation in IPCop which IPFire doesn't have, I'll add one
>> to these lang files if I can find the appropriate translations.
>> 

I checked /var/ipfire/langs/en.pl and there is a translation for 'apply' as:
'apply' => 'Apply now' and in de.pl as: 'apply' => 'Jetzt anwenden'.
The button on the Filter rule on my box is shown as 'Apply now' so it looks 
like the translation is working OK here.
> 
> Besides, all "umlauts" are looking weird in the log, as seen above:
> 
> ...
> 21:49:50	banish	: Adding Banished entries to DROP
> 21:49:50	banish	: Regel hinzugefügt: 50.22.0.0/15
>                                         ^^^
> ...
> 21:50:41	banish	: Regel gelöscht:
>                                    ^^^
I think this must be an apache problem. The umlauts in the lang files 
display OK in a text console on my box but I don't have any umlauts in my 
message logs to compare. Do the words display correctly if you grep the 
banish entries in /var/log/messages?

>> 'captive' => $Lang::tr{'Captive'},
>> with a capital 'C' and not:
> 
> It seems so. I'm running heavily tuned language files here, so I
> overlooked this. I'll take a look.

I see you generated a patch - glad I could help :)
> 

I'll upload a 0.3 version with your suggestions

Regards

Rob

      reply	other threads:[~2019-01-08 16:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-06 18:12 Bob Brewer
2019-01-07  7:39 ` Daniel Weismüller
2019-01-07 10:07   ` Bob Brewer
2019-01-07 12:17     ` Daniel Weismüller
2019-01-07 14:36       ` Bob Brewer
2019-01-07 12:13 ` Matthias Fischer
2019-01-07 12:26   ` Bob Brewer
2019-01-07 12:38     ` Bob Brewer
2019-01-07 14:48       ` Matthias Fischer
2019-01-07 19:28         ` Bob Brewer
2019-01-07 21:13           ` Matthias Fischer
2019-01-08 16:42             ` Bob Brewer [this message]

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='q12jte$2m6$1@tuscan3.grantura.co.uk' \
    --to=ipfire-devel@grantura.co.uk \
    --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