Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: avahi (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
** Changed in: avahi
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1102906
Title:
Cannot broadcast both on global and link address on same
When I say bind, I actually meant to bind the outgoing connection from
Pidgin (not related to Avahi). So when creating the socket, specify the
source IP address.
The problem is that when you connect (without specifying a source) then
at least for IPv6 due to the routing table specification of the
Would it be possible to add a flag to AvahiPublishFlags to allow the
application to request the required behaviour on a per-service basis? I
can't see any options for Pidgin that don't require pretty radical
restructuring of its codebase (more discussion at
Part of the reason this behavior exists in Avahi is that many
applications do not correctly retrieve the scope ID (interface index)
when doing hostname resolution, and if not supplied then connection to
such a link local address will fail. Applications are likely to receive
such an address at
** Bug watch added: github.com/lathiat/avahi/issues #243
https://github.com/lathiat/avahi/issues/243
** Also affects: avahi via
https://github.com/lathiat/avahi/issues/243
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of
I found a mailing list post which mentioned this, but no replies:
https://lists.freedesktop.org/archives/avahi/2010-March/001863.html
It actually causes problems for Pidgin in certain circumstances, see bug
#1841621.
--
You received this bug notification because you are a member of Ubuntu
7 matches
Mail list logo