WIFI with Connmann All Versions

[Moderator ModdIt]

While searching for a solution to blocked wifi on a netbook where rfkill did not work I came across some information
from archwiki. Many thanks to the Archers who with so much in depth knowledge have helped me in many situations.
URL to the full article is at end of post !.
Hopefully this will be of help to other antiX users with wifi problems.

$ connmanctl enable wifi was in my case the key to unblocking.

————————————————————————————————————————-
# Warning: connman grabs rfkill events. It is most likely impossible to use rfkill or bluetoothctl to (un)block devices,
yet hardware keys may still work.[1] Always use connmanctl enable|disable
————————————————————————————————————————–

Hardware interfaces are referred to as Technologies by ConnMan.

To list available technologies run:

$ connmanctl technologies

To get just the types by their name one can use this one liner:

$ connmanctl technologies | awk ‘/Type/ { print $NF }’

Note: The field Type = tech_name provides the technology type used with connmanctl commands

To interact with them one must refer to the technology by type. Technologies can be toggled on/off with:

$ connmanctl enable technology_type

To toggle on wifi:

$ connmanctl enable wifi

and:

$ connmanctl disable technology_type

To toggle off wifi:

$ connmanctl disable wifi
———————————————————————————————————————–

Using connmann interface for diagnostic or connection:

$ connmanctl scan wifi

To list the available networks found after a scan run :

$ connmanctl services

(example outputbelow)
*AO MyNetwork wifi_dc85de828967_68756773616d_managed_psk
OtherNET wifi_dc85de828967_38303944616e69656c73_managed_psk
AnotherOne wifi_dc85de828967_3257495245363836_managed_wep
FourthNetwork wifi_dc85de828967_4d7572706879_managed_wep
AnOpenNetwork wifi_dc85de828967_4d6568657272696e_managed_none

To connect to an open network, use the second field beginning with wifi_:
$ connmanctl connect wifi_dc85de828967_4d6568657272696e_managed_none

For password protected wifi:

For protected access points you will need to provide some information to the ConnMan daemon, at the very least a password or a passphrase.

The commands in this section show how to run connmanctl in interactive mode, it is required for running the agent command. To start interactive mode simply type:

$ connmanctl

You then proceed almost as above, first scan for any Wi-Fi technologies:

connmanctl> scan wifi

To list services:

connmanctl> services

Now you need to register the agent to handle user requests. The command is:

connmanctl> agent on

You now need to connect to one of the protected services. To do this easily, just use tab completion for the wifi_ service. If you were connecting to OtherNET in the example above you would type:

connmanctl> connect wifi_dc85de828967_38303944616e69656c73_managed_psk

The agent will then ask you to provide any information the daemon needs to complete the connection. The information requested will vary depending on the type of network you are connecting to. The agent will also print additional data about the information it needs as shown in the example below.

Agent RequestInput wifi_dc85de828967_38303944616e69656c73_managed_psk
Passphrase = [ Type=psk, Requirement=mandatory ]
Passphrase?

Provide the information requested, in this example the passphrase, and then type:

connmanctl> quit

If the information you provided is correct you should now be connected to the protected access point.
Settings. Warning here, some special characters are not always accepted in passwords.

On old hardware:
For a 40 bit WEP network the password is 5-characters.
For a 128 bit WEP network the password is 13-characters.
The now usual WPA uses either a passphrase (a shared secret) that is comprised of 8 to 63 characters or a fixed-length of 64 HEX characters.

For networks the user connects to often Settings and profiles are automatically created . They contain fields for the passphrase, essid and other
information. Profile settings are stored in directories under /var/lib/connman/ by their service name.

To view all network profiles run this command from root shell:

# cat /var/lib/connman/*/settings

VPN settings: # cat /var/lib/connman-vpn/.

https://www.linuxsecrets.com/archlinux-wiki/wiki.archlinux.org/index.php%3Ftitle=Connman&mobileaction=toggle_view_desktop.html
Content is available under GNU Free Documentation License 1.3 or later but I have only used some excerpts as the work was done
by others.

• This topic was modified 1 week, 3 days ago by ModdIt.

[Member Xecure]

Xecure wrote:

All interfaces of connman (in antiX full cmst, in antiX base, connman-ui) are comunicating with the real connman service conmanctl

If you launch in terminal
connmanctl
You will see that the terminal input has changed. Inside that change, see what
technologies
outputs. It should tell you all detected interfaces and if they are on/off.
For wlanX interfaces, it usually identifies them as “wifi”. We need to know how it identifies your eth1 interface.

Let us imagine that it identifies it as “wifi”

/net/connman/technology/wifi
  Name = Wifi
  Type = wifi
  Powered = False

We need to enable it
enable wifi
and check technologies again

/net/connman/technology/wifi
  Name = Wifi
  Type = wifi
  Powered = True
  Connected = False

To make sure it can scan, you run
scan wifi
If it spits out an error, lets try restarting connman. Exit connmanctl with
quit
and restart connman service
sudo service restart connman

Then again enter connmanctl and scan again

connmanctl
> scan wifi

If everything goes well, you will see that scan was a success, and see your wireless connections with
services

If it is there, exit connmanctl with quit and try to use the connman gui to connect to your wireless AP.

If there is no wifi option, paste the connmanctl technologies output so we may see.

• This reply was modified 1 week, 3 days ago by Xecure.

[Author]

Posts