What does routing an IP address mean?












6















From https://stackoverflow.com/a/40189197/156458




Blocking 0.0.0.0 makes no sense. In IPv4 it is never routed.




What does "routing" a IP address mean?



Why is it the reason that blocking 0.0.0.0 does not make sense?



Thanks.










share|improve this question




















  • 2





    You route packets, not addresses. The packets are routed based on the destination address in the packet header. The 0.0.0.0 address (actually, any address in the 0.0.0.0/8 network) is not allowed to be a destination address, so explicitly blocking that address doesn't really make sense.

    – Ron Maupin
    Mar 23 at 18:57
















6















From https://stackoverflow.com/a/40189197/156458




Blocking 0.0.0.0 makes no sense. In IPv4 it is never routed.




What does "routing" a IP address mean?



Why is it the reason that blocking 0.0.0.0 does not make sense?



Thanks.










share|improve this question




















  • 2





    You route packets, not addresses. The packets are routed based on the destination address in the packet header. The 0.0.0.0 address (actually, any address in the 0.0.0.0/8 network) is not allowed to be a destination address, so explicitly blocking that address doesn't really make sense.

    – Ron Maupin
    Mar 23 at 18:57














6












6








6








From https://stackoverflow.com/a/40189197/156458




Blocking 0.0.0.0 makes no sense. In IPv4 it is never routed.




What does "routing" a IP address mean?



Why is it the reason that blocking 0.0.0.0 does not make sense?



Thanks.










share|improve this question
















From https://stackoverflow.com/a/40189197/156458




Blocking 0.0.0.0 makes no sense. In IPv4 it is never routed.




What does "routing" a IP address mean?



Why is it the reason that blocking 0.0.0.0 does not make sense?



Thanks.







routing ip-address






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 23 at 17:58









Zac67

32.5k22163




32.5k22163










asked Mar 23 at 15:47









TimTim

655518




655518








  • 2





    You route packets, not addresses. The packets are routed based on the destination address in the packet header. The 0.0.0.0 address (actually, any address in the 0.0.0.0/8 network) is not allowed to be a destination address, so explicitly blocking that address doesn't really make sense.

    – Ron Maupin
    Mar 23 at 18:57














  • 2





    You route packets, not addresses. The packets are routed based on the destination address in the packet header. The 0.0.0.0 address (actually, any address in the 0.0.0.0/8 network) is not allowed to be a destination address, so explicitly blocking that address doesn't really make sense.

    – Ron Maupin
    Mar 23 at 18:57








2




2





You route packets, not addresses. The packets are routed based on the destination address in the packet header. The 0.0.0.0 address (actually, any address in the 0.0.0.0/8 network) is not allowed to be a destination address, so explicitly blocking that address doesn't really make sense.

– Ron Maupin
Mar 23 at 18:57





You route packets, not addresses. The packets are routed based on the destination address in the packet header. The 0.0.0.0 address (actually, any address in the 0.0.0.0/8 network) is not allowed to be a destination address, so explicitly blocking that address doesn't really make sense.

– Ron Maupin
Mar 23 at 18:57










1 Answer
1






active

oldest

votes


















6














"Routing" means forwarding a packet based on its network-layer destination address, usually IPv4 or IPv6.



Routing is done by comparing the destination address to the entries in the local routing table and using the best (=longest prefix) match. The entry contains the next-hop gateway or the interface that the packet is then sent to/out of.



0.0.0.0/0 is the default route - because the prefix has zero length it matches any address. However, it is only selected when no other routing entry matches.



As IP address, 0.0.0.0 generally cannot be used (except as source address when configuring an interface, such as with DHCP).






share|improve this answer


























  • Thanks. Does 0.0.0.0 (as an IP address) have two completely different meanings? (1) A process specifies its own unknown address to another process not in the same host, e.g. the DHCP example, and (2) a process specifies that it is listening on all the addresses on the local host, e.g. netstat shows mysql server is listening at ::mysql (unix.stackexchange.com/q/508009/674)?

    – Tim
    Mar 23 at 16:42













  • In "Blocking 0.0.0.0 makes no sense. In IPv4 it is never routed", does 0.0.0.0 mean a IP address? Why is it never routed?

    – Tim
    Mar 23 at 16:45











  • Yes, 0.0.0.0 is also used when specifying "all local IP addresses" when allocating a BSD-style socket - however, this is host-specific and thus off-topic here.

    – Zac67
    Mar 23 at 16:46











  • You can't use 0.0.0.0 as destination address - so it's never routed.

    – Zac67
    Mar 23 at 16:56











  • Thanks. When a server uses 0.0.0.0 to indicate it is listening at all the IP adresses of local host, is 0.0.0.0 used as source address, destination address, or neither?

    – Tim
    Mar 23 at 21:46












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%2f57905%2fwhat-does-routing-an-ip-address-mean%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









