Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.networking > #581 > unrolled thread
| Started by | InuY4sha <riccardomanfrin@email.it> |
|---|---|
| First post | 2011-09-13 06:59 -0700 |
| Last post | 2011-09-13 21:36 +0700 |
| Articles | 2 — 2 participants |
Back to article view | Back to comp.os.linux.networking
Link Local Address InuY4sha <riccardomanfrin@email.it> - 2011-09-13 06:59 -0700
Re: Link Local Address Ivan Shmakov <ivan@gray.siamics.net> - 2011-09-13 21:36 +0700
| From | InuY4sha <riccardomanfrin@email.it> |
|---|---|
| Date | 2011-09-13 06:59 -0700 |
| Subject | Link Local Address |
| Message-ID | <3a3e671b-2efd-41f2-9494-4e1c71936b1b@glegroupsg2000goo.googlegroups.com> |
Can a Link Local Address be routable? What ISO/OSI layer is a Link Local Address bounded to? L2 or L3? Thanks
[toc] | [next] | [standalone]
| From | Ivan Shmakov <ivan@gray.siamics.net> |
|---|---|
| Date | 2011-09-13 21:36 +0700 |
| Message-ID | <86zki8v797.fsf@gray.siamics.net> |
| In reply to | #581 |
>>>>> InuY4sha <riccardomanfrin@email.it> writes: > Can a Link Local Address be routable? What ISO/OSI layer is a Link > Local Address bounded to? L2 or L3? Why this question sounds like a homework assignment, I wonder? For the second part, a shared-media link layer (such as Ethernet, even though it's more point-to-point these days) generally employs some kind of addressing: as all the nodes receive the message sent (the media is shared, remember?), there has to be a way for the receiving node to determine whether the message is targeted at it. However, as the link layer has no knowledge whatsoever about anything beyond its own link, the only addresses it may ever get are the link local ones. On the other hand, the /network/ layer covers a /network/ of multiple links. It may, however, for some specific needs (such as autoconfiguration) have to use some kind of “generic”, predefined addresses, whose scope we, however, have to limit to a specific link. To distinguish these addresses from the network-wide addresses (which are the ones we've introduced the network layer for in the first place) we call them “link local.” As for the routing, it's sometimes stated that the network level addresses are introduced to uniquely name all the nodes in the network. It's not quite true — the Media Access Control sublayer addresses (as per Ethernet) are already sufficiently unique; and, IPv6 link local (and, sometimes, global) addresses are derived from them. Think, however, of what a kind of routing table it will require to support forwarding to such addresses at the scale of Internet. Hopefully, this will allow you to attain the enlightment. -- FSF associate member #7257 Coming soon: Software Freedom Day http://mail.sf-day.org/lists/listinfo/ planning-ru (ru), sfd-discuss (en)
[toc] | [prev] | [standalone]
Back to top | Article view | comp.os.linux.networking
csiph-web