Date: Wed, 1 Feb 2017 08:33:14 -0600 From: Eric van Gyzen <vangyzen@FreeBSD.org> To: Peter Blok <pblok@bsd4all.org>, freebsd-net@freebsd.org Subject: Re: 11-stable mountd listens on port 993 Message-ID: <aeda2524-f36d-8680-ca4d-082d4c0e36a4@FreeBSD.org> In-Reply-To: <33C2BACA-E500-4C57-9827-797F5206C572@bsd4all.org> References: <33C2BACA-E500-4C57-9827-797F5206C572@bsd4all.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02/01/2017 06:28, Peter Blok wrote: > I just updated to 11-stable@313042 and when I rebootted my system dovecot > didn’t want to start because port 993 was already in use. > > Checked with lsof and it was mountd that was listening on this port. When I > stopped mountd and started dovecot everything was fine. When I started mountd > after this it worked ok. > > Next reboot everything was fine. > > Anybody know why mountd could have been listening to port 993? Since mountd uses bindresvport_sa(3), the kernel chooses a port in the "low" range, configured via sysctl: net.inet.ip.portrange.lowlast: 600 net.inet.ip.portrange.lowfirst: 1023 There is some randomness in the algorithm, so there is roughly a 1/424 chance of conflict. You might use the -p flag to mountd or reduce lowfirst below 993. Cheers, Eric
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aeda2524-f36d-8680-ca4d-082d4c0e36a4>