NetworkManager appears to be running, however cannot connect to router. I am in my first days of using a new computer with a then newly loaded opensuse 13.2. The first few days all appeared to function properly (I really do not know for sure) or at least without error messages. So this problem is probably due to something I did. In the effort to solve this I loaded several other live CD linux distros and the network still did not connect. Changed cables between router and pc. Reset router. Connection to router with old notebook pc is successful.Using YaST2 and selecting, Network Devices, returns this warning: Network is currently handled by NetworkManager or completely disabled...OS version Linux 3.16.7.21-desktopopenSUSE (Harlequin)(x86_64)KDE 4.14.6motherboard Gigabyte H97-HD3New info. 2015-05-08.If I understand correctly, ifconfig is not telling me about the ethernet card so there is no name at this point.linux-mi46:~ # ifconfig  lo        Link encap:Local Loopback            inet addr:127.0.0.1  Mask:255.0.0.0          inet6 addr: ::1/128 Scope:Host          UP LOOPBACK RUNNING  MTU:65536  Metric:1          RX packets:328 errors:0 dropped:0 overruns:0 frame:0          TX packets:328 errors:0 dropped:0 overruns:0 carrier:0          collisions:0 txqueuelen:0           RX bytes:26876 (26.2 Kb)  TX bytes:26876 (26.2 Kb)  More Info. 2015-05-09.  A closer look following certain advice:the result of,  yast -- kdesu /sbin/yast2 lan, global options, shows the network setup method as NetworkManager service. And Overview, shows the Ethernet Network Card DHCP eth0. Started automatically at boot. Do not know if that configuration is correct. None the less continuing...The command systemctl status NetworkManager.service output the following:  linux-mi46:~ # systemctl status NetworkManager.serviceNetworkManager.service - Network ManagerLoaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled)Active: active (running) since Sat 2015-05-09 19:30:36 CEST; 55min agoMain PID: 1086 (NetworkManager)CGroup: /system.slice/NetworkManager.service       1086 /usr/sbin/NetworkManager --no-daemonMay 09 19:30:36 linux-mi46 NetworkManager[1086]: <info> WiMAX enabled by radio killswitch; enabled by state fileMay 09 19:30:36 linux-mi46 NetworkManager[1086]: <info> Networking is enabled by state fileMay 09 19:30:36 linux-mi46.site NetworkManager[1086]: <info> Setting system hostname to 'linux-mi46.site' (from syst...ion)May 09 19:30:36 linux-mi46.site NetworkManager[1086]: <info> (lo): link connectedMay 09 19:30:36 linux-mi46.site NetworkManager[1086]: <info> (lo): carrier is ONMay 09 19:30:36 linux-mi46.site NetworkManager[1086]: <info> (lo): new Generic device (driver: 'unknown' ifindex: 1)May 09 19:30:36 linux-mi46.site NetworkManager[1086]: <info> (lo): exported as /org/freedesktop/NetworkManager/Devices/0May 09 19:30:36 linux-mi46.site NetworkManager[1086]: <info> startup complete                                              May 09 19:30:36 linux-mi46.site NetworkManager[1086]: <info> ModemManager available in the bus                             May 09 19:30:39 linux-mi46.site NetworkManager[1086]: <info> use BlueZ version 5      New info 2015-05-22.The command ifconfig was not telling me about the ethernet card because I had disabled the network card in the BIOS.  It was only after reinstalling the OS and seeing the same ifconfig result that I looked more closely at my settings in the  BIOS. New lesson learned. 
Suse 13.2 fails to connect to router
opensuse;networkmanager;network interface
This is a case where only a closer look could provide a certain answer. So, this is a little bit of a troubleshooting:First thing, check yast  -- kdesu /sbin/yast2 lan. Go to global options, check if the network setup method is set to NetworkManager service. Then go back to Overview, check if your NICs appear and if their configuration is correct.Then, check if NetworkManager is running -- systemctl status NetworkManager.service. If it's not running, run sudo systemctl start NetworkManager.service. If you haven't seen any error to this point, your network interfaces should appear. Or, at least, you might be able to get a specific error message.