Home Lab – Page 3 – routingloop.net

Faster EIGRP Feasible Successor Failover

The feasible successor is EIGRP predetermining an alternate next hop to reach a destination for fast failover. The feasible successor route is stored in the EIGRP topology table but is not installed in the RIB/FIB by default. The variance command can be used to promote the feasible successor to the routing table and traffic will

OSPF in Phase 1 DMVPN Networks

21JuneStevenENSLD, Home Lab, Routing

When designing hub and spoke networks, most architects will opt for distance or path vector routing protocols when given the choice. I don’t blame them, distance/path vector provides several benefits that work well in hub and spoke topologies. EIGRP based hub and spoke networks can scale to thousands of spokes without much work. Route summarization

OSPFv2 Link State Advertisements

14MayStevenHome Lab, Routing

Link State Advertisements (LSAs) are one of hardest things to understand while learning OSPF. I believe that having a basic understanding of the LSA types and being able to interpret them is crucial to understanding OSPF operation. LSAs are flooded to populate the Link State Database (LSDB) on routers participating in OSPF. The content of

HSRP vs VRRP

8AprilStevenHome Lab

On the surface Cisco’s HSRP and the IETF’s VRRP appear to be the same thing. They both provide IP next hop redundancy by using an election process to determine which router should host a virtual IP address. The router that wins the election will host the VIP and respond to ARP requests for the VIP.

It works! (kinda)

25MarchStevenHome Lab, Routing

We finally have spoke to spoke traffic working in our phase 1 DMVPN! After fixing the BGP third party next hop issue described in the last post we still had reachability issues between spokes. The spokes could reach the hub and the hub could reach the spokes just fine. Traffic transiting the hub to route

Home Lab DMVPN Lessons Learned

19MarchStevenHome Lab, Routing

My last post was about the home-to-home DMVPN we’ve been working on. The design intent was to build a phase 1 DMVPN so spoke to spoke traffic should use the hub as a transit node. It wasn’t until we tried to forward traffic from spoke to spoke that we realized we have issues. Spoke to

Home to Home DMVPN and Raspberry Pi Wireless Links

17MarchStevenHome Lab, Routing

Some months ago, I got in contact with one of my old colleagues and friend. Our discussion led to trying to decide what to do next with our home labs. He mentioned that he has a small block of provider assigned public IPv4 addresses. We got what seemed like a crazy idea – “Let’s do

eBGP, TTL and Connected-Check

4MarchStevenHome Lab, Routing

It is well known that eBGP packets default to having a Time to Live (TTL) value of 1. This has caused confusion for many network practitioners who wish to run eBGP between loopback addresses of directly connected routers. This misunderstanding sometimes leads to ebgp-multihop being configured when it is not necessary. This also gave me

Dead Peer Detection in Multipath Networks

22FebruaryStevenHome Lab

When I learned about Dead Peer Detection, I assumed it to be some generic IPsec keepalive and didn’t put much thought into it. A few weeks ago, I became more interested in DPD and started reading RFC 3706. I learned that DPD is a feature of IKE and I started considering how the protocol may

Next Hop Recursive-Looped

4FebruaryStevenHome Lab, Routing

In this morning’s lab exercise I intentionally designed and configured a network to cause recursively looped routing lookups. When I started the experiment, I did not know this is the term for this condition. I simply wanted to see what would happen if the route to the destination was also the route to the next

routingloop.net

A place for me to ramble about computer networking.

Category Archives: Home Lab