[arch-general] avahi problem
Jochen Maes (Gcool)
gcool.be at gmail.com
Thu Apr 5 08:05:15 EDT 2012
Are you running a firewall on the Arch box (or elsewhere in the
network) through which the avahi traffic has to pass? As I understand
it (various similar issues found through Google), you need to
explicitly allow mulitcast DNS traffic (udp 5353) for this feature to
work.
2012/4/5, Alper Kanat <tunix at raptiye.org>:
> I did. However I found out that there's not much difference in the case of
> host resolution. When hosts line is like the following:
>
> $ cat /etc/nsswitch.conf | grep hosts
> hosts: files dns
>
> I can ping office.local from other machines on the network. If I change
> that line like this:
>
> hosts: files mdns4_minimal dns mdns4
>
> then I realized that host resolution is a little bit more slower.
> Connecting via SSH takes 3-4 seconds longer. Even if I change the line like
> this, office.local becomes inaccessible after a few minutes. I tried
> enabling avahi-dnsconfd which also made no difference.
>
> ---
> Quis custodiet ipsos custodes?
>
>
> On Thu, Apr 5, 2012 at 14:32, Jochen Maes (Gcool) <gcool.be at gmail.com>wrote:
>
>> Have you configured your /etc/nsswitch.conf (server side) as suggested
>> on https://wiki.archlinux.org/index.php/Avahi#Hostname_resolution ?
>>
>> 2012/4/5, Alper Kanat <tunix at raptiye.org>:
>> > Hey There,
>> >
>> > I've installed an Arch Linux server in our office for serving files over
>> > the network via Bonjour/avahi. All computers are connected to an ADSL
>> modem
>> > via wireless. Only the server is connected via LAN. When I start the
>> > server, I can ping it:
>> >
>> > --- CMD OUTPUT
>> >
>> -------------------------------------------------------------------------------
>> >
>> > $ ping office.local
>> > PING office.local (192.168.1.107): 56 data bytes
>> > 64 bytes from 192.168.1.107: icmp_seq=0 ttl=64 time=1.080 ms
>> > 64 bytes from 192.168.1.107: icmp_seq=1 ttl=64 time=1.671 ms
>> > 64 bytes from 192.168.1.107: icmp_seq=2 ttl=64 time=0.979 ms
>> > ^C
>> > --- office.local ping statistics ---
>> > 3 packets transmitted, 3 packets received, 0.0% packet loss
>> > round-trip min/avg/max/stddev = 0.979/1.243/1.671/0.305 ms
>> >
>> > $ ping 192.168.1.107
>> > PING 192.168.1.107 (192.168.1.107): 56 data bytes
>> > 64 bytes from 192.168.1.107: icmp_seq=0 ttl=64 time=1.194 ms
>> > 64 bytes from 192.168.1.107: icmp_seq=1 ttl=64 time=1.229 ms
>> > ^C
>> > --- 192.168.1.107 ping statistics ---
>> > 2 packets transmitted, 2 packets received, 0.0% packet loss
>> > round-trip min/avg/max/stddev = 1.194/1.212/1.229/0.017 ms
>> >
>> > After a few minutes however I can't ping it using the .local address:
>> >
>> > *$ ping office.local*
>> > *ping: cannot resolve office.local: Unknown host*
>> >
>> > $ ping 192.168.1.107
>> > PING 192.168.1.107 (192.168.1.107): 56 data bytes
>> > 64 bytes from 192.168.1.107: icmp_seq=0 ttl=64 time=1.375 ms
>> > 64 bytes from 192.168.1.107: icmp_seq=1 ttl=64 time=1.562 ms
>> > ^C
>> > --- 192.168.1.107 ping statistics ---
>> > 2 packets transmitted, 2 packets received, 0.0% packet loss
>> > round-trip min/avg/max/stddev = 1.375/1.469/1.562/0.094 ms
>> >
>> > --- CMD OUTPUT
>> >
>> -------------------------------------------------------------------------------
>> >
>> > If I restart avahi-daemon, we can ping office.local for another few
>> > minutes. Any ideas?
>> >
>> > ---
>> > Quis custodiet ipsos custodes?
>> >
>>
>
More information about the arch-general
mailing list