#multicast #discovery #mdns #dns #avahi

multicast_dns

Simple Rust wrapper around Avahi Daemon

3 unstable releases

Uses old Rust 2015

0.5.0 Feb 25, 2020
0.4.2 Jan 24, 2019
0.4.1 Nov 28, 2018

#3 in #avahi

22 downloads per month

MPL-2.0 license

65KB
1.5K SLoC

Multicast DNS

Build Status

multicust_dns - is essentially a Rust wrapper around Avahi that internally uses AvahiDaemon to manage host name and browse services on the local network.

Requires avahi-common, avahi-client and dbus-1 libs to compile sucessfully.

For non-linux platforms that don't have required avahi libs, fake implementation is used.

See Multicast DNS Utils command line app as an example.

Examples (see ./examples folder):

extern crate multicast_dns;
use multicast_dns::host::HostManager;

fn main() {
    let host_name = format!("custom-host");

    let host_manager = HostManager::new();

    if !host_manager.is_valid_name(&host_name).unwrap() {
        panic!("Host name `{}` is not a valid host name!", &host_name);
    }

    // The `new_host_name` can be different from the one we are trying to set,
    // due to possible collisions that may happen.
    let new_host_name = host_manager.set_name(&host_name).unwrap();

    println!("New host name is: {:?}", &new_host_name);
}

or

extern crate multicast_dns;
use multicast_dns::discovery::*;

fn main() {
    let service_type = format!("_device-info._tcp");
    
    let discovery_manager = DiscoveryManager::new();

    let on_service_resolved = |service: ServiceInfo| {
        println!("Service resolved: {:?}", service);
    };

    let on_service_discovered = |service: ServiceInfo| {
        println!("Service discovered: {:?}", service);

        let resolve_listeners = ResolveListeners {
            on_service_resolved: Some(&on_service_resolved),
        };

        discovery_manager.resolve_service(service, resolve_listeners);
    };

    let on_all_discovered = || {
        println!("All services has been discovered");
    };

    let discovery_listeners = DiscoveryListeners {
        on_service_discovered: Some(&on_service_discovered),
        on_all_discovered: Some(&on_all_discovered),
    };

    discovery_manager.discover_services(&service_type, discovery_listeners);
}

Look at RFC 6762 and RFC 6763 for the standard specifications.

Also one can take a look at Service Name and Transport Protocol Port Number Registry to see currently available and registered services.

Dependencies

~125KB