Do the concepts of IP address and network interface not belong to the same layer?












2















https://unix.stackexchange.com/a/508065/674




You are confusing the device driver layers and the IP layers of the
stack.



At the IP layer, 127.0.0.1 is just another IP address and treated the
same.



At the driver layer, packets sent via the loopback interface are
"simply and immediately passed back up the network software stack" as
opposed to being sent to a network card.



This concept is not OS specific; various OSes use the same concept.



You have confusion between localhost (127.0.0.1) and loopback interfaces. Yes, you are confused between the network stack layers.




In computer networks, the lower layers than the network layer is the data link layer and the physical layer. Where is the device driver layer in computer networks?



It claims the concept is not OS specific, so I try my luck here. So did I in the question (Does a loop back IP address not need to be assigned to a network interface, in order to communicate with?) which I want to know the most. Some users on both sites (Unix and Network Engineering) claimed the same questions belong to the other side, saddening me.



Thanks.










share|improve this question

























  • "In computer networks, the lower layers than the network layer is the data link layer and the physical layer" Only per a completely antiquated and over-simplified system called the OSI model that has very little to do with how things actually work, particularly in the modern age!

    – Lightness Races in Orbit
    7 hours ago


















2















https://unix.stackexchange.com/a/508065/674




You are confusing the device driver layers and the IP layers of the
stack.



At the IP layer, 127.0.0.1 is just another IP address and treated the
same.



At the driver layer, packets sent via the loopback interface are
"simply and immediately passed back up the network software stack" as
opposed to being sent to a network card.



This concept is not OS specific; various OSes use the same concept.



You have confusion between localhost (127.0.0.1) and loopback interfaces. Yes, you are confused between the network stack layers.




In computer networks, the lower layers than the network layer is the data link layer and the physical layer. Where is the device driver layer in computer networks?



It claims the concept is not OS specific, so I try my luck here. So did I in the question (Does a loop back IP address not need to be assigned to a network interface, in order to communicate with?) which I want to know the most. Some users on both sites (Unix and Network Engineering) claimed the same questions belong to the other side, saddening me.



Thanks.










share|improve this question

























  • "In computer networks, the lower layers than the network layer is the data link layer and the physical layer" Only per a completely antiquated and over-simplified system called the OSI model that has very little to do with how things actually work, particularly in the modern age!

    – Lightness Races in Orbit
    7 hours ago
















2












2








2








https://unix.stackexchange.com/a/508065/674




You are confusing the device driver layers and the IP layers of the
stack.



At the IP layer, 127.0.0.1 is just another IP address and treated the
same.



At the driver layer, packets sent via the loopback interface are
"simply and immediately passed back up the network software stack" as
opposed to being sent to a network card.



This concept is not OS specific; various OSes use the same concept.



You have confusion between localhost (127.0.0.1) and loopback interfaces. Yes, you are confused between the network stack layers.




In computer networks, the lower layers than the network layer is the data link layer and the physical layer. Where is the device driver layer in computer networks?



It claims the concept is not OS specific, so I try my luck here. So did I in the question (Does a loop back IP address not need to be assigned to a network interface, in order to communicate with?) which I want to know the most. Some users on both sites (Unix and Network Engineering) claimed the same questions belong to the other side, saddening me.



Thanks.










share|improve this question
















https://unix.stackexchange.com/a/508065/674




You are confusing the device driver layers and the IP layers of the
stack.



At the IP layer, 127.0.0.1 is just another IP address and treated the
same.



At the driver layer, packets sent via the loopback interface are
"simply and immediately passed back up the network software stack" as
opposed to being sent to a network card.



This concept is not OS specific; various OSes use the same concept.



You have confusion between localhost (127.0.0.1) and loopback interfaces. Yes, you are confused between the network stack layers.




In computer networks, the lower layers than the network layer is the data link layer and the physical layer. Where is the device driver layer in computer networks?



It claims the concept is not OS specific, so I try my luck here. So did I in the question (Does a loop back IP address not need to be assigned to a network interface, in order to communicate with?) which I want to know the most. Some users on both sites (Unix and Network Engineering) claimed the same questions belong to the other side, saddening me.



Thanks.







ip-address interface osi






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 16 hours ago









Zac67

32k22163




32k22163










asked 16 hours ago









TimTim

613516




613516













  • "In computer networks, the lower layers than the network layer is the data link layer and the physical layer" Only per a completely antiquated and over-simplified system called the OSI model that has very little to do with how things actually work, particularly in the modern age!

    – Lightness Races in Orbit
    7 hours ago





















  • "In computer networks, the lower layers than the network layer is the data link layer and the physical layer" Only per a completely antiquated and over-simplified system called the OSI model that has very little to do with how things actually work, particularly in the modern age!

    – Lightness Races in Orbit
    7 hours ago



















