On Mon, 2013-12-09 at 20:16 +0100, Javier Fernández-Sanguino Peña wrote: > On Mon, Dec 09, 2013 at 09:41:34AM -0700, Jason Fergus wrote: > > > > > > On Sat, 2013-12-07 at 10:55 -0600, Richard Owlett wrote: > > > I chose phrasing of subject line to emphasize some peculiarities > > > of my needs. > > > > > > End-user emphasizes: > > > - I am *NOT* an expert > > > - my system is never intended to be a "server" > > > > > Without any services running, you won't really have any ports open. Of > > course some user style services (like samba) may be running. I always > > like running 'lsof -i' as root to see what ports / services are open. > > lsof -i is equivalent to 'netstat -punta' it will provide also provide > information on existing (outbound/inbound) connections. This might provides > too much information. > I figured if he'd done that while not connected to any network, lsof would have worked. But you're right. > To list the service *listening* to the network 'netstat -puntl' might be more > useful as it provides *just* listening services (-l) in either UDP or TCP. As > an advantage, it does not require root privileges (the only information you > will miss if run by a regular user is the processes, i.e. the -p option) > > > Additionally, you can use 'ss' a tool similar to netstat (in iproute2 > package). 'ss -l' lists open TCP/UDP sockets. > > All these are command-line tools, I'm not aware of any GUI tool putting this > information in a "friendly" interface in a Desktop (i.e. similar to what > gnome-system-monitor does for processes). Anyone? > Gnome's network tools has a netstat tab. > Regards > > Javier >
Attachment:
signature.asc
Description: This is a digitally signed message part