<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Raspbery Pi on</title><link>http://salopst.yearl.us/tags/raspbery-pi/</link><description>Recent content in Raspbery Pi on</description><generator>Hugo</generator><language>en</language><copyright>&lt;a href="https://creativecommons.org/licenses/by-nc/4.0/" target="_blank" rel="noopener"&gt;CC BY-NC 4.0&lt;/a&gt;</copyright><lastBuildDate>Fri, 21 Sep 2018 11:42:50 +0000</lastBuildDate><atom:link href="http://salopst.yearl.us/tags/raspbery-pi/index.xml" rel="self" type="application/rss+xml"/><item><title>pi-hole route del</title><link>http://salopst.yearl.us/pi-hole-route-del/</link><pubDate>Fri, 21 Sep 2018 11:42:50 +0000</pubDate><guid>http://salopst.yearl.us/pi-hole-route-del/</guid><description>&lt;p&gt;Sooo, my TP-Link Archer C8 AC1750 Gigabit router decided to not play nice after a short power outage. Didn&amp;rsquo;t do much anyway except keep a couple of machines in a their own little subnet in which the &lt;a href="http://stephen.yearl.us/pi-hole-dns-level-ad-blocker/"&gt;pi-hole&lt;/a&gt; was located.&lt;/p&gt;&#10;&lt;p&gt;Replaced it with a NETGEAR GS108Tv2 (link below) 8-Port Gigabit managed switch and flatten the network a little. Everything was peachy with that set up, but the pihole was still on &lt;code&gt;172.16.0.0/24&lt;/code&gt;&amp;hellip; reconfigured that with &lt;code&gt;pihole -r&lt;/code&gt; and all looked well except for the pi-hole could not ping outside of the LAN. Grrr! Much hair pulling until&amp;hellip;&lt;/p&gt;</description></item></channel></rss>