<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://baranoski.ca/index.php?action=history&amp;feed=atom&amp;title=Using_HSRP_On_A_%2F30_or_%2F31</id>
	<title>Using HSRP On A /30 or /31 - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://baranoski.ca/index.php?action=history&amp;feed=atom&amp;title=Using_HSRP_On_A_%2F30_or_%2F31"/>
	<link rel="alternate" type="text/html" href="https://baranoski.ca/index.php?title=Using_HSRP_On_A_/30_or_/31&amp;action=history"/>
	<updated>2026-04-15T08:28:42Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.35.1</generator>
	<entry>
		<id>https://baranoski.ca/index.php?title=Using_HSRP_On_A_/30_or_/31&amp;diff=57&amp;oldid=prev</id>
		<title>Casey: Created page with &quot;__NOTOC__  It&#039;s common for business ISPs to use a /30 as a point-to-point to their customers, then route them a /29 or larger.  Normally, using a /30 precludes the possibility...&quot;</title>
		<link rel="alternate" type="text/html" href="https://baranoski.ca/index.php?title=Using_HSRP_On_A_/30_or_/31&amp;diff=57&amp;oldid=prev"/>
		<updated>2013-06-20T20:52:22Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;__NOTOC__  It&amp;#039;s common for business ISPs to use a /30 as a point-to-point to their customers, then route them a /29 or larger.  Normally, using a /30 precludes the possibility...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;__NOTOC__&lt;br /&gt;
&lt;br /&gt;
It&amp;#039;s common for business ISPs to use a /30 as a point-to-point to their customers, then route them a /29 or larger.  Normally, using a /30 precludes the possibility of having redundant routers terminating the connection.  The common belief is that you need a minimum of a /29 for HSRP: one IP for router A, one for router B, one for the HSRP High Availability address, and the rest for the clients.&lt;br /&gt;
&lt;br /&gt;
In reality, the IPs on router A and B need to be in the same subnet, but it does not need to be the same subnet as the HA address. For example:&lt;br /&gt;
&lt;br /&gt;
* ISP Gateway: 24.1.1.0/31&lt;br /&gt;
* Customer HA address: 24.1.1.1/31&lt;br /&gt;
* Customer Router A Outside Interface (Fa0): 192.168.0.1/30&lt;br /&gt;
* Customer Router B Outside Interface (Fa0): 192.168.0.2/30&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Interface Config==&lt;br /&gt;
====Router A====&lt;br /&gt;
&amp;lt;PRE&amp;gt;&lt;br /&gt;
interface FastEthernet0&lt;br /&gt;
 ip address 192.168.0.1 255.255.255.252&lt;br /&gt;
 standby 1 ip 24.1.1.1&lt;br /&gt;
&amp;lt;/PRE&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Router B====&lt;br /&gt;
&amp;lt;PRE&amp;gt;&lt;br /&gt;
interface FastEthernet0&lt;br /&gt;
 ip address 192.168.0.2 255.255.255.252&lt;br /&gt;
 standby 1 ip 24.1.1.1&lt;br /&gt;
&amp;lt;/PRE&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Route Config==&lt;br /&gt;
Routers A and B just need an interface route to be able to direct the traffic to the ISP&amp;#039;s gateway, and their default route pointing to the ISP&amp;#039;s gateway&lt;br /&gt;
&lt;br /&gt;
====Router A====&lt;br /&gt;
&amp;lt;PRE&amp;gt;&lt;br /&gt;
ip route 24.1.1.0 255.255.255.254 fa0&lt;br /&gt;
ip route 0.0.0.0 0.0.0.0 24.1.1.0&lt;br /&gt;
&amp;lt;/PRE&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Router B==== &lt;br /&gt;
&amp;lt;PRE&amp;gt;&lt;br /&gt;
ip route 24.1.1.0 255.255.255.254 fa0&lt;br /&gt;
ip route 0.0.0.0 0.0.0.0 24.1.1.0&lt;br /&gt;
&amp;lt;/PRE&amp;gt;&lt;/div&gt;</summary>
		<author><name>Casey</name></author>
	</entry>
</feed>