How can I find out which processes are using or listening on which network interfaces?How to kill processes using a network interfaceHow do I fix Debian that refuses to connect to the internet in VirtualBox?Detecting which application is using which network interfaceWhen are interfaces names? (Scripts under /etc/sysconfig/network-scripts)Two LXC containers using two different physical network interfacesHow can I change the priority of network interfaces?Why are some network interfaces named eth1 or wlan0 while others are named wlp4s0?rx_drops_no_pbuf drops on Emulex Corporation OneConnect 10Gb NICWhich programs configure the network based on the settings in /etc/network/interfaces?Can you assign different DNS servers to different network interfaces?
Personal Teleportation as a Weapon
Curses work by shouting - How to avoid collateral damage?
How do I define a right arrow with bar in LaTeX?
Coordinate position not precise
What defines a dissertation?
Greatest common substring
Is expanding the research of a group into machine learning as a PhD student risky?
Can I use my Chinese passport to enter China after I acquired another citizenship?
What is difference between behavior and behaviour
How can I get through very long and very dry, but also very useful technical documents when learning a new tool?
Is this Spell Mimic feat balanced?
Everything Bob says is false. How does he get people to trust him?
Is there a problem with hiding "forgot password" until it's needed?
Is there an Impartial Brexit Deal comparison site?
Is a roofing delivery truck likely to crack my driveway slab?
Why did Kant, Hegel, and Adorno leave some words and phrases in the Greek alphabet?
Why does John Bercow say “unlock” after reading out the results of a vote?
Is exact Kanji stroke length important?
Can criminal fraud exist without damages?
Stereotypical names
Is it correct to write "is not focus on"?
Have I saved too much for retirement so far?
What's the purpose of "true" in bash "if sudo true; then"
How can I replace every global instance of "x[2]" with "x_2"
How can I find out which processes are using or listening on which network interfaces?
How to kill processes using a network interfaceHow do I fix Debian that refuses to connect to the internet in VirtualBox?Detecting which application is using which network interfaceWhen are interfaces names? (Scripts under /etc/sysconfig/network-scripts)Two LXC containers using two different physical network interfacesHow can I change the priority of network interfaces?Why are some network interfaces named eth1 or wlan0 while others are named wlp4s0?rx_drops_no_pbuf drops on Emulex Corporation OneConnect 10Gb NICWhich programs configure the network based on the settings in /etc/network/interfaces?Can you assign different DNS servers to different network interfaces?
ifconfig
lists several network interfaces, some of which are virtual ones.
How can I find out which processes are using or listening on which network interfaces? Thanks.
$ ifconfig
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
ether 02:42:a6:79:a6:bc txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
enp0s25: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 20 memory 0xfc400000-fc420000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 3102389 bytes 174723039 (174.7 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3102389 bytes 174723039 (174.7 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
virbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255
ether 52:54:00:b1:aa:1f txqueuelen 1000 (Ethernet)
RX packets 708 bytes 68468 (68.4 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 316 bytes 51806 (51.8 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::fc54:ff:fe99:5eee prefixlen 64 scopeid 0x20<link>
ether fe:54:00:99:5e:ee txqueuelen 1000 (Ethernet)
RX packets 257 bytes 28494 (28.4 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 23514 bytes 1240204 (1.2 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlx8: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.97 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 prefixlen 64 scopeid 0x20<link>
ether 80:1f:02:b5:c3:89 txqueuelen 1000 (Ethernet)
RX packets 1269625 bytes 1045069752 (1.0 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 646600 bytes 101897054 (101.8 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
network-interface socket
add a comment |
ifconfig
lists several network interfaces, some of which are virtual ones.
How can I find out which processes are using or listening on which network interfaces? Thanks.
$ ifconfig
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
ether 02:42:a6:79:a6:bc txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
enp0s25: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 20 memory 0xfc400000-fc420000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 3102389 bytes 174723039 (174.7 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3102389 bytes 174723039 (174.7 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
virbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255
ether 52:54:00:b1:aa:1f txqueuelen 1000 (Ethernet)
RX packets 708 bytes 68468 (68.4 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 316 bytes 51806 (51.8 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::fc54:ff:fe99:5eee prefixlen 64 scopeid 0x20<link>
ether fe:54:00:99:5e:ee txqueuelen 1000 (Ethernet)
RX packets 257 bytes 28494 (28.4 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 23514 bytes 1240204 (1.2 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlx8: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.97 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 prefixlen 64 scopeid 0x20<link>
ether 80:1f:02:b5:c3:89 txqueuelen 1000 (Ethernet)
RX packets 1269625 bytes 1045069752 (1.0 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 646600 bytes 101897054 (101.8 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
network-interface socket
Network Interface? They're listening on addresses, or say holding an opened socket, if on POSIX system.
– 炸鱼薯条德里克
yesterday
add a comment |
ifconfig
lists several network interfaces, some of which are virtual ones.
How can I find out which processes are using or listening on which network interfaces? Thanks.
$ ifconfig
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
ether 02:42:a6:79:a6:bc txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
enp0s25: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 20 memory 0xfc400000-fc420000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 3102389 bytes 174723039 (174.7 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3102389 bytes 174723039 (174.7 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
virbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255
ether 52:54:00:b1:aa:1f txqueuelen 1000 (Ethernet)
RX packets 708 bytes 68468 (68.4 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 316 bytes 51806 (51.8 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::fc54:ff:fe99:5eee prefixlen 64 scopeid 0x20<link>
ether fe:54:00:99:5e:ee txqueuelen 1000 (Ethernet)
RX packets 257 bytes 28494 (28.4 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 23514 bytes 1240204 (1.2 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlx8: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.97 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 prefixlen 64 scopeid 0x20<link>
ether 80:1f:02:b5:c3:89 txqueuelen 1000 (Ethernet)
RX packets 1269625 bytes 1045069752 (1.0 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 646600 bytes 101897054 (101.8 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
network-interface socket
ifconfig
lists several network interfaces, some of which are virtual ones.
How can I find out which processes are using or listening on which network interfaces? Thanks.
$ ifconfig
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
ether 02:42:a6:79:a6:bc txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
enp0s25: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 20 memory 0xfc400000-fc420000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 3102389 bytes 174723039 (174.7 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3102389 bytes 174723039 (174.7 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
virbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255
ether 52:54:00:b1:aa:1f txqueuelen 1000 (Ethernet)
RX packets 708 bytes 68468 (68.4 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 316 bytes 51806 (51.8 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::fc54:ff:fe99:5eee prefixlen 64 scopeid 0x20<link>
ether fe:54:00:99:5e:ee txqueuelen 1000 (Ethernet)
RX packets 257 bytes 28494 (28.4 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 23514 bytes 1240204 (1.2 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlx8: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.97 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 prefixlen 64 scopeid 0x20<link>
ether 80:1f:02:b5:c3:89 txqueuelen 1000 (Ethernet)
RX packets 1269625 bytes 1045069752 (1.0 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 646600 bytes 101897054 (101.8 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
network-interface socket
network-interface socket
asked yesterday
TimTim
28.1k78269490
28.1k78269490
Network Interface? They're listening on addresses, or say holding an opened socket, if on POSIX system.
– 炸鱼薯条德里克
yesterday
add a comment |
Network Interface? They're listening on addresses, or say holding an opened socket, if on POSIX system.
– 炸鱼薯条德里克
yesterday
Network Interface? They're listening on addresses, or say holding an opened socket, if on POSIX system.
– 炸鱼薯条德里克
yesterday
Network Interface? They're listening on addresses, or say holding an opened socket, if on POSIX system.
– 炸鱼薯条德里克
yesterday
add a comment |
1 Answer
1
active
oldest
votes
ss -plnt
will list p
rocesses l
istening n
umerically on t
cp ports and will show you the IP and port bound to, as well as relevant PIDs and file descriptors:
$ sudo ss -plnt | grep -E ':(22|8384)[^0-9]'
LISTEN 0 128 192.168.42.2:8384 0.0.0.0:* users:(("syncthing",pid=14565,fd=8))
LISTEN 0 128 0.0.0.0:22 0.0.0.0:* users:(("sshd",pid=6099,fd=3))
LISTEN 0 128 [::]:22 [::]:* users:(("sshd",pid=6099,fd=4))
Compare the same from the older netstat -plnt
:
$ sudo netstat -plnt | grep -E ':(22|8384)[^0-9]'
tcp 0 0 192.168.42.2:8384 0.0.0.0:* LISTEN 14565/syncthing
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 6099/sshd
tcp6 0 0 :::22 :::* LISTEN 6099/sshd
Shown are the secure shell daemon (listening on all interfaces), and my local install of SyncThing (which has its management interface is bound explicitly to one network address).
Strange ss -plnt did not show ssh for me, but netstat does.
– Luciano Andress Martini
yesterday
Try looking for the numerical port:ss -plnt | grep ':22'
.
– DopeGhoti
yesterday
netstat looks better! Is it being deprecated? ( I always used it, never heared about ss replacing it, I thinked it is just an alternative, seems that every alternative in Linux are replacing the old ones )
– Luciano Andress Martini
yesterday
I prefernetstat
as well, though admittedly largely due to familiarity from long usage. As to the why of it? That is beyond my pay-grade.
– DopeGhoti
yesterday
add a comment |
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',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f508545%2fhow-can-i-find-out-which-processes-are-using-or-listening-on-which-network-inter%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
ss -plnt
will list p
rocesses l
istening n
umerically on t
cp ports and will show you the IP and port bound to, as well as relevant PIDs and file descriptors:
$ sudo ss -plnt | grep -E ':(22|8384)[^0-9]'
LISTEN 0 128 192.168.42.2:8384 0.0.0.0:* users:(("syncthing",pid=14565,fd=8))
LISTEN 0 128 0.0.0.0:22 0.0.0.0:* users:(("sshd",pid=6099,fd=3))
LISTEN 0 128 [::]:22 [::]:* users:(("sshd",pid=6099,fd=4))
Compare the same from the older netstat -plnt
:
$ sudo netstat -plnt | grep -E ':(22|8384)[^0-9]'
tcp 0 0 192.168.42.2:8384 0.0.0.0:* LISTEN 14565/syncthing
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 6099/sshd
tcp6 0 0 :::22 :::* LISTEN 6099/sshd
Shown are the secure shell daemon (listening on all interfaces), and my local install of SyncThing (which has its management interface is bound explicitly to one network address).
Strange ss -plnt did not show ssh for me, but netstat does.
– Luciano Andress Martini
yesterday
Try looking for the numerical port:ss -plnt | grep ':22'
.
– DopeGhoti
yesterday
netstat looks better! Is it being deprecated? ( I always used it, never heared about ss replacing it, I thinked it is just an alternative, seems that every alternative in Linux are replacing the old ones )
– Luciano Andress Martini
yesterday
I prefernetstat
as well, though admittedly largely due to familiarity from long usage. As to the why of it? That is beyond my pay-grade.
– DopeGhoti
yesterday
add a comment |
ss -plnt
will list p
rocesses l
istening n
umerically on t
cp ports and will show you the IP and port bound to, as well as relevant PIDs and file descriptors:
$ sudo ss -plnt | grep -E ':(22|8384)[^0-9]'
LISTEN 0 128 192.168.42.2:8384 0.0.0.0:* users:(("syncthing",pid=14565,fd=8))
LISTEN 0 128 0.0.0.0:22 0.0.0.0:* users:(("sshd",pid=6099,fd=3))
LISTEN 0 128 [::]:22 [::]:* users:(("sshd",pid=6099,fd=4))
Compare the same from the older netstat -plnt
:
$ sudo netstat -plnt | grep -E ':(22|8384)[^0-9]'
tcp 0 0 192.168.42.2:8384 0.0.0.0:* LISTEN 14565/syncthing
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 6099/sshd
tcp6 0 0 :::22 :::* LISTEN 6099/sshd
Shown are the secure shell daemon (listening on all interfaces), and my local install of SyncThing (which has its management interface is bound explicitly to one network address).
Strange ss -plnt did not show ssh for me, but netstat does.
– Luciano Andress Martini
yesterday
Try looking for the numerical port:ss -plnt | grep ':22'
.
– DopeGhoti
yesterday
netstat looks better! Is it being deprecated? ( I always used it, never heared about ss replacing it, I thinked it is just an alternative, seems that every alternative in Linux are replacing the old ones )
– Luciano Andress Martini
yesterday
I prefernetstat
as well, though admittedly largely due to familiarity from long usage. As to the why of it? That is beyond my pay-grade.
– DopeGhoti
yesterday
add a comment |
ss -plnt
will list p
rocesses l
istening n
umerically on t
cp ports and will show you the IP and port bound to, as well as relevant PIDs and file descriptors:
$ sudo ss -plnt | grep -E ':(22|8384)[^0-9]'
LISTEN 0 128 192.168.42.2:8384 0.0.0.0:* users:(("syncthing",pid=14565,fd=8))
LISTEN 0 128 0.0.0.0:22 0.0.0.0:* users:(("sshd",pid=6099,fd=3))
LISTEN 0 128 [::]:22 [::]:* users:(("sshd",pid=6099,fd=4))
Compare the same from the older netstat -plnt
:
$ sudo netstat -plnt | grep -E ':(22|8384)[^0-9]'
tcp 0 0 192.168.42.2:8384 0.0.0.0:* LISTEN 14565/syncthing
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 6099/sshd
tcp6 0 0 :::22 :::* LISTEN 6099/sshd
Shown are the secure shell daemon (listening on all interfaces), and my local install of SyncThing (which has its management interface is bound explicitly to one network address).
ss -plnt
will list p
rocesses l
istening n
umerically on t
cp ports and will show you the IP and port bound to, as well as relevant PIDs and file descriptors:
$ sudo ss -plnt | grep -E ':(22|8384)[^0-9]'
LISTEN 0 128 192.168.42.2:8384 0.0.0.0:* users:(("syncthing",pid=14565,fd=8))
LISTEN 0 128 0.0.0.0:22 0.0.0.0:* users:(("sshd",pid=6099,fd=3))
LISTEN 0 128 [::]:22 [::]:* users:(("sshd",pid=6099,fd=4))
Compare the same from the older netstat -plnt
:
$ sudo netstat -plnt | grep -E ':(22|8384)[^0-9]'
tcp 0 0 192.168.42.2:8384 0.0.0.0:* LISTEN 14565/syncthing
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 6099/sshd
tcp6 0 0 :::22 :::* LISTEN 6099/sshd
Shown are the secure shell daemon (listening on all interfaces), and my local install of SyncThing (which has its management interface is bound explicitly to one network address).
edited yesterday
answered yesterday
DopeGhotiDopeGhoti
46.6k56190
46.6k56190
Strange ss -plnt did not show ssh for me, but netstat does.
– Luciano Andress Martini
yesterday
Try looking for the numerical port:ss -plnt | grep ':22'
.
– DopeGhoti
yesterday
netstat looks better! Is it being deprecated? ( I always used it, never heared about ss replacing it, I thinked it is just an alternative, seems that every alternative in Linux are replacing the old ones )
– Luciano Andress Martini
yesterday
I prefernetstat
as well, though admittedly largely due to familiarity from long usage. As to the why of it? That is beyond my pay-grade.
– DopeGhoti
yesterday
add a comment |
Strange ss -plnt did not show ssh for me, but netstat does.
– Luciano Andress Martini
yesterday
Try looking for the numerical port:ss -plnt | grep ':22'
.
– DopeGhoti
yesterday
netstat looks better! Is it being deprecated? ( I always used it, never heared about ss replacing it, I thinked it is just an alternative, seems that every alternative in Linux are replacing the old ones )
– Luciano Andress Martini
yesterday
I prefernetstat
as well, though admittedly largely due to familiarity from long usage. As to the why of it? That is beyond my pay-grade.
– DopeGhoti
yesterday
Strange ss -plnt did not show ssh for me, but netstat does.
– Luciano Andress Martini
yesterday
Strange ss -plnt did not show ssh for me, but netstat does.
– Luciano Andress Martini
yesterday
Try looking for the numerical port:
ss -plnt | grep ':22'
.– DopeGhoti
yesterday
Try looking for the numerical port:
ss -plnt | grep ':22'
.– DopeGhoti
yesterday
netstat looks better! Is it being deprecated? ( I always used it, never heared about ss replacing it, I thinked it is just an alternative, seems that every alternative in Linux are replacing the old ones )
– Luciano Andress Martini
yesterday
netstat looks better! Is it being deprecated? ( I always used it, never heared about ss replacing it, I thinked it is just an alternative, seems that every alternative in Linux are replacing the old ones )
– Luciano Andress Martini
yesterday
I prefer
netstat
as well, though admittedly largely due to familiarity from long usage. As to the why of it? That is beyond my pay-grade.– DopeGhoti
yesterday
I prefer
netstat
as well, though admittedly largely due to familiarity from long usage. As to the why of it? That is beyond my pay-grade.– DopeGhoti
yesterday
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f508545%2fhow-can-i-find-out-which-processes-are-using-or-listening-on-which-network-inter%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
-network-interface, socket
Network Interface? They're listening on addresses, or say holding an opened socket, if on POSIX system.
– 炸鱼薯条德里克
yesterday