Network Manager Disabled - Cannot connect to Interfaces.

Hi.

I seem to have a similar problem as member Nivla regarding Network Manager app.
Been following Nivla thread. Maybe Nivla issues are somewhat related to mine.

I cannot enable the network manager app in my Linux environment on my Android 7.1.2 OnePlus One device. Without enabling, I am unable to connect wireless to wlan0 & wlan1.
Been trying to resolve this problem for 2 weeks, but cannot find a solution. Hopefully someone can help. Thanks. Jef.

Info:
- ROM: Lineageos 14.1 bacon Android 7.1.2 Marshmallow. Device: OnePlus One.
- Uname: Linux Nethunter 3.15. Kernel 3.4.112-lineageos-g23c699a armv71.
- Distro: Kali Linux Rolling V2017.1
- Architecture: Armhf
- CurrentDesktop: XFce V4.1,2
- Client: VNC Viewer V3.3.1 connect via localhost 127.0.0.1 to linux
- Network-Manager and Gnome v1-8-2-1 armhf

Wireless WIFI Use:
Have 2. Wlan0 and Wlan1.
Wlan0 owned/operated by the hotel I'm currently staying temporarily.
Connect using Windows on my XPS13 laptop.

Wlan1 is my external wifi dongle TP-Link-TL-WN722N, use specifically for Linux.
Use otg cable to connect Phone Device to wifi dongle.
I can successfully run all aircrack-ng commands putting wlan1 in monitor mode.
BTW: TL-WN722N dongle works fine when I access Linux with my Xps13 Laptop.

Prior to starting network manager, I initiate Ifconfig & airmon-ng cmds to start Wlan0 & Wlan1.
After this, I can ping google.com network.

Network Manager Applet responses:
Installed network-manager successfully. NM-applet appears on the top-right panel. Two monitors joined displaying “x” in window.
Right click the nm-applet shows the following:
- enable networking option (greyed out),
- enable notification open,
- connection info option(greyed out),
- edit connection open,
(see attached Screen-Shot).
Tic edit connections get not response.

Left click nm-applet, shows the following message:
“network manager is not running” grayed out (see attached Screen-Shot).
Go to application, settings, network connection and double click network connections, get no response.
Click on the front nm-applet, display message “network manager is disable”.


My Question is: How can I enable network manager in kali linux to configure my network connections? I cannot see any available wireless networks.
Once enabled, I should be able to “Ticked On” networking option in the applet, then connect wireless to the internet. From what I've read, most Networking problems are related to missing or faulty drivers. Is this true?

Tried:
- stop, restarting network manager service
- uninstalling/reinstalling network-manager & Gnome.
- Setting Managed=true In r.conf
- Killed all using rfkill command.
- Nm-connection-editor - 7214 Warning couldn't construct the client instance.
Could not connect, no such file or directory. Failed to initialize the UI.
- /etc/init.d/network-manager restart

Countenance of Files:
etc/network/Interfaces:
source-directory /etc/network/interfaces.d
auto lo
iface lo inet loopback

etc/network manager:
system connection – has only Network Manager USRP document.
Network manager r.conf - (main) plugins=ifupdown,keyfile (ifupdown) managed=false

Var /Network Manager - NetworkEnable=true, WirelessEnabled=true, WWANenabled=true

Some commands:
lspci
pcilib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method
I have Pcutils installed. I may not have any bus/pci installed.
Is there substitute command or file you can recommend to display?

AIRMON-NG
root@kali:~# airmon-ng start wlan1
Found 1 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to run 'airmon-ng check kill'

PID Name
2627 wpa_supplicant

PHY Interface Driver Chipset

phy0 p2p0 ?????? Not pci, usb, or sdio
phy0 wlan0 ?????? Not pci, usb, or sdio
phy1 wlan1 ?????? Atheros Communications, Inc. AR9271 802.11n

(mac80211 monitor mode vif enabled for [phy1]wlan1 on [phy1]wlan1mon)
(mac80211 station mode vif disabled for [phy1]wlan1)
rfkill list all
root@kali:~# rfkill list all
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: phy1: Wireless LAN
Soft blocked: no
Hard blocked: no
lsusb
root@kali:~# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

