[lkml]   [1997]   [Sep]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Subjectipv4 bind()ing bug
    First off, sorry if this problem is known and will be fixed in 2.0.31.
    I try to keep up with the list, but find it impossible to read every

    The problem occurs when a UDP or TCP socket has a local port number of
    zero. Normal un*x behavior is to assign a "random" port number
    between IPPORT_RESERVED (1024) and IPPORT_USERRESERVED (5000). Linux,
    however, assigns a port number between 1024 and 32767. This can be a
    problem, for instance, if X starts up and port 6000 is bound by
    something else. There are a number of servers out there that assume
    they can bind to a port number above 5000 without conflicting with the
    randomly assigned ports. That is, after all, the purpose of
    IPPOR_USERRESERVED. This can also screw with firewalls and packet
    filters which assume normal clients only use port numbers in the
    1024-5000 range.
    Paul H. Hargrove All material not otherwise attributed is the opinion of the author or a typo.

     \ /
      Last update: 2005-03-22 13:40    [W:0.019 / U:185.020 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site