not bound port listening












0














Here is what netstat shows:



Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode      PID/Program name    

tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 0 17668 -

udp 0 0 0.0.0.0:68 0.0.0.0:* 0 22969 -


I do not have any PID nor program name related to local port 631 and 68; how do I stop these ports from listening? Does this allow tunnels to be created or is this could be the result of previously created tunnels?



regarding ipv6:



tcp6       0      0 ::1:631                 :::*                    LISTEN      0          17667      -   


I do not want Ipv6, but doing the following does not change what I see above :



echo 'net.ipv6.conf.all.disable_ipv6 = 1' >> /etc/sysctl.conf

echo 'net.ipv6.conf.default.disable_ipv6 = 1' >> /etc/sysctl.conf

echo 'net.ipv6.conf.lo.disable_ipv6 = 1' >> /etc/sysctl.conf

sysctl -p


thankx in advance folks!










share|improve this question






















  • To get process names/PIDs, you need to run netstat as root.
    – Daniel B
    Dec 13 at 10:49
















0














Here is what netstat shows:



Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode      PID/Program name    

tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 0 17668 -

udp 0 0 0.0.0.0:68 0.0.0.0:* 0 22969 -


I do not have any PID nor program name related to local port 631 and 68; how do I stop these ports from listening? Does this allow tunnels to be created or is this could be the result of previously created tunnels?



regarding ipv6:



tcp6       0      0 ::1:631                 :::*                    LISTEN      0          17667      -   


I do not want Ipv6, but doing the following does not change what I see above :



echo 'net.ipv6.conf.all.disable_ipv6 = 1' >> /etc/sysctl.conf

echo 'net.ipv6.conf.default.disable_ipv6 = 1' >> /etc/sysctl.conf

echo 'net.ipv6.conf.lo.disable_ipv6 = 1' >> /etc/sysctl.conf

sysctl -p


thankx in advance folks!










share|improve this question






















  • To get process names/PIDs, you need to run netstat as root.
    – Daniel B
    Dec 13 at 10:49














0












0








0







Here is what netstat shows:



Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode      PID/Program name    

tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 0 17668 -

udp 0 0 0.0.0.0:68 0.0.0.0:* 0 22969 -


I do not have any PID nor program name related to local port 631 and 68; how do I stop these ports from listening? Does this allow tunnels to be created or is this could be the result of previously created tunnels?



regarding ipv6:



tcp6       0      0 ::1:631                 :::*                    LISTEN      0          17667      -   


I do not want Ipv6, but doing the following does not change what I see above :



echo 'net.ipv6.conf.all.disable_ipv6 = 1' >> /etc/sysctl.conf

echo 'net.ipv6.conf.default.disable_ipv6 = 1' >> /etc/sysctl.conf

echo 'net.ipv6.conf.lo.disable_ipv6 = 1' >> /etc/sysctl.conf

sysctl -p


thankx in advance folks!










share|improve this question













Here is what netstat shows:



Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode      PID/Program name    

tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 0 17668 -

udp 0 0 0.0.0.0:68 0.0.0.0:* 0 22969 -


I do not have any PID nor program name related to local port 631 and 68; how do I stop these ports from listening? Does this allow tunnels to be created or is this could be the result of previously created tunnels?



regarding ipv6:



tcp6       0      0 ::1:631                 :::*                    LISTEN      0          17667      -   


I do not want Ipv6, but doing the following does not change what I see above :



echo 'net.ipv6.conf.all.disable_ipv6 = 1' >> /etc/sysctl.conf

echo 'net.ipv6.conf.default.disable_ipv6 = 1' >> /etc/sysctl.conf

echo 'net.ipv6.conf.lo.disable_ipv6 = 1' >> /etc/sysctl.conf

sysctl -p


thankx in advance folks!







networking netstat






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Dec 13 at 10:29









achille

31




31












  • To get process names/PIDs, you need to run netstat as root.
    – Daniel B
    Dec 13 at 10:49


















  • To get process names/PIDs, you need to run netstat as root.
    – Daniel B
    Dec 13 at 10:49
















