Hi, Simen Stavdal([email protected]) on 2019.01.14 21:29:43 +0100: > 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.
Your mail is missing - what version of openbsd you are running, i.e. dmesg - your bgpd.conf and ospfd.conf files would be helpful. - you describe what you have currently configured, but not what your actual intent is. It may be better if you say what you want your network devices to do. That said, if i understand what you are doing right, maybe "network inet connected" on router B bgpd.conf will help. (you may also need filters to allow the prefix to be sent to C). /Benno
