0.0.0.0/32 Special-Use address












1















I was wondering what is the role of this special-use address.



The similar 0.0.0.0/8 represents a host with no IP assigned,but it's not the same with the 0.0.0.0/32 address



What is the difference?










share|improve this question


















  • 1





    Where did you see this address used? Some context would help us give you an answer.

    – Ron Trunk
    Jan 26 at 15:19











  • I personally have never seen either of those. You usually see 0.0.0.0/0, which is an equivalent for 'any IP address'.

    – Teun Vink
    Jan 26 at 15:26











  • My book says the following "0.0.0.0/8 (Limited source): Seen only as a source address and indicates packets from computers of the "same" network on which it belongs to the specific computer while 0.0.0.0/32 expresses packages of the "same" computer."

    – Zach
    Jan 26 at 15:34






  • 3





    What is the title and author of that book?

    – Ron Trunk
    Jan 26 at 16:19
















1















I was wondering what is the role of this special-use address.



The similar 0.0.0.0/8 represents a host with no IP assigned,but it's not the same with the 0.0.0.0/32 address



What is the difference?










share|improve this question


















  • 1





    Where did you see this address used? Some context would help us give you an answer.

    – Ron Trunk
    Jan 26 at 15:19











  • I personally have never seen either of those. You usually see 0.0.0.0/0, which is an equivalent for 'any IP address'.

    – Teun Vink
    Jan 26 at 15:26











  • My book says the following "0.0.0.0/8 (Limited source): Seen only as a source address and indicates packets from computers of the "same" network on which it belongs to the specific computer while 0.0.0.0/32 expresses packages of the "same" computer."

    – Zach
    Jan 26 at 15:34






  • 3





    What is the title and author of that book?

    – Ron Trunk
    Jan 26 at 16:19














1












1








1








I was wondering what is the role of this special-use address.



The similar 0.0.0.0/8 represents a host with no IP assigned,but it's not the same with the 0.0.0.0/32 address



What is the difference?










share|improve this question














I was wondering what is the role of this special-use address.



The similar 0.0.0.0/8 represents a host with no IP assigned,but it's not the same with the 0.0.0.0/32 address



What is the difference?







ip ipv4 ip-address






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 26 at 15:12









ZachZach

363




363








  • 1





    Where did you see this address used? Some context would help us give you an answer.

    – Ron Trunk
    Jan 26 at 15:19











  • I personally have never seen either of those. You usually see 0.0.0.0/0, which is an equivalent for 'any IP address'.

    – Teun Vink
    Jan 26 at 15:26











  • My book says the following "0.0.0.0/8 (Limited source): Seen only as a source address and indicates packets from computers of the "same" network on which it belongs to the specific computer while 0.0.0.0/32 expresses packages of the "same" computer."

    – Zach
    Jan 26 at 15:34






  • 3





    What is the title and author of that book?

    – Ron Trunk
    Jan 26 at 16:19














  • 1





    Where did you see this address used? Some context would help us give you an answer.

    – Ron Trunk
    Jan 26 at 15:19











  • I personally have never seen either of those. You usually see 0.0.0.0/0, which is an equivalent for 'any IP address'.

    – Teun Vink
    Jan 26 at 15:26











  • My book says the following "0.0.0.0/8 (Limited source): Seen only as a source address and indicates packets from computers of the "same" network on which it belongs to the specific computer while 0.0.0.0/32 expresses packages of the "same" computer."

    – Zach
    Jan 26 at 15:34






  • 3





    What is the title and author of that book?

    – Ron Trunk
    Jan 26 at 16:19








1




1





Where did you see this address used? Some context would help us give you an answer.

– Ron Trunk
Jan 26 at 15:19





Where did you see this address used? Some context would help us give you an answer.

– Ron Trunk
Jan 26 at 15:19













I personally have never seen either of those. You usually see 0.0.0.0/0, which is an equivalent for 'any IP address'.

– Teun Vink
Jan 26 at 15:26





I personally have never seen either of those. You usually see 0.0.0.0/0, which is an equivalent for 'any IP address'.

