From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: allowing packets from dynamic-dns IP
Date: Sat, 26 Apr 2008 14:25:04 -0500 [thread overview]
Message-ID: <48138190.8030305@riverviewtech.net> (raw)
In-Reply-To: <alpine.LNX.1.10.0804262016000.20150@fbirervta.pbzchgretzou.qr>
On 4/26/2008 1:16 PM, Jan Engelhardt wrote:
> The best solution is a script that runs after the interface was
> brought up. Usually this is -- depending on distro -- in
> /etc/sysconfig/network/if-up.d/.
I took the OP's question to be how does the static IP destination system
adjust rules to allow a dynamic IP source system in based on the dynamic
IP, not how does the dynamic IP system update its rules. If the latter
is the case, what you suggest will work great.
I think I would be tempted to use port knocking to initiate updating the
IPTables rules. I.e. have the dynamic system connect on a range of
ports that will then trigger the firewall to do a DNS query and then
update the firewall rules if need be. I would never update the firewall
rules based on the source IP of the knock. I would be much more
comfortable initiating a DNS query and trusting the query results than I
would the arbitrary source of the port knock.
I also would be tempted to check the result of the DNS query against the
currently allowed IP address and only change the IPTables rule if the IP
changes.
Grant. . . .
next prev parent reply other threads:[~2008-04-26 19:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-26 16:34 allowing packets from dynamic-dns IP Yakov Lerner
2008-04-26 18:16 ` Jan Engelhardt
2008-04-26 19:25 ` Grant Taylor [this message]
2008-04-26 19:29 ` Jan Engelhardt
2008-04-26 19:42 ` Grant Taylor
2008-04-26 20:02 ` Yakov Lerner
2008-04-26 22:07 ` Josh Cepek
2008-04-26 22:23 ` Jan Engelhardt
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=48138190.8030305@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