The thing to remember with this though (which can be good and bad) is that it will automatically send any connected interface's route to any OSPF neighbours, so if you added loopback2 with 10.20.20.20/24 you'd see that in R2's routing table without touching the routing protocol. You'll never advertise anything 'through' the loopback interface, so redistributing the connected interfaces will also work. That will advertise all routes from R1 to R2.Īdding networks to the OSPF process actually enables OSPF on the interfaces where the IP sits. router ospf 1 redistribute connected network 10.1.1.1 0.0.0.0 area 0 As another option, you could also use the redistribute connected command in the OSPF process rather than including the network statement for the loopback. Predrag's comment lets you use dynamic routes without adding a static, which is more to the point here, considering you're using OSPF, but you didn't reveal that until after Fred commented. Packets destined for that address will likely be dropped somewhere pretty quickly unless there's a route.
It's a means to transport IP traffic while conserving IP addresses. 255.255.255.252 has but 2 usable addresses. Written By Lazaros Agapidis A loopback interface is a virtual interface that can be created within a network device and behaves much the same as a physical interface.
