Your message dated Sun, 28 Nov 2010 23:20:11 +0000 with message-id <1290986411.3292.360.camel@localhost> and subject line Re: Bug#605335: nfs-kernel-server: IP address wildcards don't work when avahi-daemon is running has caused the Debian Bug report #605335, regarding nfs-kernel-server: IP address wildcards don't work when avahi-daemon is running to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 605335: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605335 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: nfs-kernel-server: IP address wildcards don't work when avahi-daemon is running
- From: Aaron Barany <akb825@gmail.com>
- Date: Sun, 28 Nov 2010 15:07:29 -0800
- Message-id: <[🔎] 20101128230729.3798.99078.reportbug@localhost.localdomain>
Package: nfs-kernel-server Version: 1:1.2.2-4 Severity: important I just installed avahi-daemon on my server, and after I had restarted nfs- kernel-server I was no longer able to mount my nfs drives. (it would give me access denied errors) After trying some different things, I had found out that the problem was with using wildcards for IP addresses. (example: 192.168.*.*) I had one export with an exact IP address, which worked fine, but the wildcard addresses gave access denied errors. When I stopped avahi-daemon and restarted nfs-kernel-server I was able to connect again. I was able to work around this by adding another export with *.local as the wildcard, but that isn't as safe as using IP addresses. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
- To: 605335-done@bugs.debian.org
- Subject: Re: Bug#605335: nfs-kernel-server: IP address wildcards don't work when avahi-daemon is running
- From: Ben Hutchings <ben@decadent.org.uk>
- Date: Sun, 28 Nov 2010 23:20:11 +0000
- Message-id: <1290986411.3292.360.camel@localhost>
- In-reply-to: <[🔎] 20101128230729.3798.99078.reportbug@localhost.localdomain>
- References: <[🔎] 20101128230729.3798.99078.reportbug@localhost.localdomain>
On Sun, 2010-11-28 at 15:07 -0800, Aaron Barany wrote: > Package: nfs-kernel-server > Version: 1:1.2.2-4 > Severity: important > > I just installed avahi-daemon on my server, and after I had restarted nfs- > kernel-server I was no longer able to mount my nfs drives. (it would give me > access denied errors) After trying some different things, I had found out that > the problem was with using wildcards for IP addresses. (example: 192.168.*.*) I > had one export with an exact IP address, which worked fine, but the wildcard > addresses gave access denied errors. When I stopped avahi-daemon and restarted > nfs-kernel-server I was able to connect again. I was able to work around this > by adding another export with *.local as the wildcard, but that isn't as safe > as using IP addresses. This is not a bug. The manual page exports(5) says that "[w]ildcard characters generally do not work on IP addresses, though they may work by accident when reverse DNS lookups fail." avahi's multicast DNS service presumably causes reverse DNS lookups for the local network to succeed when they did not before. The correct syntax is address/netmask, e.g. 192.168.0.0/16. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.Attachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---