Does Windows Firewall block ICMPv6 by default?












5














After a long struggle trying to establish IPv6 connectivity with Windows box (and failing) I noticed that Windows Firewall blocks a lot of ICMPv6 packets. Closest predefined rule I could find does allow ICMPv6, but only for Local network connections, which is too limited compared to recommendations from rfc4890 dated "May 2007" (which is way before Windows 7 was released).



Of course I did expand that rule to Any as well as tried adding separate ICMPv6 rule — both successful independently. It does a little difference for usual network activity, but gives a huge benefit for tunnelled connections (IPv6 tunnelled over IPv4 for P2P IPv6 direct connections for instance), which hardly operate otherwise.



Am I missing something here or getting it wrong?



If that is "by design", what is the point in limiting this rule to Local network by default contrary to recommendations?










share|improve this question
























  • Even if this question has no answer it might serve a reference for anyone, encountering such a behaviour of Windows.
    – PF4Public
    Sep 4 '17 at 18:41
















5














After a long struggle trying to establish IPv6 connectivity with Windows box (and failing) I noticed that Windows Firewall blocks a lot of ICMPv6 packets. Closest predefined rule I could find does allow ICMPv6, but only for Local network connections, which is too limited compared to recommendations from rfc4890 dated "May 2007" (which is way before Windows 7 was released).



Of course I did expand that rule to Any as well as tried adding separate ICMPv6 rule — both successful independently. It does a little difference for usual network activity, but gives a huge benefit for tunnelled connections (IPv6 tunnelled over IPv4 for P2P IPv6 direct connections for instance), which hardly operate otherwise.



Am I missing something here or getting it wrong?



If that is "by design", what is the point in limiting this rule to Local network by default contrary to recommendations?










share|improve this question
























  • Even if this question has no answer it might serve a reference for anyone, encountering such a behaviour of Windows.
    – PF4Public
    Sep 4 '17 at 18:41














5












5








5







After a long struggle trying to establish IPv6 connectivity with Windows box (and failing) I noticed that Windows Firewall blocks a lot of ICMPv6 packets. Closest predefined rule I could find does allow ICMPv6, but only for Local network connections, which is too limited compared to recommendations from rfc4890 dated "May 2007" (which is way before Windows 7 was released).



Of course I did expand that rule to Any as well as tried adding separate ICMPv6 rule — both successful independently. It does a little difference for usual network activity, but gives a huge benefit for tunnelled connections (IPv6 tunnelled over IPv4 for P2P IPv6 direct connections for instance), which hardly operate otherwise.



Am I missing something here or getting it wrong?



If that is "by design", what is the point in limiting this rule to Local network by default contrary to recommendations?










share|improve this question















After a long struggle trying to establish IPv6 connectivity with Windows box (and failing) I noticed that Windows Firewall blocks a lot of ICMPv6 packets. Closest predefined rule I could find does allow ICMPv6, but only for Local network connections, which is too limited compared to recommendations from rfc4890 dated "May 2007" (which is way before Windows 7 was released).



Of course I did expand that rule to Any as well as tried adding separate ICMPv6 rule — both successful independently. It does a little difference for usual network activity, but gives a huge benefit for tunnelled connections (IPv6 tunnelled over IPv4 for P2P IPv6 direct connections for instance), which hardly operate otherwise.



Am I missing something here or getting it wrong?



If that is "by design", what is the point in limiting this rule to Local network by default contrary to recommendations?







networking ipv6 windows-firewall






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jul 8 '17 at 21:27

























asked Jun 17 '17 at 3:43









PF4Public

1878




1878












  • Even if this question has no answer it might serve a reference for anyone, encountering such a behaviour of Windows.
    – PF4Public
    Sep 4 '17 at 18:41


















  • Even if this question has no answer it might serve a reference for anyone, encountering such a behaviour of Windows.
    – PF4Public
    Sep 4 '17 at 18:41
















Even if this question has no answer it might serve a reference for anyone, encountering such a behaviour of Windows.
– PF4Public
Sep 4 '17 at 18:41




Even if this question has no answer it might serve a reference for anyone, encountering such a behaviour of Windows.
– PF4Public
Sep 4 '17 at 18:41










1 Answer
1






active

oldest

votes


















1














Yes. You need to explicitly create a new custom inbound rule that passes ICMPv6 for the needed needed interface and network type. It's rather easy to do:



Passing ICMPv6 on Windows Defender Firewall






share|improve this answer





















  • Unfortunately, you seem to just rephrase the quote from the question itself: Of course I did expand that rule to Any as well as tried adding separate ICMPv6 rule — both successful independently. Given that this information is already present in question, what additional knowledge does your answer provide?
    – PF4Public
    Aug 4 at 9:33











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1220171%2fdoes-windows-firewall-block-icmpv6-by-default%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









1














Yes. You need to explicitly create a new custom inbound rule that passes ICMPv6 for the needed needed interface and network type. It's rather easy to do:



Passing ICMPv6 on Windows Defender Firewall






share|improve this answer





















  • Unfortunately, you seem to just rephrase the quote from the question itself: Of course I did expand that rule to Any as well as tried adding separate ICMPv6 rule — both successful independently. Given that this information is already present in question, what additional knowledge does your answer provide?
    – PF4Public
    Aug 4 at 9:33
















1














Yes. You need to explicitly create a new custom inbound rule that passes ICMPv6 for the needed needed interface and network type. It's rather easy to do:



Passing ICMPv6 on Windows Defender Firewall






share|improve this answer





















  • Unfortunately, you seem to just rephrase the quote from the question itself: Of course I did expand that rule to Any as well as tried adding separate ICMPv6 rule — both successful independently. Given that this information is already present in question, what additional knowledge does your answer provide?
    – PF4Public
    Aug 4 at 9:33














1












1








1






Yes. You need to explicitly create a new custom inbound rule that passes ICMPv6 for the needed needed interface and network type. It's rather easy to do:



Passing ICMPv6 on Windows Defender Firewall






share|improve this answer












Yes. You need to explicitly create a new custom inbound rule that passes ICMPv6 for the needed needed interface and network type. It's rather easy to do:



Passing ICMPv6 on Windows Defender Firewall







share|improve this answer












share|improve this answer



share|improve this answer










answered Aug 2 at 16:46









bviktor

46243




46243












  • Unfortunately, you seem to just rephrase the quote from the question itself: Of course I did expand that rule to Any as well as tried adding separate ICMPv6 rule — both successful independently. Given that this information is already present in question, what additional knowledge does your answer provide?
    – PF4Public
    Aug 4 at 9:33


















  • Unfortunately, you seem to just rephrase the quote from the question itself: Of course I did expand that rule to Any as well as tried adding separate ICMPv6 rule — both successful independently. Given that this information is already present in question, what additional knowledge does your answer provide?
    – PF4Public
    Aug 4 at 9:33
















Unfortunately, you seem to just rephrase the quote from the question itself: Of course I did expand that rule to Any as well as tried adding separate ICMPv6 rule — both successful independently. Given that this information is already present in question, what additional knowledge does your answer provide?
– PF4Public
Aug 4 at 9:33




Unfortunately, you seem to just rephrase the quote from the question itself: Of course I did expand that rule to Any as well as tried adding separate ICMPv6 rule — both successful independently. Given that this information is already present in question, what additional knowledge does your answer provide?
– PF4Public
Aug 4 at 9:33


















draft saved

draft discarded




















































Thanks for contributing an answer to Super User!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1220171%2fdoes-windows-firewall-block-icmpv6-by-default%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Index of /

Tribalistas

Listed building