Issue #9544 has been updated by Akira Tanaka.


I found GNU/Hurd and Haiku also allocates ports sequentially.

GNU/Hurd:

    % ./ruby -v -rsocket -e '10.times { p Addrinfo.udp("0.0.0.0", 0).bind.local_address }'
    ruby 2.2.0dev (2014-01-21 trunk 44678) [i686-gnu0.3]
    #<Addrinfo: 0.0.0.0:32777 UDP>
    #<Addrinfo: 0.0.0.0:32778 UDP>
    #<Addrinfo: 0.0.0.0:32779 UDP>
    #<Addrinfo: 0.0.0.0:32780 UDP>
    #<Addrinfo: 0.0.0.0:32781 UDP>
    #<Addrinfo: 0.0.0.0:32782 UDP>
    #<Addrinfo: 0.0.0.0:32783 UDP>
    #<Addrinfo: 0.0.0.0:32784 UDP>
    #<Addrinfo: 0.0.0.0:32785 UDP>
    #<Addrinfo: 0.0.0.0:32786 UDP>
    % uname -mrsv
    GNU 0.3 GNU-Mach 1.3.99-486/Hurd-0.3 i686-AT386

Haiku:

    > ./ruby -v -rsocket -e '10.times { p Addrinfo.udp("0.0.0.0", 0).bind.local_address }'
    ruby 2.1.0dev (2013-05-11 trunk 40642) [i586-haiku]
    #<Addrinfo: 0.0.0.0:63208 UDP>
    #<Addrinfo: 0.0.0.0:63209 UDP>
    #<Addrinfo: 0.0.0.0:63210 UDP>
    #<Addrinfo: 0.0.0.0:63211 UDP>
    #<Addrinfo: 0.0.0.0:63212 UDP>
    #<Addrinfo: 0.0.0.0:63213 UDP>
    #<Addrinfo: 0.0.0.0:63214 UDP>
    #<Addrinfo: 0.0.0.0:63215 UDP>
    #<Addrinfo: 0.0.0.0:63216 UDP>
    #<Addrinfo: 0.0.0.0:63217 UDP>
    > uname -mrsv
    Haiku 1 hrevr1alpha4-44702 Nov 14 2012  BePC
    

----------------------------------------
Bug #9544: Ruby resolver not using autoport
https://bugs.ruby-lang.org/issues/9544#change-45425

* Author: Jakub Szafranski
* Status: Feedback
* Priority: Normal
* Assignee: 
* Category: core
* Target version: current: 2.2.0
* ruby -v: ruby 2.1.0p0 (2013-12-25 revision 44422) [x86_64-freebsd9.1]
* Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
### Problem

On one of my production servers I've noticed that customers were failing to install anything using gem and the latest ruby. After a bit of debugging we've found out, that it's related to ruby resolve module:

<pre>
> p Resolv.getaddress "google.com"
Errno::EPERM: Operation not permitted - bind(2) for "0.0.0.0" port 62374
        from /home/pudlobe/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/resolv.rb:654:in `bind'
        from /home/pudlobe/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/resolv.rb:654:in `bind_random_port'
        from /home/pudlobe/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/resolv.rb:747:in `block in initialize'
        from /home/pudlobe/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/resolv.rb:735:in `each'
        ...
</pre>

The interesting part is _bind_random_port_ function. What for? The standard way of binding to a random port for udp connection is to use port 0. And on that particular machine it fails because it's using a mac_portacl module to filter which user can bind to what ports. **However, port 0 is excepted from this rule, because it's the AUTOPORT** - practically every system that allows such port filtering also allows to set an exception for the autoport.

### Docs

<pre>
Purpose:

Port 0 is officially a reserved port in TCP/IP networking, meaning that it should not be used for any TCP or UDP network communications. However, port 0 sometimes takes on a special meaning in network programming, particularly Unix socket programming. In that environment, port 0 is a programming technique for specifying system-allocated (dynamic) ports.
Description:

Configuring a new socket connection requires assigning a TCP or UDP port number. Instead of hard-coding a particular port number, or writing code that searches for an available port on the local system, network programmers can instead specify port 0 as a connection parameter. That triggers the operating system to automatically search for and return the next available port in the dynamic port number range.</pre>

### Impact

This bug affects every system that has a restricted port-binding policy, making ruby unavailable for security-freak admins ;)

### Suggested fix:

Either use port 0 to bind to the port, or at least make an option for the system admin/end user to specify the port by himself.




-- 
http://bugs.ruby-lang.org/