diff options
| author | Maria Matejka <mq@ucw.cz> | 2022-06-20 19:10:49 +0200 |
|---|---|---|
| committer | Maria Matejka <mq@ucw.cz> | 2022-07-11 16:07:09 +0200 |
| commit | 6b0368cc2c317d1acc0881a96b32ded291d82741 (patch) | |
| tree | 8e8eeb29b6bb2eb7edc6f701a71e2b0569799eb9 /nest/protocol.h | |
| parent | d5e3272f3d9b1bad7ceb6d0d5897a7269e28a537 (diff) | |
Export tables merged with BGP prefix hash
Until now, if export table was enabled, Nest was storing exactly the
route before rt_notify() was called on it. This was quite sloppy and
spooky and it also wasn't reflecting the changes BGP does before
sending. And as BGP is storing the routes to be sent anyway, we are
simply keeping the already-sent routes in there to better rule out
unneeded reexports.
Some of the route attributes (IGP metric, preference) make no sense in
BGP, therefore these will be probably replaced by something sensible.
Also the nexthop shown in the short output is the BGP nexthop.
Diffstat (limited to 'nest/protocol.h')
| -rw-r--r-- | nest/protocol.h | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/nest/protocol.h b/nest/protocol.h index a1701a7e..3ccd364a 100644 --- a/nest/protocol.h +++ b/nest/protocol.h @@ -537,7 +537,7 @@ struct channel { u8 refeed_pending; /* Refeeding and another refeed is scheduled */ u8 rpki_reload; /* RPKI changes trigger channel reload */ - struct rtable *out_table; /* Internal table for exported routes */ + struct rt_exporter *out_table; /* Internal table for exported routes */ list roa_subscriptions; /* List of active ROA table subscriptions based on filters roa_check() */ }; @@ -610,7 +610,6 @@ int proto_configure_channel(struct proto *p, struct channel **c, struct channel_ void channel_set_state(struct channel *c, uint state); void channel_setup_in_table(struct channel *c); -void channel_setup_out_table(struct channel *c); void channel_schedule_reload(struct channel *c); static inline void channel_init(struct channel *c) { channel_set_state(c, CS_START); } |