<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>MTIN xISP topics</title>
	<atom:link href="http://www.mtin.net/blog/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mtin.net/blog</link>
	<description>Writings about the world of the ISP by Justin Wilson</description>
	<lastBuildDate>Sat, 20 Apr 2013 22:26:55 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
<meta xmlns="http://www.w3.org/1999/xhtml" name="robots" content="noindex,follow" />
		<item>
		<title>Helpful IPV6 Link</title>
		<link>http://www.mtin.net/blog/helpful-ipv6-link/</link>
		<comments>http://www.mtin.net/blog/helpful-ipv6-link/#comments</comments>
		<pubDate>Sat, 20 Apr 2013 22:26:55 +0000</pubDate>
		<dc:creator>j2sw</dc:creator>
				<category><![CDATA[Mikrotik]]></category>
		<category><![CDATA[IPV6]]></category>
		<category><![CDATA[tools]]></category>

		<guid isPermaLink="false">http://www.mtin.net/blog/?p=1522</guid>
		<description><![CDATA[http://www.si6networks.com/tools/ipv6toolkit/ The SI6 Networks&#8217; IPv6 toolkit is a set of IPv6 security/trouble-shooting tools, that can send arbitrary IPv6-based packets.]]></description>
				<content:encoded><![CDATA[<p><a href="http://www.si6networks.com/tools/ipv6toolkit/">http://www.si6networks.com/tools/ipv6toolkit/</a><br />
The SI6 Networks&#8217; IPv6 toolkit is a set of IPv6 security/trouble-shooting tools, that can send arbitrary IPv6-based packets.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mtin.net/blog/helpful-ipv6-link/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mikrotik 6.0RC13</title>
		<link>http://www.mtin.net/blog/mikrotik-6-0rc13/</link>
		<comments>http://www.mtin.net/blog/mikrotik-6-0rc13/#comments</comments>
		<pubDate>Tue, 09 Apr 2013 13:45:06 +0000</pubDate>
		<dc:creator>j2sw</dc:creator>
				<category><![CDATA[Mikrotik]]></category>
		<category><![CDATA[rc13]]></category>

		<guid isPermaLink="false">http://www.mtin.net/blog/?p=1518</guid>
		<description><![CDATA[From the Mikrotik e-mail What&#8217;s new in 6.0rc13 (2013-Apr-08 14:25): *) pppoe, l2tp, pptp server &#8211; increased lcp retransmit count to 10; *) pptp, l2tp &#038; pppoe clients &#8211; added ability to specify keepalive timeout; *) graphing &#8211; fixed problem were interface graphs are lost on reboot; *) dhcpv6 &#8211; added relay; *) sstp server [...]]]></description>
				<content:encoded><![CDATA[<p>From the Mikrotik e-mail<br />
What&#8217;s new in 6.0rc13 (2013-Apr-08 14:25):</p>
<p>*) pppoe, l2tp, pptp server &#8211; increased lcp retransmit count to 10;<br />
*) pptp, l2tp &#038; pppoe clients &#8211; added ability to specify keepalive timeout;<br />
*) graphing &#8211; fixed problem were interface graphs are lost on reboot;<br />
*) dhcpv6 &#8211; added relay;<br />
*) sstp server &#8211; restore (disabled in rc12) test mode which allows<br />
    running server without certificate;<br />
*) lcd &#8211; added option for turning backlight on/off;<br />
*) bgp &#8211; fix med comparison check if routes are received from iBGP peer;<br />
*) fixed simple queues &#8211; sometimes some simple queues did not limit traffic<br />
   (bug introduced in 6.0rc12);<br />
*) allow to change arp timeout (in /ip settings);<br />
*) added /ip neighbor discovery settings setting &#8220;default-for-dynamic&#8221; to control<br />
   discovery on new dynamic interfaces (off by default);</p>
