Windows Firewall - difference between disable and âblockâ

Clash Royale CLAN TAG#URR8PPP
up vote
2
down vote
favorite
In "Windows Firewall with advanced security", what is the difference between disabling a rule and setting it to "block traffic"?
Besides knowing the difference, in my case I want to diminish the system vulnerability to exploits by keeping open only the minimal ports that I need. For that, would it make a difference if I use block or disable?
windows firewall windows-firewall
add a comment |Â
up vote
2
down vote
favorite
In "Windows Firewall with advanced security", what is the difference between disabling a rule and setting it to "block traffic"?
Besides knowing the difference, in my case I want to diminish the system vulnerability to exploits by keeping open only the minimal ports that I need. For that, would it make a difference if I use block or disable?
windows firewall windows-firewall
add a comment |Â
up vote
2
down vote
favorite
up vote
2
down vote
favorite
In "Windows Firewall with advanced security", what is the difference between disabling a rule and setting it to "block traffic"?
Besides knowing the difference, in my case I want to diminish the system vulnerability to exploits by keeping open only the minimal ports that I need. For that, would it make a difference if I use block or disable?
windows firewall windows-firewall
In "Windows Firewall with advanced security", what is the difference between disabling a rule and setting it to "block traffic"?
Besides knowing the difference, in my case I want to diminish the system vulnerability to exploits by keeping open only the minimal ports that I need. For that, would it make a difference if I use block or disable?
windows firewall windows-firewall
asked Aug 22 at 22:14
msb
1691114
1691114
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
4
down vote
Disabling a rule means that the rule will no longer take effect. The block action refers to the behaviour of the rule itself...that is should it allow or block the traffic matched by that rule.
So for example you can have a block rule that is preventing traffic, but you may want to temporarily allow that traffic for testing or other purposes, so you can select that rule and then disable it. Then if you want to reactivate the rule you can enable it again.
As Ryan says below. Another concept that might help you understand is "default behavior" of inbound versus outbound rules. By default, Windows Firewall is configured to block incoming traffic by default, and allow outgoing traffic by default. So a "Block" rule typically isn't needed for inbound traffic, but you might want it if you're specifically targeting outbound traffic. Depends on the context.
1
Another concept that might help you understand is "default behavior" of inbound versus outbound rules. By default, Windows Firewall is configured to block incoming traffic by default, and allow outgoing traffic by default. So a "Block" rule typically isn't needed for inbound traffic, but you might want it if you're specifically targeting outbound traffic. Depends on the context.
â Ryan Ries
Aug 23 at 0:18
Thanks Ryan, and Alex. Just based on Alex' reply I was still not sure about the behaviour, but I understand your both comments combined. :-) @Alex if you incorporate the comment of the general inbound/outbout rule, I can accept it. ^_^
â msb
Aug 23 at 0:24
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
4
down vote
Disabling a rule means that the rule will no longer take effect. The block action refers to the behaviour of the rule itself...that is should it allow or block the traffic matched by that rule.
So for example you can have a block rule that is preventing traffic, but you may want to temporarily allow that traffic for testing or other purposes, so you can select that rule and then disable it. Then if you want to reactivate the rule you can enable it again.
As Ryan says below. Another concept that might help you understand is "default behavior" of inbound versus outbound rules. By default, Windows Firewall is configured to block incoming traffic by default, and allow outgoing traffic by default. So a "Block" rule typically isn't needed for inbound traffic, but you might want it if you're specifically targeting outbound traffic. Depends on the context.
1
Another concept that might help you understand is "default behavior" of inbound versus outbound rules. By default, Windows Firewall is configured to block incoming traffic by default, and allow outgoing traffic by default. So a "Block" rule typically isn't needed for inbound traffic, but you might want it if you're specifically targeting outbound traffic. Depends on the context.
â Ryan Ries
Aug 23 at 0:18
Thanks Ryan, and Alex. Just based on Alex' reply I was still not sure about the behaviour, but I understand your both comments combined. :-) @Alex if you incorporate the comment of the general inbound/outbout rule, I can accept it. ^_^
â msb
Aug 23 at 0:24
add a comment |Â
up vote
4
down vote
Disabling a rule means that the rule will no longer take effect. The block action refers to the behaviour of the rule itself...that is should it allow or block the traffic matched by that rule.
So for example you can have a block rule that is preventing traffic, but you may want to temporarily allow that traffic for testing or other purposes, so you can select that rule and then disable it. Then if you want to reactivate the rule you can enable it again.
As Ryan says below. Another concept that might help you understand is "default behavior" of inbound versus outbound rules. By default, Windows Firewall is configured to block incoming traffic by default, and allow outgoing traffic by default. So a "Block" rule typically isn't needed for inbound traffic, but you might want it if you're specifically targeting outbound traffic. Depends on the context.
1
Another concept that might help you understand is "default behavior" of inbound versus outbound rules. By default, Windows Firewall is configured to block incoming traffic by default, and allow outgoing traffic by default. So a "Block" rule typically isn't needed for inbound traffic, but you might want it if you're specifically targeting outbound traffic. Depends on the context.
â Ryan Ries
Aug 23 at 0:18
Thanks Ryan, and Alex. Just based on Alex' reply I was still not sure about the behaviour, but I understand your both comments combined. :-) @Alex if you incorporate the comment of the general inbound/outbout rule, I can accept it. ^_^
â msb
Aug 23 at 0:24
add a comment |Â
up vote
4
down vote
up vote
4
down vote
Disabling a rule means that the rule will no longer take effect. The block action refers to the behaviour of the rule itself...that is should it allow or block the traffic matched by that rule.
So for example you can have a block rule that is preventing traffic, but you may want to temporarily allow that traffic for testing or other purposes, so you can select that rule and then disable it. Then if you want to reactivate the rule you can enable it again.
As Ryan says below. Another concept that might help you understand is "default behavior" of inbound versus outbound rules. By default, Windows Firewall is configured to block incoming traffic by default, and allow outgoing traffic by default. So a "Block" rule typically isn't needed for inbound traffic, but you might want it if you're specifically targeting outbound traffic. Depends on the context.
Disabling a rule means that the rule will no longer take effect. The block action refers to the behaviour of the rule itself...that is should it allow or block the traffic matched by that rule.
So for example you can have a block rule that is preventing traffic, but you may want to temporarily allow that traffic for testing or other purposes, so you can select that rule and then disable it. Then if you want to reactivate the rule you can enable it again.
As Ryan says below. Another concept that might help you understand is "default behavior" of inbound versus outbound rules. By default, Windows Firewall is configured to block incoming traffic by default, and allow outgoing traffic by default. So a "Block" rule typically isn't needed for inbound traffic, but you might want it if you're specifically targeting outbound traffic. Depends on the context.
edited Aug 23 at 5:51
answered Aug 22 at 23:30
Alex Moore
4496
4496
1
Another concept that might help you understand is "default behavior" of inbound versus outbound rules. By default, Windows Firewall is configured to block incoming traffic by default, and allow outgoing traffic by default. So a "Block" rule typically isn't needed for inbound traffic, but you might want it if you're specifically targeting outbound traffic. Depends on the context.
â Ryan Ries
Aug 23 at 0:18
Thanks Ryan, and Alex. Just based on Alex' reply I was still not sure about the behaviour, but I understand your both comments combined. :-) @Alex if you incorporate the comment of the general inbound/outbout rule, I can accept it. ^_^
â msb
Aug 23 at 0:24
add a comment |Â
1
Another concept that might help you understand is "default behavior" of inbound versus outbound rules. By default, Windows Firewall is configured to block incoming traffic by default, and allow outgoing traffic by default. So a "Block" rule typically isn't needed for inbound traffic, but you might want it if you're specifically targeting outbound traffic. Depends on the context.
â Ryan Ries
Aug 23 at 0:18
Thanks Ryan, and Alex. Just based on Alex' reply I was still not sure about the behaviour, but I understand your both comments combined. :-) @Alex if you incorporate the comment of the general inbound/outbout rule, I can accept it. ^_^
â msb
Aug 23 at 0:24
1
1
Another concept that might help you understand is "default behavior" of inbound versus outbound rules. By default, Windows Firewall is configured to block incoming traffic by default, and allow outgoing traffic by default. So a "Block" rule typically isn't needed for inbound traffic, but you might want it if you're specifically targeting outbound traffic. Depends on the context.
â Ryan Ries
Aug 23 at 0:18
Another concept that might help you understand is "default behavior" of inbound versus outbound rules. By default, Windows Firewall is configured to block incoming traffic by default, and allow outgoing traffic by default. So a "Block" rule typically isn't needed for inbound traffic, but you might want it if you're specifically targeting outbound traffic. Depends on the context.
â Ryan Ries
Aug 23 at 0:18
Thanks Ryan, and Alex. Just based on Alex' reply I was still not sure about the behaviour, but I understand your both comments combined. :-) @Alex if you incorporate the comment of the general inbound/outbout rule, I can accept it. ^_^
â msb
Aug 23 at 0:24
Thanks Ryan, and Alex. Just based on Alex' reply I was still not sure about the behaviour, but I understand your both comments combined. :-) @Alex if you incorporate the comment of the general inbound/outbout rule, I can accept it. ^_^
â msb
Aug 23 at 0:24
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f927583%2fwindows-firewall-difference-between-disable-and-block%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password