Comment 3 for bug 1581846

I asked because I know very little about this topic. :-/ The attached file is what my own machine outputted when I ran the "nm-tool" command.

I now think that the "nmcli dev" command would be a better replacement:

$ nmcli dev
DEVICE TYPE STATE CONNECTION
wlan0 wifi connected GuestWNET
eth0 ethernet disconnected --
ttyUSB0 gsm unavailable --
lo loopback unmanaged --

It shows the state of each device.

On 2016-05-14 23:21, Dave Harper wrote:
> I should also point out that is a really low priority issue (IMHO)
> - anyone following the documentation will quickly find (as I did)
> that nm-tool is no longer available and the substitute is nmcli.

Well, it's a docs bug, and now when you have pointed it out, we'd better change it somehow.

> Since my problem has more to do with authentication rather than
> actual connection I have not pursued the nmcli tool much further.

I see.