sockstat

  • Permalink
  • submit to reddit
  • Email
  • Follow


Stumbled across this little command-line app, ported from FreeBSD:

   sockstat

The output is a bit like netstat -t -p.

sockstat doesn't do reverse DNS lookup, but netstat doesn't always show all
of the apps that are connected (e.g. firefox-bin!).

Another interesting package is socat, which looks like it is similar
to Windows' com2com.

-- 
I will not play at tug o' war.
I'd rather play at hug o' war,
Where everyone hugs
Instead of tugs,
Where everyone giggles
And rolls on the rug,
Where everyone kisses,
And everyone grins,
And everyone cuddles,
And everyone wins.
		-- Shel Silverstein, "Hug o' War"
0
Reply Chris 5/27/2010 1:31:45 AM

See related articles to this posting

Chris Ahlstrom pulled this Usenet boner:

> Stumbled across this little command-line app, ported from FreeBSD:
>
>    sockstat
>
> The output is a bit like netstat -t -p.
>
> sockstat doesn't do reverse DNS lookup, but netstat doesn't always show all
> of the apps that are connected (e.g. firefox-bin!).
>
> Another interesting package is socat, which looks like it is similar
> to Windows' com2com.

Actually, I meant com0com:

   http://com0com.sourceforge.net/

It's for Windows, but GPL'ed.  We used it so that to connect a serial port
on a virtual machine to a serial port on the actual host computer.

OSS crapware:   :-)

-- 
I think it's a new feature.  Don't tell anyone it was an accident.  :-)
		-- Larry Wall on s/foo/bar/eieio in <10911@jpl-devvax.JPL.NASA.GOV>
0
Reply Chris 5/27/2010 10:24:16 AM

Chris Ahlstrom <ahlstromc@launchmodem.com> wrote:
> Stumbled across this little command-line app, ported from FreeBSD:
> 
>   sockstat
> 
> The output is a bit like netstat -t -p.
> 
> sockstat doesn't do reverse DNS lookup, but netstat doesn't always show all
> of the apps that are connected (e.g. firefox-bin!).
> 
> Another interesting package is socat, which looks like it is similar
> to Windows' com2com.
> 

I like 
$ sudo lsof -i

0
Reply owl 5/29/2010 7:01:25 AM

owl pulled this Usenet boner:

> Chris Ahlstrom <ahlstromc@launchmodem.com> wrote:
>> Stumbled across this little command-line app, ported from FreeBSD:
>> 
>>   sockstat
>> 
>> The output is a bit like netstat -t -p.
>> 
>> sockstat doesn't do reverse DNS lookup, but netstat doesn't always show all
>> of the apps that are connected (e.g. firefox-bin!).
>> 
>> Another interesting package is socat, which looks like it is similar
>> to Windows' com2com.
>
> I like 
> $ sudo lsof -i

Shows all the LISTENing ports, though.

How to beknight a troll:

-- 
I will make you shorter by the head.
		-- Elizabeth I
0
Reply Chris 5/29/2010 11:14:07 AM

Chris Ahlstrom <ahlstromc@launchmodem.com> wrote:
> owl pulled this Usenet boner:

> > Chris Ahlstrom <ahlstromc@launchmodem.com> wrote:
> >> Stumbled across this little command-line app, ported from FreeBSD:
> >> 
> >>   sockstat
> >> 
> >> The output is a bit like netstat -t -p.
> >> 
> >> sockstat doesn't do reverse DNS lookup, but netstat doesn't always show all
> >> of the apps that are connected (e.g. firefox-bin!).
> >> 
> >> Another interesting package is socat, which looks like it is similar
> >> to Windows' com2com.
> >
> > I like 
> > $ sudo lsof -i

> Shows all the LISTENing ports, though.

It shows all client connections also.

0
Reply owl 5/30/2010 12:23:32 AM
comp.os.linux.advocacy 117336 articles. 8 followers. Post

4 Replies
263 Views

Similar Articles

[PageSpeed] 44

  • Permalink
  • submit to reddit
  • Email
  • Follow


Reply:

Similar Artilces:

What is tw at /proc/net/sockstat?!
Hi everybody~! I just want to know tw at /proc/net/sockstat ...!! In my server -------------------------------------------------------------------------------------------- ~$cat /proc/net/sockstat sockets: used 108 TCP: inuse 38 orphan 0 tw 100 alloc 38 mem 23 UDP: inuse 5 RAW: inuse 3 FRAG: inuse 0 memory 0 -------------------------------------------------------------------------------------------- Thank you for reading this topic~! and please anwer if you know.. bh98013@gmail.com wrote: > Hi everybody~! > I just want to know tw at /proc/net/sockstat ...!! > > In my server...

rpc.lockd part 1: invisible ports vs. lsof / sockstat / fstat
People generally expect lsof, sockstat, and fstat to identify which processes own which network connections. Unfortunately, it appears that rpc.lockd is capable of creating network connections that work but are invisible to these three programs. A malware writer might find the ability to hide a network connection from these tools useful. For example, when I recently started up rpc.lockd, these ports were opened: tcp4 0 0 *.1001 *.* LISTEN udp4 0 0 *.1017 *.* udp4 0 0 *.* *.* tcp6 0 0 *.698 *.* ...