Can't block certain port on my linux server
I'm trying to block my server from getting requests on port 8001.
I ran sudo iptables -A INPUT -p tcp --dport 8001 -j DROP
, then I ran netstat -nlp
to see if the port is still listening.
The output was:
will not be shown, you would have to be root to see it all.)
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:8000 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:8001 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:10050 0.0.0.0:* LISTEN -
tcp6 0 0 :::22 :::* LISTEN -
tcp6 0 0 :::7777 :::* LISTEN 1173/node
tcp6 0 0 :::10050 :::* LISTEN -
udp 0 0 0.0.0.0:39192 0.0.0.0:* -
udp 0 0 0.0.0.0:68 0.0.0.0:* -
It's seems that the port is still open and listening to requests.
How can I close it?
iptables
add a comment |
I'm trying to block my server from getting requests on port 8001.
I ran sudo iptables -A INPUT -p tcp --dport 8001 -j DROP
, then I ran netstat -nlp
to see if the port is still listening.
The output was:
will not be shown, you would have to be root to see it all.)
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:8000 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:8001 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:10050 0.0.0.0:* LISTEN -
tcp6 0 0 :::22 :::* LISTEN -
tcp6 0 0 :::7777 :::* LISTEN 1173/node
tcp6 0 0 :::10050 :::* LISTEN -
udp 0 0 0.0.0.0:39192 0.0.0.0:* -
udp 0 0 0.0.0.0:68 0.0.0.0:* -
It's seems that the port is still open and listening to requests.
How can I close it?
iptables
add a comment |
I'm trying to block my server from getting requests on port 8001.
I ran sudo iptables -A INPUT -p tcp --dport 8001 -j DROP
, then I ran netstat -nlp
to see if the port is still listening.
The output was:
will not be shown, you would have to be root to see it all.)
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:8000 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:8001 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:10050 0.0.0.0:* LISTEN -
tcp6 0 0 :::22 :::* LISTEN -
tcp6 0 0 :::7777 :::* LISTEN 1173/node
tcp6 0 0 :::10050 :::* LISTEN -
udp 0 0 0.0.0.0:39192 0.0.0.0:* -
udp 0 0 0.0.0.0:68 0.0.0.0:* -
It's seems that the port is still open and listening to requests.
How can I close it?
iptables
I'm trying to block my server from getting requests on port 8001.
I ran sudo iptables -A INPUT -p tcp --dport 8001 -j DROP
, then I ran netstat -nlp
to see if the port is still listening.
The output was:
will not be shown, you would have to be root to see it all.)
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:8000 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:8001 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:10050 0.0.0.0:* LISTEN -
tcp6 0 0 :::22 :::* LISTEN -
tcp6 0 0 :::7777 :::* LISTEN 1173/node
tcp6 0 0 :::10050 :::* LISTEN -
udp 0 0 0.0.0.0:39192 0.0.0.0:* -
udp 0 0 0.0.0.0:68 0.0.0.0:* -
It's seems that the port is still open and listening to requests.
How can I close it?
iptables
iptables
asked 2 days ago
KeselmeKeselme
1062
1062
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I may be suffering from a misunderstanding (if so, people will tell me!)
iptables
sets up firewall rules, and you have configured the firewall not to pass on items directed to port 8001
netstat
shows ports that programs are listening to
So, your firewall is not allowing port 8001 through, but a program is listening for pings on that port. There is no conflict here - if you want your program not to listen to the port, close the program.
If you are interested in what rules that you have active in the firewall, look at iptables -L
or iptables -S
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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%2faskubuntu.com%2fquestions%2f1114135%2fcant-block-certain-port-on-my-linux-server%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
I may be suffering from a misunderstanding (if so, people will tell me!)
iptables
sets up firewall rules, and you have configured the firewall not to pass on items directed to port 8001
netstat
shows ports that programs are listening to
So, your firewall is not allowing port 8001 through, but a program is listening for pings on that port. There is no conflict here - if you want your program not to listen to the port, close the program.
If you are interested in what rules that you have active in the firewall, look at iptables -L
or iptables -S
add a comment |
I may be suffering from a misunderstanding (if so, people will tell me!)
iptables
sets up firewall rules, and you have configured the firewall not to pass on items directed to port 8001
netstat
shows ports that programs are listening to
So, your firewall is not allowing port 8001 through, but a program is listening for pings on that port. There is no conflict here - if you want your program not to listen to the port, close the program.
If you are interested in what rules that you have active in the firewall, look at iptables -L
or iptables -S
add a comment |
I may be suffering from a misunderstanding (if so, people will tell me!)
iptables
sets up firewall rules, and you have configured the firewall not to pass on items directed to port 8001
netstat
shows ports that programs are listening to
So, your firewall is not allowing port 8001 through, but a program is listening for pings on that port. There is no conflict here - if you want your program not to listen to the port, close the program.
If you are interested in what rules that you have active in the firewall, look at iptables -L
or iptables -S
I may be suffering from a misunderstanding (if so, people will tell me!)
iptables
sets up firewall rules, and you have configured the firewall not to pass on items directed to port 8001
netstat
shows ports that programs are listening to
So, your firewall is not allowing port 8001 through, but a program is listening for pings on that port. There is no conflict here - if you want your program not to listen to the port, close the program.
If you are interested in what rules that you have active in the firewall, look at iptables -L
or iptables -S
answered 2 days ago
Charles GreenCharles Green
13.3k73658
13.3k73658
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f1114135%2fcant-block-certain-port-on-my-linux-server%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