MonoTorrent.Dht.MessageLoop.ReceiveMessage doesn't appear to react to fresh queries from others

[miniksa]

I've been playing around with MonoTorrent this week to figure out and explore various BitTorrent functionality for some of my existing C# tooling.

However, I'm experiencing a headache when it comes to the DhtEngine.

I can stand up one instance of the MonoTorrent DhtEngine listening on one port and an another on another port on the same machine.

I tell instance A that a peer is available on instance B by loading it in during engine.StartAsync. And I walk through under a debugger and observe Instance A will send the UDP FindNode message correctly. I can also breakpoint inside Instance B and watch it receive the FindNode message and head into MessageLoop.ReceiveMessage.

monotorrent/src/MonoTorrent.Dht/MonoTorrent.Dht/MessageLoop.cs

Line 262 in 9e98a44

void ReceiveMessage ()

However, inside that method, it looks like it does the following:

1. Update its routing table with the peer it heard from
2. Handle a response or error message
3. Return

It seems to have no provisions to handle any incoming message that's derived from QueryMessage.

Further, the only call to the Handle virtual method that all these messages implement seems to be locked behind the "Response" flow of this loop

monotorrent/src/MonoTorrent.Dht/MonoTorrent.Dht/MessageLoop.cs

Line 302 in 9e98a44

response.Handle (Engine, node);

Is this intentional? I would think that this loop should also be responding to fresh queries from others, not just responses to its own outbound messages.

Something like

 if (rawResponse is QueryMessage q) {
     q.Handle (Engine, node);
 }

stuck inside that loop as well +/- the other event and logging handlers that I have to admit I don't completely grok on first read.

Thanks for your time!