Re: [systemd-devel] plans/roadmap for mdns support in resolved
On Wed, 19.11.14 15:57, Vasiliy Tolstov (v.tols...@selfip.ru) wrote: Note that link-local ipv6 addresses for the name resolution stuff aren't fun to use in Linux right now, as the glibc NSS eats up the scopeid, when a client wants to resolve a hostname and specifies an address family. THis has the effect that resolving to link-local IPv6 addresses via ssh will just work (since ssh makes no restrictions on the address family when resolving the hostname), but via ping6 will actually fail (since ping6 specifies AF_INET6 as address family...). Hm I need very specific use-case. I have eth0, eth1, dummy0 with ipv6 addresses in different nets and i need to assign hostname to dummy0 address, that can be reacheable via eth0 or eth1 =). Does this possible? Both LLMNR and mDNS are strictly per-link, they will not announce IP addresses that are not on the very link that is used for traffic. That means if you have eth0 then the hostname will be announced with eth0's set of addersses on it. If you have eth1, then the hostname will be announced with only eth1's addresses. And similar for dummy0's addresses, or any other interface's. Also note that LLMNR/mDNS only works on interfaces that provide multicasting, i.e. only those which appear in ip link with the MULTICAST flag set. I am not sure I grok what you are trying to do, but do note that you can easily add an additional address to any interface you like, including the same address to multiple links. This means to make resolved announce a specific address via LLMNR/mDNS is just a matter of adding it to the interface via ip addr add. Lennart -- Lennart Poettering, Red Hat ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] plans/roadmap for mdns support in resolved
2014-11-20 15:22 GMT+03:00 Lennart Poettering lenn...@poettering.net: Both LLMNR and mDNS are strictly per-link, they will not announce IP addresses that are not on the very link that is used for traffic. That means if you have eth0 then the hostname will be announced with eth0's set of addersses on it. If you have eth1, then the hostname will be announced with only eth1's addresses. And similar for dummy0's addresses, or any other interface's. Also note that LLMNR/mDNS only works on interfaces that provide multicasting, i.e. only those which appear in ip link with the MULTICAST flag set. I am not sure I grok what you are trying to do, but do note that you can easily add an additional address to any interface you like, including the same address to multiple links. This means to make resolved announce a specific address via LLMNR/mDNS is just a matter of adding it to the interface via ip addr add. My use case is useful when i have ecmp routing for dummy0 address (yes it have multicast option). In this case on other nodes this address available via two routing entries with equal cost. Why not add ability to advertise hostname based on one interface addresses, but use for communication another devices (in my case eth0, eth1). -- Vasiliy Tolstov, e-mail: v.tols...@selfip.ru jabber: v...@selfip.ru ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] plans/roadmap for mdns support in resolved
On Fri, 21.11.14 02:24, Vasiliy Tolstov (v.tols...@selfip.ru) wrote: 2014-11-20 15:22 GMT+03:00 Lennart Poettering lenn...@poettering.net: Both LLMNR and mDNS are strictly per-link, they will not announce IP addresses that are not on the very link that is used for traffic. That means if you have eth0 then the hostname will be announced with eth0's set of addersses on it. If you have eth1, then the hostname will be announced with only eth1's addresses. And similar for dummy0's addresses, or any other interface's. Also note that LLMNR/mDNS only works on interfaces that provide multicasting, i.e. only those which appear in ip link with the MULTICAST flag set. I am not sure I grok what you are trying to do, but do note that you can easily add an additional address to any interface you like, including the same address to multiple links. This means to make resolved announce a specific address via LLMNR/mDNS is just a matter of adding it to the interface via ip addr add. My use case is useful when i have ecmp routing for dummy0 address (yes it have multicast option). In this case on other nodes this address available via two routing entries with equal cost. Why not add ability to advertise hostname based on one interface addresses, but use for communication another devices (in my case eth0, eth1). LLMNR/mDNS are really about zeroconf, i.e. something you don't really have to configure to work... Hence each time we add an option to configure it we kinda work against the whole concept... Can't you just add the address to all of your interfaces, and give them a low priority there, so that they aren't used as source address there? Lennart -- Lennart Poettering, Red Hat ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] plans/roadmap for mdns support in resolved
2014-11-19 1:32 GMT+03:00 Lennart Poettering lenn...@poettering.net: Yeah, that should just work already. LLMNR uses single-label names, hence resolving the unqualified hostname of local link-local peers should just work if resolved and nss-resolve are used. Thats fine. Note that link-local ipv6 addresses for the name resolution stuff aren't fun to use in Linux right now, as the glibc NSS eats up the scopeid, when a client wants to resolve a hostname and specifies an address family. THis has the effect that resolving to link-local IPv6 addresses via ssh will just work (since ssh makes no restrictions on the address family when resolving the hostname), but via ping6 will actually fail (since ping6 specifies AF_INET6 as address family...). Hm I need very specific use-case. I have eth0, eth1, dummy0 with ipv6 addresses in different nets and i need to assign hostname to dummy0 address, that can be reacheable via eth0 or eth1 =). Does this possible? -- Vasiliy Tolstov, e-mail: v.tols...@selfip.ru jabber: v...@selfip.ru ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] plans/roadmap for mdns support in resolved
On Tue, Nov 18, 2014 at 11:55 AM, Vasiliy Tolstov v.tols...@selfip.ru wrote: Hello. Does somebody have more concrete info about mdns support in resolved (also with ability to publish hostname via mdns). As i remember Lennart want to add this features... This is on the TODO (still). Anything in particular you wonder about? Cheers, Tom ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] plans/roadmap for mdns support in resolved
2014-11-18 14:40 GMT+03:00 Tom Gundersen t...@jklm.no: This is on the TODO (still). Anything in particular you wonder about? Cheers, Hm. Does LLMNR can replace my needs - i want to able to resolve hostnames via multicast (all my servers have only pure ipv6 (slaac) addresses and statically assigned hostnames). -- Vasiliy Tolstov, e-mail: v.tols...@selfip.ru jabber: v...@selfip.ru ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] plans/roadmap for mdns support in resolved
On Tue, 18.11.14 14:55, Vasiliy Tolstov (v.tols...@selfip.ru) wrote: Hello. Does somebody have more concrete info about mdns support in resolved (also with ability to publish hostname via mdns). As i remember Lennart want to add this features... It's one of the things I am working on right at the moment. Lennart -- Lennart Poettering, Red Hat ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] plans/roadmap for mdns support in resolved
On Tue, 18.11.14 15:45, Vasiliy Tolstov (v.tols...@selfip.ru) wrote: 2014-11-18 14:40 GMT+03:00 Tom Gundersen t...@jklm.no: This is on the TODO (still). Anything in particular you wonder about? Cheers, Hm. Does LLMNR can replace my needs - i want to able to resolve hostnames via multicast (all my servers have only pure ipv6 (slaac) addresses and statically assigned hostnames). Yeah, that should just work already. LLMNR uses single-label names, hence resolving the unqualified hostname of local link-local peers should just work if resolved and nss-resolve are used. Note that link-local ipv6 addresses for the name resolution stuff aren't fun to use in Linux right now, as the glibc NSS eats up the scopeid, when a client wants to resolve a hostname and specifies an address family. THis has the effect that resolving to link-local IPv6 addresses via ssh will just work (since ssh makes no restrictions on the address family when resolving the hostname), but via ping6 will actually fail (since ping6 specifies AF_INET6 as address family...). Also see for this issue: https://bugzilla.redhat.com/show_bug.cgi?id=1118723 Lennart -- Lennart Poettering, Red Hat ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
