Netstat doesn't show my machine IP as listening on port 22

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












I am able to ssh to the machine.

But my machine not shown as listening on port 22.

Below is what I see.

It show as listening on port 53, 21, 8080, 8443 etc. But no entry for 22(ssh).

My machine IP is 10.8.113.30. OS is windriver linux.

Why is this?



netstat -antu | grep LISTEN 
tcp 0 0 127.0.0.1:8083 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:8084 0.0.0.0:* LISTEN
tcp 0 0 10.8.113.30:8021 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:8021 0.0.0.0:* LISTEN
tcp 0 0 10.8.113.30:21 0.0.0.0:* LISTEN
tcp 0 0 10.8.113.30:53 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:3128 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN
tcp 0 0 10.8.113.30:8443 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:8123 0.0.0.0:* LISTEN
tcp 0 0 10.8.113.30:8128 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:8128 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:25255 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:5000 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:5001 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:6379 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:5580 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:5581 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN
tcp 0 0 10.8.113.30:8080 0.0.0.0:* LISTEN
tcp 0 0 10.8.113.30:81 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:81 0.0.0.0:* LISTEN
tcp6 0 0 ::1:8021 :::* LISTEN
tcp6 0 0 :::53 :::* LISTEN
tcp6 0 0 :::22 :::* LISTEN
tcp6 0 0 :::3128 :::* LISTEN
tcp6 0 0 ::1:8128 :::* LISTEN
tcp6 0 0 127.0.0.1:18081 :::* LISTEN
tcp6 0 0 :::80 :::* LISTEN
tcp6 0 0 ::1:81 :::* LISTEN






share|improve this question






















  • It's listening on the IPv6 port 22.
    – Kusalananda
    Nov 6 '17 at 10:57










  • On freebsd it used to show the exact IP address. Isn't that the case with linux? Exact IP address would really help. Anyway to get the same?
    – BRT
    Nov 6 '17 at 11:03














up vote
0
down vote

favorite












I am able to ssh to the machine.

But my machine not shown as listening on port 22.

Below is what I see.

It show as listening on port 53, 21, 8080, 8443 etc. But no entry for 22(ssh).

My machine IP is 10.8.113.30. OS is windriver linux.

Why is this?



netstat -antu | grep LISTEN 
tcp 0 0 127.0.0.1:8083 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:8084 0.0.0.0:* LISTEN
tcp 0 0 10.8.113.30:8021 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:8021 0.0.0.0:* LISTEN
tcp 0 0 10.8.113.30:21 0.0.0.0:* LISTEN
tcp 0 0 10.8.113.30:53 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:3128 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN
tcp 0 0 10.8.113.30:8443 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:8123 0.0.0.0:* LISTEN
tcp 0 0 10.8.113.30:8128 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:8128 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:25255 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:5000 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:5001 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:6379 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:5580 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:5581 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN
tcp 0 0 10.8.113.30:8080 0.0.0.0:* LISTEN
tcp 0 0 10.8.113.30:81 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:81 0.0.0.0:* LISTEN
tcp6 0 0 ::1:8021 :::* LISTEN
tcp6 0 0 :::53 :::* LISTEN
tcp6 0 0 :::22 :::* LISTEN
tcp6 0 0 :::3128 :::* LISTEN
tcp6 0 0 ::1:8128 :::* LISTEN
tcp6 0 0 127.0.0.1:18081 :::* LISTEN
tcp6 0 0 :::80 :::* LISTEN
tcp6 0 0 ::1:81 :::* LISTEN






share|improve this question






















  • It's listening on the IPv6 port 22.
    – Kusalananda
    Nov 6 '17 at 10:57










  • On freebsd it used to show the exact IP address. Isn't that the case with linux? Exact IP address would really help. Anyway to get the same?
    – BRT
    Nov 6 '17 at 11:03












up vote
0
down vote

favorite









up vote
0
down vote

favorite











I am able to ssh to the machine.

But my machine not shown as listening on port 22.

Below is what I see.

It show as listening on port 53, 21, 8080, 8443 etc. But no entry for 22(ssh).

My machine IP is 10.8.113.30. OS is windriver linux.

