nmcli dev list iface <interfacename>

project722 · 06-04-2014, 07:24 AM

I have Ubuntu 14.04 - I ran the command below and it displayed tons of output. After a long bout with configuring a static IP, ((which in order to get a static to stick and the networking daemon to restart properly I had to revert back to the 13.10 scripts)) the command no longer works. It simply goes back to the prompt.

nmcli dev list iface <interfacename> | grep IP4

I can run the command without grepping and that works fine but I don't get the output I had before.

I still have the same version of networkmanager (0.9.8.8) however I think something I did when reverting back to the old scripts may have changed something. I followed the instructions here to revert back.

http://www.simpleprecision.com/how-t...-14-04-server/

Anyone know what may have happened?

910 · 06-05-2014, 03:53 AM

Quote:

the command no longer works. It simply goes back to the prompt.

So it doesn't find anything matching "IP4", which probably means that the <interface> either doesn't have an IPv4 address or isn't controlled by network-manager. If you added the static IP information in the interfaces file, I guess network-manager doesn't know about it (didn't check, though).

You can find out the correct interface and its IP by issuing the following command:

Code:

ip addr

project722 · 06-05-2014, 05:32 AM

eth0 does have an IP assigned however I did put in the static through the interfaces file. This sceenshot attached says "general.state - 10(unmanaged)"

Is that what you mean by isn't controlled by network manager?

910 · 06-05-2014, 06:04 AM

I'm not too familiar with NetworkManager but yeah, I guess that's what it means.

If you want the nmcli command to work as it used to, you probably need to set the static IP via NetworkManager instead of the interfaces file. If you're using a graphical desktop environment you should be able to set a static IP via the NetworkManager GUI. You can probably set it using nmcli as well.

But what are you in fact trying to achieve? Why must the nmcli command work?

project722 · 06-05-2014, 06:59 PM

Quote:

But what are you in fact trying to achieve? Why must the nmcli command work?

In a word - consistency. I have just got back into the world of Linux and I find it to be much more user-friendly. However installing packages and getting them to work properly while not breaking other things I've yet to master.

Thanks for the tips. I'm reluctant to try them however as I have had to revert back to the 13.10 networking scripts in order to stabilize the networking service. I don't know for sure if what you are suggesting would then break what I have already fixed.