<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Tech-Recipes - Latest Comments in The dark secrets of loopback addresses | Cisco networking | Tech-Recipes</title><link>http://tech-recipes.disqus.com/</link><description>Cookbook of Tech Tutorials</description><language>en</language><lastBuildDate>Fri, 27 Jun 2008 07:04:05 -0000</lastBuildDate><item><title>Re: The dark secrets of loopback addresses | Cisco networking | Tech-Recipes</title><link>http://www.tech-recipes.com/rx/2019/dark_secrets_of_loopback_addresses_cisco/#comment-2770609</link><description>I don't know quite where to start with this but if you're looking for info I'd suggest looking elsewhere.&lt;br&gt;&lt;br&gt;First, loopbacks don't have much to do with troubleshooting. You can ping one or use it as the source for pings but you can do that with any interface with an IP. &lt;br&gt;&lt;br&gt;Loopbacks are often used for router management but can also be used to provide virtual interfaces for things like GRE tunnels. The reason you use a loopback is that a physical interface can go down but the loopback, being virtual, is up as long as the router is up.&lt;br&gt;&lt;br&gt;Regarding OSPF, the term "feasible successor" is from EIGRP, it's not used in OSPF. I think the author was looking for is Router ID. This the IP the router uses to identify itself to other routers running OSPF.  The router is determined thusly:&lt;br&gt;&lt;br&gt;1 Use the address configured by the ospf router-id command&lt;br&gt;2 Use the address of the loopback 0 interface&lt;br&gt;3 Use the highest IP address of any interface&lt;br&gt;4 If no interface exists, set the router-ID to 0.0.0.0</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AWfki</dc:creator><pubDate>Fri, 27 Jun 2008 07:04:05 -0000</pubDate></item></channel></rss>