summaryrefslogtreecommitdiffstats
path: root/zebra/zserv.h
diff options
context:
space:
mode:
authorDonald Sharp <sharpd@cumulusnetworks.com>2019-02-04 17:45:31 +0100
committerDonald Sharp <sharpd@cumulusnetworks.com>2019-02-05 15:13:30 +0100
commita8a20c4e3c602fb132090178799813a2dfcf3c4a (patch)
treeba487681dc6d1fbe7e405d30b9bddc117766081f /zebra/zserv.h
parentMerge pull request #3698 from donaldsharp/netlink_is_serious_business (diff)
downloadfrr-a8a20c4e3c602fb132090178799813a2dfcf3c4a.tar.xz
frr-a8a20c4e3c602fb132090178799813a2dfcf3c4a.zip
zebra: Remove zclient->idinfo restrictions
The restricting of data about interfaces was both inconsistent in application and allowed protocol developers to get into states where they did not have the expected data about an interface that they thought that they would. These restrictions and inconsistencies keep causing bugs that have to be sorted through. The latest iteration of this bug was that commit: f20b478ef3d25e153939516a473bb2e80603cbd5 Has caused pim to not receive interface up notifications( but it knows the interface is back in the vrf and it knows the relevant ip addresses on the interface as they were changed as part of an ifdown/ifup cycle ). Remove this restriction and allow the interface events to be propagated to all clients. Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
Diffstat (limited to 'zebra/zserv.h')
-rw-r--r--zebra/zserv.h3
1 files changed, 0 insertions, 3 deletions
diff --git a/zebra/zserv.h b/zebra/zserv.h
index f7c4e3df7..ac016e65f 100644
--- a/zebra/zserv.h
+++ b/zebra/zserv.h
@@ -89,9 +89,6 @@ struct zserv {
/* Redistribute default route flag. */
vrf_bitmap_t redist_default[AFI_MAX];
- /* Interface information. */
- vrf_bitmap_t ifinfo;
-
/* Router-id information. */
vrf_bitmap_t ridinfo;