Daniel Butzu wrote: > Package: dnsmasq Version: 2.35-1 Severity: normal > > > > > During the installation of the dnsmasq debian package, init script > links are created named S15dnsmasq. However, if on the same system > nfs-kernel-server is installed, dnsmasq is started before > nfs-kernel-server (since S15dnsmasq comes before > S20nfs-kernel-server). This leads to the impossibility of starting > nfs-kernel-server, because dnsmasq will listen to 2049 udp and > nfs-kernel-server will refuse to start, stating "nfssvc: Address > already in use". When dnsmasq is started after nfs-kernel-server, > both work fine. I suggest that dnsmasq should create S22dnsmasq > symlinks, so that it will start after S20nfs-kernel-server and after > S21nfs-common. > > > >
What is the result of doing cat /proc/sys/net/ipv4/ip_local_port_range on your system? Unless you have told it otherwise, dnsmasq will only use port 2049 if it's allocated as an ephmeral port by the operating system. If your local port range includes 2049 then that's a configuration bug, I think. On my Sarge system, the range is 32768 to 61000. As a workaround, your change-the-startup-order has potential problems (what happens if NFS startup needs to do DNS resolution and that goes via dnsmasq?). A better workaround would be to use the dnsmasq --query-port option to nail down the port to something other than 2049. Cheers, Simon. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