Why is this?



netstat -antu | grep LISTEN 
tcp 0 0 127.0.0.1:8083 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:8084 0.0.0.0:* LISTEN
tcp 0 0 10.8.113.30:8021 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:8021 0.0.0.0:* LISTEN
tcp 0 0 10.8.113.30:21 0.0.0.0:* LISTEN
tcp 0 0 10.8.113.30:53 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:3128 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN
tcp 0 0 10.8.113.30:8443 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:8123 0.0.0.0:* LISTEN
tcp 0 0 10.8.113.30:8128 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:8128 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:25255 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:5000 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:5001 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:6379 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:5580 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:5581 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN
tcp 0 0 10.8.113.30:8080 0.0.0.0:* LISTEN
tcp 0 0 10.8.113.30:81 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:81 0.0.0.0:* LISTEN
tcp6 0 0 ::1:8021 :::* LISTEN
tcp6 0 0 :::53 :::* LISTEN
tcp6 0 0 :::22 :::* LISTEN
tcp6 0 0 :::3128 :::* LISTEN
tcp6 0 0 ::1:8128 :::* LISTEN
tcp6 0 0 127.0.0.1:18081 :::* LISTEN
tcp6 0 0 :::80 :::* LISTEN
tcp6 0 0 ::1:81 :::* LISTEN






share|improve this question














I am able to ssh to the machine.

But my machine not shown as listening on port 22.

Below is what I see.

It show as listening on port 53, 21, 8080, 8443 etc. But no entry for 22(ssh).

My machine IP is 10.8.113.30. OS is windriver linux.

Why is this?



netstat -antu | grep LISTEN 
tcp 0 0 127.0.0.1:8083 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:8084 0.0.0.0:* LISTEN
tcp 0 0 10.8.113.30:8021 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:8021 0.0.0.0:* LISTEN
tcp 0 0 10.8.113.30:21 0.0.0.0:* LISTEN
tcp 0 0 10.8.113.30:53 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:3128 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN
tcp 0 0 10.8.113.30:8443 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:8123 0.0.0.0:* LISTEN
tcp 0 0 10.8.113.30:8128 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:8128 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:25255 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:5000 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:5001 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:6379 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:5580 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:5581 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN
tcp 0 0 10.8.113.30:8080 0.0.0.0:* LISTEN
tcp 0 0 10.8.113.30:81 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:81 0.0.0.0:* LISTEN
tcp6 0 0 ::1:8021 :::* LISTEN
tcp6 0 0 :::53 :::* LISTEN
tcp6 0 0 :::22 :::* LISTEN
tcp6 0 0 :::3128 :::* LISTEN
tcp6 0 0 ::1:8128 :::* LISTEN
tcp6 0 0 127.0.0.1:18081 :::* LISTEN
tcp6 0 0 :::80 :::* LISTEN
tcp6 0 0 ::1:81 :::* LISTEN








share|improve this question













share|improve this question




share|improve this question








edited Nov 6 '17 at 10:56









Kiwy

5,50643352




5,50643352










asked Nov 6 '17 at 10:51









BRT

184




184











  • It's listening on the IPv6 port 22.
    – Kusalananda
    Nov 6 '17 at 10:57










  • On freebsd it used to show the exact IP address. Isn't that the case with linux? Exact IP address would really help. Anyway to get the same?
    – BRT
    Nov 6 '17 at 11:03
















  • It's listening on the IPv6 port 22.
    – Kusalananda
    Nov 6 '17 at 10:57










  • On freebsd it used to show the exact IP address. Isn't that the case with linux? Exact IP address would really help. Anyway to get the same?
    – BRT
    Nov 6 '17 at 11:03















It's listening on the IPv6 port 22.
– Kusalananda
Nov 6 '17 at 10:57




It's listening on the IPv6 port 22.
– Kusalananda
Nov 6 '17 at 10:57












On freebsd it used to show the exact IP address. Isn't that the case with linux? Exact IP address would really help. Anyway to get the same?
– BRT
Nov 6 '17 at 11:03




On freebsd it used to show the exact IP address. Isn't that the case with linux? Exact IP address would really help. Anyway to get the same?
– BRT
Nov 6 '17 at 11:03










