Re: nmcli -d ??
On 5/17/24 3:56 AM, ToddAndMargo via users wrote: On 5/17/24 03:54, ToddAndMargo via users wrote: Hi All, In CentOS 8, I have the following command: # nmcli -d example output: DEVICE TYPE STATE CONNECTION ens3 ethernet disconnected ens3 lo loopback unmanaged --- But under Fedora 39, the same command gives me # nmcli -d Error: Option '-d' is unknown, try 'nmcli -help'. I really like the output that CentOS gives. Is there a way to get it back? Not finding anything under --help or search.brave.com Many thanks, -T Never mind. I just figured it out: # nmcli device DEVICE TYPE STATE CONNECTION eno2 ethernet connected Wired connection 2 lo loopback connected (externally) lo br0 bridge connected bridge-br0 eno1 ethernet unavailable -- I guess it used to use a dash for the options. All you need now is an unambiguous prefix. "nmcli d" will work. -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: nmcli -d ??
How about nmcli device status Regards Andrew On 17 May 2024 11:55:23 ToddAndMargo via users wrote: Hi All, In CentOS 8, I have the following command: # nmcli -d example output: DEVICE TYPE STATE CONNECTION ens3ethernet disconnected ens3 lo loopback unmanaged --- But under Fedora 39, the same command gives me # nmcli -d Error: Option '-d' is unknown, try 'nmcli -help'. I really like the output that CentOS gives. Is there a way to get it back? Not finding anything under --help or search.brave.com Many thanks, -T -- ~~ Computers are like air conditioners. They malfunction when you open windows ~~ -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: nmcli -d ??
On 5/17/24 03:54, ToddAndMargo via users wrote: Hi All, In CentOS 8, I have the following command: # nmcli -d example output: DEVICE TYPE STATE CONNECTION ens3 ethernet disconnected ens3 lo loopback unmanaged --- But under Fedora 39, the same command gives me # nmcli -d Error: Option '-d' is unknown, try 'nmcli -help'. I really like the output that CentOS gives. Is there a way to get it back? Not finding anything under --help or search.brave.com Many thanks, -T Never mind. I just figured it out: # nmcli device DEVICE TYPE STATE CONNECTION eno2ethernet connected Wired connection 2 lo loopback connected (externally) lo br0 bridgeconnected bridge-br0 eno1ethernet unavailable -- -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
nmcli -d ??
Hi All, In CentOS 8, I have the following command: # nmcli -d example output: DEVICE TYPE STATE CONNECTION ens3ethernet disconnected ens3 lo loopback unmanaged --- But under Fedora 39, the same command gives me # nmcli -d Error: Option '-d' is unknown, try 'nmcli -help'. I really like the output that CentOS gives. Is there a way to get it back? Not finding anything under --help or search.brave.com Many thanks, -T -- ~~ Computers are like air conditioners. They malfunction when you open windows ~~ -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: nmcli d wifi list shows no AP's
On Fri, Jun 10, 2016 at 3:34 PM, Chris Murphy <li...@colorremedies.com> wrote: > On Fri, Jun 10, 2016 at 3:28 PM, Chris Murphy <li...@colorremedies.com> wrote: >> Here we go again! >> >> Fedora 23 Server, no GUI, running on an Intel NUC which has Intel >> Corporation Wireless 3165. The problem is, despite the radio being on >> and no obvious complaints, no APs are listed with nmcli d list. >> >> # nmcli r >> WIFI-HW WIFI WWAN-HW WWAN >> enabled enabled enabled enabled >> [root@f23s ~]# nmcli c >> NAMEUUID TYPEDEVICE >> virbr0-nic 9b346e45-60a4-48d4-a4d2-b5452946093b generic virbr0-nic >> virbr0 a4bc029b-716c-41d7-82a1-71af8f2a045e bridge virbr0 >> enp3s0 5cfa14cc-0d22-4c12-ae08-d61d8f47a011 802-3-ethernet enp3s0 >> [root@f23s ~]# nmcli d >> DEVICE TYPE STATE CONNECTION >> virbr0 bridgeconnected virbr0 >> enp3s0 ethernet connected enp3s0 >> virbr0-nic tap connected virbr0-nic >> lo loopback unmanaged -- >> wlp2s0 wifi unmanaged -- >> [root@f23s ~]# nmcli d wifi list >> [root@f23s ~]# >> >> That's not expected. A laptop sees many APs for this same command, but >> it's running Workstation so I wonder if there's something Server needs >> that it doesn't get by default (other than firmware and wpa_supplicant >> which I installed afterward). >> >> Also suspicious: >> >> # journalctl -b | grep iwlwifi >> https://paste.fedoraproject.org/377327/ >> >> It's a model 3165 but it wants 7265D firmware, which it finds and uses >> without complaint. But the Carrier: OFF is curious, not sure what that >> means. >> >> Although this is Fedora 23, it is the Fedora 24 kernel and firmware >> files being used which could be related. But it's the first time I've >> tried to use this wifi. > > Fedora 23 Server > [chris@f23s ~]$ rpm -qa | grep NetworkManager > NetworkManager-1.0.12-2.fc23.x86_64 > NetworkManager-libnm-1.0.12-2.fc23.x86_64 > > Fedora 24 Workstation > [chris@f24m Downloads]$ rpm -qa | grep NetworkManager > NetworkManager-wifi-1.2.2-2.fc24.x86_64 > NetworkManager-pptp-1.2.2-1.fc24.x86_64 > NetworkManager-openvpn-gnome-1.2.2-1.fc24.x86_64 > NetworkManager-1.2.2-2.fc24.x86_64 > NetworkManager-bluetooth-1.2.2-2.fc24.x86_64 > NetworkManager-pptp-gnome-1.2.2-1.fc24.x86_64 > NetworkManager-adsl-1.2.2-2.fc24.x86_64 > NetworkManager-openvpn-1.2.2-1.fc24.x86_64 > NetworkManager-wwan-1.2.2-2.fc24.x86_64 > NetworkManager-libnm-1.2.2-2.fc24.x86_64 > NetworkManager-vpnc-gnome-1.2.2-1.fc24.x86_64 > NetworkManager-vpnc-1.2.2-1.fc24.x86_64 > NetworkManager-config-connectivity-fedora-1.2.2-2.fc24.x86_64 > NetworkManager-team-1.2.2-2.fc24.x86_64 > NetworkManager-openconnect-1.2.2-1.fc24.x86_64 > NetworkManager-glib-1.2.2-2.fc24.x86_64 > > > OK! So I'm gonna guess it wants at least NetworkManager-wifi... That did it. It needed some other things also, ModemManager and a few libraries. But now the command works. And I've connected. -- Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: nmcli d wifi list shows no AP's
On Fri, Jun 10, 2016 at 3:28 PM, Chris Murphy <li...@colorremedies.com> wrote: > Here we go again! > > Fedora 23 Server, no GUI, running on an Intel NUC which has Intel > Corporation Wireless 3165. The problem is, despite the radio being on > and no obvious complaints, no APs are listed with nmcli d list. > > # nmcli r > WIFI-HW WIFI WWAN-HW WWAN > enabled enabled enabled enabled > [root@f23s ~]# nmcli c > NAMEUUID TYPEDEVICE > virbr0-nic 9b346e45-60a4-48d4-a4d2-b5452946093b generic virbr0-nic > virbr0 a4bc029b-716c-41d7-82a1-71af8f2a045e bridge virbr0 > enp3s0 5cfa14cc-0d22-4c12-ae08-d61d8f47a011 802-3-ethernet enp3s0 > [root@f23s ~]# nmcli d > DEVICE TYPE STATE CONNECTION > virbr0 bridgeconnected virbr0 > enp3s0 ethernet connected enp3s0 > virbr0-nic tap connected virbr0-nic > lo loopback unmanaged -- > wlp2s0 wifi unmanaged -- > [root@f23s ~]# nmcli d wifi list > [root@f23s ~]# > > That's not expected. A laptop sees many APs for this same command, but > it's running Workstation so I wonder if there's something Server needs > that it doesn't get by default (other than firmware and wpa_supplicant > which I installed afterward). > > Also suspicious: > > # journalctl -b | grep iwlwifi > https://paste.fedoraproject.org/377327/ > > It's a model 3165 but it wants 7265D firmware, which it finds and uses > without complaint. But the Carrier: OFF is curious, not sure what that > means. > > Although this is Fedora 23, it is the Fedora 24 kernel and firmware > files being used which could be related. But it's the first time I've > tried to use this wifi. Fedora 23 Server [chris@f23s ~]$ rpm -qa | grep NetworkManager NetworkManager-1.0.12-2.fc23.x86_64 NetworkManager-libnm-1.0.12-2.fc23.x86_64 Fedora 24 Workstation [chris@f24m Downloads]$ rpm -qa | grep NetworkManager NetworkManager-wifi-1.2.2-2.fc24.x86_64 NetworkManager-pptp-1.2.2-1.fc24.x86_64 NetworkManager-openvpn-gnome-1.2.2-1.fc24.x86_64 NetworkManager-1.2.2-2.fc24.x86_64 NetworkManager-bluetooth-1.2.2-2.fc24.x86_64 NetworkManager-pptp-gnome-1.2.2-1.fc24.x86_64 NetworkManager-adsl-1.2.2-2.fc24.x86_64 NetworkManager-openvpn-1.2.2-1.fc24.x86_64 NetworkManager-wwan-1.2.2-2.fc24.x86_64 NetworkManager-libnm-1.2.2-2.fc24.x86_64 NetworkManager-vpnc-gnome-1.2.2-1.fc24.x86_64 NetworkManager-vpnc-1.2.2-1.fc24.x86_64 NetworkManager-config-connectivity-fedora-1.2.2-2.fc24.x86_64 NetworkManager-team-1.2.2-2.fc24.x86_64 NetworkManager-openconnect-1.2.2-1.fc24.x86_64 NetworkManager-glib-1.2.2-2.fc24.x86_64 OK! So I'm gonna guess it wants at least NetworkManager-wifi... -- Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
nmcli d wifi list shows no AP's
Here we go again! Fedora 23 Server, no GUI, running on an Intel NUC which has Intel Corporation Wireless 3165. The problem is, despite the radio being on and no obvious complaints, no APs are listed with nmcli d list. # nmcli r WIFI-HW WIFI WWAN-HW WWAN enabled enabled enabled enabled [root@f23s ~]# nmcli c NAMEUUID TYPEDEVICE virbr0-nic 9b346e45-60a4-48d4-a4d2-b5452946093b generic virbr0-nic virbr0 a4bc029b-716c-41d7-82a1-71af8f2a045e bridge virbr0 enp3s0 5cfa14cc-0d22-4c12-ae08-d61d8f47a011 802-3-ethernet enp3s0 [root@f23s ~]# nmcli d DEVICE TYPE STATE CONNECTION virbr0 bridgeconnected virbr0 enp3s0 ethernet connected enp3s0 virbr0-nic tap connected virbr0-nic lo loopback unmanaged -- wlp2s0 wifi unmanaged -- [root@f23s ~]# nmcli d wifi list [root@f23s ~]# That's not expected. A laptop sees many APs for this same command, but it's running Workstation so I wonder if there's something Server needs that it doesn't get by default (other than firmware and wpa_supplicant which I installed afterward). Also suspicious: # journalctl -b | grep iwlwifi https://paste.fedoraproject.org/377327/ It's a model 3165 but it wants 7265D firmware, which it finds and uses without complaint. But the Carrier: OFF is curious, not sure what that means. Although this is Fedora 23, it is the Fedora 24 kernel and firmware files being used which could be related. But it's the first time I've tried to use this wifi. -- Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
