Timeline for When is the source address of ICMPv6 message types 133, 135 and 136 other than unspecified(::/128) or link-local(fe80::/10)?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 7, 2021 at 7:34 | history | edited | CommunityBot |
replaced https://tools.ietf.org/html/rfc with https://www.rfc-editor.org/rfc/rfc
|
|
| Mar 3, 2020 at 8:41 | vote | accept | Martin | ||
| Feb 18, 2020 at 15:56 | answer | added | KillianDS | timeline score: 1 | |
| Jan 28, 2020 at 15:22 | comment | added | Ron Maupin♦ | Be sure to also look at RFC 4890, Recommendations for Filtering ICMPv6 Messages in Firewalls. It has some good explanations, and what you should allow seems to shock many people with IPv4 experience. | |
| Jan 28, 2020 at 15:17 | comment | added | Martin | @RonMaupin I meant the firewall which filters the traffic to router control plane, e.g punted traffic. | |
| Jan 28, 2020 at 14:30 | comment | added | Ron Maupin♦ | Remember that packets with Link-Local addressing cannot be routed to a different network, so firewall rules play no part in that because those packets will not pass through a firewall. | |
| Jan 28, 2020 at 10:04 | comment | added | Konstantin Goncharenko | In the most scenarios ICMPv6 uses link-local as source. Of course when device advertises another address from interface, it can uses this one. But if we are talking about firewall rules, we don't need to use source address at all, only ICMP type. | |
| Jan 28, 2020 at 8:19 | history | asked | Martin | CC BY-SA 4.0 |