1 Answer
1






active

oldest

votes

















up vote
4
down vote



accepted










You machine is listening to port 22. Here's the line:



tcp6 0 0 :::22 :::* LISTEN 


The socket is listening for both IPv6 and IPv4 connections.






share|improve this answer




















  • On freebsd it used to show the exact IP address. Isn't that the case with linux? Exact IP address would really help. Anyway to get the same?
    – BRT
    Nov 6 '17 at 11:02










  • A process can listen on a specific interface address, or it can use INADDR_ANY or INADDR6_ANY, which means is accepts connections on all interfaces. Linux by default listens on both IPV4 and IPv6 connections if INADDR6_ANY (::) is used.
    – Johan Myréen
    Nov 6 '17 at 11:05











  • My idea is to look for interfaces listening on port 22 and establish a ssh tunnel with tunnel server using a particular interface IP. So I am looking for IP address here.. In freebsd I see that we get this info with netstat command - netstat -na -p tcp -f inet | grep LISTEN. Anyways to get the IP on linux too? Also, pointing at your sentence -> "Linux by default listens on both IPV4 and IPv6 connections if INADDR6_ANY (::) is used".. Is it safe to get the ip address from ifconfig's output and use this to establish tunnel as you say that linux by default listens on both IPV4/6"
    – BRT
    Nov 6 '17 at 11:18










  • To listen on a specific address only, you will have to configure the ssh server to listen to that address only. For example, you could put this in /etc/ssh/sshd_config: ListenAddress 10.8.113.30. This forces the ssh server to only listen on that address.
    – Johan Myréen
    Nov 6 '17 at 11:28










  • @BRT: The point is that in this specific case the SSH daemon is not listening on a specific address; it's listening on any address. Poor netstat shows the truth.
    – AlexP
    Nov 6 '17 at 12:00










Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
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',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f402806%2fnetstat-doesnt-show-my-machine-ip-as-listening-on-port-22%23new-answer', 'question_page');

);

Post as a guest






























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
4
down vote



accepted










You machine is listening to port 22. Here's the line:



tcp6 0 0 :::22 :::* LISTEN 


The socket is listening for both IPv6 and IPv4 connections.






share|improve this answer




















  • On freebsd it used to show the exact IP address. Isn't that the case with linux? Exact IP address would really help. Anyway to get the same?
    – BRT
    Nov 6 '17 at 11:02










  • A process can listen on a specific interface address, or it can use INADDR_ANY or INADDR6_ANY, which means is accepts connections on all interfaces. Linux by default listens on both IPV4 and IPv6 connections if INADDR6_ANY (::) is used.
    – Johan Myréen
    Nov 6 '17 at 11:05











  • My idea is to look for interfaces listening on port 22 and establish a ssh tunnel with tunnel server using a particular interface IP. So I am looking for IP address here.. In freebsd I see that we get this info with netstat command - netstat -na -p tcp -f inet | grep LISTEN. Anyways to get the IP on linux too? Also, pointing at your sentence -> "Linux by default listens on both IPV4 and IPv6 connections if INADDR6_ANY (::) is used".. Is it safe to get the ip address from ifconfig's output and use this to establish tunnel as you say that linux by default listens on both IPV4/6"
    – BRT
    Nov 6 '17 at 11:18










  • To listen on a specific address only, you will have to configure the ssh server to listen to that address only. For example, you could put this in /etc/ssh/sshd_config: ListenAddress 10.8.113.30. This forces the ssh server to only listen on that address.
    – Johan Myréen
    Nov 6 '17 at 11:28










  • @BRT: The point is that in this specific case the SSH daemon is not listening on a specific address; it's listening on any address. Poor netstat shows the truth.
    – AlexP
    Nov 6 '17 at 12:00














up vote
4
down vote



accepted










You machine is listening to port 22. Here's the line:



tcp6 0 0 :::22 :::* LISTEN 


The socket is listening for both IPv6 and IPv4 connections.






