Feature #4357
closedmDNS: don't receive requests sent by self
0%
Description
It's not a huge problem, but it would be an optimisation / less noise if an mDNS server would be able to skip requests sent by its own mDNS client:
20200110160308476 DMSLOOKUP DEBUG sending mDNS query: gsup.hlr.901700000014705.imsi (mslookup_client_mdns.c:121) 20200110160308477 DMSLOOKUP DEBUG mDNS rx request: gsup.hlr.901700000014705.imsi (mslookup_server_mdns.c:85) 20200110160308477 DMSLOOKUP DEBUG gsup.hlr.901700000014705.imsi: does not exist in local HLR (mslookup_server.c:210)
Not sure how to achieve that -- we can't filter by sender address, right?
Related issues
Updated by keith over 4 years ago
Hi!
right, if you filter by sender address, then you filter out this case, correct?
if the client is a subprocess of say, FreeSwitch PBX looking for voice call routing info, it wants it's "own" mDNS server to respond. I guess for hlr requests, you could filter requests coming from "my" ip address.
Do you want to add a HLR ID or somesuch, then include it in the request, and filter on that? - don't answer requests for hlr IMSI lookups from my own ID
Sounds like effort for not so much gain?
Updated by osmith over 4 years ago
Whenever a request is arriving at the server, we could check if the client is waiting for an answer with the same packet-id (and domain, if we want to be 100% sure). If that is the case, then ignore the request.
Sounds like effort for not so much gain?
Agreed.
Updated by neels almost 4 years ago
- Is duplicate of Feature #4253: in mDNS socket rx, implicitly drop own messages sent out instead of receiving and parsing added