lsmod (file empty)
root@kali:~# lsmod
Module Size Used by

modrobe.d/blacklist
root@kali:~# cat /etc/modrobe.d/blacklist.libnfc.conf
blacklist nfc blacklist pn533

dmesg | grep usb
root@kali:~# dmesg | grep usb
[ 461.249782] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 461.250106] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 461.250596] usb usb1: Product: xHCI Host Controller
[ 461.250848] usb usb1: Manufacturer: Linux 3.4.113-lightning-kernel-v38-ga6181dd88ba-dirty xhci-hcd
[ 461.251161] usb usb1: SerialNumber: xhci-hcd
[ 461.261324] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[ 461.268275] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 461.269008] usb usb2: Product: xHCI Host Controller
[ 461.269281] usb usb2: Manufacturer: Linux 3.4.113-lightning-kernel-v38-ga6181dd88ba-dirty xhci-hcd
[ 461.269369] usb usb2: SerialNumber: xhci-hcd
[ 462.011147] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[ 462.035979] usb 1-1: New USB device found, idVendor=0cf3, idProduct=9271
[ 462.036415] usb 1-1: New USB device strings: Mfr=16, Product=32, SerialNumber=48
[ 462.036639] usb 1-1: Product: USB2.0 WLAN
[ 462.037038] usb 1-1: Manufacturer: ATHEROS
[ 462.037261] usb 1-1: SerialNumber: 12345
[ 462.067316] usb 1-1: ath9k_htc: Firmware htc_9271.fw requested
[ 462.388608] usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272


