Now this is strange. On my Etch system (netinstall) : # cat /proc/sys/net/ipv4/ip_local_port_range 2048 4999
So it does include 2049 (+ it causes problems with other services aswell). Adding "net.ipv4.ip_local_port_range = 32768 61000" to /etc/sysctl.conf fixes this problem. Of course, this has nothing to do with dnsmasq. Thank you and sorry for the trouble. Best wishes, Daniel On Wed, 12 Dec 2007 14:17:46 +0000 Simon Kelley <[EMAIL PROTECTED]> wrote: > > 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]
