From mboxrd@z Thu Jan  1 00:00:00 1970
From: Grant Taylor <gtaylor@riverviewtech.net>
Subject: Re: How to filter packets resulting from hosts with
	dynamic	IP-address
Date: Tue, 06 Feb 2007 10:30:33 -0600
Message-ID: <45C8AD29.2080108@riverviewtech.net>
References: <200702061042.21497.frank.petran@inpho.de>	<45C896E7.3010105@riverviewtech.net>
	<200702061652.24892.frank.petran@inpho.de>
Reply-To: gtaylor+reply@riverviewtech.net
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Return-path: <netfilter-bounces@lists.netfilter.org>
In-Reply-To: <200702061652.24892.frank.petran@inpho.de>
List-Id: <netfilter.vger.kernel.org>
List-Unsubscribe: <https://lists.netfilter.org/mailman/listinfo/netfilter>,
	<mailto:netfilter-request@lists.netfilter.org?subject=unsubscribe>
List-Archive: </pipermail/netfilter>
List-Post: <mailto:netfilter@lists.netfilter.org>
List-Help: <mailto:netfilter-request@lists.netfilter.org?subject=help>
List-Subscribe: <https://lists.netfilter.org/mailman/listinfo/netfilter>,
	<mailto:netfilter-request@lists.netfilter.org?subject=subscribe>
Sender: netfilter-bounces@lists.netfilter.org
Errors-To: netfilter-bounces@lists.netfilter.org
Content-Type: text/plain; charset="us-ascii"; format="flowed"
To: Mail List - Netfilter <netfilter@lists.netfilter.org>

Frank Petran wrote:
> Port knocking is in my opinion a little bit clumsy to use especially if the 
> users involved are no experts and something goes wrong.

I was thinking that the port knocking would be for nothing more than a 
request for the router to initiate an update with the information that 
it found, not with any thing that is provided by the port knock. I.e. 
the only thing that a port knock will do is request an update, NOT 
provide the information for the update.



Grant. . . .