From: Michele Petrazzo - Unipex srl <michele.petrazzo@unipex.it>
To: "Roland Häder" <r.haeder@web.de>
Cc: netfilter@vger.kernel.org
Subject: Re: Bastille/netfilter with Linux 2.6.28 blocks connections
Date: Wed, 07 Jan 2009 09:51:34 +0100 [thread overview]
Message-ID: <49646D16.8040505@unipex.it> (raw)
In-Reply-To: <665067273@web.de>
Roland Häder wrote:
> I suppose I should not replace my _whole_ ruleset but a small part?
> Else these rules will be a little less secure.
>
Those replace only the forward one and add some debug. Of course, at the
end of tests, you'll modify and replace your rules with mine :)
> And currently my firewall got attacked on port 110 which is (sadly!)
> reachable on all NICs.
>
IP -I INPUT -m state --state NEW -p tcp --dport 110 -j ACCEPT
> So where should I add/replace your rules?
>
For test, into a "running" env, so after yours.
>> For this into the above iptables.list there are no rules! IP -A
>> PREROUTING -i eth0 -p tcp --dport 30017 -j DNAT --to-destination
>> 192.168.1.17
>>
>> and add the forward one
> I have a similar one already and as I said, it worked before like a
> sharm. :)
>
Strange. Start with a "rule clean" and recreate the only one that do the
work you want. Make them work and after, and only after, start to debug
Bye
next prev parent reply other threads:[~2009-01-07 8:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 16:37 Bastille/netfilter with Linux 2.6.28 blocks connections Roland Häder
2009-01-07 8:51 ` Michele Petrazzo - Unipex srl [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-07 21:55 Roland Häder
2009-01-07 22:16 ` Mart Frauenlob
2009-01-07 1:16 ` Roland Haeder
2009-01-07 21:09 Roland Häder
2009-01-07 21:04 Roland Häder
2009-01-07 20:04 Roland Häder
2009-01-07 20:15 ` Mart Frauenlob
2009-01-07 15:45 Roland Häder
2009-01-07 19:43 ` Mart Frauenlob
2009-01-05 16:52 Roland Häder
2009-01-05 13:41 Roland Häder
2009-01-05 14:37 ` Michele Petrazzo - Unipex srl
2009-01-07 15:16 ` Mart Frauenlob
2009-01-03 21:02 Roland Häder
2009-01-05 11:47 ` Michele Petrazzo - Unipex srl
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=49646D16.8040505@unipex.it \
--to=michele.petrazzo@unipex.it \
--cc=netfilter@vger.kernel.org \
--cc=r.haeder@web.de \
/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