<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: fwknop: Single Packet Authorization in Ubuntu</title>
	<atom:link href="http://www.savvyadmin.com/fwknop-single-packet-authorization-in-ubuntu/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.savvyadmin.com/fwknop-single-packet-authorization-in-ubuntu/</link>
	<description>For savvy admins everywhere...</description>
	<pubDate>Wed, 07 Jan 2009 02:34:05 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: gmendoza</title>
		<link>http://www.savvyadmin.com/fwknop-single-packet-authorization-in-ubuntu/#comment-96</link>
		<dc:creator>gmendoza</dc:creator>
		<pubDate>Sun, 20 Apr 2008 16:33:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.savvyadmin.com/2007/06/24/fwknop-single-packet-authorization-in-ubuntu/#comment-96</guid>
		<description>Thanks for the comment!  I need to update this doc for the latest release, so I'll do that shortly.

Take a look at "fwknop.conf", as it has the server side variable you can use to change the listening default port:

&lt;code&gt;PCAP_FILTER    udp port 62201;&lt;/code&gt;

You can change this to something that's typically not blocked by any firewall your client may find itself behind, e.g. udp port 53, typically used for DNS.

Also, if you read the header notes describing this variable, you can have it listen on any or all ports.

Something cool to remember is that the fwknop service does not actually "open" this port on the server, so you don't have to worry about conflicts.  Even if that port is already in use on the server, the fwknop service uses PCAP to sniff the wire for SPA packets to work with.  Just remember, the process of capturing the data can increase the load on the server if you choose a port that has a lot of traffic already.  So, just be cautious.

Also, you don't need to use "sudo" to run the client.  You are simply using fwknop to perform a function that requires no special privileges.  Woot!

Again, thanks for visiting.</description>
		<content:encoded><![CDATA[<p>Thanks for the comment!  I need to update this doc for the latest release, so I&#8217;ll do that shortly.</p>
<p>Take a look at &#8220;fwknop.conf&#8221;, as it has the server side variable you can use to change the listening default port:</p>
<p><code>PCAP_FILTER    udp port 62201;</code></p>
<p>You can change this to something that&#8217;s typically not blocked by any firewall your client may find itself behind, e.g. udp port 53, typically used for DNS.</p>
<p>Also, if you read the header notes describing this variable, you can have it listen on any or all ports.</p>
<p>Something cool to remember is that the fwknop service does not actually &#8220;open&#8221; this port on the server, so you don&#8217;t have to worry about conflicts.  Even if that port is already in use on the server, the fwknop service uses PCAP to sniff the wire for SPA packets to work with.  Just remember, the process of capturing the data can increase the load on the server if you choose a port that has a lot of traffic already.  So, just be cautious.</p>
<p>Also, you don&#8217;t need to use &#8220;sudo&#8221; to run the client.  You are simply using fwknop to perform a function that requires no special privileges.  Woot!</p>
<p>Again, thanks for visiting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KevDog</title>
		<link>http://www.savvyadmin.com/fwknop-single-packet-authorization-in-ubuntu/#comment-95</link>
		<dc:creator>KevDog</dc:creator>
		<pubDate>Sun, 20 Apr 2008 15:42:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.savvyadmin.com/2007/06/24/fwknop-single-packet-authorization-in-ubuntu/#comment-95</guid>
		<description>Great writeup -- 

Quick question however -- say the UDP port 62201 is blocked on the client machine.  The fwknop documentation stated this port could be changed, however I couldn't find how to do this.  Also do you need to be root or issue any sudo commands to use fwknop as a regular user.</description>
		<content:encoded><![CDATA[<p>Great writeup &#8212; </p>
<p>Quick question however &#8212; say the UDP port 62201 is blocked on the client machine.  The fwknop documentation stated this port could be changed, however I couldn&#8217;t find how to do this.  Also do you need to be root or issue any sudo commands to use fwknop as a regular user.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Rash</title>
		<link>http://www.savvyadmin.com/fwknop-single-packet-authorization-in-ubuntu/#comment-6</link>
		<dc:creator>Michael Rash</dc:creator>
		<pubDate>Sun, 08 Jul 2007 23:13:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.savvyadmin.com/2007/06/24/fwknop-single-packet-authorization-in-ubuntu/#comment-6</guid>
		<description>Thanks for an excellent write up on getting fwknop working on Ubuntu systems.  It is good to see more documentation out there for fwknop.</description>
		<content:encoded><![CDATA[<p>Thanks for an excellent write up on getting fwknop working on Ubuntu systems.  It is good to see more documentation out there for fwknop.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