"In computer networks, the lower layers than the network layer is the data link layer and the physical layer" Only per a completely antiquated and over-simplified system called the OSI model that has very little to do with how things actually work, particularly in the modern age!

– Lightness Races in Orbit
7 hours ago







"In computer networks, the lower layers than the network layer is the data link layer and the physical layer" Only per a completely antiquated and over-simplified system called the OSI model that has very little to do with how things actually work, particularly in the modern age!

– Lightness Races in Orbit
7 hours ago












2 Answers
2






active

oldest

votes


















6














Tim, you are trying very hard to map abstract concepts to real life hardware and software. They don't map exactly, so you always will have things that don't fit. Software is modularized for ease of coding and troubleshooting, but the divisions between modules don't line up with the concept of network layers. When we talk about software (or hardware) operating at this layer or that layer, we are abstracting their functions. Which piece of code might actually be doing the work is dependent on the particular implementation. It may be based more on the hardware functions, like a device driver. There is no "device driver layer" in the OSI or TCPIP model.



If you ping the loopback address (127.0.0.1) or the network interface address, the practical result is the same. It may be that different parts of the operating system software are being used, but that is transparent to you*.



*The one difference is that the network interface can be down (or completely removed for that matter), but the loopback IP will always respond as long as the OS is running.






share|improve this answer































    4














    Your question is very close to being off-topic here due to host-specific details.



    A NIC is a physical interface, implementing layers 1 and 2. In order to use it in an OS's harwdare abstraction layer, a driver is required. That driver presents a standardized interface ("upwards") for the OS (or "the stack") to talk to. Also, it contains hardware-specific code ("downwards") to make the hardware do what the OS tells it to.



    Accordingly, the driver belongs to layer 2 in the OSI stack. The "device driver layer" is an unconnected OS concept.



    I'm not sure if the poster is completely right though. Very commonly, a local or a loopback address is detected within the OS stack, before a packet reaches the driver layer. This however, is definitely host-specific and off-topic here.



    An IP address is an address in the network layer, L3.



    You check out the numerous Q&A to OSI layering. Each layer has its specific purpose and tasks.






    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%2f57926%2fdo-the-concepts-of-ip-address-and-network-interface-not-belong-to-the-same-layer%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









      6














      Tim, you are trying very hard to map abstract concepts to real life hardware and software. They don't map exactly, so you always will have things that don't fit. Software is modularized for ease of coding and troubleshooting, but the divisions between modules don't line up with the concept of network layers. When we talk about software (or hardware) operating at this layer or that layer, we are abstracting their functions. Which piece of code might actually be doing the work is dependent on the particular implementation. It may be based more on the hardware functions, like a device driver. There is no "device driver layer" in the OSI or TCPIP model.



      If you ping the loopback address (127.0.0.1) or the network interface address, the practical result is the same. It may be that different parts of the operating system software are being used, but that is transparent to you*.



      *The one difference is that the network interface can be down (or completely removed for that matter), but the loopback IP will always respond as long as the OS is running.






      share|improve this answer




























        6














        Tim, you are trying very hard to map abstract concepts to real life hardware and software. They don't map exactly, so you always will have things that don't fit. Software is modularized for ease of coding and troubleshooting, but the divisions between modules don't line up with the concept of network layers. When we talk about software (or hardware) operating at this layer or that layer, we are abstracting their functions. Which piece of code might actually be doing the work is dependent on the particular implementation. It may be based more on the hardware functions, like a device driver. There is no "device driver layer" in the OSI or TCPIP model.



        If you ping the loopback address (127.0.0.1) or the network interface address, the practical result is the same. It may be that different parts of the operating system software are being used, but that is transparent to you*.



        *The one difference is that the network interface can be down (or completely removed for that matter), but the loopback IP will always respond as long as the OS is running.






        share|improve this answer


























          6












          6








          6







          Tim, you are trying very hard to map abstract concepts to real life hardware and software. They don't map exactly, so you always will have things that don't fit. Software is modularized for ease of coding and troubleshooting, but the divisions between modules don't line up with the concept of network layers. When we talk about software (or hardware) operating at this layer or that layer, we are abstracting their functions. Which piece of code might actually be doing the work is dependent on the particular implementation. It may be based more on the hardware functions, like a device driver. There is no "device driver layer" in the OSI or TCPIP model.



          If you ping the loopback address (127.0.0.1) or the network interface address, the practical result is the same. It may be that different parts of the operating system software are being used, but that is transparent to you*.



          *The one difference is that the network interface can be down (or completely removed for that matter), but the loopback IP will always respond as long as the OS is running.






          share|improve this answer













          Tim, you are trying very hard to map abstract concepts to real life hardware and software. They don't map exactly, so you always will have things that don't fit. Software is modularized for ease of coding and troubleshooting, but the divisions between modules don't line up with the concept of network layers. When we talk about software (or hardware) operating at this layer or that layer, we are abstracting their functions. Which piece of code might actually be doing the work is dependent on the particular implementation. It may be based more on the hardware functions, like a device driver. There is no "device driver layer" in the OSI or TCPIP model.



          If you ping the loopback address (127.0.0.1) or the network interface address, the practical result is the same. It may be that different parts of the operating system software are being used, but that is transparent to you*.



          *The one difference is that the network interface can be down (or completely removed for that matter), but the loopback IP will always respond as long as the OS is running.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 14 hours ago









          Ron TrunkRon Trunk

          38.7k33780




          38.7k33780























              4














              Your question is very close to being off-topic here due to host-specific details.



              A NIC is a physical interface, implementing layers 1 and 2. In order to use it in an OS's harwdare abstraction layer, a driver is required. That driver presents a standardized interface ("upwards") for the OS (or "the stack") to talk to. Also, it contains hardware-specific code ("downwards") to make the hardware do what the OS tells it to.



              Accordingly, the driver belongs to layer 2 in the OSI stack. The "device driver layer" is an unconnected OS concept.



              I'm not sure if the poster is completely right though. Very commonly, a local or a loopback address is detected within the OS stack, before a packet reaches the driver layer. This however, is definitely host-specific and off-topic here.



              An IP address is an address in the network layer, L3.



              You check out the numerous Q&A to OSI layering. Each layer has its specific purpose and tasks.






              share|improve this answer




























                4














                Your question is very close to being off-topic here due to host-specific details.



                A NIC is a physical interface, implementing layers 1 and 2. In order to use it in an OS's harwdare abstraction layer, a driver is required. That driver presents a standardized interface ("upwards") for the OS (or "the stack") to talk to. Also, it contains hardware-specific code ("downwards") to make the hardware do what the OS tells it to.



                Accordingly, the driver belongs to layer 2 in the OSI stack. The "device driver layer" is an unconnected OS concept.



                I'm not sure if the poster is completely right though. Very commonly, a local or a loopback address is detected within the OS stack, before a packet reaches the driver layer. This however, is definitely host-specific and off-topic here.



                An IP address is an address in the network layer, L3.



                You check out the numerous Q&A to OSI layering. Each layer has its specific purpose and tasks.






                share|improve this answer


























                  4












                  4








                  4







                  Your question is very close to being off-topic here due to host-specific details.



                  A NIC is a physical interface, implementing layers 1 and 2. In order to use it in an OS's harwdare abstraction layer, a driver is required. That driver presents a standardized interface ("upwards") for the OS (or "the stack") to talk to. Also, it contains hardware-specific code ("downwards") to make the hardware do what the OS tells it to.



                  Accordingly, the driver belongs to layer 2 in the OSI stack. The "device driver layer" is an unconnected OS concept.



                  I'm not sure if the poster is completely right though. Very commonly, a local or a loopback address is detected within the OS stack, before a packet reaches the driver layer. This however, is definitely host-specific and off-topic here.



                  An IP address is an address in the network layer, L3.



                  You check out the numerous Q&A to OSI layering. Each layer has its specific purpose and tasks.






                  share|improve this answer













                  Your question is very close to being off-topic here due to host-specific details.



                  A NIC is a physical interface, implementing layers 1 and 2. In order to use it in an OS's harwdare abstraction layer, a driver is required. That driver presents a standardized interface ("upwards") for the OS (or "the stack") to talk to. Also, it contains hardware-specific code ("downwards") to make the hardware do what the OS tells it to.



                  Accordingly, the driver belongs to layer 2 in the OSI stack. The "device driver layer" is an unconnected OS concept.



                  I'm not sure if the poster is completely right though. Very commonly, a local or a loopback address is detected within the OS stack, before a packet reaches the driver layer. This however, is definitely host-specific and off-topic here.



                  An IP address is an address in the network layer, L3.



                  You check out the numerous Q&A to OSI layering. Each layer has its specific purpose and tasks.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered 16 hours ago









                  Zac67Zac67

                  32k22163




                  32k22163






























                      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%2f57926%2fdo-the-concepts-of-ip-address-and-network-interface-not-belong-to-the-same-layer%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

                      How to reconfigure Docker Trusted Registry 2.x.x to use CEPH FS mount instead of NFS and other traditional...

                      is 'sed' thread safe

                      How to make a Squid Proxy server?