From 21213be523baa7f2cbf0feaa617f265c55e9b17a Mon Sep 17 00:00:00 2001 From: Ondrej Zajicek Date: Mon, 2 Oct 2023 15:09:30 +0200 Subject: Nest: Expand rte_src.private_id to u64 In general, private_id is sparse and protocols may want to map some internal values directly into it. For example, L3VPN needs to map VPN route discriminators to private_id. OTOH, u32 is enough for global_id, as these identifiers are dense. --- nest/rt-table.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'nest/rt-table.c') diff --git a/nest/rt-table.c b/nest/rt-table.c index 8b41ffee..5e677465 100644 --- a/nest/rt-table.c +++ b/nest/rt-table.c @@ -675,7 +675,7 @@ rte_mergable(rte *pri, rte *sec) static void rte_trace(struct channel *c, rte *e, int dir, char *msg) { - log(L_TRACE "%s.%s %c %s %N %uL %uG %s", + log(L_TRACE "%s.%s %c %s %N %luL %uG %s", c->proto->name, c->name ?: "?", dir, msg, e->net->n.addr, e->src->private_id, e->src->global_id, rta_dest_name(e->attrs->dest)); } -- cgit v1.2.3