<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Who&#8217;s for an OpenPF?	</title>
	<atom:link href="https://www.dragonflydigest.com/2013/12/19/whos-for-an-openpf/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.dragonflydigest.com/2013/12/19/whos-for-an-openpf/</link>
	<description>A running description of activity related to DragonFly BSD.</description>
	<lastBuildDate>Sat, 17 May 2014 13:03:58 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0.1</generator>
	<item>
		<title>
		By: In Other BSDs for 2014/05/17 &#8211; DragonFly BSD Digest		</title>
		<link>https://www.dragonflydigest.com/2013/12/19/whos-for-an-openpf/comment-page-1/#comment-115139</link>

		<dc:creator><![CDATA[In Other BSDs for 2014/05/17 &#8211; DragonFly BSD Digest]]></dc:creator>
		<pubDate>Sat, 17 May 2014 13:03:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=13008#comment-115139</guid>

					<description><![CDATA[[&#8230;] LibreSSL will be portable.  I still want a portable pf. [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] LibreSSL will be portable.  I still want a portable pf. [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Lars Schotte		</title>
		<link>https://www.dragonflydigest.com/2013/12/19/whos-for-an-openpf/comment-page-1/#comment-102307</link>

		<dc:creator><![CDATA[Lars Schotte]]></dc:creator>
		<pubDate>Mon, 28 Apr 2014 17:27:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=13008#comment-102307</guid>

					<description><![CDATA[The sad thing about this situation is that the only firewall that is working and is available to all BSDs is the old ipfilter. So that runs against the original intention to get rid of it and replace it with something better. pf was a try. I do not believe in it any more, even though it was a good one. npf is the next try. I hope this time it will finally work out for good.]]></description>
			<content:encoded><![CDATA[<p>The sad thing about this situation is that the only firewall that is working and is available to all BSDs is the old ipfilter. So that runs against the original intention to get rid of it and replace it with something better. pf was a try. I do not believe in it any more, even though it was a good one. npf is the next try. I hope this time it will finally work out for good.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: In Other BSDs for 2014/04/26 &#8211; DragonFly BSD Digest		</title>
		<link>https://www.dragonflydigest.com/2013/12/19/whos-for-an-openpf/comment-page-1/#comment-101140</link>

		<dc:creator><![CDATA[In Other BSDs for 2014/04/26 &#8211; DragonFly BSD Digest]]></dc:creator>
		<pubDate>Sat, 26 Apr 2014 13:15:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=13008#comment-101140</guid>

					<description><![CDATA[[&#8230;] So I&#8217;ll bring up this point again: pf is fragmenting, and we should do something about it. [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] So I&#8217;ll bring up this point again: pf is fragmenting, and we should do something about it. [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Sukosevato		</title>
		<link>https://www.dragonflydigest.com/2013/12/19/whos-for-an-openpf/comment-page-1/#comment-75407</link>

		<dc:creator><![CDATA[Sukosevato]]></dc:creator>
		<pubDate>Mon, 06 Jan 2014 21:49:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=13008#comment-75407</guid>

					<description><![CDATA[I agree, I don&#039;t think it is feasible to bring it back into one source tree, but ensuring the same syntax is used across all pf versions would be something that should be possible and would be very nice to have.]]></description>
			<content:encoded><![CDATA[<p>I agree, I don&#8217;t think it is feasible to bring it back into one source tree, but ensuring the same syntax is used across all pf versions would be something that should be possible and would be very nice to have.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: BSDNow 18: Eclipsing Binaries &#8211; DragonFly BSD Digest		</title>
		<link>https://www.dragonflydigest.com/2013/12/19/whos-for-an-openpf/comment-page-1/#comment-75002</link>

		<dc:creator><![CDATA[BSDNow 18: Eclipsing Binaries &#8211; DragonFly BSD Digest]]></dc:creator>
		<pubDate>Wed, 01 Jan 2014 19:10:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=13008#comment-75002</guid>

					<description><![CDATA[[&#8230;] 18, first of the new year, is up.  Among other things, it mentions my crazy &#8216;OpenPF&#8217; idea, and there&#8217;s an interview with Baptiste Daroussin.  He&#8217;s one of the people working on [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] 18, first of the new year, is up.  Among other things, it mentions my crazy &#8216;OpenPF&#8217; idea, and there&#8217;s an interview with Baptiste Daroussin.  He&#8217;s one of the people working on [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Franco		</title>
		<link>https://www.dragonflydigest.com/2013/12/19/whos-for-an-openpf/comment-page-1/#comment-74985</link>

		<dc:creator><![CDATA[Franco]]></dc:creator>
		<pubDate>Wed, 01 Jan 2014 12:17:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=13008#comment-74985</guid>

					<description><![CDATA[Oops, a little late to the discussion. The underlying issue really is SMP scaling... that&#039;s what&#039;s driving FreeBSD and NetBSD. That&#039;s why there&#039;s no motivation to stay in sync with OpenBSD. In DragonFly, we have exactly the same issue so sooner or later OpenBSD networking guys need to step up. Questions about this (and help offered) have been brought up in 2012 on the mailing lists (and probably before that as well). pf is great work and I&#039;m not convinced npf will be of much relevance. Not sure if the FreeBSD 10 pf is going to cut it as well being based on an outdated version. OpenBSD really holds all the power to change that (for now).

FWIW, I can take a shot at updating pf after netmap has settled in.

&#062;&#062;&#062; https://twitter.com/HenningBrauer/status/418348714294779904]]></description>
			<content:encoded><![CDATA[<p>Oops, a little late to the discussion. The underlying issue really is SMP scaling&#8230; that&#8217;s what&#8217;s driving FreeBSD and NetBSD. That&#8217;s why there&#8217;s no motivation to stay in sync with OpenBSD. In DragonFly, we have exactly the same issue so sooner or later OpenBSD networking guys need to step up. Questions about this (and help offered) have been brought up in 2012 on the mailing lists (and probably before that as well). pf is great work and I&#8217;m not convinced npf will be of much relevance. Not sure if the FreeBSD 10 pf is going to cut it as well being based on an outdated version. OpenBSD really holds all the power to change that (for now).</p>
<p>FWIW, I can take a shot at updating pf after netmap has settled in.</p>
<p>&gt;&gt;&gt; <a href="https://twitter.com/HenningBrauer/status/418348714294779904" rel="nofollow ugc">https://twitter.com/HenningBrauer/status/418348714294779904</a></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Eclipsing Binaries &#124; BSD Now 18 &#124; Jupiter Broadcasting		</title>
		<link>https://www.dragonflydigest.com/2013/12/19/whos-for-an-openpf/comment-page-1/#comment-74948</link>

		<dc:creator><![CDATA[Eclipsing Binaries &#124; BSD Now 18 &#124; Jupiter Broadcasting]]></dc:creator>
		<pubDate>Wed, 01 Jan 2014 05:37:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=13008#comment-74948</guid>

					<description><![CDATA[[&#8230;] OpenPF? [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] OpenPF? [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: www		</title>
		<link>https://www.dragonflydigest.com/2013/12/19/whos-for-an-openpf/comment-page-1/#comment-74498</link>

		<dc:creator><![CDATA[www]]></dc:creator>
		<pubDate>Sat, 28 Dec 2013 11:37:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=13008#comment-74498</guid>

					<description><![CDATA[FYI, NetBSD&#039;s npf has nothing in common with OpeBSD&#039;s pf:
http://mail-index.netbsd.org/netbsd-announce/2010/09/13/msg000110.html
http://www.netbsd.org/~rmind/npf/]]></description>
			<content:encoded><![CDATA[<p>FYI, NetBSD&#8217;s npf has nothing in common with OpeBSD&#8217;s pf:<br />
<a href="http://mail-index.netbsd.org/netbsd-announce/2010/09/13/msg000110.html" rel="nofollow ugc">http://mail-index.netbsd.org/netbsd-announce/2010/09/13/msg000110.html</a><br />
<a href="http://www.netbsd.org/~rmind/npf/" rel="nofollow ugc">http://www.netbsd.org/~rmind/npf/</a></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Eric Radman		</title>
		<link>https://www.dragonflydigest.com/2013/12/19/whos-for-an-openpf/comment-page-1/#comment-73820</link>

		<dc:creator><![CDATA[Eric Radman]]></dc:creator>
		<pubDate>Sat, 21 Dec 2013 16:40:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=13008#comment-73820</guid>

					<description><![CDATA[Likewise FreeBSD is not interested in staying current with PF; they&#039;re interested in SMP:

&quot;The pf firewall, originally from OpenBSD, got upgraded to support fine-grain locking and better utilization on multi-cpu machines&quot; [https://wiki.freebsd.org/WhatsNew/FreeBSD10]]]></description>
			<content:encoded><![CDATA[<p>Likewise FreeBSD is not interested in staying current with PF; they&#8217;re interested in SMP:</p>
<p>&#8220;The pf firewall, originally from OpenBSD, got upgraded to support fine-grain locking and better utilization on multi-cpu machines&#8221; [https://wiki.freebsd.org/WhatsNew/FreeBSD10]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Corey		</title>
		<link>https://www.dragonflydigest.com/2013/12/19/whos-for-an-openpf/comment-page-1/#comment-73691</link>

		<dc:creator><![CDATA[Corey]]></dc:creator>
		<pubDate>Fri, 20 Dec 2013 04:43:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=13008#comment-73691</guid>

					<description><![CDATA[That would be cool,  but I think the porting effort for pf is probably higher than that for something like OpenSSH due to its deeper hooks into the kernel and network stack. NetBSD even has some different goals in mind I think with npf (multicore filtering), so they may no longer want a port in the strict sense. But an agreement on a base level of functionality and configuration file syntax would be nice.]]></description>
			<content:encoded><![CDATA[<p>That would be cool,  but I think the porting effort for pf is probably higher than that for something like OpenSSH due to its deeper hooks into the kernel and network stack. NetBSD even has some different goals in mind I think with npf (multicore filtering), so they may no longer want a port in the strict sense. But an agreement on a base level of functionality and configuration file syntax would be nice.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