root@kali:~# ifconfig wlan0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.218 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::c2ee:fbff:fe27:c9f prefixlen 64 scopeid 0x20<link>
ether c0:ee:fb:27:0c:9f txqueuelen 1000 (Ethernet)
RX packets 18557 bytes 10006056 (9.5 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4262 bytes 552857 (539.8 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

root@kali:~# ifconfig wlan1
wlan1: error fetching interface information: Device not found
root@kali:~# ifconfig wlan1mon
wlan1mon: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
unspec 84-16-F9-07-CA-88-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC)
RX packets 11926 bytes 5538795 (5.2 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

IWCONFIG
root@kali:~# ifconfig wlan0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.218 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::c2ee:fbff:fe27:c9f prefixlen 64 scopeid 0x20<link>
ether c0:ee:fb:27:0c:9f txqueuelen 1000 (Ethernet)
RX packets 18557 bytes 10006056 (9.5 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4262 bytes 552857 (539.8 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

root@kali:~# ifconfig wlan1
wlan1: error fetching interface information: Device not found
root@kali:~# ifconfig wlan1mon
wlan1mon: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
unspec 84-16-F9-07-CA-88-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC)
RX packets 11926 bytes 5538795 (5.2 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

root@kali:~# ifconfig wlan0 up
root@kali:~# ifconfig wlan1 up
wlan1: ERROR while getting interface flags: No such device
root@kali:~# ifconfig wlan1mon up
root@kali:~# iwconfig
rmnet3 no wireless extensions.

rev_rmnet0 no wireless extensions.

rev_rmnet5 no wireless extensions.

wlan0 Qcom:802.11n ESSID:"BayBreeze Hotel" Nickname:""
Mode:Managed Frequency:2.437 GHz Access Point: 26:A4:3C:4F:49:4A
Bit Rate=9 Mb/s Tx-Power=16 dBm
RTS thr=2347 B Fragment thr=8000 B
Encryption key:B776-423D-5C59-D0D9-C5C1-1CA0-DD8B-F04A-C03E-B990-525C-9620-5BA4-6A58-3254-3048 [2] Security mode:restricted

rmnet4 no wireless extensions.

rev_rmnet1 no wireless extensions.

p2p0 Qcom:802.11n ESSID:off/any Nickname:""
Mode:Managed Channel:0 Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power=0 dBm
RTS thr=2347 B Fragment thr=8000 B
Encryption key:off

sit0 no wireless extensions.

dummy0 no wireless extensions.

lo no wireless extensions.

wlan1mon IEEE 802.11bgn Mode:Monitor Frequency:2.457 GHz Tx-Power=30 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off

Try this:

service network-manager start
nmcli networking on

Had both wlan0 and wlan1 up before entering the commands.
Entered: Service network-manager start
Terminal response: Ok starting network connection manager NetworkManager.

Entered: nmcli networking on.
Terminal response: Error could not create NMClient object: Could not connect:
No such file or directory.

Tried nmcli -f all con & nm c show active Same error as above.
Maybe nmcli running before connecting the interfaces.
Tried nmcli -v received tool, version 1.8.2.

Did a service network-manager status and network manager is running.
But nm-applet still disable (see my previous screenshots).

It seems the nm service is up, but cannot find any interfaces to connect.
Is it possible network manager is not detecting the Atheros AR9271 drivers?
Are there additional statements to be added in the network Interface file?

Jef.

can anybody else assist me. thanks Jef.

Quote:

---

Originally Posted by jefx3

can anybody else assist me. thanks Jef.

---

The issue can be that Nethunter is not recognizing your wifi adapter. You need to install the right driver. How do you have 2 wifi interfaces- wlan0 and wlan1 when your phone has only one wifi adapter?

@defalt.

I probably did not describe my problem better showing 2 interfaces.
Wlan0 is a wifi connection owned by the hotel I'm currently staying.
I am given a userid/password to access their wifi network.
I use this connecting to Windows 10 on my XPS 13 laptop.

In addition, if I perform apt-get update cmd, kali nethunter access wlan0 internet to resolve source.list. Wlan0 has nothing to do with my problem. I was just pointing out (badly I guess), wlan0 can be seen in nethunter when I perform commands Ifconfig & Iwconfig on my OPO device.

Wlan1 (TP-Link-TL-WN722N) is my only wireless adapter dongle I'm using.
From my understanding, the firmware (drivers) Atheros AR9271, ath9k_htc are built in the current kernel versions of Kali Nethunter. Post installation should be Plug & Play. I can go into “Monitor Mode” and perform successful Airmon-ng, airodump-ng wifite cmds within nethunter 3.0.
lsusb shows the machine does recognized the adapter.

But I cannot enable nm-applet to add or edit connection in Kali Nethunter using the wireless adapter.
Clicking edit connections returns no response from the machine.

Is it possible, I have the right drivers, but Kali Nethunter is not finding them in a specific file location?
Or does /etc/network/interface need additional statements?

Jef.

Quote:

---

Originally Posted by jefx3

Wlan0 owned/operated by the hotel I'm currently staying temporarily.

Wlan1 is my external wifi dongle TP-Link-TL-WN722N, use specifically for Linux.

---

Quote:

---

Originally Posted by jefx3

Wlan0 is a wifi connection owned by the hotel I'm currently staying.

Wlan1 (TP-Link-TL-WN722N) is my only wireless adapter dongle I'm using.

---

Wlan0 is not your hotel wifi. It is the interface name of your phone's internal wifi adapter. The SSID of your hotel wifi has its own name, most of the time it is the name of your hotel.
wlan1 is the interface name of your external wifi adapter. TP-Link-TL-WN722N is not a wifi dongle, it is a USB wifi adapter. There is a difference between the two.

You are providing incorrect information.

Can you post a screenshot of your network manager when you run it? your output of lsmod is empty and that's weird because there are lot of modules run which interact with your hardware.

Can you use internet from both of your wifi adapter? If there was a driver issue, you wouldn't be able to use your wifi adapter and browse internet. The fault can be with network manager itself.

Show the output of sudo network-manager status

@defalt

Thanks for the explanation regarding Wlan0 & wlan1. I am new at Linux.
nm-applet is located in the top right of my screen.
In terms or running, I only have “edit connection” enabled which does nothing when I click it.
The “x” displayed in the window applet remains constant regardless of the status.
It basically is stating the nm-applet is disable.
I am re sending the Network Manager screenshots (see Attachment).

I also tried nm-connection-editor, here is the results.
** (nm-connection-editor 12978) : Warning ** couldn't construct the client instance: Could not connect: No such file or directory. Failed to initialized the UI.


I am providing you with Network Manager status output.
root@kali:~# airmon-ng start wlan1

PHY Interface Driver Chipset

phy0 p2p0 ?????? Not pci, usb, or sdio
phy0 wlan0 ?????? Not pci, usb, or sdio
phy1 wlan1 ?????? Atheros Communications, Inc. AR9271 802.11n

(mac80211 monitor mode vif enabled for [phy1]wlan1 on [phy1]wlan1mon)
(mac80211 station mode vif disabled for [phy1]wlan1)

root@kali:~# ifconfig wlan1mon up
root@kali:~# sudo service network-manager start
[ ok ] Starting network connection manager: NetworkManager.
root@kali:~# sudo service network-manager status
[ ok ] NetworkManager is running.


What I can/cannot do using wlan0 and wlan1.
I cannot connect to the internet using Linux nethunter with wlan0 or wlan1 w/o a network manager.
Launched Firefox using wlan1, FF page opens but does not connect to the internet. Screen hangs on first page.

I can connect successfully to the internet using Linux on my XPS 13 laptop with wlan0 and wlan1.
Btw the Network Manager version used on my xps13 laptop is V1.4.2 .2 (10/2016).
The version I am currently using on kali nethunter V1.8.2.1(08/2017).

Just booting into my OPO Phone, I can connect to the internet using my interface wifi adapter wlan0.
Setting/select wireless network. This is w/o linux.

lsmod -Looked in Lib/Modules and it is indeed empty.
I did some research, another user of Nethunter found his modules in sys/modules. I listed these modules for your review. See Below for list of Modules. If you want me to open a particular folder from these modules let me know.


A thought:
Since network-manager is working for my xps13 laptop on V1.4.2.2 , should I try to downgrade and install Network Manager & Applet release version v1.4.2.2 on my Phone.

Jef.

list of Modules fron Sys/Modules
/sys/module/loop
/sys/module/adreno_idler
/sys/module/lowmemorykiller
/sys/module/lpm_levels
/sys/module/mac80211
/sys/module/maple_iosched
/sys/module/mdss_dsi
/sys/module/mdss_fb
/sys/module/mmcblk
/sys/module/mmc_core
/sys/module/mousedev
/sys/module/mpm_of
/sys/module/msm_adreno
/sys/module/msm_bus_core
/sys/module/msm_buspm_dev
/sys/module/msm_hotplug
/sys/module/msm_otg
/sys/module/msm_pm
/sys/module/msm_rmnet_bam
/sys/module/msm_serial_hs
/sys/module/msm_show_resume_irq
/sys/module/msm_thermal
/sys/module/mt20xx
/sys/module/nfc
/sys/module/nf_conntrack
/sys/module/nf_conntrack_amanda
/sys/module/nf_conntrack_ftp
/sys/module/nf_conntrack_h323
/sys/module/nf_conntrack_ipv4
/sys/module/nf_conntrack_irc
/sys/module/nf_conntrack_sane
/sys/module/nf_conntrack_tftp
/sys/module/ntfs
/sys/module/ocmem_audio
/sys/module/oprofile
/sys/module/peripheral_loader
/sys/module/pil_msa
/sys/module/ppp_generic
/sys/module/ppp_mppe
/sys/module/printk
/sys/module/process_reclaim
/sys/module/qpnp_charger
/sys/module/qpnp_regulator
/sys/module/qpnp_rtc
/sys/module/rcutree
/sys/module/rfkill
/sys/module/rpm_log
/sys/module/rpm_master_stat
/sys/module/rpm_regulator_smd
/sys/module/rpm_smd
/sys/module/rpm_stats

/sys/module/alarm_dev
/sys/module/asix
/sys/module/ath6kl_core
/sys/module/ath9k_htc
/sys/module/ath9k_hw
/sys/module/autosmp
/sys/module/bam_dmux
/sys/module/binder
/sys/module/block
/sys/module/bluetooth
/sys/module/bluetooth_power
/sys/module/blu_plug
/sys/module/brd
/sys/module/bridge
/sys/module/carl9170
/sys/module/cfg80211
/sys/module/ch
/sys/module/ci13xxx_msm
/sys/module/cifs
/sys/module/clock_krait_8974
/sys/module/configfs
/sys/module/cpu_boost
/sys/module/cpuidle
/sys/module/diagchar
/sys/module/dm_bufio
/sys/module/dm_verity
/sys/module/dwc3
/sys/module/dwc3_msm
/sys/module/event_timer
/sys/module/fuse
/sys/module/g_android
/sys/module/hci_smd
/sys/module/hci_uart
/sys/module/hid
/sys/module/hid_apple
/sys/module/hid_magicmouse
/sys/module/hid_ntrig
/sys/module/hidp
/sys/module/hid_prodikeys
/sys/module/i2c_qup
/sys/module/ipc_router
/sys/module/ipc_router_smd_xprt
/sys/module/ipv6
/sys/module/kernel
/sys/module/krait_regulator
/sys/module/l2tp_core

/sys/module/rt2x00lib
/sys/module/rt2x00usb
/sys/module/rt73usb
/sys/module/rt2500usb
/sys/module/rt2800lib
/sys/module/rt2800usb
/sys/module/rtl8192cu
/sys/module/sch_htb
/sys/module/scm_mpu
/sys/module/scm_pas
/sys/module/scsi_mod
/sys/module/sdhci
/sys/module/sdhci_msm
/sys/module/sg
/sys/module/sio_iosched
/sys/module/slimbus
/sys/module/smd
/sys/module/smd_pkt
/sys/module/smem
/sys/module/smem_log
/sys/module/smp2p
/sys/module/snd
/sys/module/snd_pcm
/sys/module/snd_soc_msm_stub
/sys/module/snd_soc_wcd9320
/sys/module/snd_timer
/sys/module/snd_usb_audio
/sys/module/spi_qsd
/sys/module/spmi
/sys/module/spmi_pmic_arb
/sys/module/spm_v2
/sys/module/sps_bam
/sys/module/spurious
/sys/module/state_notifier
/sys/module/stub_regulator
/sys/module/subsystem_notif
/sys/module/subsystem_restart
/sys/module/sweep2sleep
/sys/module/sync
/sys/module/tcp_bic
/sys/module/tcp_cubic
/sys/module/tcp_htcp
/sys/module/tcp_hybla
/sys/module/tcp_illinois
/sys/module/tcp_vegas
/sys/module/tda827x
/sys/module/tda8290
/sys/module/tda9887
/sys/module/tda18271
/sys/module/tea5761
/sys/module/tea5767
/sys/module/tuner_simple
/sys/module/tuner_xc2028
/sys/module/tz_log
/sys/module/uinput
/sys/module/usbcore
/sys/module/usbhid
/sys/module/usbserial
/sys/module/usb_storage
/sys/module/uvcvideo
/sys/module/videobuf2_core
/sys/module/vmpressure
/sys/module/wakeup
/sys/module/wcd9xxx_core
/sys/module/wcnsscore
/sys/module/wlan
/sys/module/workqueue
/sys/module/xc4000
/sys/module/xc5000
/sys/module/xhci_hcd
/sys/module/xpad
/sys/module/xt_qtaguid
/sys/module/xt_quota2
/sys/module/zen_iosched

Nethunter and kali linux are not same. Nethunter is built for Android architecture whereas kali linux is standard for all PCs. Although Nethunter ROM is compiled for One plus One yet i'm not able to locate the problem. It can be a problem with drivers or the network-manager app itself. You can try reinstalling it. You can earn experience in kali if you use it in your PC first.

@defalt.

Ok, I'll do this again, uninstall / reinstall network-manager & network-manager-gnome (Applet) latest version (1.8.2) onto Nethunter.
After install & nm-applet is still disabled, I'll create PC Linux on a pendrive for the xps 13 laptop.
Then install the latest network-manager & Applet (1.8.2). (Don't remember if network-manager is installed by default). Will see if I can connect with nm v1.8.2.

2 quick (Q's):
1. Given that the architecture is different, are there any NM related files I can compare between NH/PC that should be a consistent match after installing network-manager program?

2. The last time I uninstalled network-manager & network-manager-gnome from kali NH, the nm-applet still appeared in the top right of the notification bar.
Is their a command I can kill the network-manager applet to be completely removed from the panel?
I did apt-get purge network-manager-gnome cmd, but applet was still visible.

Thanks. Jef.

sudo service network-manager stop
sudo apt-get remove network-manager
sudo apt-get purge network-manager