From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: Forward Rule, Client access only specific ip's, rest of world access client unrestricted.
Date: Tue, 26 Apr 2011 11:05:55 -0500 [thread overview]
Message-ID: <4DB6ED63.6040502@riverviewtech.net> (raw)
In-Reply-To: <000501cc040b$e0151090$a03f31b0$@com>
On 04/26/11 07:17, Becskei Robert wrote:
> I have a problem here, I have a client, which should only be able to access
> a few ip's and not the rest. But the rest of my network should be allowed to
> access this client unrestricted (that is if they initiate the connection).
...
> What I want is :
> - Client should be able to only access a few selected ip's (see above)
> - Client should not be able to access anything else
> - BUT! If someone from the network initiates a connection to the client, be
> it ping, vnc, or whatever it should be allowed ( I don't know how to do
> this)
This should be possible and relatively easy to do.
> If someone can please help me :) . Thank you
You are asking for stateful packet inspection, just like you are
probably using to filter traffic coming back in from the internet.
Try adding a rule like the following somewhere before your DROP rule.
iptables -A FORWARD -s 192.168.220.28 -m state --state
ESTABLISHED,RELATED -j ACCEPT
This will allow reply traffic back out while still allowing you to
control everything else like you are wanting to do.
Grant. . . .
next prev parent reply other threads:[~2011-04-26 16:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 12:17 Forward Rule, Client access only specific ip's, rest of world access client unrestricted Becskei Robert
2011-04-26 16:05 ` Grant Taylor [this message]
2011-04-26 20:03 ` Becskei Robert
2011-04-26 20:49 ` Grant Taylor
2011-04-26 21:25 ` Becskei Robert
2011-04-26 21:34 ` Grant Taylor
-- strict thread matches above, loose matches on Subject: below --
2011-04-26 13:01 Becskei Robert
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=4DB6ED63.6040502@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=netfilter@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).