6














"Routing" means forwarding a packet based on its network-layer destination address, usually IPv4 or IPv6.



Routing is done by comparing the destination address to the entries in the local routing table and using the best (=longest prefix) match. The entry contains the next-hop gateway or the interface that the packet is then sent to/out of.



0.0.0.0/0 is the default route - because the prefix has zero length it matches any address. However, it is only selected when no other routing entry matches.



As IP address, 0.0.0.0 generally cannot be used (except as source address when configuring an interface, such as with DHCP).






share|improve this answer


























  • Thanks. Does 0.0.0.0 (as an IP address) have two completely different meanings? (1) A process specifies its own unknown address to another process not in the same host, e.g. the DHCP example, and (2) a process specifies that it is listening on all the addresses on the local host, e.g. netstat shows mysql server is listening at ::mysql (unix.stackexchange.com/q/508009/674)?

    – Tim
    Mar 23 at 16:42













  • In "Blocking 0.0.0.0 makes no sense. In IPv4 it is never routed", does 0.0.0.0 mean a IP address? Why is it never routed?

    – Tim
    Mar 23 at 16:45











  • Yes, 0.0.0.0 is also used when specifying "all local IP addresses" when allocating a BSD-style socket - however, this is host-specific and thus off-topic here.

    – Zac67
    Mar 23 at 16:46











  • You can't use 0.0.0.0 as destination address - so it's never routed.

    – Zac67
    Mar 23 at 16:56











  • Thanks. When a server uses 0.0.0.0 to indicate it is listening at all the IP adresses of local host, is 0.0.0.0 used as source address, destination address, or neither?

    – Tim
    Mar 23 at 21:46
















6














"Routing" means forwarding a packet based on its network-layer destination address, usually IPv4 or IPv6.



Routing is done by comparing the destination address to the entries in the local routing table and using the best (=longest prefix) match. The entry contains the next-hop gateway or the interface that the packet is then sent to/out of.



0.0.0.0/0 is the default route - because the prefix has zero length it matches any address. However, it is only selected when no other routing entry matches.



As IP address, 0.0.0.0 generally cannot be used (except as source address when configuring an interface, such as with DHCP).






share|improve this answer


























  • Thanks. Does 0.0.0.0 (as an IP address) have two completely different meanings? (1) A process specifies its own unknown address to another process not in the same host, e.g. the DHCP example, and (2) a process specifies that it is listening on all the addresses on the local host, e.g. netstat shows mysql server is listening at ::mysql (unix.stackexchange.com/q/508009/674)?

    – Tim
    Mar 23 at 16:42













  • In "Blocking 0.0.0.0 makes no sense. In IPv4 it is never routed", does 0.0.0.0 mean a IP address? Why is it never routed?

    – Tim
    Mar 23 at 16:45











  • Yes, 0.0.0.0 is also used when specifying "all local IP addresses" when allocating a BSD-style socket - however, this is host-specific and thus off-topic here.

    – Zac67
    Mar 23 at 16:46











  • You can't use 0.0.0.0 as destination address - so it's never routed.

    – Zac67
    Mar 23 at 16:56











  • Thanks. When a server uses 0.0.0.0 to indicate it is listening at all the IP adresses of local host, is 0.0.0.0 used as source address, destination address, or neither?

    – Tim
    Mar 23 at 21:46














6












6








6







"Routing" means forwarding a packet based on its network-layer destination address, usually IPv4 or IPv6.



Routing is done by comparing the destination address to the entries in the local routing table and using the best (=longest prefix) match. The entry contains the next-hop gateway or the interface that the packet is then sent to/out of.



0.0.0.0/0 is the default route - because the prefix has zero length it matches any address. However, it is only selected when no other routing entry matches.



As IP address, 0.0.0.0 generally cannot be used (except as source address when configuring an interface, such as with DHCP).






share|improve this answer















"Routing" means forwarding a packet based on its network-layer destination address, usually IPv4 or IPv6.



Routing is done by comparing the destination address to the entries in the local routing table and using the best (=longest prefix) match. The entry contains the next-hop gateway or the interface that the packet is then sent to/out of.



0.0.0.0/0 is the default route - because the prefix has zero length it matches any address. However, it is only selected when no other routing entry matches.



As IP address, 0.0.0.0 generally cannot be used (except as source address when configuring an interface, such as with DHCP).







share|improve this answer














share|improve this answer



share|improve this answer








edited Mar 23 at 16:43

























answered Mar 23 at 16:33









Zac67Zac67

32.5k22163




