[Bugs] [Bug 1335813] New: rpc: change client insecure port ceiling from 65535 to 49151

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1335813

            Bug ID: 1335813
           Summary: rpc: change client insecure port ceiling from 65535 to
                    49151
           Product: GlusterFS
           Version: 3.7.11
         Component: rpc
          Assignee: bugs at gluster.org
          Reporter: prasanna.kalever at redhat.com
                CC: bugs at gluster.org
        Depends On: 1335776



+++ This bug was initially created as a clone of Bug #1335776 +++

Description of problem:
current port allocation to various processes (clumsy):

 1023 - 1       -> client ports range if bind secure is turned on
49151 - 1024    -> fall back to this, if in above case ports exhaust
65535 - 1024    -> client port range if bind insecure is on
49152 - 65535   -> brick port range

now, we should have segregated port ranges 0 - 65535 to below 3 ranges

 1023 - 1       -> client ports range if bind secure is turned on
49151 - 1024    -> client port range if bind insecure is on
                   (fall back to this, if in above case ports exhaust)
49152 - 65535   -> brick port range

for a cleaner way of segregation this is necessary, and since  bind insecure
is on by default, there could be a chance of port clashes between brick and
clients

Version-Release number of selected component (if applicable):
3.7.11

--- Additional comment from Vijay Bellur on 2016-05-13 04:20:20 EDT ---

REVIEW: http://review.gluster.org/14326 (rpc: change client insecure port
ceiling from 65535 to 49151) posted (#1) for review on master by Prasanna Kumar
Kalever (pkalever at redhat.com)


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1335776
[Bug 1335776] rpc: change client insecure port ceiling from 65535 to 49151
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.