Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • 1
    Do you have a literature reference for your statement "scope influences address selection" that explicitly links this to routes? My understanding of RFC 6724 is that only addresses have scope, but the RFC is silent on any scope property of routes. If there is in fact a scope defined for routes, it would be great if you could reference it in your answer. Thanks! Commented Apr 26, 2018 at 10:53
  • @TheDiveO That fact is already part of the question I'm answering here. Commented Apr 26, 2018 at 22:26
  • 1
    If scope is only used for restricting the range of IPs selected as source IP, then why people don't simply name the scope as "A", "B", "C" etc. instead they name the scope as "link", "site" and "global" (man7.org/linux/man-pages/man8/ip-address.8.html, "scope SCOPE_VALUE") I think there are some implicit meaning behind these terms but I could not find them out by myself Commented Dec 19, 2023 at 6:17
  • @torez233 Yes, they have a meaning. And the link you provide explains them. Commented Dec 19, 2023 at 13:57