Re: ss issue on arm not showing UDP listening ports

[jesse_cooper]

Quoting Guillaume Nault :


On Wed, Feb 21, 2018 at 07:59:24PM -0600, Jesse Cooper wrote:

Thank you for the suggestions. This is on a raspberry pi 3 not sure if
that fact matters. I will notify Raspbian of the issue.


Does your kernel have CONFIG_INET_UDP_DIAG?


grep CONFIG_INET_UDP_DIAG kernel.config
# CONFIG_INET_UDP_DIAG is not set

sudo modprobe udp_diag
modprobe: FATAL: Module udp_diag not found in directory  
/lib/modules/4.9.59-v7+


Can this module be loaded after the fact? If so what is the easiest  
way to get the proper .ko file?

Re: ss issue on arm not showing UDP listening ports

[jesse_cooper]

ss utility, iproute2-ss161212

Quoting Stefano Brivio :


Hi,

On Wed, 21 Feb 2018 11:30:16 -0500
jesse_coo...@codeholics.com wrote:


Hi,

I currently had the follow issues with ss where it was not displaying
the UDP listening ports.This was on:

Linux 4.9.59-v7+ #1047 SMP Sun Oct 29 12:19:23 GMT 2017 armv7l GNU/Linux

ss -ul
State Recv-Q Send-Q Local Address:Port Peer Address:Port


Could you please also report the version of 'ss'? That is, the output
of:

ss --version

Thanks.

--
Stefano

ss issue on arm not showing UDP listening ports

[jesse_cooper]

Hi,

I currently had the follow issues with ss where it was not displaying  
the UDP listening ports.This was on:


Linux 4.9.59-v7+ #1047 SMP Sun Oct 29 12:19:23 GMT 2017 armv7l GNU/Linux

ss -ul
State Recv-Q Send-Q Local Address:Port Peer Address:Port

netstat -ul
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address   Foreign Address State
udp0  0 0.0.0.0:mdns0.0.0.0:*
udp0  0 0.0.0.0:bootpc  0.0.0.0:*
udp0  0 0.0.0.0:55887   0.0.0.0:*
udp0  0 192.168.1.80:ntp0.0.0.0:*
udp0  0 localhost:ntp   0.0.0.0:*
udp0  0 0.0.0.0:ntp 0.0.0.0:*
udp0  0 0.0.0.0:46739   0.0.0.0:*
udp0  0 0.0.0.0:snmp0.0.0.0:*
udp6   0  0 [::]:mdns   [::]:*
udp6   0  0 [::]:40880  [::]:*
udp6   0  0 fe80::bcdd:e603:7d8:ntp [::]:*
udp6   0  0 localhost:ntp   [::]:*
udp6   0  0 [::]:ntp[::]:*

I hope I have found the proper way to report this issue.