<p>http://www.mikrotik.com/download</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mtin.net/blog/mikrotik-6-0rc13/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WISPAMERICA day 1</title>
		<link>http://www.mtin.net/blog/wispamerica-day-1/</link>
		<comments>http://www.mtin.net/blog/wispamerica-day-1/#comments</comments>
		<pubDate>Wed, 03 Apr 2013 17:58:59 +0000</pubDate>
		<dc:creator>j2sw</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[Wireless]]></category>
		<category><![CDATA[WISP]]></category>
		<category><![CDATA[conference]]></category>
		<category><![CDATA[Covington]]></category>
		<category><![CDATA[KY]]></category>
		<category><![CDATA[wispa]]></category>

		<guid isPermaLink="false">http://www.mtin.net/blog/?p=1516</guid>
		<description><![CDATA[About half way through the day. Had a moment to to sit for lunch. Some highlights of the day. -UBNT had some of the new Unifi 3 on display. Very heavy duty feeling unit. The new Nanobridge was on display. I am impressed with the design. Much easier to replace the things which go bad. [...]]]></description>
				<content:encoded><![CDATA[<p>About half way through the day. Had a moment to to sit for lunch. Some highlights of the day.</p>
<p>-UBNT had some of the new Unifi 3 on display. Very heavy duty feeling unit.  The new Nanobridge was on display. I am impressed with the design. Much easier to replace the things which go bad. The ethernet port no longer has the grommet. </p>
<p>-The lunch Keynote included the CEO of ARIN John Curran. Very good talk. Great amount of humor mixed with useful information.</p>
<p>to be continued&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mtin.net/blog/wispamerica-day-1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>802.11AC Channel Planning</title>
		<link>http://www.mtin.net/blog/802-11ac-channel-planning/</link>
		<comments>http://www.mtin.net/blog/802-11ac-channel-planning/#comments</comments>
		<pubDate>Wed, 20 Mar 2013 16:42:47 +0000</pubDate>
		<dc:creator>j2sw</dc:creator>
				<category><![CDATA[Wireless]]></category>
		<category><![CDATA[80.11ac]]></category>
		<category><![CDATA[channels]]></category>

		<guid isPermaLink="false">http://www.mtin.net/blog/?p=1513</guid>
		<description><![CDATA[Found this Gem http://revolutionwifi.blogspot.com/2013/03/80211ac-channel-planning.html]]></description>
				<content:encoded><![CDATA[<p>Found this Gem</p>
<p><a href="http://revolutionwifi.blogspot.com/2013/03/80211ac-channel-planning.html">http://revolutionwifi.blogspot.com/2013/03/80211ac-channel-planning.html</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.mtin.net/blog/802-11ac-channel-planning/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>UBNT Factory Reset via Terminal</title>
		<link>http://www.mtin.net/blog/ubnt-factory-reset-via-terminal/</link>
		<comments>http://www.mtin.net/blog/ubnt-factory-reset-via-terminal/#comments</comments>
		<pubDate>Wed, 27 Feb 2013 18:01:32 +0000</pubDate>
		<dc:creator>j2sw</dc:creator>
				<category><![CDATA[UBNT]]></category>
		<category><![CDATA[WISP]]></category>
		<category><![CDATA[reset]]></category>
		<category><![CDATA[ssh]]></category>
		<category><![CDATA[terminal]]></category>
		<category><![CDATA[ubnt]]></category>

		<guid isPermaLink="false">http://www.mtin.net/blog/?p=1509</guid>
		<description><![CDATA[Do you have a Ubiquiti radio you can SSH into but can&#8217;t do much else with? If you are needing to do a factory reset via terminal here is the command: cp /etc/default.cfg /tmp/system.cfg Thanks to SamT for the heads up.]]></description>
				<content:encoded><![CDATA[<p>Do you have a Ubiquiti radio you can SSH into but can&#8217;t do much else with? If you are needing to do a factory reset via terminal here is the command:</p>
<p><code>cp /etc/default.cfg /tmp/system.cfg </code></p>
<p>Thanks to SamT for the heads up.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mtin.net/blog/ubnt-factory-reset-via-terminal/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Airmax QOS</title>
		<link>http://www.mtin.net/blog/airmax-qos/</link>
		<comments>http://www.mtin.net/blog/airmax-qos/#comments</comments>
		<pubDate>Sun, 27 Jan 2013 19:33:56 +0000</pubDate>
		<dc:creator>j2sw</dc:creator>
				<category><![CDATA[Ubiquiti]]></category>
		<category><![CDATA[qos]]></category>
		<category><![CDATA[tos]]></category>
		<category><![CDATA[ubnt]]></category>
		<category><![CDATA[video]]></category>
		<category><![CDATA[voip]]></category>

		<guid isPermaLink="false">http://www.mtin.net/blog/?p=1505</guid>
		<description><![CDATA[For thos of you looking for some information on QOS for VOIP and such on Ubiquiti Airmax check out this wiki article http://wiki.ubnt.com/AirMax_-_QoS_DSCP/TOS_Mappings &#160; In order for AirMax to classify and differentiate types of traffic when applying QoS rules, the traffic must have a special value set in the IP Header DSCP field. The originating [...]]]></description>
				<content:encoded><![CDATA[<p>For thos of you looking for some information on QOS for VOIP and such on Ubiquiti Airmax check out this wiki article</p>
<p><a href="http://wiki.ubnt.com/AirMax_-_QoS_DSCP/TOS_Mappings">http://wiki.ubnt.com/AirMax_-_QoS_DSCP/TOS_Mappings</a></p>
<p>&nbsp;</p>
<p>In order for AirMax to classify and differentiate types of traffic when applying QoS rules, the traffic must have a special value set in the IP Header DSCP field. The originating software or hardware device is responsible for applying this value, and only if this field is set will traffic be prioritized.</p>
<p>There are four traffic categories: Best Effort, Background, Video, and Voice, which range from priorities lowest to highest in that order.</p>
<p>By default, all traffic is classified as &#8220;Best Effort&#8221;, meaning there is no prioritization applied. The other categories can be defined with the following values:</p>
<p>&nbsp;</p>
<table width="65%">
<tbody>
<tr>
<th scope="col">802.1p Class of Service</th>
<th scope="col">TOS Range</th>
<th scope="col">DSCP Range</th>
<th scope="col">WME Category</th>
</tr>
<tr>
<td>0 &#8211; Best Effort</td>
<td>0&#215;00-0x1f</td>
<td>0-7</td>
<td>Best Effort</td>
</tr>
<tr>
<td>1 &#8211; Background</td>
<td>0&#215;20-0x3f</td>
<td>8-15</td>
<td>Background</td>
</tr>
<tr>
<td>2 &#8211; Spare</td>
<td>0&#215;40-0x5f</td>
<td>16-23</td>
<td>Background</td>
</tr>
<tr>
<td>3 &#8211; Excellent Effort</td>
<td>0&#215;60-0x7f</td>
<td>24-31</td>
<td>Best Effort</td>
</tr>
<tr>
<td>4 &#8211; Controlled Load</td>
<td>0&#215;80-0x9f</td>
<td>32-39</td>
<td>Video</td>
</tr>
<tr>
<td>5 &#8211; Video (&lt;100ms latency)</td>
<td>0xa0-0xbf</td>
<td>40-47</td>
<td>Video</td>
</tr>
<tr>
<td>6 &#8211; Voice (&lt;10ms latency)</td>
<td>0xc0-0xdf</td>
<td>48-55</td>
<td>Voice</td>
</tr>
<tr>
<td>7 &#8211; Network Control</td>
<td>0xe0-0xff</td>
<td>56-63</td>
<td>Voice</td>
</tr>
</tbody>
</table>
]]></content:encoded>
			<wfw:commentRss>http://www.mtin.net/blog/airmax-qos/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How BGP chooses its routes</title>
		<link>http://www.mtin.net/blog/how-bgp-chooses-its-routes/</link>
		<comments>http://www.mtin.net/blog/how-bgp-chooses-its-routes/#comments</comments>
		<pubDate>Wed, 26 Dec 2012 21:28:20 +0000</pubDate>
		<dc:creator>j2sw</dc:creator>
				<category><![CDATA[ISPOPS]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[bgp]]></category>

		<guid isPermaLink="false">http://www.mtin.net/blog/?p=1499</guid>
		<description><![CDATA[]]></description>
				<content:encoded><![CDATA[<p><object width="560" height="315"><param name="movie" value="http://www.youtube.com/v/XRetkD4UUL4?version=3&amp;hl=en_US"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/v/XRetkD4UUL4?version=3&amp;hl=en_US" type="application/x-shockwave-flash" width="560" height="315" allowscriptaccess="always" allowfullscreen="true"></embed></object></p>
]]></content:encoded>
			<wfw:commentRss>http://www.mtin.net/blog/how-bgp-chooses-its-routes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MTIN now offers spam filtering services</title>
		<link>http://www.mtin.net/blog/mtin-now-offers-spam-filtering-services/</link>
		<comments>http://www.mtin.net/blog/mtin-now-offers-spam-filtering-services/#comments</comments>
		<pubDate>Fri, 21 Dec 2012 16:00:23 +0000</pubDate>
		<dc:creator>j2sw</dc:creator>
				<category><![CDATA[Mikrotik]]></category>

		<guid isPermaLink="false">http://www.mtin.net/blog/?p=1496</guid>
		<description><![CDATA[MTIN now offers spam and virus filtering services at an affordable rate. Rates start at $8.95 a month for 100,000 messages a month. Features include: -Unlimited e-mail addresses -Spam,Virus, and malware filtering -over 7 million filter rues -Custom filter rules available -Control panel for management -e-mail archiving -multiple fail-over support -whitelisting Many more features. Let [...]]]></description>
				<content:encoded><![CDATA[<p>MTIN now offers spam and virus filtering services at an affordable rate.  Rates start at $8.95 a month for 100,000 messages a month.</p>
<p>Features include:<br />
-Unlimited e-mail addresses<br />
-Spam,Virus, and malware filtering<br />
-over 7 million filter rues<br />
-Custom filter rules available<br />
-Control panel for management<br />
-e-mail archiving<br />
-multiple fail-over support<br />
-whitelisting</p>
<p>Many more features.  Let MTIN set this up for you for a low price of $125 plus 1st months&#8217;s service. <a href="mailto:support@mtin.net">Contact us for more details</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.mtin.net/blog/mtin-now-offers-spam-filtering-services/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>D-Root Changing Ipv4 address</title>
		<link>http://www.mtin.net/blog/d-root-changing-ipv4-address/</link>
		<comments>http://www.mtin.net/blog/d-root-changing-ipv4-address/#comments</comments>
		<pubDate>Sat, 15 Dec 2012 06:01:43 +0000</pubDate>
		<dc:creator>j2sw</dc:creator>
				<category><![CDATA[ISPOPS]]></category>
		<category><![CDATA[internic]]></category>
		<category><![CDATA[IPV4]]></category>
		<category><![CDATA[nameserver]]></category>
		<category><![CDATA[root]]></category>

		<guid isPermaLink="false">http://www.mtin.net/blog/?p=1492</guid>
		<description><![CDATA[From Internic This is advance notice that there is a scheduled change to the IPv4 address for one of the authorities listed for the DNS root zone and the .ARPA TLD. The change is to D.ROOT-SERVERS.NET, which is administered by the University of Maryland. The new IPv4 address for this authority is 199.7.91.13 The current [...]]]></description>
				<content:encoded><![CDATA[<p>From Internic</p>
<p>This is advance notice that there is a scheduled change to the IPv4<br />
address for one of the authorities listed for the DNS root zone and<br />
the .ARPA TLD. The change is to D.ROOT-SERVERS.NET, which is<br />
administered by the University of Maryland.</p>
<p>The new IPv4 address for this authority is 199.7.91.13</p>
<p>The current IPv6 address for this authority is  2001:500:2d::d and it<br />
will continue to remain unchanged.</p>
<p>This change is anticipated to be implemented in the root zone on 3<br />
January 2013, however the new address is currently operational. It<br />
will replace the previous IP address of 128.8.10.90 (also once known<br />
as TERP.UMD.EDU).</p>
<p>We encourage operators of DNS infrastructure to update any references<br />
to the old IP address, and replace it with the new address. In<br />
particular, many DNS resolvers have a DNS root “hints” file. This<br />
should be updated with the new IP address.</p>
<p>New hints files will be available at the following URLs once the<br />
change has been formally executed:</p>
<p>http://www.internic.net/domain/named.root</p>
<p>http://www.internic.net/domain/named.cache</p>
<p>The old address will continue to work for at least six months after<br />
the transition, but will ultimately be retired from service.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mtin.net/blog/d-root-changing-ipv4-address/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Some IPV6 best practices</title>
		<link>http://www.mtin.net/blog/some-ipv6-best-practices/</link>
		<comments>http://www.mtin.net/blog/some-ipv6-best-practices/#comments</comments>
		<pubDate>Tue, 11 Dec 2012 19:10:23 +0000</pubDate>
		<dc:creator>j2sw</dc:creator>
				<category><![CDATA[Networking]]></category>
		<category><![CDATA[addressing]]></category>
		<category><![CDATA[IP]]></category>
		<category><![CDATA[IPV6]]></category>

		<guid isPermaLink="false">http://www.mtin.net/blog/?p=1490</guid>
		<description><![CDATA[There has been a run of IPV6 questions to myself and on some of the mailing lists. I figured I would do a short list of some best practices for those of you who have a basic understanding of IPV6. -Use /48 for customer allocations. Give each customer a /48 unless they can show greater [...]]]></description>
				<content:encoded><![CDATA[<p>There has been a run of IPV6 questions to myself and on some of the mailing lists. I figured I would do a short list of some best practices for those of you who have a basic understanding of IPV6.</p>
<p>-Use /48 for customer allocations. Give each customer a /48 unless they can show greater justification.<br />
-Use /64 or /126 or /127 for P2P links<br />
-Use /128 for loopbacks. Assign the same loopbacks out of the same /64.  You won&#8217;t run out of looback addresses. <img src='http://www.mtin.net/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://www.mtin.net/blog/some-ipv6-best-practices/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.477 seconds -->
<!-- Cached page served by WP-Cache -->
