<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pfsense on</title><link>https://dawning.ca/tags/pfsense/</link><description>Recent content in Pfsense on</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Copyright © James Snell</copyright><lastBuildDate>Wed, 17 Jan 2018 15:17:57 +0000</lastBuildDate><atom:link href="https://dawning.ca/tags/pfsense/index.xml" rel="self" type="application/rss+xml"/><item><title>Using pfsense to sign private wildcard SSL certificates</title><link>https://dawning.ca/posts/using-pfsense-to-sign-private-wildcard-ssl-certificates/</link><pubDate>Wed, 17 Jan 2018 15:17:57 +0000</pubDate><guid>https://dawning.ca/posts/using-pfsense-to-sign-private-wildcard-ssl-certificates/</guid><description>
&lt;p>&lt;figure>
&lt;picture>
&lt;img
loading="lazy"
decoding="async"
alt=""
class="image_figure image_internal image_unprocessed"
src="https://dawning.ca/uploads/2018/01/Screen-Shot-2018-01-17-at-3.09.38-PM.png"
/>
&lt;/picture>
&lt;/figure>
&lt;a href="https://www.pfsense.org/download/">pfsense&lt;/a> is a wonderful router appliance &lt;a href="https://en.wikipedia.org/wiki/FreeBSD">BSD&lt;/a> distro that I&amp;rsquo;ve enjoyed for some years now.&lt;/p>
&lt;p>I use the &lt;a href="https://doc.pfsense.org/index.php/Certificate_Management">pfsense certificate manager&lt;/a> to issue certs for my VPN client devices. For my Internet-facing life, I have legit SSL certs for everything, I&amp;rsquo;ve a neurosis about it. But it&amp;rsquo;s bothered me that for my LAN servers, I&amp;rsquo;ve continued to use Self-Signed certs for interfaces. Today I fix that.&lt;/p>
&lt;p>Here are my notes on how to create and sign a wild-card SSL cert using pfsense for internal use. Note that this approach means you will make your own certificate authority which then must have its root cert installed on any machine you want to use your own certs.&lt;/p></description></item><item><title>AirPlay Through pfsense Bridge</title><link>https://dawning.ca/posts/airplay-through-pfsense-bridge/</link><pubDate>Thu, 23 Dec 2010 19:27:48 +0000</pubDate><guid>https://dawning.ca/posts/airplay-through-pfsense-bridge/</guid><description>
&lt;p>&lt;a href="https://dawning.ca/uploads/external/WiresharkOnAirTunes_a3fe1ae5.png">&lt;figure>
&lt;picture>
&lt;img
loading="lazy"
decoding="async"
alt=""
class="image_figure image_internal image_unprocessed"
src="https://dawning.ca/uploads/external/WiresharkOnAirTunes_a3fe1ae5.png"
/>
&lt;/picture>
&lt;/figure>
&lt;/a>Howdy all, geek-mode enabled.&lt;/p>
&lt;p>So I&amp;rsquo;ve been fighting somewhat to get my &lt;a href="http://en.wikipedia.org/wiki/Airtunes">AirPlay &lt;/a>enabled device (&lt;a href="http://en.wikipedia.org/wiki/Appletv">Apple TV&lt;/a>) to function perfectly. I use &lt;a href="http://en.wikipedia.org/wiki/Pfsense">pfsense&lt;/a> to run my router and in so doing I&amp;rsquo;ve got a Wireless and Wired network that are &lt;a href="http://en.wikipedia.org/wiki/Network_bridge">bridged together&lt;/a>. I found with the &lt;a href="http://en.wikipedia.org/wiki/Appletv">AppleTV&lt;/a> that only devices on the same physical media could stream to it, though all devices could &amp;ldquo;see&amp;rdquo; it.&lt;/p>
&lt;p>After submitting a feature request to Apple over this, I decided I wanted it solved for me anyway and I felt close to the solution. Since I had no logs to go by, I decided to bust out &lt;a href="http://en.wikipedia.org/wiki/Wireshark">Wireshark&lt;/a> to sniff all the involved network traffic. Suffice to say, I was rather entertained to find that when using AirPlay the payloads are flying around in &lt;a href="http://en.wikipedia.org/wiki/Ipv6">IPv6&lt;/a>, not &lt;a href="http://en.wikipedia.org/wiki/Ipv4">IPv4&lt;/a>. Just look at the caption in this post. All those teal packets is iTunes streaming audio to my AppleTV via AirPlay. It&amp;rsquo;s &lt;a href="http://en.wikipedia.org/wiki/User_Datagram_Protocol">UDP&lt;/a> over IPv6. Neato.&lt;/p></description></item></channel></rss>