diff options
| author | Donald Sharp <sharpd@cumulusnetworks.com> | 2019-02-04 17:45:31 +0100 |
|---|---|---|
| committer | Donald Sharp <sharpd@cumulusnetworks.com> | 2019-02-05 15:13:30 +0100 |
| commit | a8a20c4e3c602fb132090178799813a2dfcf3c4a (patch) | |
| tree | ba487681dc6d1fbe7e405d30b9bddc117766081f /zebra/zebra_ptm_redistribute.c | |
| parent | Merge pull request #3698 from donaldsharp/netlink_is_serious_business (diff) | |
| download | frr-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/zebra_ptm_redistribute.c')
| -rw-r--r-- | zebra/zebra_ptm_redistribute.c | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/zebra/zebra_ptm_redistribute.c b/zebra/zebra_ptm_redistribute.c index 0c24c732a..01d5114b9 100644 --- a/zebra/zebra_ptm_redistribute.c +++ b/zebra/zebra_ptm_redistribute.c @@ -36,10 +36,6 @@ static int zsend_interface_bfd_update(int cmd, struct zserv *client, int blen; struct stream *s; - /* Check this client need interface information. */ - if (!vrf_bitmap_check(client->ifinfo, ifp->vrf_id)) - return 0; - s = stream_new(ZEBRA_MAX_PACKET_SIZ); zclient_create_header(s, cmd, vrf_id); |