share|improve this answer




















  • On freebsd it used to show the exact IP address. Isn't that the case with linux? Exact IP address would really help. Anyway to get the same?
    – BRT
    Nov 6 '17 at 11:02










  • A process can listen on a specific interface address, or it can use INADDR_ANY or INADDR6_ANY, which means is accepts connections on all interfaces. Linux by default listens on both IPV4 and IPv6 connections if INADDR6_ANY (::) is used.
    – Johan Myréen
    Nov 6 '17 at 11:05











  • My idea is to look for interfaces listening on port 22 and establish a ssh tunnel with tunnel server using a particular interface IP. So I am looking for IP address here.. In freebsd I see that we get this info with netstat command - netstat -na -p tcp -f inet | grep LISTEN. Anyways to get the IP on linux too? Also, pointing at your sentence -> "Linux by default listens on both IPV4 and IPv6 connections if INADDR6_ANY (::) is used".. Is it safe to get the ip address from ifconfig's output and use this to establish tunnel as you say that linux by default listens on both IPV4/6"
    – BRT
    Nov 6 '17 at 11:18










  • To listen on a specific address only, you will have to configure the ssh server to listen to that address only. For example, you could put this in /etc/ssh/sshd_config: ListenAddress 10.8.113.30. This forces the ssh server to only listen on that address.
    – Johan Myréen
    Nov 6 '17 at 11:28










  • @BRT: The point is that in this specific case the SSH daemon is not listening on a specific address; it's listening on any address. Poor netstat shows the truth.
    – AlexP
    Nov 6 '17 at 12:00












up vote
4
down vote



accepted







up vote
4
down vote



accepted






You machine is listening to port 22. Here's the line:



tcp6 0 0 :::22 :::* LISTEN 


The socket is listening for both IPv6 and IPv4 connections.






share|improve this answer












You machine is listening to port 22. Here's the line:



tcp6 0 0 :::22 :::* LISTEN 


The socket is listening for both IPv6 and IPv4 connections.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 6 '17 at 10:58









Johan Myréen

6,93711322




6,93711322











  • On freebsd it used to show the exact IP address. Isn't that the case with linux? Exact IP address would really help. Anyway to get the same?
    – BRT
    Nov 6 '17 at 11:02










  • A process can listen on a specific interface address, or it can use INADDR_ANY or INADDR6_ANY, which means is accepts connections on all interfaces. Linux by default listens on both IPV4 and IPv6 connections if INADDR6_ANY (::) is used.
    – Johan Myréen
    Nov 6 '17 at 11:05











  • My idea is to look for interfaces listening on port 22 and establish a ssh tunnel with tunnel server using a particular interface IP. So I am looking for IP address here.. In freebsd I see that we get this info with netstat command - netstat -na -p tcp -f inet | grep LISTEN. Anyways to get the IP on linux too? Also, pointing at your sentence -> "Linux by default listens on both IPV4 and IPv6 connections if INADDR6_ANY (::) is used".. Is it safe to get the ip address from ifconfig's output and use this to establish tunnel as you say that linux by default listens on both IPV4/6"
    – BRT
    Nov 6 '17 at 11:18










  • To listen on a specific address only, you will have to configure the ssh server to listen to that address only. For example, you could put this in /etc/ssh/sshd_config: ListenAddress 10.8.113.30. This forces the ssh server to only listen on that address.
    – Johan Myréen
    Nov 6 '17 at 11:28










  • @BRT: The point is that in this specific case the SSH daemon is not listening on a specific address; it's listening on any address. Poor netstat shows the truth.
    – AlexP
    Nov 6 '17 at 12:00
















  • On freebsd it used to show the exact IP address. Isn't that the case with linux? Exact IP address would really help. Anyway to get the same?
    – BRT
    Nov 6 '17 at 11:02










  • A process can listen on a specific interface address, or it can use INADDR_ANY or INADDR6_ANY, which means is accepts connections on all interfaces. Linux by default listens on both IPV4 and IPv6 connections if INADDR6_ANY (::) is used.
    – Johan Myréen
    Nov 6 '17 at 11:05











  • My idea is to look for interfaces listening on port 22 and establish a ssh tunnel with tunnel server using a particular interface IP. So I am looking for IP address here.. In freebsd I see that we get this info with netstat command - netstat -na -p tcp -f inet | grep LISTEN. Anyways to get the IP on linux too? Also, pointing at your sentence -> "Linux by default listens on both IPV4 and IPv6 connections if INADDR6_ANY (::) is used".. Is it safe to get the ip address from ifconfig's output and use this to establish tunnel as you say that linux by default listens on both IPV4/6"
    – BRT
    Nov 6 '17 at 11:18










  • To listen on a specific address only, you will have to configure the ssh server to listen to that address only. For example, you could put this in /etc/ssh/sshd_config: ListenAddress 10.8.113.30. This forces the ssh server to only listen on that address.
    – Johan Myréen
    Nov 6 '17 at 11:28










  • @BRT: The point is that in this specific case the SSH daemon is not listening on a specific address; it's listening on any address. Poor netstat shows the truth.
    – AlexP
    Nov 6 '17 at 12:00