– Teun Vink
Jan 26 at 15:26













My book says the following "0.0.0.0/8 (Limited source): Seen only as a source address and indicates packets from computers of the "same" network on which it belongs to the specific computer while 0.0.0.0/32 expresses packages of the "same" computer."

– Zach
Jan 26 at 15:34





My book says the following "0.0.0.0/8 (Limited source): Seen only as a source address and indicates packets from computers of the "same" network on which it belongs to the specific computer while 0.0.0.0/32 expresses packages of the "same" computer."

– Zach
Jan 26 at 15:34




3




3





What is the title and author of that book?

– Ron Trunk
Jan 26 at 16:19





What is the title and author of that book?

– Ron Trunk
Jan 26 at 16:19










2 Answers
2






active

oldest

votes


















4














According to the IANA which is the authoritative source regarding IP address assignment. 0.0.0.0/8 is reserved:



From the IANA IPv4 Address Space Registry page:




Prefix    Designation     Date    WHOIS   RDAP    Status [1]  Note  
000/8 IANA - Local Identification 1981-09 RESERVED [2]



And the footnote [2]:




0.0.0.0/8 reserved for self-identification [RFC1122], section 3.2.1.3. Reserved by protocol. For authoritative registration, see [IANA
registry iana-ipv4-special-registry].




RFC1122 states that:




3.2.1 Internet Protocol -- IP



     3.2.1.3  Addressing: RFC-791 Section 3.2

We now summarize the important special cases for Class A, B,
and C IP addresses, using the following notation for an IP
address:

{ <Network-number>, <Host-number> }

or
{ <Network-number>, <Subnet-number>, <Host-number> }


(a) { 0, 0 }



             This host on this network.  MUST NOT be sent, except as
a source address as part of an initialization procedure
by which the host learns its own IP address.

See also Section 3.3.6 for a non-standard use of {0,0}.



(Section 3.3.6 is related to all zero broadcast addresses)



Conclusion



0.0.0.0/8 is the first /8 network of the Internet and it is reserved.



0.0.0.0/32 is the very first host address of the Internet, and, as part of the 0.0.0.0/8 network it is reserved.



A 0.0.0.0 address is only use locally as part of an initialization procedure, I.E. DHCP / BOOTP.
This procedure being local, it doesn't involve a subnet mask, so there's no notion of /32.






