Skip to content

Lost TXT packets when server is started after client #59

@flotter

Description

@flotter

Hi,

I do not have much experience with DNS-SD, but I have observed a difference in behaviour I cannot explain. Perhaps someone could help me understand this?

  1. Working Example:

I start the responder first (which includes TXT key-value fields). After the responder was started (given ample time), I run the client browser with a context with timeout (e.g. 5 seconds).

In this case the browser service reponse includes the TXT fields.

  1. Non-working Example:

I start the client first with context timeout 5 seconds. Just one second after the client is started, I start the responder.

In this case the browser is showing the service, but it does not include the TXT key / value data. However, the TXT packets are indeed sent (as I can confirm via wireshark).

Replacing the client/browser with avahi-browse -a -r, shows the results I expect, with the TXT fields populated.

Is this a known issue, or expected behaviour?

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions