[Bugs] [Bug 1342045] New: port-map: respect local port range as well as local reserved ports

bugzilla at redhat.com bugzilla at redhat.com
Thu Jun 2 10:32:48 UTC 2016


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

            Bug ID: 1342045
           Summary: port-map: respect local port range as well as local
                    reserved ports
           Product: GlusterFS
           Version: mainline
         Component: rpc
          Assignee: bugs at gluster.org
          Reporter: prasanna.kalever at redhat.com
                CC: bugs at gluster.org



Description of problem:
respect local port range as well as local reserved ports              

local port ranges:                                                              
-----------------                                                               
The ports mentioned in '/proc/sys/net/ipv4/ip_local_port_range'                 
separated by space defines the local port range that are used by TCP and UDP    
traffic to choose the local port, only a port from this range is allowed to     
use by applications, this makes the life of admin easy to open firewall         
to this range                                                                   

local reserved ports:                                                           
---------------------                                                           
The ports mentioned in '/proc/sys/net/ipv4/ip_local_reserved_ports'             
separated by comma (,) or hyphen (-) are reserved for some specific             
applications this ports can be ingested only by mentioning that port            
number with bind()                                                              

Problem:                                                                        
--------                                                                        
In the existing implementation of portmap registry, the bricks port             
range was strictly limited within 49152-65535 (follow IANA standard)            
and the client port ranges from 0 - 49151 (secure & in-secure).                 
Also we have our own function 'gf_get_reserved_ports' that will read            
admin mentioned reserved ports from
'/proc/sys/net/ipv4/ip_local_reserved_ports'
and marks them as false (not to use) in port mapper registry [0 - 65535]        
maintained by glusterd across nodes; but the actual problem is that glusterfs   
don't respect local port range '/proc/sys/net/ipv4/ip_local_port_range'         
which is something disappoints admins.   

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

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list