Discussion:
WPA2 connection problem
(too old to reply)
Wawrzek Niewodniczanski
2015-10-19 09:57:23 UTC
Permalink
Hi,

I try to connected to Enterprise WPA2 and what I see in console is:
'Could not connect net.connman.Error.InvalidArguments: Invalid arguments'

I'm using:
connmand - 1.30 from Arch repo

How can I debug it?

Thanks,
Wawrzek
--
Dr Wawrzyniec Niewodniczański or Wawrzek for short
PhD in Quantum Chemistry & MSc in Molecular Engineering
WWW: http://wawrzek.name E-MAIL: ***@wawrzek.name
Linux User #177124
Patrik Flykt
2015-10-19 10:45:29 UTC
Permalink
Hi,
Post by Wawrzek Niewodniczanski
'Could not connect net.connman.Error.InvalidArguments: Invalid
arguments'
WPA2 EAP networks need to be configured using doc/config-format.txt.
After that ConnMan may ask a username/passphrase so and Agent is advised
to be running. The simplest Agent is connmanctl run with 'agent on'.

Cheers,

Patrik
Wawrzek Niewodniczanski
2015-10-21 09:55:19 UTC
Permalink
Post by Patrik Flykt
Hi,
Post by Wawrzek Niewodniczanski
'Could not connect net.connman.Error.InvalidArguments: Invalid arguments'
WPA2 EAP networks need to be configured using doc/config-format.txt.
After that ConnMan may ask a username/passphrase so and Agent is advised
to be running. The simplest Agent is connmanctl run with 'agent on'.
Hi,

I'm using connmanctl, Agent is one. I configured my WPA2 Enterprise in
/var/lib/network_name.config but I still get 'Invalid arguments' after
connection attempt to the network.

My configuration is:

[service service_name]
Type = wifi
SSID = ServiceName
EAP = peap
Phase2 = MSCHAPV2
Identity = user_name

Network, service and user names are actual names. I started connmand
in nodaemon mode and see

connmand[712]: Config file /var/lib/connman/network_name.config does
not contain any configuration that can be provisioned!

What do I do wrong?

Wawrzek
--
Dr Wawrzyniec Niewodniczański or Wawrzek for short
PhD in Quantum Chemistry & MSc in Molecular Engineering
WWW: http://wawrzek.name E-MAIL: ***@wawrzek.name
Linux User #177124
Patrik Flykt
2015-10-21 10:10:21 UTC
Permalink
Post by Wawrzek Niewodniczanski
Post by Patrik Flykt
Hi,
Post by Wawrzek Niewodniczanski
'Could not connect net.connman.Error.InvalidArguments: Invalid arguments'
WPA2 EAP networks need to be configured using doc/config-format.txt.
After that ConnMan may ask a username/passphrase so and Agent is advised
to be running. The simplest Agent is connmanctl run with 'agent on'.
Hi,
I'm using connmanctl, Agent is one. I configured my WPA2 Enterprise in
/var/lib/network_name.config but I still get 'Invalid arguments' after
connection attempt to the network.
/var/lib/connman/network_name.config
Post by Wawrzek Niewodniczanski
[service service_name]
[service_XXXX] here, see doc/config-format.txt, "Service sections
[service_*]" part.

HTH,

Patrik
Wawrzek Niewodniczanski
2015-10-21 15:40:32 UTC
Permalink
[...]

Hello,
Post by Patrik Flykt
Post by Wawrzek Niewodniczanski
[service service_name]
[service_XXXX] here, see doc/config-format.txt, "Service sections
[service_*]" part.
I fixed that, but still have problem in connecting to enterprise WPA2.
I stopped connmand service and start in nodeamon mode then I saw that
connman complains on my SSID. Looking at my configuration I noticed
that mixed Name and SSID values.

Now I can connect.

Thanks for support,
Wawrzek
--
Dr Wawrzyniec Niewodniczański or Wawrzek for short
PhD in Quantum Chemistry & MSc in Molecular Engineering
WWW: http://wawrzek.name E-MAIL: ***@wawrzek.name
Linux User #177124
Loading...