On Mon, Apr 9, 2012 at 4:52 PM, Adrian Sevcenco <[email protected]> wrote: > On 04/09/12 22:36, Tom H wrote: >> On Mon, Apr 9, 2012 at 1:27 PM, Konstantin Olchanski <[email protected]> >> wrote: >>> On Mon, Apr 09, 2012 at 12:03:33PM -0500, Pat Riehecky wrote: >>>> On 04/09/2012 12:02 PM, Konstantin Olchanski wrote: >>>>> >>>>> That's right. Nm manager gui or vi. Our way or the highway. So you arrive >>>>> to a remote location >>>>> to fix broken network config and find that the mouse walked away, too, >>>>> welcome to vi. >>>> >>>> or nmcli >>> >>> The best I can tell, "nmcli" cannot change any configuration settings - >>> only report existing settings and do "ifconfig down"/"ifconfig up". >>> >>> (I tried to use the "up"/"down" function once but failed to figure out >>> what "id" to use for eth0. There are no examples and nmcli rejected >>> everything I tried. I did not try to use the UUID syntax on a text console >>> with no mouse). >> >> NM's like udev. That's why nmcli is used to bring up, take down, >> delete, or list connections or devices. >> >> For eth0 the "id" was probably "Wired connection 1". >> >> If you have one NIC, "nmcli -t -f UUID con list" will return the UUID. >> Without a mouse the "id" option's simpler... > if you are on a laptop that command will return the UID of ALL wireless > connection that you had ... > nmcli -t -f uuid con status > will return the UUID of current connection
Good catch. The "id" is my preferred method anyway. I wish that we could change its value via nmcli but we have to use an ifcfg-* script to do so.
