<?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 for A private BSD laboratory</title>
	<atom:link href="http://weblogs.valsania.it/bsdlab/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://weblogs.valsania.it/bsdlab</link>
	<description>Just another Phoibos hosted weblog</description>
	<lastBuildDate>Tue, 23 Sep 2008 09:36:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>Comment on Migration to BSD near complete by Andrea Valsania</title>
		<link>http://weblogs.valsania.it/bsdlab/2008/09/10/migration-to-bsd-near-complete/comment-page-1/#comment-1097</link>
		<dc:creator>Andrea Valsania</dc:creator>
		<pubDate>Tue, 23 Sep 2008 09:36:36 +0000</pubDate>
		<guid isPermaLink="false">http://weblogs.valsania.it/bsdlab/?p=59#comment-1097</guid>
		<description>I&#039;m using isc-dhcpd 3.0.5 too, on a FreeBSD 7.0-p4/amd64 release. The first time I installed it in a jail with the DHCP_SOCKETS build option: the daemon started up without any error, but it was not issuing any lease. Thus I installed the daemon on the host (without jailing it) with the same build option, in order to get what it was wrong and... it didn&#039;t issue any lease yet!&lt;br/&gt;Then I rebuild it on the same host machine, but without the DHCP_SOCKETS option, and it started working immediately. I didn&#039;t have the time to investigate further (I&#039;m pretty sure it was a configuration-related problem, since it was the first time I was working with this product), so I created a new devfs ruleset by writing these lines in /etc/devfs.rules:

&lt;em&gt;[devfsrules_jail_dhcpd=5]
add include $devfsrules_hide_all
add include $devfsrules_unhide_basic
add include $devfsrules_unhide_login
add path &#039;bpf*&#039; unhide&lt;/em&gt;

then I allowed only the dhcpd jail to access the bpf device by setting the variable &lt;em&gt;jail_&lt;/em&gt;jailname&lt;em&gt;_devfs_ruleset=&quot;devfsrules_jail_dhcpd&quot;&lt;/em&gt;. All is working like a charm since then!</description>
		<content:encoded><![CDATA[<p>I&#8217;m using isc-dhcpd 3.0.5 too, on a FreeBSD 7.0-p4/amd64 release. The first time I installed it in a jail with the DHCP_SOCKETS build option: the daemon started up without any error, but it was not issuing any lease. Thus I installed the daemon on the host (without jailing it) with the same build option, in order to get what it was wrong and&#8230; it didn&#8217;t issue any lease yet!<br />Then I rebuild it on the same host machine, but without the DHCP_SOCKETS option, and it started working immediately. I didn&#8217;t have the time to investigate further (I&#8217;m pretty sure it was a configuration-related problem, since it was the first time I was working with this product), so I created a new devfs ruleset by writing these lines in /etc/devfs.rules:</p>
<p><em>[devfsrules_jail_dhcpd=5]<br />
add include $devfsrules_hide_all<br />
add include $devfsrules_unhide_basic<br />
add include $devfsrules_unhide_login<br />
add path &#8216;bpf*&#8217; unhide</em></p>
<p>then I allowed only the dhcpd jail to access the bpf device by setting the variable <em>jail_</em>jailname<em>_devfs_ruleset=&#8221;devfsrules_jail_dhcpd&#8221;</em>. All is working like a charm since then!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Migration to BSD near complete by stu</title>
		<link>http://weblogs.valsania.it/bsdlab/2008/09/10/migration-to-bsd-near-complete/comment-page-1/#comment-1096</link>
		<dc:creator>stu</dc:creator>
		<pubDate>Tue, 23 Sep 2008 06:24:28 +0000</pubDate>
		<guid isPermaLink="false">http://weblogs.valsania.it/bsdlab/?p=59#comment-1096</guid>
		<description>Can you provide details on how you got dhcpd running inside a full jail sandbox?  The isc-dhcpd (3.0.5) gives an error message &quot;unable to create icmp socket&quot;.  I configured the compile to use sockets instead of bpf. I can&#039;t figure out how to get everything to work correctly without exposing every single jail on that interface to packet snooping from the other jails on that same interface.</description>
		<content:encoded><![CDATA[<p>Can you provide details on how you got dhcpd running inside a full jail sandbox?  The isc-dhcpd (3.0.5) gives an error message &#8220;unable to create icmp socket&#8221;.  I configured the compile to use sockets instead of bpf. I can&#8217;t figure out how to get everything to work correctly without exposing every single jail on that interface to packet snooping from the other jails on that same interface.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on WordPress µ now running by andreav</title>
		<link>http://weblogs.valsania.it/bsdlab/2006/10/04/wordpress-%c2%b5-now-running/comment-page-1/#comment-5</link>
		<dc:creator>andreav</dc:creator>
		<pubDate>Fri, 02 Feb 2007 16:25:22 +0000</pubDate>
		<guid isPermaLink="false">http://weblogs.valsania.it/bsdlab/?p=4#comment-5</guid>
		<description>The latest version of WPMU is now under testing, please read the &lt;a href=&quot;http://weblogs.valsania.it/bsdlab/2007/02/02/wordpress-is-back-online&quot; rel=&quot;nofollow&quot;&gt;new post &lt;/a&gt;about it.</description>
		<content:encoded><![CDATA[<p>The latest version of WPMU is now under testing, please read the <a href="http://weblogs.valsania.it/bsdlab/2007/02/02/wordpress-is-back-online" rel="nofollow">new post </a>about it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on WordPress µ now running by andreav</title>
		<link>http://weblogs.valsania.it/bsdlab/2006/10/04/wordpress-%c2%b5-now-running/comment-page-1/#comment-2</link>
		<dc:creator>andreav</dc:creator>
		<pubDate>Sat, 07 Oct 2006 16:27:53 +0000</pubDate>
		<guid isPermaLink="false">http://weblogs.valsania.it/bsdlab/?p=4#comment-2</guid>
		<description>From now on the WPMU collection is out of order. At the same URL you can now use a free blog hosting service powered by the standard WordPress 2.0.4 engine.
At the time I&#039;m writing, you must send an e-mail to webmaster@valsania.it in order to have your blog activated on this space.

Happy blogging!</description>
		<content:encoded><![CDATA[<p>From now on the WPMU collection is out of order. At the same URL you can now use a free blog hosting service powered by the standard WordPress 2.0.4 engine.<br />
At the time I&#8217;m writing, you must send an e-mail to <a href="mailto:webmaster@valsania.it">webmaster@valsania.it</a> in order to have your blog activated on this space.</p>
<p>Happy blogging!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

