IBM Support

PQ74543: PING TREATS IP ADDRESSES WITH LEADING ZEROES AS OCTAL NUMBERS INSTEAD OF DECIMAL NUMBERS.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • Ping treats IP addresses with leading zeroes as octal numbers.
    A ping of IP address 9.017.3.4 will result in a ping being
    sent to IP address 9.15.3.4.  Ping is using the C library call
    inet_addr to convert the IP address into a in_addr structure.
    inet_addr interprets number with leading zeroes as octal. Ping
    should be using inet_pton, which does not do this conversion.
    .
    KEYWORDS:
    ping oping timeout time out
    

Local fix

  • Do not use leading zeroes when entering IP addresses on the
    ping command.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of the IBM Communications Server   *
    *                 for z/OS Version 1 Release 4 IP: PING.       *
    ****************************************************************
    * PROBLEM DESCRIPTION: If an user attempts to PING an IP       *
    *                      address that contains a leading         *
    *                      zero, that request will time out.       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The attempt to PING an IP address that contains a leading
    zero will possibly time out because the portion of the IP
    address that contains a leading zero will be converted to
    an octal number.
    +-------------------------------------------------------------+
    + Please check our Communications Server for OS/390 homepages +
    + for common networking tips and fixes.  The URL for these    +
    + homepages can be found in Informational APAR II11334.       +
    +-------------------------------------------------------------+
    

Problem conclusion

Temporary fix

Comments

  • This APAR is being closed FIN (Fixed If Next) with concurrence
    from the submitting customer. This means that a fix to this
    APAR is expected to be delivered from IBM in a release (if any)
    to be available within the next 18 months.
    
    This problem will be tracked as PTR MV28322 by Communications
    Server for z/OS Development.
    
    PTR28322   PTR 28322
    

APAR Information

  • APAR number

    PQ74543

  • Reported component name

    TCP/IP V3 MVS

  • Reported component ID

    5655HAL00

  • Reported release

    140

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2003-05-23

  • Closed date

    2003-05-28

  • Last modified date

    2003-05-28

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

  • R140 PSN

       UP

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"140","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCY4DZ","label":"DO NOT USE"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"140","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
28 May 2003