Re: [systemd-devel] mdns support to networkd
2014-06-23 23:27 GMT+04:00 Simon McVittie simon.mcvit...@collabora.co.uk: It sounds as though you have a misconfigured nss_mdns: you should reconfigure nsswitch.conf to have mdns4_minimal [NOTFOUND=return], or maybe mdns_minimal [NOTFOUND=return], but not mdns4 or mdns. New installations of Debian's libnss-mdns do this: hosts: files mdns4_minimal [NOTFOUND=return] dns _minimal have bugs and very ugly code. For example it send multicast only via first interface that up. But i have first interface private with virtualbox and need multicast on second.. (perhaps with some extra resolvers like Lennart's myhostname, but what I quoted is the minimum) and that gets rid of the 5 second delay, at the cost of not using mDNS for PTR lookups of addresses outside the link-local 169.254.0.0/16 and fe80::/16 blocks. I've wondered whether to implement an extended syntax for /etc/mdns.allow so you can do something like # /etc/mdns.allow .lan. .lan .local. .local ptr 169.254.0.0/16 ptr 192.168.0.0/24 ptr fe80::/16 but haven't got round to it so far. -- 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] mdns support to networkd
2014-06-23 23:12 GMT+04:00 Reindl Harald h.rei...@thelounge.net: why don't you just setup PTR records? not having so brings a lot of implications, not only avahi as example sane configured ssh-daemons won't allow to login Because mdns order before dns. If i ping google.com ipv6 address it tries to resolve via avahi ptr records and fail. Why i can't use _minimal - see previous post (its have very very bad code) -- 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] mdns support to networkd
On 24/06/14 07:15, Vasiliy Tolstov wrote: _minimal have bugs and very ugly code. For example it send multicast only via first interface that up. Are you confusing libnss_mdns*_minimal.so (which refuse to resolve names outside .local and addresses outside the link-local range) with ./configure --enable-legacy (which uses a built-in mini-mDNS stack instead of relying on Avahi)? Whether to compile as mdns*_minimal is determined by ENABLE_MINIMAL, whereas the choice of Avahi, legacy or Avahi if available, else legacy is determined by ENABLE_AVAHI and ENABLE_LEGACY. The minimal configuration is good, the legacy configuration is (in general) not. The Debian packages that I maintain are compiled without legacy support, include all (minimal, non-minimal)x(IPv4, IPv6, both) builds, but only enable the IPv4 minimal build by default in new installations: I believe that matches upstream recommendations. S ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] mdns support to networkd
On Mon, 23.06.14 23:09, Vasiliy Tolstov (v.tols...@selfip.ru) wrote: 2014-06-23 16:13 GMT+04:00 Lennart Poettering lenn...@poettering.net: Both. mDNS is a very much a peer-to-peer system, hence all participants tend to implement both sides. I actually intend to make this useful enough so that we can use it for containers and the host to discover earch other and their services. Does exists any roadmap for this? Because now with avahi i can't publish additional addresses and need to patch sources to minimize timeout from 5000msec to 1000msec. (my hosts does not have ptr records and for each ping i have 5 sec timeout =() Not sure I can make sense of what you write above. Regarding the roadmap: we generally try to avoid giving roadmaps regarding when we will have done what. However, I think getting resolved be truly useful is the next bigger thing i will look into. 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] mdns support to networkd
On Fri, 20.06.14 21:28, Christian Hesse (l...@eworm.de) wrote: Lennart Poettering lenn...@poettering.net on Fri, 2014/06/20 20:19: On Sat, 14.06.14 01:13, Vasiliy Tolstov (v.tols...@selfip.ru) wrote: As i see avahi development stopped. Well, yeah, I am doign a shitty job at maintaining it. Does mdns support goes to networkd or no? Well, no. But into systemd-resolved. Our plan is to turn systemd-resolved into an nscd compatible daemon that speaks dns/dnssec, mdns, llmnr, in the long run replacing avahi. Does this cover server functionality only or will there be client bits as well? Both. mDNS is a very much a peer-to-peer system, hence all participants tend to implement both sides. I actually intend to make this useful enough so that we can use it for containers and the host to discover earch other and their services. 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] mdns support to networkd
2014-06-23 16:13 GMT+04:00 Lennart Poettering lenn...@poettering.net: Both. mDNS is a very much a peer-to-peer system, hence all participants tend to implement both sides. I actually intend to make this useful enough so that we can use it for containers and the host to discover earch other and their services. Does exists any roadmap for this? Because now with avahi i can't publish additional addresses and need to patch sources to minimize timeout from 5000msec to 1000msec. (my hosts does not have ptr records and for each ping i have 5 sec timeout =() -- 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] mdns support to networkd
On 23/06/14 20:09, Vasiliy Tolstov wrote: Because now with avahi i can't publish additional addresses and need to patch sources to minimize timeout from 5000msec to 1000msec. (my hosts does not have ptr records and for each ping i have 5 sec timeout =() It sounds as though you have a misconfigured nss_mdns: you should reconfigure nsswitch.conf to have mdns4_minimal [NOTFOUND=return], or maybe mdns_minimal [NOTFOUND=return], but not mdns4 or mdns. New installations of Debian's libnss-mdns do this: hosts: files mdns4_minimal [NOTFOUND=return] dns (perhaps with some extra resolvers like Lennart's myhostname, but what I quoted is the minimum) and that gets rid of the 5 second delay, at the cost of not using mDNS for PTR lookups of addresses outside the link-local 169.254.0.0/16 and fe80::/16 blocks. I've wondered whether to implement an extended syntax for /etc/mdns.allow so you can do something like # /etc/mdns.allow .lan. .lan .local. .local ptr 169.254.0.0/16 ptr 192.168.0.0/24 ptr fe80::/16 but haven't got round to it so far. S ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] mdns support to networkd
Am 23.06.2014 21:09, schrieb Vasiliy Tolstov: 2014-06-23 16:13 GMT+04:00 Lennart Poettering lenn...@poettering.net: Both. mDNS is a very much a peer-to-peer system, hence all participants tend to implement both sides. I actually intend to make this useful enough so that we can use it for containers and the host to discover earch other and their services. Does exists any roadmap for this? Because now with avahi i can't publish additional addresses and need to patch sources to minimize timeout from 5000msec to 1000msec. (my hosts does not have ptr records and for each ping i have 5 sec timeout =() why don't you just setup PTR records? not having so brings a lot of implications, not only avahi as example sane configured ssh-daemons won't allow to login signature.asc Description: OpenPGP digital signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] mdns support to networkd
On Sat, 14.06.14 01:13, Vasiliy Tolstov (v.tols...@selfip.ru) wrote: As i see avahi development stopped. Well, yeah, I am doign a shitty job at maintaining it. Does mdns support goes to networkd or no? Well, no. But into systemd-resolved. Our plan is to turn systemd-resolved into an nscd compatible daemon that speaks dns/dnssec, mdns, llmnr, in the long run replacing avahi. 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] mdns support to networkd
On Fri, Jun 20, 2014 at 08:19:17PM +0200, Lennart Poettering wrote: On Sat, 14.06.14 01:13, Vasiliy Tolstov (v.tols...@selfip.ru) wrote: As i see avahi development stopped. Well, yeah, I am doign a shitty job at maintaining it. Does mdns support goes to networkd or no? Well, no. But into systemd-resolved. Our plan is to turn systemd-resolved into an nscd compatible daemon that speaks dns/dnssec, mdns, llmnr, in the long run replacing avahi. Is there a intersection with SSSD? It is quite heavily promoted by one company with color headgear in name, and slighlty conflicts with nscd (and compatibile) solutions: https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/usingnscd-sssd.html -- Tomasz Torcz Never underestimate the bandwidth of a station xmpp: zdzich...@chrome.plwagon filled with backup tapes. -- Jim Gray ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] mdns support to networkd
On Fri, 20.06.14 20:35, Tomasz Torcz (to...@pipebreaker.pl) wrote: On Fri, Jun 20, 2014 at 08:19:17PM +0200, Lennart Poettering wrote: On Sat, 14.06.14 01:13, Vasiliy Tolstov (v.tols...@selfip.ru) wrote: As i see avahi development stopped. Well, yeah, I am doign a shitty job at maintaining it. Does mdns support goes to networkd or no? Well, no. But into systemd-resolved. Our plan is to turn systemd-resolved into an nscd compatible daemon that speaks dns/dnssec, mdns, llmnr, in the long run replacing avahi. Is there a intersection with SSSD? It is quite heavily promoted by one company with color headgear in name, and slighlty conflicts with nscd (and compatibile) solutions: https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/usingnscd-sssd.html Well, we have no intention to do anything fancy with users/groups at this time. We do this only for hostnames and stuff, which should be fine and compatible with sssd. 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] mdns support to networkd
Lennart Poettering lenn...@poettering.net on Fri, 2014/06/20 20:19:
On Sat, 14.06.14 01:13, Vasiliy Tolstov (v.tols...@selfip.ru) wrote:
As i see avahi development stopped.
Well, yeah, I am doign a shitty job at maintaining it.
Does mdns support goes to networkd or no?
Well, no. But into systemd-resolved. Our plan is to turn
systemd-resolved into an nscd compatible daemon that speaks dns/dnssec,
mdns, llmnr, in the long run replacing avahi.
Does this cover server functionality only or will there be client bits as
well?
--
main(a){char*c=/*Schoene Gruesse */B?IJj;MEH
CX:;,b;for(a/*Chris get my mail address:*/=0;b=c[a++];)
putchar(b-1/(/* gcc -o sig sig.c ./sig*/b/42*2-3)*42);}
signature.asc
Description: PGP signature
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