On freebsd it used to show the exact IP address. Isn't that the case with linux? Exact IP address would really help. Anyway to get the same?
– BRT
Nov 6 '17 at 11:02




On freebsd it used to show the exact IP address. Isn't that the case with linux? Exact IP address would really help. Anyway to get the same?
– BRT
Nov 6 '17 at 11:02












A process can listen on a specific interface address, or it can use INADDR_ANY or INADDR6_ANY, which means is accepts connections on all interfaces. Linux by default listens on both IPV4 and IPv6 connections if INADDR6_ANY (::) is used.
– Johan Myréen
Nov 6 '17 at 11:05





A process can listen on a specific interface address, or it can use INADDR_ANY or INADDR6_ANY, which means is accepts connections on all interfaces. Linux by default listens on both IPV4 and IPv6 connections if INADDR6_ANY (::) is used.
– Johan Myréen
Nov 6 '17 at 11:05













My idea is to look for interfaces listening on port 22 and establish a ssh tunnel with tunnel server using a particular interface IP. So I am looking for IP address here.. In freebsd I see that we get this info with netstat command - netstat -na -p tcp -f inet | grep LISTEN. Anyways to get the IP on linux too? Also, pointing at your sentence -> "Linux by default listens on both IPV4 and IPv6 connections if INADDR6_ANY (::) is used".. Is it safe to get the ip address from ifconfig's output and use this to establish tunnel as you say that linux by default listens on both IPV4/6"
– BRT
Nov 6 '17 at 11:18




My idea is to look for interfaces listening on port 22 and establish a ssh tunnel with tunnel server using a particular interface IP. So I am looking for IP address here.. In freebsd I see that we get this info with netstat command - netstat -na -p tcp -f inet | grep LISTEN. Anyways to get the IP on linux too? Also, pointing at your sentence -> "Linux by default listens on both IPV4 and IPv6 connections if INADDR6_ANY (::) is used".. Is it safe to get the ip address from ifconfig's output and use this to establish tunnel as you say that linux by default listens on both IPV4/6"
– BRT
Nov 6 '17 at 11:18












To listen on a specific address only, you will have to configure the ssh server to listen to that address only. For example, you could put this in /etc/ssh/sshd_config: ListenAddress 10.8.113.30. This forces the ssh server to only listen on that address.
– Johan Myréen
Nov 6 '17 at 11:28




To listen on a specific address only, you will have to configure the ssh server to listen to that address only. For example, you could put this in /etc/ssh/sshd_config: ListenAddress 10.8.113.30. This forces the ssh server to only listen on that address.
– Johan Myréen
Nov 6 '17 at 11:28












@BRT: The point is that in this specific case the SSH daemon is not listening on a specific address; it's listening on any address. Poor netstat shows the truth.
– AlexP
Nov 6 '17 at 12:00




@BRT: The point is that in this specific case the SSH daemon is not listening on a specific address; it's listening on any address. Poor netstat shows the truth.
– AlexP
Nov 6 '17 at 12:00

















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f402806%2fnetstat-doesnt-show-my-machine-ip-as-listening-on-port-22%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

How to check contact read email or not when send email to Individual?

Displaying single band from multi-band raster using QGIS

How many registers does an x86_64 CPU actually have?