| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
https://bugzilla.redhat.com/show_bug.cgi?id=690416
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| | |
New status: 164 messages complete with 1 fuzzy and 0 untranslated.
Transmitted-via: Transifex (www.transifex.net).
|
| |
| |
| |
| |
| |
| | |
New status: 165 messages complete with 0 fuzzies and 0 untranslated.
Transmitted-via: Transifex (www.transifex.net).
|
| |
| |
| |
| |
| |
| | |
New status: 40 messages complete with 68 fuzzies and 57 untranslated.
Transmitted-via: Transifex (www.transifex.net).
|
| | |
|
| |
| |
| |
| |
| | |
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617948
http://avahi.org/ticket/333
|
| | |
|
| | |
|
| |
| |
| |
| | |
config reload
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
New status: 164 messages complete with 1 fuzzy and 0 untranslated.
Transmitted-via: Transifex (www.transifex.net).
|
| |
| |
| |
| |
| |
| | |
New status: 165 messages complete with 0 fuzzies and 0 untranslated.
Transmitted-via: Transifex (www.transifex.net).
|
| |
| |
| |
| |
| |
| | |
New status: 40 messages complete with 68 fuzzies and 57 untranslated.
Transmitted-via: Transifex (www.transifex.net).
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Hi,
I sent a less knowledgeable question about avahi-daemon and
point-to-point links a few days ago,
http://lists.freedesktop.org/archives/avahi/2011-January/001969.html.
When I didn't get a response to this, I decided to build avahi from
source and step through it and see how it builds its list of interfaces
and their addresses.
This is in iface-linux.c, netlink_callback(). It looks for a RTM_NEWADDR
message, then extracts the payload of type IFA_ADDRESS.
Short story: I think it should be using the payload of type IFA_LOCAL,
not the payload of type IFA_ADDRESS.
In the VM where I was running these experiments, there are 3 interfaces
-- lo, eth0 and tun0. I printed out the IFA_ADDRESS and IFA_LOCAL for
all 3 of these; for lo and eth0 these are the same address; for tun0
(IFF_POINTOPOINT), IFA_ADDRESS is the remote end and IFA_LOCAL is the
local end.
I'm no expert on Linux rtnetlink or these IFA fields, but quoting
/usr/include/linux/if_addr.h:
/*
* Important comment:
* IFA_ADDRESS is prefix address, rather than local interface address.
* It makes no difference for normally configured broadcast
* interfaces,
* but for point-to-point IFA_ADDRESS is DESTINATION address,
* local address is supplied in IFA_LOCAL attribute.
*/
See also this stackoverflow question/answer:
http://stackoverflow.com/questions/4678637/what-is-difference-between-ifa-local-and-ifa-address-in-rtnetlink-linux
Does anyone know why avahi is looking for IFA_ADDRESS here, and whether
there's any reason not to use IFA_LOCAL instead?
Assuming there's not a specific reason to use IFA_ADDRESS here, I
propose the patch attached at the end of this message, which works for
me. (The bug this fixes is described in the earlier message linked above
-- avahi chooses the wrong address to associate with the P-t-P
interface, and if you enable avahi's reflector, avahi tries to call
sendmsg() using that as the source address and the kernel always,
correctly, fails the sendmsg() call with EINVAL.)
(And when/why this changed -- I was able to use avahi over P-t-P
interfaces on Linux several years ago; I don't know what avahi version I
was using at the time.)
thanks,
Matt
|
| |
| |
| |
| | |
Do not reflect cache entry with ipv6 link-local addresses on query.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
On 07.03.2011 19:04, Lennart Poettering wrote:
>
> Oh, I had assumed that .vimrc trick would allow project-wide vim
> modelines without having to edit each and every single file.
>
> Currently, every file does contain an emacs modeline at the top. It
> would be fair I guess to add a vim modeline to all those files too, even
> though it's not necessarily pretty.
Hi,
maybe it makes sense to go in the opposite direction: add .dir-locals.el
in the top directory. The settings are actually identical in all .[ch]
files.
|
| |
| |
| |
| |
| | |
ga_service_browser_new() and ga_service_browser_new_full() should
accept const gchar*.
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Else, we end up with an infinite loop with 100% CPU.
http://www.avahi.org/ticket/325
https://bugzilla.redhat.com/show_bug.cgi?id=667187
|
| |
| |
| |
| |
| | |
https://bugzilla.redhat.com/show_bug.cgi?id=673812
https://bugzilla.redhat.com/show_bug.cgi?id=673810
|
| |
| |
| |
| |
| | |
https://bugzilla.redhat.com/show_bug.cgi?id=673812
https://bugzilla.redhat.com/show_bug.cgi?id=673810
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The avahi-daemon uses a wrong flag combination to operate with
rtnetlink. This patch fixes the problems.
No need to set NLM_F_ACK since the dump operation already includes
the trailing NLMSG_DONE message that informs about the end of the
dump operation.
|
| |
| |
| |
| | |
core dump
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Here are two patches for avahi. The avahi website is extremly slow
today, so I didn't file them.
- avahi-fix-howl.pc.patch: fix a small issue introduced in
c8eacc0f13f6df529f2f40961e2ddb3a45dc9f93
- avahi-init-lsb.patch: update the suse initscripts, with a patch
we've had for a while
Cheers,
Vincent
--
Les gens heureux ne sont pas pressés.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Here are two patches for avahi. The avahi website is extremly slow
today, so I didn't file them.
- avahi-fix-howl.pc.patch: fix a small issue introduced in
c8eacc0f13f6df529f2f40961e2ddb3a45dc9f93
- avahi-init-lsb.patch: update the suse initscripts, with a patch
we've had for a while
Cheers,
Vincent
--
Les gens heureux ne sont pas pressés.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Ping() should work more reliably on systems where dbus activation of
avahi is not available.
http://avahi.org/ticket/319
|
|
|
|
| |
to deactivate it
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| | |
New status: 160 messages complete with 0 fuzzies and 5 untranslated.
Transmitted-via: Transifex (www.transifex.net).
|
| |
| |
| |
| |
| |
| | |
New status: 135 messages complete with 10 fuzzies and 20 untranslated.
Transmitted-via: Transifex (www.transifex.net).
|
| |
| |
| |
| |
| |
| | |
New status: 40 messages complete with 100 fuzzies and 25 untranslated.
Transmitted-via: Transifex (www.transifex.net).
|
| |
| |
| |
| |
| |
| | |
New status: 113 messages complete with 5 fuzzies and 47 untranslated.
Transmitted-via: Transifex (www.transifex.net).
|
| |
| |
| |
| |
| |
| | |
New status: 162 messages complete with 2 fuzzies and 1 untranslated.
Transmitted-via: Transifex (www.transifex.net).
|
| |
| |
| |
| |
| |
| | |
New status: 165 messages complete with 0 fuzzies and 0 untranslated.
Transmitted-via: Transifex (www.transifex.net).
|
| |
| |
| |
| |
| |
| | |
New status: 165 messages complete with 0 fuzzies and 0 untranslated.
Transmitted-via: Transifex (www.transifex.net).
|