32.5k22163













  • Thanks. Does 0.0.0.0 (as an IP address) have two completely different meanings? (1) A process specifies its own unknown address to another process not in the same host, e.g. the DHCP example, and (2) a process specifies that it is listening on all the addresses on the local host, e.g. netstat shows mysql server is listening at ::mysql (unix.stackexchange.com/q/508009/674)?

    – Tim
    Mar 23 at 16:42













  • In "Blocking 0.0.0.0 makes no sense. In IPv4 it is never routed", does 0.0.0.0 mean a IP address? Why is it never routed?

    – Tim
    Mar 23 at 16:45











  • Yes, 0.0.0.0 is also used when specifying "all local IP addresses" when allocating a BSD-style socket - however, this is host-specific and thus off-topic here.

    – Zac67
    Mar 23 at 16:46











  • You can't use 0.0.0.0 as destination address - so it's never routed.

    – Zac67
    Mar 23 at 16:56











  • Thanks. When a server uses 0.0.0.0 to indicate it is listening at all the IP adresses of local host, is 0.0.0.0 used as source address, destination address, or neither?

    – Tim
    Mar 23 at 21:46



















  • Thanks. Does 0.0.0.0 (as an IP address) have two completely different meanings? (1) A process specifies its own unknown address to another process not in the same host, e.g. the DHCP example, and (2) a process specifies that it is listening on all the addresses on the local host, e.g. netstat shows mysql server is listening at ::mysql (unix.stackexchange.com/q/508009/674)?

    – Tim
    Mar 23 at 16:42













  • In "Blocking 0.0.0.0 makes no sense. In IPv4 it is never routed", does 0.0.0.0 mean a IP address? Why is it never routed?

    – Tim
    Mar 23 at 16:45











  • Yes, 0.0.0.0 is also used when specifying "all local IP addresses" when allocating a BSD-style socket - however, this is host-specific and thus off-topic here.

    – Zac67
    Mar 23 at 16:46











  • You can't use 0.0.0.0 as destination address - so it's never routed.

    – Zac67
    Mar 23 at 16:56











  • Thanks. When a server uses 0.0.0.0 to indicate it is listening at all the IP adresses of local host, is 0.0.0.0 used as source address, destination address, or neither?

    – Tim
    Mar 23 at 21:46

















Thanks. Does 0.0.0.0 (as an IP address) have two completely different meanings? (1) A process specifies its own unknown address to another process not in the same host, e.g. the DHCP example, and (2) a process specifies that it is listening on all the addresses on the local host, e.g. netstat shows mysql server is listening at ::mysql (unix.stackexchange.com/q/508009/674)?

– Tim
Mar 23 at 16:42







Thanks. Does 0.0.0.0 (as an IP address) have two completely different meanings? (1) A process specifies its own unknown address to another process not in the same host, e.g. the DHCP example, and (2) a process specifies that it is listening on all the addresses on the local host, e.g. netstat shows mysql server is listening at ::mysql (unix.stackexchange.com/q/508009/674)?

– Tim
Mar 23 at 16:42















In "Blocking 0.0.0.0 makes no sense. In IPv4 it is never routed", does 0.0.0.0 mean a IP address? Why is it never routed?

– Tim
Mar 23 at 16:45





In "Blocking 0.0.0.0 makes no sense. In IPv4 it is never routed", does 0.0.0.0 mean a IP address? Why is it never routed?

– Tim
Mar 23 at 16:45













Yes, 0.0.0.0 is also used when specifying "all local IP addresses" when allocating a BSD-style socket - however, this is host-specific and thus off-topic here.

– Zac67
Mar 23 at 16:46





Yes, 0.0.0.0 is also used when specifying "all local IP addresses" when allocating a BSD-style socket - however, this is host-specific and thus off-topic here.

– Zac67
Mar 23 at 16:46













You can't use 0.0.0.0 as destination address - so it's never routed.

– Zac67
Mar 23 at 16:56





You can't use 0.0.0.0 as destination address - so it's never routed.

– Zac67
Mar 23 at 16:56













Thanks. When a server uses 0.0.0.0 to indicate it is listening at all the IP adresses of local host, is 0.0.0.0 used as source address, destination address, or neither?

– Tim
Mar 23 at 21:46





Thanks. When a server uses 0.0.0.0 to indicate it is listening at all the IP adresses of local host, is 0.0.0.0 used as source address, destination address, or neither?

– Tim
Mar 23 at 21:46


















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%2f57905%2fwhat-does-routing-an-ip-address-mean%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

If I really need a card on my start hand, how many mulligans make sense? [duplicate]

Alcedinidae

Can an atomic nucleus contain both particles and antiparticles? [duplicate]