share|improve this answer

































    1














    I think you are confusing networks with addresses because packets have source and destination addresses, but no mask information. That means that any host address is the full 32 bits of the address.



    An address in the 0.0.0.0/8 network can be used as a source address when a host does not know its own address, e,g, in a DHCP request, but they can never be used as a destination address because a host cannot be assigned an address in that network.



    This is spelled out in RFC 1122, Requirements for Internet Hosts -- Communication Layers:




    (a)  { 0, 0 }

    This host on this network. MUST NOT be sent, except as a source
    address as part of an initialization procedure by which the host
    learns its own IP address.

    See also Section 3.3.6 for a non-standard use of {0,0}.

    (b) { 0, <Host-number> }

    Specified host on this network. It MUST NOT be sent, except as a
    source address as part of an initialization procedure by which the
    host learns its full IP address.



    Network masks (or a mask length, such as /8) are used in routing tables by a router to determine where to send packets destined for a particular address. A destination address is masked to see if it matches any routing table entry, and if it does not match any routing table entry, the packet is dropped. Every IPv4 address is in the 0.0.0.0/0 network, so every address would match that network in a routing table, which is why it is used as a default route. Routers drop any traffic for which they do not have a route, but because 0.0.0.0/0 matches every address, then a router with that network in its routing table has a match for every address.






    share|improve this answer























      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "496"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: false,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      noCode: true, onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fnetworkengineering.stackexchange.com%2fquestions%2f56406%2f0-0-0-0-32-special-use-address%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      4














      According to the IANA which is the authoritative source regarding IP address assignment. 0.0.0.0/8 is reserved:



      From the IANA IPv4 Address Space Registry page:




      Prefix    Designation     Date    WHOIS   RDAP    Status [1]  Note  
      000/8 IANA - Local Identification 1981-09 RESERVED [2]



      And the footnote [2]:




      0.0.0.0/8 reserved for self-identification [RFC1122], section 3.2.1.3. Reserved by protocol. For authoritative registration, see [IANA
      registry iana-ipv4-special-registry].




      RFC1122 states that:




      3.2.1 Internet Protocol -- IP



           3.2.1.3  Addressing: RFC-791 Section 3.2

      We now summarize the important special cases for Class A, B,
      and C IP addresses, using the following notation for an IP
      address:

      { <Network-number>, <Host-number> }

      or
      { <Network-number>, <Subnet-number>, <Host-number> }


      (a) { 0, 0 }



                   This host on this network.  MUST NOT be sent, except as
      a source address as part of an initialization procedure
      by which the host learns its own IP address.

      See also Section 3.3.6 for a non-standard use of {0,0}.



      (Section 3.3.6 is related to all zero broadcast addresses)



      Conclusion



      0.0.0.0/8 is the first /8 network of the Internet and it is reserved.



      0.0.0.0/32 is the very first host address of the Internet, and, as part of the 0.0.0.0/8 network it is reserved.



      A 0.0.0.0 address is only use locally as part of an initialization procedure, I.E. DHCP / BOOTP.
      This procedure being local, it doesn't involve a subnet mask, so there's no notion of /32.






      share|improve this answer






























        4














        According to the IANA which is the authoritative source regarding IP address assignment. 0.0.0.0/8 is reserved:



        From the IANA IPv4 Address Space Registry page:




        Prefix    Designation     Date    WHOIS   RDAP    Status [1]  Note  
        000/8 IANA - Local Identification 1981-09 RESERVED [2]



        And the footnote [2]:




        0.0.0.0/8 reserved for self-identification [RFC1122], section 3.2.1.3. Reserved by protocol. For authoritative registration, see [IANA
        registry iana-ipv4-special-registry].




        RFC1122 states that:




        3.2.1 Internet Protocol -- IP



             3.2.1.3  Addressing: RFC-791 Section 3.2

        We now summarize the important special cases for Class A, B,
        and C IP addresses, using the following notation for an IP
        address:

        { <Network-number>, <Host-number> }

        or
        { <Network-number>, <Subnet-number>, <Host-number> }


        (a) { 0, 0 }



                     This host on this network.  MUST NOT be sent, except as
        a source address as part of an initialization procedure
        by which the host learns its own IP address.

        See also Section 3.3.6 for a non-standard use of {0,0}.



        (Section 3.3.6 is related to all zero broadcast addresses)



        Conclusion



        0.0.0.0/8 is the first /8 network of the Internet and it is reserved.



        0.0.0.0/32 is the very first host address of the Internet, and, as part of the 0.0.0.0/8 network it is reserved.



        A 0.0.0.0 address is only use locally as part of an initialization procedure, I.E. DHCP / BOOTP.
        This procedure being local, it doesn't involve a subnet mask, so there's no notion of /32.






        share|improve this answer




























          4












          4








          4







          According to the IANA which is the authoritative source regarding IP address assignment. 0.0.0.0/8 is reserved:



          From the IANA IPv4 Address Space Registry page:




          Prefix    Designation     Date    WHOIS   RDAP    Status [1]  Note  
          000/8 IANA - Local Identification 1981-09 RESERVED [2]



          And the footnote [2]:




          0.0.0.0/8 reserved for self-identification [RFC1122], section 3.2.1.3. Reserved by protocol. For authoritative registration, see [IANA
          registry iana-ipv4-special-registry].




          RFC1122 states that:




          3.2.1 Internet Protocol -- IP



               3.2.1.3  Addressing: RFC-791 Section 3.2

          We now summarize the important special cases for Class A, B,
          and C IP addresses, using the following notation for an IP
          address:

          { <Network-number>, <Host-number> }

          or
          { <Network-number>, <Subnet-number>, <Host-number> }


          (a) { 0, 0 }



                       This host on this network.  MUST NOT be sent, except as
          a source address as part of an initialization procedure
          by which the host learns its own IP address.

          See also Section 3.3.6 for a non-standard use of {0,0}.



          (Section 3.3.6 is related to all zero broadcast addresses)



          Conclusion



          0.0.0.0/8 is the first /8 network of the Internet and it is reserved.



          0.0.0.0/32 is the very first host address of the Internet, and, as part of the 0.0.0.0/8 network it is reserved.



          A 0.0.0.0 address is only use locally as part of an initialization procedure, I.E. DHCP / BOOTP.
          This procedure being local, it doesn't involve a subnet mask, so there's no notion of /32.






          share|improve this answer















          According to the IANA which is the authoritative source regarding IP address assignment. 0.0.0.0/8 is reserved:



          From the IANA IPv4 Address Space Registry page:




          Prefix    Designation     Date    WHOIS   RDAP    Status [1]  Note  
          000/8 IANA - Local Identification 1981-09 RESERVED [2]



          And the footnote [2]:




          0.0.0.0/8 reserved for self-identification [RFC1122], section 3.2.1.3. Reserved by protocol. For authoritative registration, see [IANA
          registry iana-ipv4-special-registry].




          RFC1122 states that:




          3.2.1 Internet Protocol -- IP



               3.2.1.3  Addressing: RFC-791 Section 3.2

          We now summarize the important special cases for Class A, B,
          and C IP addresses, using the following notation for an IP
          address:

          { <Network-number>, <Host-number> }

          or
          { <Network-number>, <Subnet-number>, <Host-number> }


          (a) { 0, 0 }



                       This host on this network.  MUST NOT be sent, except as
          a source address as part of an initialization procedure
          by which the host learns its own IP address.

          See also Section 3.3.6 for a non-standard use of {0,0}.



          (Section 3.3.6 is related to all zero broadcast addresses)



          Conclusion



          0.0.0.0/8 is the first /8 network of the Internet and it is reserved.



          0.0.0.0/32 is the very first host address of the Internet, and, as part of the 0.0.0.0/8 network it is reserved.



          A 0.0.0.0 address is only use locally as part of an initialization procedure, I.E. DHCP / BOOTP.
          This procedure being local, it doesn't involve a subnet mask, so there's no notion of /32.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Jan 26 at 21:16

























          answered Jan 26 at 17:00









          JFLJFL

          11.6k11339




          11.6k11339























              1














              I think you are confusing networks with addresses because packets have source and destination addresses, but no mask information. That means that any host address is the full 32 bits of the address.



              An address in the 0.0.0.0/8 network can be used as a source address when a host does not know its own address, e,g, in a DHCP request, but they can never be used as a destination address because a host cannot be assigned an address in that network.



              This is spelled out in RFC 1122, Requirements for Internet Hosts -- Communication Layers:




              (a)  { 0, 0 }

              This host on this network. MUST NOT be sent, except as a source
              address as part of an initialization procedure by which the host
              learns its own IP address.

              See also Section 3.3.6 for a non-standard use of {0,0}.

              (b) { 0, <Host-number> }

              Specified host on this network. It MUST NOT be sent, except as a
              source address as part of an initialization procedure by which the
              host learns its full IP address.



              Network masks (or a mask length, such as /8) are used in routing tables by a router to determine where to send packets destined for a particular address. A destination address is masked to see if it matches any routing table entry, and if it does not match any routing table entry, the packet is dropped. Every IPv4 address is in the 0.0.0.0/0 network, so every address would match that network in a routing table, which is why it is used as a default route. Routers drop any traffic for which they do not have a route, but because 0.0.0.0/0 matches every address, then a router with that network in its routing table has a match for every address.






              share|improve this answer




























                1














                I think you are confusing networks with addresses because packets have source and destination addresses, but no mask information. That means that any host address is the full 32 bits of the address.



                An address in the 0.0.0.0/8 network can be used as a source address when a host does not know its own address, e,g, in a DHCP request, but they can never be used as a destination address because a host cannot be assigned an address in that network.



                This is spelled out in RFC 1122, Requirements for Internet Hosts -- Communication Layers:




                (a)  { 0, 0 }

                This host on this network. MUST NOT be sent, except as a source
                address as part of an initialization procedure by which the host
                learns its own IP address.

                See also Section 3.3.6 for a non-standard use of {0,0}.

                (b) { 0, <Host-number> }

                Specified host on this network. It MUST NOT be sent, except as a
                source address as part of an initialization procedure by which the
                host learns its full IP address.



                Network masks (or a mask length, such as /8) are used in routing tables by a router to determine where to send packets destined for a particular address. A destination address is masked to see if it matches any routing table entry, and if it does not match any routing table entry, the packet is dropped. Every IPv4 address is in the 0.0.0.0/0 network, so every address would match that network in a routing table, which is why it is used as a default route. Routers drop any traffic for which they do not have a route, but because 0.0.0.0/0 matches every address, then a router with that network in its routing table has a match for every address.






                share|improve this answer


























                  1












                  1








                  1







                  I think you are confusing networks with addresses because packets have source and destination addresses, but no mask information. That means that any host address is the full 32 bits of the address.



                  An address in the 0.0.0.0/8 network can be used as a source address when a host does not know its own address, e,g, in a DHCP request, but they can never be used as a destination address because a host cannot be assigned an address in that network.



                  This is spelled out in RFC 1122, Requirements for Internet Hosts -- Communication Layers:




                  (a)  { 0, 0 }

                  This host on this network. MUST NOT be sent, except as a source
                  address as part of an initialization procedure by which the host
                  learns its own IP address.

                  See also Section 3.3.6 for a non-standard use of {0,0}.

                  (b) { 0, <Host-number> }

                  Specified host on this network. It MUST NOT be sent, except as a
                  source address as part of an initialization procedure by which the
                  host learns its full IP address.



                  Network masks (or a mask length, such as /8) are used in routing tables by a router to determine where to send packets destined for a particular address. A destination address is masked to see if it matches any routing table entry, and if it does not match any routing table entry, the packet is dropped. Every IPv4 address is in the 0.0.0.0/0 network, so every address would match that network in a routing table, which is why it is used as a default route. Routers drop any traffic for which they do not have a route, but because 0.0.0.0/0 matches every address, then a router with that network in its routing table has a match for every address.






                  share|improve this answer













                  I think you are confusing networks with addresses because packets have source and destination addresses, but no mask information. That means that any host address is the full 32 bits of the address.



                  An address in the 0.0.0.0/8 network can be used as a source address when a host does not know its own address, e,g, in a DHCP request, but they can never be used as a destination address because a host cannot be assigned an address in that network.



                  This is spelled out in RFC 1122, Requirements for Internet Hosts -- Communication Layers:




                  (a)  { 0, 0 }

                  This host on this network. MUST NOT be sent, except as a source
                  address as part of an initialization procedure by which the host
                  learns its own IP address.

                  See also Section 3.3.6 for a non-standard use of {0,0}.

                  (b) { 0, <Host-number> }

                  Specified host on this network. It MUST NOT be sent, except as a
                  source address as part of an initialization procedure by which the
                  host learns its full IP address.



                  Network masks (or a mask length, such as /8) are used in routing tables by a router to determine where to send packets destined for a particular address. A destination address is masked to see if it matches any routing table entry, and if it does not match any routing table entry, the packet is dropped. Every IPv4 address is in the 0.0.0.0/0 network, so every address would match that network in a routing table, which is why it is used as a default route. Routers drop any traffic for which they do not have a route, but because 0.0.0.0/0 matches every address, then a router with that network in its routing table has a match for every address.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Jan 26 at 17:00









                  Ron MaupinRon Maupin

                  67.4k1369126




                  67.4k1369126






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Network Engineering Stack Exchange!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fnetworkengineering.stackexchange.com%2fquestions%2f56406%2f0-0-0-0-32-special-use-address%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

                      SQL update select statement

                      'app-layout' is not a known element: how to share Component with different Modules