whitelist 127.0.0.1 on IPSEC Windows
How do we whitelist the localhost 0r 127.0.0.1 on IPSec?
Currently I have two policy.
1. Block All IPs.
2. Permit some IP.
Rule number 1 has blocked localhost IP also.
windows windows-server ipsec
add a comment |
How do we whitelist the localhost 0r 127.0.0.1 on IPSec?
Currently I have two policy.
1. Block All IPs.
2. Permit some IP.
Rule number 1 has blocked localhost IP also.
windows windows-server ipsec
add a comment |
How do we whitelist the localhost 0r 127.0.0.1 on IPSec?
Currently I have two policy.
1. Block All IPs.
2. Permit some IP.
Rule number 1 has blocked localhost IP also.
windows windows-server ipsec
How do we whitelist the localhost 0r 127.0.0.1 on IPSec?
Currently I have two policy.
1. Block All IPs.
2. Permit some IP.
Rule number 1 has blocked localhost IP also.
windows windows-server ipsec
windows windows-server ipsec
asked Jan 25 at 15:02
xyonmexyonme
14
14
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Your deny all rule should always be last in your list, that way your permitted IP rules will be reached first and executed.
Okay let me try. I have created blocked and allowed rules but it did not apply anyhow. because this server has been hacked before ,I am still figuring out why the IPSec did not work on this server while work on others
– xyonme
Jan 25 at 15:11
add a comment |
I found the answer already.
Inputting specific IP address 127.0.0.1 is not doable.
You can use the Add IP wizard on Permit function you have created earlier .
Select A Specific DNS Name -> Input 'localhost'
DNS Name
add a comment |
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
});
}
});
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1398406%2fwhitelist-127-0-0-1-on-ipsec-windows%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Your deny all rule should always be last in your list, that way your permitted IP rules will be reached first and executed.
Okay let me try. I have created blocked and allowed rules but it did not apply anyhow. because this server has been hacked before ,I am still figuring out why the IPSec did not work on this server while work on others
– xyonme
Jan 25 at 15:11
add a comment |
Your deny all rule should always be last in your list, that way your permitted IP rules will be reached first and executed.
Okay let me try. I have created blocked and allowed rules but it did not apply anyhow. because this server has been hacked before ,I am still figuring out why the IPSec did not work on this server while work on others
– xyonme
Jan 25 at 15:11
add a comment |
Your deny all rule should always be last in your list, that way your permitted IP rules will be reached first and executed.
Your deny all rule should always be last in your list, that way your permitted IP rules will be reached first and executed.
answered Jan 25 at 15:05
Rory AlsopRory Alsop
3,0571530
3,0571530
Okay let me try. I have created blocked and allowed rules but it did not apply anyhow. because this server has been hacked before ,I am still figuring out why the IPSec did not work on this server while work on others
– xyonme
Jan 25 at 15:11
add a comment |
Okay let me try. I have created blocked and allowed rules but it did not apply anyhow. because this server has been hacked before ,I am still figuring out why the IPSec did not work on this server while work on others
– xyonme
Jan 25 at 15:11
Okay let me try. I have created blocked and allowed rules but it did not apply anyhow. because this server has been hacked before ,I am still figuring out why the IPSec did not work on this server while work on others
– xyonme
Jan 25 at 15:11
Okay let me try. I have created blocked and allowed rules but it did not apply anyhow. because this server has been hacked before ,I am still figuring out why the IPSec did not work on this server while work on others
– xyonme
Jan 25 at 15:11
add a comment |
I found the answer already.
Inputting specific IP address 127.0.0.1 is not doable.
You can use the Add IP wizard on Permit function you have created earlier .
Select A Specific DNS Name -> Input 'localhost'
DNS Name
add a comment |
I found the answer already.
Inputting specific IP address 127.0.0.1 is not doable.
You can use the Add IP wizard on Permit function you have created earlier .
Select A Specific DNS Name -> Input 'localhost'
DNS Name
add a comment |
I found the answer already.
Inputting specific IP address 127.0.0.1 is not doable.
You can use the Add IP wizard on Permit function you have created earlier .
Select A Specific DNS Name -> Input 'localhost'
DNS Name
I found the answer already.
Inputting specific IP address 127.0.0.1 is not doable.
You can use the Add IP wizard on Permit function you have created earlier .
Select A Specific DNS Name -> Input 'localhost'
DNS Name
answered Jan 25 at 15:09
xyonmexyonme
14
14
add a comment |
add a comment |
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.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1398406%2fwhitelist-127-0-0-1-on-ipsec-windows%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
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