Siemen, im not certain I understand why you are applying route labels. also im not certain about your aims for your network design...
If you want good documentation on best practices... the cisco case studies /juniper white papers or talks at nanog / ripe meetings are a good place to start... as a rough rule of thumb ... for a simple single AS ... (not a huge one) use OSPF for link states and internal routing , Generally add stable networks / interfaces + your loobacks to your ospfd.conf (if an interface is added to ospfd) ospfd will advertise the attached connected networks as Intra Area routes) .and you can (should) iBGP working for advertising customer prefixes and Internet prefixes , generally iBGP src / destination of peering sessions are between loopbacks of your routers ebgp is (generally) between ips on the external interfaces of your router facing your provider / peer ... and vice versa with such a setup you dont need re-distribution... OSPF provides routing for local connectivity and BGP provides a way to get lots of Prefixes learned(internet full table) BGP next hop resolution will depend on the OSPF / Connected routes to function... but if all your connected networks / interfaces on the routers are in OSPF, you dont need to redistribute connected / OSPF routes Generally speaking re-distributing networks can lead to pain ... (particularly if your prefix filters are not up to scratch) oh yeah ..set loopback and external / untrusted interfaces (from customers/ peers) to passive in ospfd if you want to learn more ... keep an eye out for Peter Hesslers tutorial BGP at the BSD Conferences it would help you a great deal and great value for money... there are some good BGP tips here and they have some OpenBGPd samples (slightly dated) becuse Claudio / Job et all are doing some great work on that at the moment ... ) https://www.ssi.gouv.fr/uploads/2016/03/bgp-configuration-best-practices.pdf ( just be careful with URPF strict mode (if you have multiple paths use loose instead) I hope this Helps Tom Smyth.... PS ... My recommendations are very generalised and not a fix all policy... On Mon, 14 Jan 2019 at 20:48, Simen Stavdal <sstav...@gmail.com> wrote: > Hello, > > I have three routers connected in a chain. > A<->B<->C > > All routers have a host address as loopback 100 (192.168.5.x/32, A=1, B=2, > C=3). > The segments between the routers are 192.168.1.0/30 (AB) and > 192.168.2.0/30 > (BC). > > A to B runs OSPF > B to C runs IBGP > > I redistribute the BGP routes into OSPF using the label I append on router > B. > router B : match from <peer> set rtlabel zyx > And this works just fine. I see the tag being applied (but only on the > advertised lo100 host address). > Reverse redistribution is based on route priority (32) for OSPF into bgp. > All good. > > The link network however between B and C is not being advertised, as it is > locally connected for both router B and C. They are added in the network > statement on both sides. > So, on B, I can see the route label on the C loopback interface marked zyx. > 192.168.2.0/30 however does not have any route label, and hence will not > be > redistributed into OSPF. > > So, I can ping router C from router B. > When I ping loopback on router C from router A using the loopback interface > as source, all is good. > When I ping with no source interface, the source address is the link > network not being advertised, and hence the far router does not know where > to send the traffic. > > I will continue to play around with this, just wondering if anybody has a > "good practice" way of dynamically advertising the network. > > Cheers, > Simon. > -- Kindest regards, Tom Smyth Mobile: +353 87 6193172 The information contained in this E-mail is intended only for the confidential use of the named recipient. If the reader of this message is not the intended recipient or the person responsible for delivering it to the recipient, you are hereby notified that you have received this communication in error and that any review, dissemination or copying of this communication is strictly prohibited. If you have received this in error, please notify the sender immediately by telephone at the number above and erase the message You are requested to carry out your own virus check before opening any attachment.
