Talk:Solicited-node multicast address
This is the talk page for discussing improvements to the Solicited-node multicast address article. This is not a forum for general discussion of the article's subject. |
Article policies
|
Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
This article is rated Start-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||
|
I think that at this point, the page has been reworked by someone who knows what they are doing. Maybe it's time to remove that notice. I believe the information is accurate. One might want to see more context, but there is a link to neighbor discovery for more context (I didn't look at the neighbor discover page). Hrob (talk) 23:07, 17 November 2014 (UTC)
i am curious what is wrong with the title, a solicited node multi-cast addresses is what it is called, and its very important to know how to compute this to make sure a device is computing it correctly :) Seanx820 (talk) 20:32, 30 November 2010 (UTC)
- To what are you referring? Go to where you received a message stating that the title is inappropriate and ask that editor to explain further. Cindamuse (talk) 21:35, 30 November 2010 (UTC)
comparing to ipv4 and arp
editi'm wondering about the statement that arp sends a ip broadcast (255.255.255.255). maybe someone can explain this use case of arp to me. i think it's not right to say that in this section of the article. — Preceding unsigned comment added by 217.67.103.216 (talk) 11:36, 9 May 2012 (UTC)
I agree that the ARP comparison belongs in the neighbor discovery section.Hrob (talk) 23:07, 17 November 2014 (UTC)
Error: You can not route packets to an fe80:: address(IPv6)
editThe example of generating an address should emphasize that the fe80 address is a link local address, only visible on the local network. fe80:* addresses (on the local network, obviously) can be pinged with the ping6 command if you specify the interface which shall be used, like e.g.
ping6 -I eth1 fe80::240:95ff:3f30:9fc4
You can not use this address for a global multicast as far as I know. I am working on this and will return with a definitive information. --d-axel (talk) 21:32, 6 June 2012 (UTC)
That is true; although, it doesn't make the page wrong, it's just not the best choice for an example (because if one is experimenting with this, one will have to use extra arguments to get the correct interface and the way to do that is system dependent).Hrob (talk) 23:07, 17 November 2014 (UTC)
What is this kind of address good for?
editAfter reading this article, I know how the "Solicited-node multicast address" is computed, but I still have no idea why one needs one, or how it is used.
- Solicited-Node multicast addresses are used in Neighbor Discovery Protocol for obtaining the layer 2 link-layer addresses of other nodes.
How is it used? -- Paul Ebermann (talk) 20:58, 4 February 2016 (UTC)