It's impossible to chat with any F17 telepathy-salut user because the default firewall is blocking incoming TCP connection.
Fedora should patch Salut to request the firewall to open the port is listening to.
This is turning into a big issue at Guadec, making Salut unusable.
I'll give this a look when I get back from vacation next week.
Is this still a problem with F18?
Not a problem anymore as far as I can see from some basic smoke testing. Fedora 18 comes with firewalld, and the "firewall-config" UI indicates that it allows mdns to pass through with its default "public" zone...
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here:
(In reply to Jean-François Fortin Tam from comment #4)
> Not a problem anymore as far as I can see from some basic smoke testing.
> Fedora 18 comes with firewalld, and the "firewall-config" UI indicates that
> it allows mdns to pass through with its default "public" zone...
I wasn't able to initiate chats without also opening port 5298/tcp (named "presence" in /etc/services) on the receiving end.
*** Bug 995014 has been marked as a duplicate of this bug. ***
Created attachment 799475 [details]
FirewallD service description
I did a bit more digging, and port 5298 is indeed the default, but if this and 5299 are already in use, a random port is selected instead (http://cgit.freedesktop.org/wocky/tree/wocky/wocky-meta-porter.c?id=779eac498ae44c0e4cb581ae73edfe2d84081673#n1129). So, opening port 5298 would work most of the time for most people, but not all.
Anyway, attached is a file which if installed in /usr/lib/firewalld/services/, will add an option to firewall-config to open these ports. I guess this is better than nothing.
I confirm the solution provided above works. Could it be pushed to default configuration (to add this file under firewall services and enable it) so it works our of the box in Fedora 20? I just upgraded to F20 and there is still the need to update firewall manually with above provided solution.
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
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.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 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 this bug is closed as described in the policy above.
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.
I believe that these ports are open by default on Fedora 21 Workstation.