summaryrefslogtreecommitdiff
path: root/ospfd/ospf_lsa.c
AgeCommit message (Collapse)Author
2023-10-12build: add -Wimplicit-fallthroughIgor Ryzhov
Also: - replace all /* fallthrough */ comments with portable fallthrough; pseudo keyword to accomodate both gcc and clang - add missing break; statements as required by older versions of gcc - cleanup some code to remove unnecessary fallthrough Signed-off-by: Igor Ryzhov <iryzhov@nfware.com>
2023-07-25* : include event ptr in event_execute apiMark Stapp
Include an event ptr-to-ptr in the event_execute() api call, like the various schedule api calls. This allows the execute() api to cancel an existing scheduled task if that task is being executed inline. Signed-off-by: Mark Stapp <mjs@labn.net>
2023-07-20ospfd: Implement OSPF prefix-suppression as specified in RFC 6860Acee
Signed-off-by: Acee <aceelindem@gmail.com>
2023-07-07ospf: fix lsa leakryndia
In the function ospf_lsa_translated_nssa_new the newly created lsa is lock however, the return lsa from ospf_lsa_new already has a lock. Therefore removing the addition lock resolve the leak below. ospf_basic_functionality.test_ospf_nssa#r3.asan.ospfd.5456 ================================================================= ==5456==ERROR: LeakSanitizer: detected memory leaks Direct leak of 640 byte(s) in 5 object(s) allocated from: #0 0x7f294f354a37 in __interceptor_calloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:154 #1 0x7f294eeed562 in qcalloc ../lib/memory.c:105 #2 0x561a16004f60 in ospf_lsa_new ../ospfd/ospf_lsa.c:186 #3 0x561a160051a1 in ospf_lsa_new_and_data ../ospfd/ospf_lsa.c:205 #4 0x561a1600f21d in ospf_exnl_lsa_prepare_and_flood ../ospfd/ospf_lsa.c:1762 #5 0x561a1600fd71 in ospf_external_lsa_new ../ospfd/ospf_lsa.c:1863 #6 0x561a160107d7 in ospf_lsa_translated_nssa_new ../ospfd/ospf_lsa.c:1985 #7 0x561a16011cfb in ospf_translated_nssa_refresh ../ospfd/ospf_lsa.c:2152 #8 0x561a16014bb2 in ospf_external_lsa_install ../ospfd/ospf_lsa.c:2871 #9 0x561a1601596b in ospf_lsa_install ../ospfd/ospf_lsa.c:3076 #10 0x561a16168b3c in ospf_flood ../ospfd/ospf_flood.c:482 #11 0x561a160462f8 in ospf_ls_upd ../ospfd/ospf_packet.c:2115 #12 0x561a1604c66c in ospf_read_helper ../ospfd/ospf_packet.c:3198 #13 0x561a1604c88e in ospf_read ../ospfd/ospf_packet.c:3229 #14 0x7f294efd6c33 in event_call ../lib/event.c:1995 #15 0x7f294eec134a in frr_run ../lib/libfrr.c:1213 #16 0x561a15fd3b6d in main ../ospfd/ospf_main.c:249 #17 0x7f294e998d8f in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:58 Objects leaked above: 0x60c000062800 (128 bytes) 0x60c000062c80 (128 bytes) 0x60c0000631c0 (128 bytes) 0x60c000063700 (128 bytes) 0x60c000063d00 (128 bytes) Direct leak of 640 byte(s) in 5 object(s) allocated from: #0 0x7f294f354a37 in __interceptor_calloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:154 #1 0x7f294eeed562 in qcalloc ../lib/memory.c:105 #2 0x561a16004f60 in ospf_lsa_new ../ospfd/ospf_lsa.c:186 #3 0x561a160051a1 in ospf_lsa_new_and_data ../ospfd/ospf_lsa.c:205 #4 0x561a1600f21d in ospf_exnl_lsa_prepare_and_flood ../ospfd/ospf_lsa.c:1762 #5 0x561a1600fd71 in ospf_external_lsa_new ../ospfd/ospf_lsa.c:1863 #6 0x561a160107d7 in ospf_lsa_translated_nssa_new ../ospfd/ospf_lsa.c:1985 #7 0x561a16010e10 in ospf_translated_nssa_originate ../ospfd/ospf_lsa.c:2034 #8 0x561a16136559 in ospf_abr_translate_nssa ../ospfd/ospf_abr.c:668 #9 0x561a161383da in ospf_abr_process_nssa_translates ../ospfd/ospf_abr.c:968 #10 0x561a1613f9b8 in ospf_abr_nssa_task ../ospfd/ospf_abr.c:2054 #11 0x561a161402e5 in ospf_abr_task_timer ../ospfd/ospf_abr.c:2168 #12 0x7f294efd6c33 in event_call ../lib/event.c:1995 #13 0x7f294eec134a in frr_run ../lib/libfrr.c:1213 #14 0x561a15fd3b6d in main ../ospfd/ospf_main.c:249 #15 0x7f294e998d8f in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:58 Objects leaked above: 0x60c00003e380 (128 bytes) 0x60c00003e740 (128 bytes) 0x60c00003eb00 (128 bytes) 0x60c00005fd40 (128 bytes) 0x60c00005ff80 (128 bytes) Indirect leak of 180 byte(s) in 5 object(s) allocated from: #0 0x7f294f354a37 in __interceptor_calloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:154 #1 0x7f294eeed562 in qcalloc ../lib/memory.c:105 #2 0x561a16005a43 in ospf_lsa_data_new ../ospfd/ospf_lsa.c:296 #3 0x561a160051b1 in ospf_lsa_new_and_data ../ospfd/ospf_lsa.c:206 #4 0x561a1600f21d in ospf_exnl_lsa_prepare_and_flood ../ospfd/ospf_lsa.c:1762 #5 0x561a1600fd71 in ospf_external_lsa_new ../ospfd/ospf_lsa.c:1863 #6 0x561a160107d7 in ospf_lsa_translated_nssa_new ../ospfd/ospf_lsa.c:1985 #7 0x561a16011cfb in ospf_translated_nssa_refresh ../ospfd/ospf_lsa.c:2152 #8 0x561a16014bb2 in ospf_external_lsa_install ../ospfd/ospf_lsa.c:2871 #9 0x561a1601596b in ospf_lsa_install ../ospfd/ospf_lsa.c:3076 #10 0x561a16168b3c in ospf_flood ../ospfd/ospf_flood.c:482 #11 0x561a160462f8 in ospf_ls_upd ../ospfd/ospf_packet.c:2115 #12 0x561a1604c66c in ospf_read_helper ../ospfd/ospf_packet.c:3198 #13 0x561a1604c88e in ospf_read ../ospfd/ospf_packet.c:3229 #14 0x7f294efd6c33 in event_call ../lib/event.c:1995 #15 0x7f294eec134a in frr_run ../lib/libfrr.c:1213 #16 0x561a15fd3b6d in main ../ospfd/ospf_main.c:249 #17 0x7f294e998d8f in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:58 Objects leaked above: 0x60400003f890 (36 bytes) 0x60400003f990 (36 bytes) 0x60400003fa50 (36 bytes) 0x60400003fb10 (36 bytes) 0x60400003fbd0 (36 bytes) Indirect leak of 180 byte(s) in 5 object(s) allocated from: #0 0x7f294f354a37 in __interceptor_calloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:154 #1 0x7f294eeed562 in qcalloc ../lib/memory.c:105 #2 0x561a16005a43 in ospf_lsa_data_new ../ospfd/ospf_lsa.c:296 #3 0x561a160051b1 in ospf_lsa_new_and_data ../ospfd/ospf_lsa.c:206 #4 0x561a1600f21d in ospf_exnl_lsa_prepare_and_flood ../ospfd/ospf_lsa.c:1762 #5 0x561a1600fd71 in ospf_external_lsa_new ../ospfd/ospf_lsa.c:1863 #6 0x561a160107d7 in ospf_lsa_translated_nssa_new ../ospfd/ospf_lsa.c:1985 #7 0x561a16010e10 in ospf_translated_nssa_originate ../ospfd/ospf_lsa.c:2034 #8 0x561a16136559 in ospf_abr_translate_nssa ../ospfd/ospf_abr.c:668 #9 0x561a161383da in ospf_abr_process_nssa_translates ../ospfd/ospf_abr.c:968 #10 0x561a1613f9b8 in ospf_abr_nssa_task ../ospfd/ospf_abr.c:2054 #11 0x561a161402e5 in ospf_abr_task_timer ../ospfd/ospf_abr.c:2168 #12 0x7f294efd6c33 in event_call ../lib/event.c:1995 #13 0x7f294eec134a in frr_run ../lib/libfrr.c:1213 #14 0x561a15fd3b6d in main ../ospfd/ospf_main.c:249 #15 0x7f294e998d8f in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:58 Objects leaked above: 0x60400003c6d0 (36 bytes) 0x60400003c790 (36 bytes) 0x60400003c810 (36 bytes) 0x60400003c890 (36 bytes) 0x60400003c910 (36 bytes) SUMMARY: AddressSanitizer: 1640 byte(s) leaked in 20 allocation(s). Signed-off-by: ryndia <dindyalsarvesh@gmail.com>
2023-05-10ospfd: Respect loopback's cost that is set and set loopback costs to 0Donald Sharp
When setting an loopback's cost, set the value to 0, unless the operator has assigned a value for the loopback's cost. RFC states: If the state of the interface is Loopback, add a Type 3 link (stub network) as long as this is not an interface to an unnumbered point-to-point network. The Link ID should be set to the IP interface address, the Link Data set to the mask 0xffffffff (indicating a host route), and the cost set to 0. FRR is going to allow this to be overridden if the operator specifically sets a value too. Fixes: #13472 Signed-off-by: Donald Sharp <sharpd@nvidia.com>
2023-04-18ospfd: handle type-7 routesJafar Al-Gharaibeh
Signed-off-by: Jafar Al-Gharaibeh <jafar@atcorp.com>
2023-04-12Merge pull request #13269 from Keelan10/ospf_lsa-memory-leakDonald Sharp
ospfd: Fix ospf_lsa memory leak
2023-04-12ospfd: Fix ospf_lsa memory leakKeelan10
Free translated LSA when LSA installation fails Signed-off-by: Keelan Cannoo <keelan.cannoo@icloud.com>
2023-03-31ospfd: remove duplicated codeRenato Westphal
Signed-off-by: Renato Westphal <renato@opensourcerouting.org>
2023-03-31ospfd: implement Type-7 default routes for NSSA areasRenato Westphal
Add the "default-information-originate" option to the "area X nssa" command. That option allows the origination of Type-7 default routes on NSSA ABRs and ASBRs. Signed-off-by: Renato Westphal <renato@opensourcerouting.org>
2023-03-24Merge pull request #12953 from donaldsharp/struct_eventJafar Al-Gharaibeh
Struct event
2023-03-24Merge pull request #13093 from manojvn/ospf_mem_leaksDonald Sharp
ospfd: Fix for memory leak issue in ospf related to flood_reduction tests.
2023-03-24*: Convert event.h to frrevent.hDonald Sharp
We should probably prevent any type of namespace collision with something else. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
2023-03-24*: Convert THREAD_XXX macros to EVENT_XXX macrosDonald Sharp
Signed-off-by: Donald Sharp <sharpd@nvidia.com>
2023-03-24*: Convert thread_should_yield and thread_set_yield_timeDonald Sharp
Convert thread_should_yield and thread_set_yield_time to event_should_yield and event_set_yield_time Signed-off-by: Donald Sharp <sharpd@nvidia.com>
2023-03-24*: Convert thread_execute to event_executeDonald Sharp
Signed-off-by: Donald Sharp <sharpd@nvidia.com>
2023-03-24*: Convert thread_add_XXX functions to event_add_XXXDonald Sharp
Signed-off-by: Donald Sharp <sharpd@nvidia.com>
2023-03-24*: Rename `struct thread` to `struct event`Donald Sharp
Effectively a massive search and replace of `struct thread` to `struct event`. Using the term `thread` gives people the thought that this event system is a pthread when it is not Signed-off-by: Donald Sharp <sharpd@nvidia.com>
2023-03-24*: Rename thread.[ch] to event.[ch]Donald Sharp
This is a first in a series of commits, whose goal is to rename the thread system in FRR to an event system. There is a continual problem where people are confusing `struct thread` with a true pthread. In reality, our entire thread.c is an event system. In this commit rename the thread.[ch] files to event.[ch]. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
2023-03-23ospfd: Fix for memory leak issue in ospf related to flood_reduction tests.Manoj Naragund
Problem: Multiple memory leaks after pr12366 RCA: ospf_lsa_unlock was not happening for the few of the LSAs in ospf_lsa_refresh_walker after pr12366 due to which memory related to lsas was leaking. Fix: Moved the ospf_lsa_unlock outside if check. Signed-off-by: Manoj Naragund <mnaragund@vmware.com>
2023-03-21ospfd: Fixing Summary origination after range configurationrgirada
Description: After area range config, summary lsas are aggerated to configured route but later it was being flushed instead of the actual summary lsa. This was seen when prefix-id of the aggregated route is same as one of the actual summary route. Here, aggregated summary lsa need to be returned to set the flag SUMMARY_APPROVE after originating aggregated summary lsa but its not. Which is being cleaned up as part of unapproved summary cleanup. Corrected this now. Issue: #13028 Signed-off-by: Rajesh Girada <rgirada@vmware.com>
2023-03-17ospfd: Ospf ABR doesnt Advertise LSA summaryrgirada
Description: OSPF ABR will summarise the networks based on configured range and re-advtertise the summarised route. But if configured range prefix id is same as one of the subset of routes prefix id then as per rcf2328 Appendex-E recommendation, it will prepare the LSID and originate. While re-advertising, it is using ospf LSDB instead of area specific LSDB which is making it fail to re-advertise the summary lsa. Fixed this by passing correct LSDB pointer. Issue: #12995 Signed-off-by: Rajesh Girada <rgirada@vmware.com>
2023-02-21Merge pull request #12366 from manojvn/ospfv2-flood-reductionRuss White
ospfd: Support OSPF Refresh and Flooding Reduction RFC4136.
2023-02-09*: auto-convert to SPDX License IDsDavid Lamparter
Done with a combination of regex'ing and banging my head against a wall. Signed-off-by: David Lamparter <equinox@opensourcerouting.org>
2023-01-19ospfd: Core logic implementation.Manoj Naragund
Description: Code changes involves. 1. Count the no.of router LSAs received with DC options bit set, supporting do not age(DNA). 2. If no of router LSAs received with DC bit set is equal to total no of LSAs in the router lsdb, then all the routers in the area support do not age processing. 3. Flood the self originated LSAs with DNA flag if all routers in the area supports the feature. 4. Stop aging of the LSAs recived with DO_NOT_AGE bit set from other routers. 5. Self originated DO_NOT_AGE lsas will still be aging in their own database. Signed-off-by: Manoj Naragund <mnaragund@vmware.com>
2023-01-17Revert "ospfd: rSPF calc and messaging for optimal route reflection"Donatas Abraitis
This reverts commit a3d3a14c09cf212c7d402670247c4d518b99d8b7.
2023-01-17Revert "ospfd: few fixes in rSPF calc when LSA received from non root node"Donatas Abraitis
This reverts commit 9f2984d97c2e23198db47d39a725f3c50d2ee0ed.
2022-12-12ospfd: fix typo and report the link name in the warningJafar Al-Gharaibeh
Submitted-by: Marc Boucher <marc@airvitesse.net> Signed-off-by: Jafar Al-Gharaibeh <jafar@atcorp.com>
2022-11-21ospfd: Fix RFC conformance test cases 25.19 and 27.6Mobashshera Rasool
Steps to reproduce: -------------------------- 1. ANVL: Establish full adjacency with DUT for neighbor Rtr-0-A on DIface-0 with DUT as DR. 2. ANVL: Listen (for up to 2 * <RxmtInterval> seconds) on DIface-0. 3. DUT: Send <OSPF-LSU> packet. 4. ANVL: Verify that the received <OSPF-LSU> packet contains a Network- LSA for network N1 originated by DUT, and the LS Sequence Number is set to <InitialSequenceNumber>. 5. ANVL: Establish full adjacency with DUT for neighbor Rtr-0-B on DIface-0 with DUT as DR. 6. ANVL: Listen (for up to 2 * <RxmtInterval> seconds) on DIface-0. 7. DUT: Send <OSPF-LSU> packet. 8. ANVL: Verify that the received <OSPF-LSU> packet contains a new instance of the Network-LSA for network N1 originated by DUT, and the LS Sequence Number is set to (<InitialSequenceNumber> + 1). Both the test cases were failing while verifying the initial sequence number for network LSA. This is because currently OSPF does not reset its LSA sequence number when it is going down. Signed-off-by: Mobashshera Rasool <mrasool@vmware.com>
2022-11-10ospfd: prevent from crashing when processing external lsaPhilippe Guibert
When using debug mode, the ei parameter may be NULL. In that case, do not display the log trace, otherwise a crash will happen. Signed-off-by: Philippe Guibert <philippe.guibert@6wind.com>
2022-10-29Merge pull request #12215 from LabNConsulting/working/lb/ospf-allow-for-zeroJafar Al-Gharaibeh
ospfd: remove asster on zero length LSA - which is permitted by spec
2022-10-28ospfd: remove assert on zero length LSA - which is permitted by specLou Berger
Signed-off-by: Lou Berger <lberger@labn.net>
2022-10-21ospfd/ospfclient: add option to flush/withdrawal with zero lengthLou Berger
default behavior is unchanged, i.e., to not zero Signed-off-by: Lou Berger <lberger@labn.net>
2022-10-12ospfd: few fixes in rSPF calc when LSA received from non root nodeMadhuri Kuruganti
Signed-off-by: Madhuri Kuruganti <maduri111@gmail.com>
2022-10-12ospfd: rSPF calc and messaging for optimal route reflectionMadhuri Kuruganti
Signed-off-by: Madhuri Kuruganti <maduri111@gmail.com>
2022-09-06Merge pull request #11864 from manojvn/clisDonatas Abraitis
ospfd: Added clis to change default timers for LSA refresh and maxage remove delay.
2022-08-31ospfd: Added clis to change default timers for LSA refresh and maxage remove ↵Manoj Naragund
delay. Description: Added hidden clis that will allow you to reset the default timers for LSA refresh and LSA maxage remove delay, these will help in testing LSA refresh scenarios in upcoming OSPFv2 Flood reduction feature(rfc4136). IETF Link : https://datatracker.ietf.org/doc/html/rfc4136 Signed-off-by: Manoj Naragund <mnaragund@vmware.com>
2022-08-30ospfd: crash when router acts as GR helper upon a topo changergirada
Description: ospf process is crashing when the current router acts as GR helper and it received a new lsa. Here, ospf_lsa_different() is being called without checking 'old' pointer. It is asserted in ospf_lsa_different() api if the 'old' pointer is NULL. corrected this by validaing old pointer before calling ospf_lsa_different() api. back tarce: Program terminated with signal SIGABRT, Aborted. 0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 [Current thread is 1 (Thread 0x6b84348827c0 (LWP 3155))] 0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 1 0x00006b8433aa4801 in __GI_abort () at abort.c:79 2 0x00006b8433a9439a in __assert_fail_base (fmt=0x6b8433c1b7d8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x162ffc0630bc "l1", file=file@entry=0x162ffc062ff7 "ospfd/ospf_lsa.c", line=line@entry=3520, function=function@entry=0x162ffc0646f0 <__PRETTY_FUNCTION__.18732> "ospf_lsa_different") at assert.c:92 3 0x00006b8433a94412 in __GI___assert_fail (assertion=assertion@entry=0x162ffc0630bc "l1", file=file@entry=0x162ffc062ff7 "ospfd/ospf_lsa.c", line=line@entry=3520, function=function@entry=0x162ffc0646f0 <__PRETTY_FUNCTION__.18732> "ospf_lsa_different") at assert.c:101 4 0x0000162ffc008c25 in ospf_lsa_different (l1=l1@entry=0x0, l2=l2@entry=0x162ffe535c60, ignore_rcvd_flag=ignore_rcvd_flag@entry=true) at ospfd/ospf_lsa.c:3520 5 0x0000162ffc00a8e8 in ospf_lsa_install (ospf=ospf@entry=0x162ffe513650, oi=oi@entry=0x162ffe531c30, lsa=lsa@entry=0x162ffe535c60) at ospfd/ospf_lsa.c:2892 6 0x0000162ffc059d16 in ospf_flood (ospf=0x162ffe513650, nbr=nbr@entry=0x162ffe52cc90, current=current@entry=0x0, new=new@entry=0x162ffe535c60) at ospfd/ospf_flood.c:429 7 0x0000162ffc01838f in ospf_ls_upd (size=<optimized out>, oi=0x162ffe531c30, s=<optimized out>, ospfh=<optimized out>, iph=<optimized out>, ospf=<optimized out>) at ospfd/ospf_packet.c:2162 8 ospf_read_helper (ospf=<optimized out>) at ospfd/ospf_packet.c:3241 9 ospf_read (thread=<optimized out>) at ospfd/ospf_packet.c:3272 10 0x00006b843450139c in thread_call (thread=thread@entry=0x7780f42c7480) at lib/thread.c:1692 11 0x00006b84344cfb18 in frr_run (master=0x162ffe34d130) at lib/libfrr.c:1068 Signed-off-by: Rajesh Girada <rgirada@vmware.com>
2022-08-24ospfd: changes for code maintainabilitysri-mohan1
these changes are for improving the code maintainability Signed-off-by: sri-mohan1 <sri.mohan@samsung.com>
2022-07-27ospfd: Coverity warns that we could possibly use unininted dataDonald Sharp
In ospf_handle_exnl_lsa_lsId_chg there is a code path where that we may be using uninitialized data for decisions. Doubtful that this happens but let's make it less likely to even more. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
2022-07-21ospfd: Remove various macros that overlap THREAD_OFFDonald Sharp
Let's just use THREAD_OFF consistently in the code base instead of each daemon having a special macro that needs to be looked at and remembered what it does. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
2022-07-20ospfd: correct one debug info for lsaanlan_cs
The index about slots should be displayed as `slot`. Additionally, adjust format. Signed-off-by: anlan_cs <vic.lan@pica8.com>
2022-05-11*: Properly use memset() when zeroingDonatas Abraitis
Wrong: memset(&a, 0, sizeof(struct ...)); Good: memset(&a, 0, sizeof(a)); Signed-off-by: Donatas Abraitis <donatas@opensourcerouting.org>
2022-04-19*: Fix spelling of accomodateDonald Sharp
Signed-off-by: Donald Sharp <sharpd@nvidia.com>
2022-04-19*: Fix spelling of comparisionDonald Sharp
Signed-off-by: Donald Sharp <sharpd@nvidia.com>
2022-03-21ospfd: Default route becomes stale route in nbrs even after flush from ↵rgirada
originator. Description: Default route is not getting flushed from neighbours though originator triggered flush and deleted LSA from its database. It become as stale LSA in neighbours databse forever. This could seen in the following sequence of configurations with less than a second interval b/w configs. And this could happen only when originator shouldnt have default route in its rib so it originates default route only when configure with 'always' option. step-1:default-information originate always step-2:no default-information originate always step-3:default-information originate In step-1, default route will be originated to AS. In step-2, default route will be flushed to AS, but neighbours will be discarding this update due to minlsainterval condition. And it is expected that DUT need to keep send this update until it receives the ack from neighbours by adding each neighbour's retransmission list. In Step-3: It is deleting the lsas from nbr's retransmission list by assuming it initiated the flush. This is cuasing to not send the lsa update anymore to neighbours which makes stale lsa in nbrs forever. Fix: Allowed to delete the lsa from retransmission list only when lsa is not in maxage during flushing procedure. Signed-off-by: Rajesh Girada <rgirada@vmware.com>
2022-02-24ospfd: NULL passed instead of ei pointer in external lsa originationrgirada
Description: NULL pointer wrongly passed instead of 'ei' pointer to ospf_external_lsa_originate() API in opaque capability enable/disable which always make it to fail in origination. Corrected it by passing actual ei pointer. Signed-off-by: Rajesh Girada <rgirada@vmware.com>
2022-02-23*: Change thread->func to return void instead of intDonald Sharp
The int return value is never used. Modify the code base to just return a void instead. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
2022-02-08Merge pull request #10293 from rgirada/ospf_lsidRuss White
ospfd: Modifying LSID generation algorithm
2022-02-07ospfd: Use AF_UNSPEC instead of setting to 0Donald Sharp
Signed-off-by: Donald Sharp <sharpd@nvidia.com>