To get process names/PIDs, you need to run netstat as root.
– Daniel B
Dec 13 at 10:49




To get process names/PIDs, you need to run netstat as root.
– Daniel B
Dec 13 at 10:49










1 Answer
1






active

oldest

votes


















0














UDP/68 is easy: That's the DHCP client



TCP/631 is no problem as well:




  • First of all it's bound to localhost only, so not reachable from the network

  • Secondly it's most likely CUPS (which you can check by stopping it), so an easy but propable explanation exists as well.






share|improve this answer





















  • -@Eugen: how would it appear if it was reachable from outside network?
    – achille
    Dec 13 at 11:14












  • See the "Local Address" column: 127.x.x.x (most often 127.0.0.1) is the loopback network, it provides a network connection only from a host to itself.
    – Eugen Rieck
    Dec 13 at 12:44











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%2f1383256%2fnot-bound-port-listening%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









0














UDP/68 is easy: That's the DHCP client



TCP/631 is no problem as well:




  • First of all it's bound to localhost only, so not reachable from the network

  • Secondly it's most likely CUPS (which you can check by stopping it), so an easy but propable explanation exists as well.






share|improve this answer





















  • -@Eugen: how would it appear if it was reachable from outside network?
    – achille
    Dec 13 at 11:14












  • See the "Local Address" column: 127.x.x.x (most often 127.0.0.1) is the loopback network, it provides a network connection only from a host to itself.
    – Eugen Rieck
    Dec 13 at 12:44
















0














UDP/68 is easy: That's the DHCP client



TCP/631 is no problem as well:




  • First of all it's bound to localhost only, so not reachable from the network

  • Secondly it's most likely CUPS (which you can check by stopping it), so an easy but propable explanation exists as well.






share|improve this answer





















  • -@Eugen: how would it appear if it was reachable from outside network?
    – achille
    Dec 13 at 11:14












  • See the "Local Address" column: 127.x.x.x (most often 127.0.0.1) is the loopback network, it provides a network connection only from a host to itself.
    – Eugen Rieck
    Dec 13 at 12:44














0












0








0






UDP/68 is easy: That's the DHCP client



TCP/631 is no problem as well:




  • First of all it's bound to localhost only, so not reachable from the network

  • Secondly it's most likely CUPS (which you can check by stopping it), so an easy but propable explanation exists as well.






share|improve this answer












UDP/68 is easy: That's the DHCP client



TCP/631 is no problem as well:




  • First of all it's bound to localhost only, so not reachable from the network

  • Secondly it's most likely CUPS (which you can check by stopping it), so an easy but propable explanation exists as well.







share|improve this answer












share|improve this answer



share|improve this answer










answered Dec 13 at 10:33









Eugen Rieck

9,65022127




9,65022127












  • -@Eugen: how would it appear if it was reachable from outside network?
    – achille
    Dec 13 at 11:14












  • See the "Local Address" column: 127.x.x.x (most often 127.0.0.1) is the loopback network, it provides a network connection only from a host to itself.
    – Eugen Rieck
    Dec 13 at 12:44


















  • -@Eugen: how would it appear if it was reachable from outside network?
    – achille
    Dec 13 at 11:14












  • See the "Local Address" column: 127.x.x.x (most often 127.0.0.1) is the loopback network, it provides a network connection only from a host to itself.
    – Eugen Rieck
    Dec 13 at 12:44
















-@Eugen: how would it appear if it was reachable from outside network?
– achille
Dec 13 at 11:14






-@Eugen: how would it appear if it was reachable from outside network?
– achille
Dec 13 at 11:14














See the "Local Address" column: 127.x.x.x (most often 127.0.0.1) is the loopback network, it provides a network connection only from a host to itself.
– Eugen Rieck
Dec 13 at 12:44




See the "Local Address" column: 127.x.x.x (most often 127.0.0.1) is the loopback network, it provides a network connection only from a host to itself.
– Eugen Rieck
Dec 13 at 12:44


















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%2f1383256%2fnot-bound-port-listening%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

flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

Mangá

 ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