This prevents Avahi working with IPv6 where it is even more useful
than in IPv4 thanks to IPv6 link-local addresses. Of course it can be administratively changed but I see no reason to IPv6 disabled by default in 2012.
Note: Avahi's IPv6 support would be even more useful if bug 719178 is also fixed. Then you could use local network services separately from network configuration.
It looks like this bug is the same as bug 195674 fixed six years ago and then reintroduced.
Avahi by Default on the Desktop Feature page for F18: http://fedoraproject.org/wiki/Features/AvahiDefaultOnDesktop
use-ipv6= Takes a boolean value ("yes" or "no"). If set to "no" avahi-
daemon will not use IPv6 sockets. Default is "yes".
I can't find any reason for having Avahi disabled on IPv6.
It looks like this should be fixed upstream, not by patching around it in distros: http://avahi.org/ticket/367
Thanks, Stef. It would be nice to make sure this gets in before Fedora 18 Alpha is out, maybe even through patching in Fedora.
So, the problem with this is that we cannot really deduplicate services we find on different networks/protocols. That means a service that is announced via IPv4 and IPv6 will appear twice in a client that browses on both Ipv4 and IPv6.
This has already been a problem when i started working on this and the mDNS/DNS-SD designers have been aware of it. But tbh I haven't checked the current drafts recently to see whether there is now a sane way to deduplicate these things...
Until there is a sane strategy on deduplicating these services I don't think we should enable Ipv6 by default.
Understood. But then it's pretty useless to promote Avahi for modern networking. Funny enough is that Fedora computers always have IPv6 addresses (but nss-mdns doesn't work for IPv6LL) but often don't have IPv4 addresses (e.g. when connected to networks without DHCP configuration or to IPv6 only networks with IPv4 services presented through NAT64.
This will soon make Fedora feel prehistoric, so please tell me if I can be of any help.
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '17'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged change the
'version' to a later Fedora version prior to Fedora 17's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Just hit this problem in Fedora 20.
As well as /etc/avahi.conf, IPv6 resolution is turned off in /etc/nsswitch.conf.
(In reply to Lennart Poettering from comment #6)
> So, the problem with this is that we cannot really deduplicate services we
> find on different networks/protocols. That means a service that is announced
> via IPv4 and IPv6 will appear twice in a client that browses on both Ipv4
> and IPv6.
> This has already been a problem when i started working on this and the
> mDNS/DNS-SD designers have been aware of it. But tbh I haven't checked the
> current drafts recently to see whether there is now a sane way to
> deduplicate these things...
> Until there is a sane strategy on deduplicating these services I don't think
> we should enable Ipv6 by default.
Despite the fact that this duplication problem is not solved, I'd also tend to slowly start and enable this feature.
With native IPv6 ISp connectiosn IPv& is - toller weise - popping up more often in user's homes. Thus I'd like to have the same mdns features over IPv6 as I have on IPv4.
(In reply to Fabian Deutsch from comment #10)
> With native IPv6 ISp connectiosn IPv& is - toller weise - popping up more
> often in user's homes. Thus I'd like to have the same mdns features over
> IPv6 as I have on IPv4.
Also link-local addresses work without ISP's IPv6 and I'm talking with glibc devs about enabling proper link-local address resolution via glibc getaddrinfo and nsswitch interface.
In trying to get everything working, I discovered that OpenSSH will fall back to IPv4 even if you have it configured to prefer IPv6 in .ssh/config, and even if you use the -6 flag on the command line. So I don't think the OpenSSH/glibc issue should be a showstopper for enabling IPv6 by default.
(In reply to mathew from comment #12)
> even if you use the -6 flag on the command line
Did you file a bug report with that? I have never seen such a behavior but I'm regularly only using -4.
> So I don't think the
> OpenSSH/glibc issue should be a showstopper for enabling IPv6 by default.
I wasn't aware that anyone would claim any OpenSSH or glibc issue was a showstopper.
Still an issue in a clean install of Fedora 21.
As well as Fedora 22.
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle.
Changing version to '23'.
(As we did not run this process for some time, it could affect also pre-Fedora 23 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.)
More information and reason for this action is here:
marking futurefeature, so this doesn't get autoclosed
The configuration issue is now fixed upstream in Avahi version 0.6.32. I just asked on IRC for a release with this change and voilá, a release we got.
Have the concerns from comment #6 been addressed? As far as I can tell, they have not.
Fwiw, updated rawhide
* Sat Oct 10 2015 Rex Dieter <firstname.lastname@example.org> - 0.6.32-0.1.rc
- -devel: move dbus-1/interfaces here
- Avahi's IPv6 support is disabled by default (#821127)
- avahi: script and/or trigger should not directly enable systemd units (#1094899)
which is a fair venue to at least try the new upstream default.
If anyone(*) feels this should be considered to be merged/backported to f23, feel free to say so and re-open.
(*) bonus if from other avahi maintainers or fedora SIG members (workstation, kde, etc...)
(In reply to Rex Dieter from comment #19)
> Have the concerns from comment #6 been addressed? As far as I can tell,
> they have not.
Well, the comment was made back in 2012. I would hope that client programs are now a bit smarter about performing deduplication and preferring IPv6 when browsing. Even if they aren't, it seems to me that it's just a cosmetic issue if two working services show up instead of one.