Mark certain routes as broken?

[jb55]

I don't yet know enough about routing internals so bear with me. This may be the next step in #635 ...

I noticed when I try to pay some invoices, some intermediate nodes reply with this message:

"failed: WIRE_UNKNOWN_NEXT_PEER (reply from remote)"

This leads to a more general problem of buggy/broken/rogue nodes that accidentally or purposefully disrupt routes. Perhaps we should mark these as temporarily broken and route around?

[ZmnSCPxj]

#638 . Sorry for the slow progress...

[cdecker]

@ZmnSCPxj no problem, you're doing an excellent job, I'd rather have slow steady progress than a quick fix that'll break soon again 😉

[cdecker]

I'll mark this as duplicate of #550

[jb55]

So much to keep on top of! I'll try to catch up on what's been going on over there. Thanks!

[cdecker]

I know, just noticed this myself :-)