+++ This bug was initially created as a clone of Bug #762989 +++
If the number of servers increase then there is a chance of GlusterFS port clashing with reserved ports.
For example if the servers increase more than 28 a pop3 over ssl daemon,
which uses 995 port, cannot start after GlusterFS client.
--- Additional comment from amarts on 2011-04-25 05:33:21 EDT ---
Please update the status of this bug as its been more than 6months since its filed (bug id < 2000)
Please resolve it with proper resolution if its not valid anymore. If its still valid and not critical, move it to 'enhancement' severity.
--- Additional comment from amarts on 2011-09-27 01:50:11 EDT ---
Planing to keep 3.4.x branch as "internal enhancements" release without any features. So moving these bugs to 3.4.0 target milestone.
--- Additional comment from sac on 2011-11-21 10:22:21 EST ---
Don't know if I can close this. Reported by Keisuke Takahashi... have to test this though.
--- Additional comment from amarts on 2012-03-25 05:11:14 EDT ---
*** Bug 806504 has been marked as a duplicate of this bug. ***
--- Additional comment from amarts on 2012-03-25 05:12:28 EDT ---
*** Bug 765228 has been marked as a duplicate of this bug. ***
--- Additional comment from rodrigo on 2012-06-04 11:33:04 EDT ---
Paraphasing David Coulson at Gluster Users mailing list:
Why does not use ports within the /proc/sys/net/ipv4/ip_local_port_range?
--- Additional comment from botsch.edu on 2012-07-11 15:44:50 EDT ---
With two servers, glusterfs (v3.3) started up listening on port 993, which kept dovecot from starting. Not good. Please fix.
Need some better security measures before fixing this behavior. As of now, port < 1024 is the only main secure way of telling 'root' is mounting the client.