Feature #11186
closedAllow lo0/Loopback as a valid interface in OSPF/OSPF6
100%
Files
Updated by Jim Pingle almost 4 years ago
- Status changed from New to Pull Request Review
- Assignee deleted (
Jim Pingle)
Updated by Christian McDonald almost 4 years ago
Any update on this PRR?
Seems like a pretty benign easily validated pull request. I've been running this code for 2 weeks now without issue.
Updated by Ben Hughes over 3 years ago
I'm probably missing something obviously but I don't see what this achieves? You can already redistribution extra addresses on lo0 without needing to add lo0 as an ospf participating interface, I know the older JunOS docs semi-recommend doing this to redistribute even on interfaces where you aren't neighbouring with other OSPF routers but in both cases it's unlikely the best way to go.
I've been redistributing extra VIPs without issues for a good while now as management addresses without having lo0 participate in a OSPF.
Updated by Christian McDonald over 3 years ago
I've never gotten that to work. Adding VIPs to lo0 and then assigning that interface as a passive interface (after modifying the code to allow for this) is what worked for me.
Likewise adding a lo0 VIP and then creating a static Zebra route and redistributing those also didn't work for me.
I certainly would like to see how you're accomplishing this without assigning lo0 as passive interface.
Updated by Ben Hughes over 3 years ago
Just enable connected redistribution and they’ll be redistributed into OSPF. Then use route-map/access-list to filter if required.
I’ve used that with FRR and quagga previously without issue for at least the last 5 years, works on Linux in the same way.
Updated by Viktor Gurov over 3 years ago
- Status changed from Pull Request Review to Feedback
Merged four month ago
Updated by Alhusein Zawi over 3 years ago
lo0/Loopback is added as interface in OSPF