Skip to content

core(routing): seqno request log spam #96

Description

@encodeous

If we remove the addr 10.1.0.2 on ct2 via a config reload, the other nodes will keep trying to request the seqno

ct4  | DBG ct4 requested seqno module=router event=seqno_requested src.router=ct2 src.prefix=10.1.0.2/32 seqno=1
ct1  | DBG ct1 requested seqno module=router event=seqno_requested src.router=ct2 src.prefix=10.1.0.2/32 seqno=1
ct3  | DBG ct3 requested seqno module=router event=seqno_requested src.router=ct2 src.prefix=10.1.0.2/32 seqno=1
ct4  | DBG ct4 requested seqno module=router event=seqno_requested src.router=ct2 src.prefix=10.1.0.2/32 seqno=1
ct1  | DBG ct1 requested seqno module=router event=seqno_requested src.router=ct2 src.prefix=10.1.0.2/32 seqno=1
ct3  | DBG ct3 requested seqno module=router event=seqno_requested src.router=ct2 src.prefix=10.1.0.2/32 seqno=1
...

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions