This is delivered via the loopback interface back to the ping program, which shows that we got a reply from 10.0.3.2. Next, the kernel sends a response to the ping: an ICMP response packet with the addresses reversed: 10.0.3.2 as source address and 10.0.3.1 as destination. (In the case of ping, the kernel processes it internally.) We have now received a "remote" ICMP packet with a destination address of 10.0.3.2, which is arguably not one of our local addresses, but it was delivered to the loopback interface nonetheless. From the kernel's point of view, we have now received an incoming packet ready for consumption by a server process listening on a socket. Now, because the packet was given to the lo interface, the loopback interface does what it normally does: it takes the packet off the send queue and puts it on the receive queue. In this case the matching entry is this: local 10.0.3.0/24 dev lo proto kernel scope host src 10.0.3.1, which says the packet should be delivered via the lo interface with the source address 10.0.3.1. Just like with any packet to be delivered, the kernel consults the routing table. Here is what happens when you ping 10.0.3.2: the kernel gets an IP packet for delivery with a destination address 10.0.3.2. Now click on the Loopback button to activate Loopback this routes the audio back in as an input on channels 1 & 2. Click on output AN 1/2 in the bottom-row of TotalMix, then click on the small wrench symbol to expand the options. This routing table entry tells that a packet sent to any address between 10.0.3.1 and 10.0.3.254 is sent via the lo interface, from which it is immediately returned.ĮDIT: clarification as a response to the comment below. 7) Before Skype or Zoom can receive audio from your mic, you’ll need to activate RME’s Loopback function. Something like local 10.0.3.0/24 dev lo proto kernel scope host src 10.0.3.1 You can see this with ip route show table local When you add an address on the loopback interface with e.g.
When you ping 10.0.3.2, the reply does not come from some external device, but from the loopback interface itself. There is nothing that can change this behaviour of the loopback interface, that's what it is coded to do. It makes little sense to put a default route on the loopback interface, because the only place it can send packets to is the imaginary piece of wire that is looped from the output of the interface to the input. whatever you send to it is received on the interface. The only purpose of the loopback interface is to return the packets sent to it, i.e.
The loopback interface is a virtual interface.
0 kommentar(er)
