<html><head></head><body><div class="ydp946c14efyahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;"><div></div>
<div dir="ltr" data-setdir="false">Hi Joakim,</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Thanks for your response.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Will try to elaborate point2 with sample config.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false"><div><div>1. Config at Router R1</div><div><br></div><div>lo interface</div><div>interface loopback lo has ip addr 100.100.100.125 </div><div><br></div><div>eth1</div><div>for unnumbered borrowing the lo address for eth1 and 100.100.100.126 is the peer address</div><div>ip addr add 100.100.100.125 peer 100.100.100.126 dev eth1</div><div><br></div><div>eth2</div><div>for unnumbered borrowing the lo address for eth2 and 100.100.100.126 is the peer address</div><div>ip addr add 100.100.100.125 peer 100.100.100.126 dev eth2</div><div><br></div><div>2. Config at Router R2</div><div>Its identical to R1 config except for the loopback ip which is 100.100.100.126 and the corresponding</div><div>peer address config for eth1 and eth2</div><div><br></div><div><br></div><div>3. Enable ospf on eth1 and eth2 at R1 and R2</div><div><br></div><div>4. Only one of the ospf adj will become FULL either over eth1 or eth2 and not both</div><div><br></div><div>5. Since the peer address configurations adds a route to other end loopback address and since the</div><div>db packets are sent as unicast, route lookup happens and db packets wont be sent out from one of the links.</div><div><br></div><div>6. one ospf adj will be FULL and the other one will stay at EXSTART</div><div><br></div><div>7. if we use different peer address for each interface then it will work.</div><div><br></div><div dir="ltr" data-setdir="false">Thanks and Regards,</div><div dir="ltr" data-setdir="false">Senthil</div><div><br></div></div></div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false"><br></div><div><br></div>
</div><div id="ydpf0791e47yahoo_quoted_0639180105" class="ydpf0791e47yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Friday, May 7, 2021, 12:33:11 AM GMT+5:30, Joakim Tjernlund <joakim.tjernlund@infinera.com> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr">On Thu, 2021-05-06 at 20:30 +0200, Joakim Tjernlund wrote:<br clear="none">> On Thu, 2021-05-06 at 17:09 +0000, Senthil Kumar Nagappan wrote:<br clear="none">> > Hi,<br clear="none">> > <br clear="none">> > I did sent this message a week back but I could not see it in the mailing, moreover just now subscribed to this mailing list, so sending this again.<br clear="none">> > <br clear="none">> > I’m seeing some issues with ospf adj over ptp numbered/unnumbered interface. <br clear="none">> > <br clear="none">> > 1. For p2p connections, ospf should be sending only multicast packets to allospfrouters, but I see its sending to unicast address.<br clear="none">> > (From RFC “On physical point-to-point networks, the IP destination is always set to the address AllSPFRouters”)<br clear="none">> <br clear="none">> Agreed, I recall fixing the same for Quagga long time ago.<br clear="none">> <br clear="none">> > 2. For ptp over unnumbered interface, bird requires peer address configuration which is not required from the ospf perspective. Because bird is using peer address and sending<br clear="none">> > unicast packets, bird cannot form multiple ospf adj over ptp unnumbered interface between 2 endpoints using same peer address.<br clear="none">> > Made some quick changes and have attached the patch that addresses the issues. Relaxed the source ip address validation for ptp link in packet.c for now. More validation can be<br clear="none">> > added to make it complete.<br clear="none">> <br clear="none">> I don't quite understand what you are saying here, can you elaborate?<br clear="none">> <br clear="none"><br clear="none">One thing I recall, BIRD OSPF seems to always require dest IP address for its routes. For a PtoP I/F<br clear="none">this is optional/not needed so I guess this is a bug in BIRD. Possibly because of bug 1)<div class="ydpf0791e47yqt6138962308" id="ydpf0791e47yqtfd24722"><br clear="none"><br clear="none"> Jocke <br clear="none"><br clear="none"></div></div></div>
</div>
</div></body></html>