Timeline for What is the interface scope (global vs. link) used for?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 19, 2023 at 13:57 | comment | added | Robert Siemer | @torez233 Yes, they have a meaning. And the link you provide explains them. | |
| Dec 19, 2023 at 6:17 | comment | added | torez233 | 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 | |
| Dec 13, 2018 at 2:02 | history | edited | Robert Siemer | CC BY-SA 4.0 | add examples |
| Apr 26, 2018 at 22:26 | comment | added | Robert Siemer | @TheDiveO That fact is already part of the question I'm answering here. | |
| Apr 26, 2018 at 10:53 | comment | added | TheDiveO | 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! | |
| May 11, 2016 at 18:13 | history | answered | Robert Siemer | CC BY-SA 3.0 |