isisd, ospfd: fix opaque zapi source parsing

Opaque zapi messages carry the sender's zclient tuple now,
daemons shouldn't try to parse those bits directly.

Signed-off-by: Mark Stapp <mjs@labn.net>
This commit is contained in:
Mark Stapp 2023-06-27 16:32:54 -04:00
parent 579d00e167
commit 220dc6df98
2 changed files with 6 additions and 6 deletions

View File

@ -772,9 +772,9 @@ static int isis_opaque_msg_handler(ZAPI_CALLBACK_ARGS)
switch (info.type) {
case LINK_STATE_SYNC:
STREAM_GETC(s, dst.proto);
STREAM_GETW(s, dst.instance);
STREAM_GETL(s, dst.session_id);
dst.proto = info.src_proto;
dst.instance = info.src_instance;
dst.session_id = info.src_session_id;
dst.type = LINK_STATE_SYNC;
ret = isis_te_sync_ted(dst);
break;

View File

@ -2161,9 +2161,9 @@ static int ospf_opaque_msg_handler(ZAPI_CALLBACK_ARGS)
switch (info.type) {
case LINK_STATE_SYNC:
STREAM_GETC(s, dst.proto);
STREAM_GETW(s, dst.instance);
STREAM_GETL(s, dst.session_id);
dst.proto = info.src_proto;
dst.instance = info.src_instance;
dst.session_id = info.src_session_id;
dst.type = LINK_STATE_SYNC;
ret = ospf_te_sync_ted(dst);
break;