re-plugging ethernet cable.
I am questioning about the behavior if I unplug and plug back in the same Ethernet cable. I receive the removed service, then when I plug it back in, it goes back online, but never do I get an event that tells me what the ip address, netmask, or gateway address is.When I receive the manager::ServicesChanged signal, and I parse the dict associated with it, the IPv4 sub-dict, doesn't contain any of these values. Later when I receive a service::PropertyChanged it is for that service changing state to 'online'. I never get an IPv4 packet telling me what the address is. Should I not be expecting these values to be sent to me before the state changes to online? Tom ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
wired network connect
All, To me it is interesting to note that when I have my network cable plugged in and have a dhcp connection, that if it for some reason becomes disconnected (ie, someone kicks the cord) and I re-plug the network cable, as I trace the reconnection, I get IPv4 settings events, but the packets never contain the IP address, subnet, or gateway, even after the state change reports that the connection is online. Is this the expected behavior? Or when it re-negotiates the connection shouldn't I get that information? Tom ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
follow-up
And as a follow up to my own question, we are running connman 1.29, and wpa_supplicant 2.0 Thanks again. ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
re-connecting to enterprise network
All, On 4/28, I posted a problem that I'm having with reconnecting to an enterprise network. The initial connection using the agent to prompt for the username/passphrase works fine, but the next connection fails with an Input/output error. The connection after that will again prompt from username/password, and connects. I've been delving into this, but have not as yet come up with a solution. I'm on connman 1.28. Is this something that can be looked at? Tom ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
re-connecting to enterprise network
All, I successfully connect to an enterprise AP, then at some point change to a different AP, and finally attempt to switch back to the original enterprise AP. The connection seems to be remembering the identity and passphrase that I originally used to connect, as the agent isn't called to prompt for them. At this point the association phase fails, and the debugging output is clear that it is moving from association to failure. The message error I get back from dbus is GDBus.Error:net.connman.Error.Failed: Input/output error. If, at this time I try yet again to connect to the enterprise AP no previous values are remembered, and the agent again prompts me for the identity and passphrase, and the connection completes. It would seem as if the failed attempt did not send the proper identity and passphrase. Is it possible to tell exactly what is being passed on the association phase? Tom ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
missing patch...
There was a patch in service.c __connman_service_set_passphrase that would let a provisioned service that was 8021x let the agent prompt for the username and passphrase. Now, in revision 1.28 there is a check in __connman_service_set_identity that seems to restore the old undesired behavior, but this time while checking for the passphrase. The check is now If (service-immutable || service-hidden) return; where currently in __connman_service_set_passphrase if (service-hidden) return -EINVAL; if (service-immutable service-security != CONNMAN_SWERVICE_SECURITY_8021X) return -EINVAL; If I am mis-reading the code, please let me know, but as of now, when I try to connect to an 8021x AP and expect the agent to prompt for the username and password it returns Error /net/connman/service/wifi_5c313e2c3958_70726976617465_managed_ieee8021x: Invalid arguments When I use connmanctl. Thanks Tom ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
dhcp issue
I've been seeing a dhcp issue lately that perhaps you can explain. I am using wireshark to watch the dhcp transaction progressing. I am on the wired (eth0) connection. I send a dhcp request, and I get two dhcp ack packets with the address info. Then I see a dhcpv6 request and response. However when I do ifconfig on my device I only have ipv6 information. I never get the IPv4 dict item in my events, only the IPv6 dict. This is only happening when I boot my system. If I go and make a dhcp request again (via a SetProperty call), everything goes fine, and I get the IPv4 dict in my PropertyChanged event, and ifconfig now displays the received IPv4 address. Any clues what could be happening here? Tom ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
Online status
When a service transitions from ready to online status, connman makes an http request to ipv[4,6].connman.net/online/status.html. I have been asked if this is a requirement or is there a way to prevent this from happening? Tom ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
Service state progression
I was wondering what the appropriate state progression for a wifi service that either gets shut off or goes out of range. From what I have seen, when I shut off an AP that I'm connected to, I get the following signals: Service.PropertyChanged association Service.PropertyChanged disconnect Service.PropertyChanged association all for the same service. Also, what causes a service to be listed in RemovedServices list when the Manager.ServicesChanged signal is emitted? Currently, after some timeout after a scan, all wireless services are being listed as removed. Tom ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
new issue in the 3.x bsp
Mike has reported an interesting error when he unplugs and plugs in a keyboard into his new setup. After he does this the user input routine is begins failing during a read from /dev/input/eventN where N is the event number. The error that the read reports is errno=19 (ENODEV - no such device). To me, this indicates that the devices are being re-enumerated, and the devices I had open and were using are no longer valid. This is not the correct behavior. Any event device that is open and being used should remain valid until closed. At this point this breaks the input from the IR remote and from the keypad, and needs to return to its prior behavior. Could you please enter a bug into jira regarding this? Thanks tom ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
oops
I apologize somehow my mail program sent this to this list as well as my company internal list... please dis-regard. Tom ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
RE: cancel connect with hidden psk network
Patrik, Yes, I'm calling net.connman.Service.Disconnect on a connection that is already in progress (the documentation seems to say that this is the proper way to cancel an in-progress connection). This is the output from connmanctl that most mirrors my use case: $ ./connmanctl Error getting peers: Method GetPeers with signature on interface net.connman.Manager doesn't exist connmanctl agent on Agent registered connmanctl services *AO Wiredethernet_b8ca3a807076_cable wifi_000272357823_hidden_managed_psk wifi_000272357823_hidden_managed_wep wifi_000272357823_hidden_managed_none EmployeeNet wifi_000272357823_456d706c6f7965654e6574_managed_ieee8021x I3 wifi_000272357823_4933_managed_psk X1 wifi_000272357823_5831_managed_none X3 wifi_000272357823_5833_managed_psk private wifi_000272357823_70726976617465_managed_ieee8021x public wifi_000272357823_7075626c6963_managed_none QABLK93 wifi_000272357823_5141424c4b3933_managed_psk MVRS-B95 wifi_000272357823_4d5652532d423935_managed_psk linksys wifi_000272357823_6c696e6b737973_managed_psk NPC_BLK111_FW wifi_000272357823_4e50435f424c4b3131315f4657_managed_psk tmptest wifi_000272357823_746d7074657374_managed_psk Test Shark wifi_000272357823_5465737420536861726b_managed_none Firewall Box wifi_000272357823_4669726577616c6c20426f78_managed_psk HP-Print-7e-LaserJet 200 wifi_000272357823_48502d5072696e742d37652d4c617365724a657420323030_managed_psk SORENSON5758 wifi_000272357823_534f52454e534f4e35373538_managed_psk connmanctl connect wifi_000272357823_hidden_managed_psk Agent RequestInput wifi_000272357823_hidden_managed_psk Name = [ Type=string, Requirement=mandatory, Alternates=[ SSID ] ] SSID = [ Type=ssid, Requirement=alternate ] Passphrase = [ Type=psk, Requirement=mandatory ] Hidden SSID name? QANVP2 Passphrase? At this point the user interface sends me an event that triggers the call to Disconnect(). The call to Disconnect completes as expected (returns a not connected error). My net.connman.Agent.RequestInput() routine then returns an empty dict. My net.connman.Agent.Disconnect routine is called. But the original net.connman.Service.Connect() call never returns. The one major difference between connmanctl and my use case is that in net.connman.Agent.RequestInput() only the hidden SSID is returned the first time, and net.connman.Agent.RequestInput is called again to prompt for the Passphrase. That is the point when the user triggers the call to Disconnect(). What I expect to be the proper behavior happens on visible access points with security, and open hidden access points. This only happens on the hidden_psk AP. I hope this helps. If you need more information, you can reply to me personally. Thank you. Tom -Original Message- From: connman [mailto:connman-boun...@connman.net] On Behalf Of Patrik Flykt Sent: Thursday, January 15, 2015 12:58 AM To: connman@connman.net Subject: Re: cancel connect with hidden psk network Hi, On Wed, 2015-01-14 at 22:55 +, Thomas Green wrote: I'm still having an issue when canceling a connection to a network that is 1) hidden, and 2) has psk security. The connection proceeds normally until the agent requests a password. At that point the user is telling me to cancel the connection. So, I call Cancel on the service. Cancel what? net.connman.Service has a Disconnect() function, are you calling that? Or are you saying that the UI replies with net.connman.Agent.Error.Canceled? The cancel call completes successfully, then the agent cancel handler is called. But at no time does the initial Connect call return (failed or otherwise). Can you run your use case entirely with connmanctl and post the printouts from that? Then we'd be in the clear with what the usage scenario is. Cheers, Patrik ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
RE: cancel connect with hidden psk network
I apologize for posting over my own question. It's just that the paragraph describing a second call to connman.agent.RequestInput() should be stricken. There are not two calls to that routine. -Original Message- From: connman [mailto:connman-boun...@connman.net] On Behalf Of Thomas Green Sent: Thursday, January 15, 2015 10:29 AM To: connman@connman.net Subject: RE: cancel connect with hidden psk network Patrik, Yes, I'm calling net.connman.Service.Disconnect on a connection that is already in progress (the documentation seems to say that this is the proper way to cancel an in-progress connection). This is the output from connmanctl that most mirrors my use case: $ ./connmanctl Error getting peers: Method GetPeers with signature on interface net.connman.Manager doesn't exist connmanctl agent on Agent registered connmanctl services *AO Wiredethernet_b8ca3a807076_cable wifi_000272357823_hidden_managed_psk wifi_000272357823_hidden_managed_wep wifi_000272357823_hidden_managed_none EmployeeNet wifi_000272357823_456d706c6f7965654e6574_managed_ieee8021x I3 wifi_000272357823_4933_managed_psk X1 wifi_000272357823_5831_managed_none X3 wifi_000272357823_5833_managed_psk private wifi_000272357823_70726976617465_managed_ieee8021x public wifi_000272357823_7075626c6963_managed_none QABLK93 wifi_000272357823_5141424c4b3933_managed_psk MVRS-B95 wifi_000272357823_4d5652532d423935_managed_psk linksys wifi_000272357823_6c696e6b737973_managed_psk NPC_BLK111_FW wifi_000272357823_4e50435f424c4b3131315f4657_managed_psk tmptest wifi_000272357823_746d7074657374_managed_psk Test Shark wifi_000272357823_5465737420536861726b_managed_none Firewall Box wifi_000272357823_4669726577616c6c20426f78_managed_psk HP-Print-7e-LaserJet 200 wifi_000272357823_48502d5072696e742d37652d4c617365724a657420323030_managed_psk SORENSON5758 wifi_000272357823_534f52454e534f4e35373538_managed_psk connmanctl connect wifi_000272357823_hidden_managed_psk Agent RequestInput wifi_000272357823_hidden_managed_psk Name = [ Type=string, Requirement=mandatory, Alternates=[ SSID ] ] SSID = [ Type=ssid, Requirement=alternate ] Passphrase = [ Type=psk, Requirement=mandatory ] Hidden SSID name? QANVP2 Passphrase? At this point the user interface sends me an event that triggers the call to Disconnect(). The call to Disconnect completes as expected (returns a not connected error). My net.connman.Agent.RequestInput() routine then returns an empty dict. My net.connman.Agent.Disconnect routine is called. But the original net.connman.Service.Connect() call never returns. The one major difference between connmanctl and my use case is that in net.connman.Agent.RequestInput() only the hidden SSID is returned the first time, and net.connman.Agent.RequestInput is called again to prompt for the Passphrase. That is the point when the user triggers the call to Disconnect(). What I expect to be the proper behavior happens on visible access points with security, and open hidden access points. This only happens on the hidden_psk AP. I hope this helps. If you need more information, you can reply to me personally. Thank you. Tom -Original Message- From: connman [mailto:connman-boun...@connman.net] On Behalf Of Patrik Flykt Sent: Thursday, January 15, 2015 12:58 AM To: connman@connman.net Subject: Re: cancel connect with hidden psk network Hi, On Wed, 2015-01-14 at 22:55 +, Thomas Green wrote: I'm still having an issue when canceling a connection to a network that is 1) hidden, and 2) has psk security. The connection proceeds normally until the agent requests a password. At that point the user is telling me to cancel the connection. So, I call Cancel on the service. Cancel what? net.connman.Service has a Disconnect() function, are you calling that? Or are you saying that the UI replies with net.connman.Agent.Error.Canceled? The cancel call completes successfully, then the agent cancel handler is called. But at no time does the initial Connect call return (failed or otherwise). Can you run your use case entirely with connmanctl and post the printouts from that? Then we'd be in the clear with what the usage scenario is. Cheers, Patrik ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
cancel connect with hidden psk network
I'm still having an issue when canceling a connection to a network that is 1) hidden, and 2) has psk security. The connection proceeds normally until the agent requests a password. At that point the user is telling me to cancel the connection. So, I call Cancel on the service. The cancel call completes successfully, then the agent cancel handler is called. But at no time does the initial Connect call return (failed or otherwise). I was going to post up the log file to pastebin, but they have a limit of 512 K and the log is 712 K. Is there another place that I can post the logfile? Is there further information needed? tom ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
cancelling an in process connection
All, I've had a new issue with cancelling an in process connection. When connecting to any visible network, the cancel works fine. But when trying to connect to a hidden network, and I cancel, The cancel call returns correctly, but the in-progress connect call never returns. Again, this only happens on a hidden network. Tom ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
RE: No carrier error
Currently the version of connman is 1.25, wpa_supplicant is v2.0, I am currently looking into the wifi driver to see if anything has changed there. Thanks -Original Message- From: connman [mailto:connman-boun...@connman.net] On Behalf Of Patrik Flykt Sent: Wednesday, January 07, 2015 4:28 AM To: connman@connman.net Subject: Re: No carrier error On Mon, 2015-01-05 at 23:16 +, Thomas Green wrote: I'll look at that, but it happens every single time I try to connect to the enterprise network And what versions of ConnMan and wpa_supplicant do you use? Is the WiFi driver upstream and have you checked that there hasn't been any recent fixes for the driver? Cheers, Patrik ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
RE: No carrier error
I'll look at that, but it happens every single time I try to connect to the enterprise network -Original Message- From: connman [mailto:connman-boun...@connman.net] On Behalf Of Patrik Flykt Sent: Monday, January 05, 2015 1:34 AM To: connman@connman.net Subject: Re: No carrier error Hi, On Tue, 2014-12-30 at 00:33 +, Thomas Green wrote: I have come across a very peculiar error. I can connect my system to an AP that is has no security, WEP security, WPA security with no issues. When I try to connect with ieee8021x, on the other hand, something very curious happens. I have kernel messages on, so I can see the local nic go into the association state after connman prompts for the username and passphrase. But then things hang there. After a couple of minutes (my timeout) The call fails. I look at the state of the connection and it says that it is in association mode. It never fails. At this point I attempt to force a disconnect of the ongoing association and I get an error that there is no carrier. At this point I try to terminate everything with severe prejudice. I stop connman, rfkill block then unblock the wireless device. I restart connman. The state of the wireless device is powered and ready. I try to initiate a scan, and I'm told that there is no carrier. I verify the state of the wireless is powered and ready. I can only get to where the wireless nic is usable only after a re-boot. What could be causing the no carrier error? wpa_supplicant has tied itself into a knot. Restart it and all should be ok. Cheers, Patrik ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
question about hidden access points
All, I am in an environment where I have multiple hidden access points. One is open, and two others have security enabled on them. If my user specifies the ssid of the hidden access point he wants to connect to, I have no way of telling which service path I need to call connect on, so I just pick whichever hidden service appears first. This leads the agent to sometimes prompting for the passphrase on the open one, or not being prompted on one that has security (and then the connection fails). Is there a way to know which service path my users ssid matches with before hand? Examples of the service path for my hidden access points: /net/connman/service/wifi_8833144faa55_hidden_managed_wep /net/connman/service/wifi_8833144faa55_hidden_managed_none /net/connman/service/wifi_8833144faa55_hidden_managed_psk If all I have is a user supplied ssid (the user shouldn't have to know in advance what kind of security it has, should he?) how do I select the correct service path issue connect on? Tom ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
crash in dbus
I am cross posting this to dbus and connman. I have an issue where I am trying
to make a call to connman using dbus and I get a crash in dbus.
I have a class that makes various connman calls, and also is set up to receive
messages asynchronously. So, In my class, I run a new thread that it's only
purpose is to create a g_main_loop, then run it, the main part of the class is
called when the user wants to initiate various events (for example a wireless
scan), and to respond to connman messages on dbus (scan complete).
I have a problem though that when I issue any connman calls after I've
initiated g_main_loop_run I get a crash. If I issue any calls (for example
GetProperties, Scan...), before I initiate the main loop, it functions just
fine. I don't have much of a stack trace to go on, but this is all I've got
at this point:
#0 0xb7d71114 in ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
#1 0xb7d6fbe7 in ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
#2 0xb7d6fc5b in ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
#3 0xb7d6ee47 in ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
#4 0xb7d6f727 in ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
#5 0xb7d55803 in ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
#6 0xb7d563b2 in dbus_connection_get_dispatch_status () from
/lib/i386-linux-gnu/libdbus-1.so.3
#7 0xb7d9df58 in ?? () from /usr/lib/i386-linux-gnu/libdbus-glib-1.so.2
#8 0xb7c339b3 in g_main_context_prepare () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#9 0xb7c342df in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#10 0xb7c3476b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
#11 0x08051373 in NetworkOjbect::NetworkLoop () at NetworkOjbect.cpp:1054
#12 0xb7ad0f70 in start_thread (arg=0xb74ffb40) at pthread_create.c:312
#13 0xb7a0770e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129
The entire function for NetworkLoop is as follows (again it's started in its
own thread):
int NetworkOjbect::NetworkLoop(size_t)
{
GMainLoop *pMainNetworkLoop;
pMainNetworkLoop = g_main_loop_new(NULL, 0);
if (!pMainNetworkLoop)
{
Trace(Could not start main network loop\n);
exit(-1);
}
g_main_loop_run(pMainNetworkLoop);
return(0);
}
Is there something with my logic in running the main loop in its own thread?
Is there a better way to debug this?
Thanks for your input.
Tom
___
connman mailing list
connman@connman.net
https://lists.connman.net/mailman/listinfo/connman
crash while cancelling an in-progress connection
I have a situation where the user has sent a connection to an open AP. Before connman returns that the connection has completed, the user attempts to cancel the connection. According to the documentation the net.connman.Service.Disconnect can also be used to abort a previous connection attempt via the Connect method. The issue is that when I attempt this, that after I make the dbus call to disconnect, and before the disconnect call returns I get a segmentation fault. The stack is hammered enough that the only traceback information is that it happens in libdbus-1.so.3. This only happens when I try to cancel a connection on an open AP. Cancelling all other attempts have worked to this point. Is there something that I need to set a guard around so this doesn't happen? Thanks Tom ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
Registering for a signal
I'm trying to register for the PropertiesChangedsignal for my wired device. The code looks like this: proxy = dbus_g_proxy_new_for_name(dbus_connection, net.connman, service_name, net.connman.Service); dbus_g_object_register_marshaller(marshal_VOID__STRING_VARIANT, G_TYPE_NONE, G_TYPE_STRING, G_TYPE_VARIANT, G_TYPE_INVALID); dbus_g_proxy_add_signal(proxy, PropertyChanged, G_TYPE_STRING, G_TYPE_VALUE, G_TYPE_INVALID); dbus_g_proxy_connect_signal(proxy, PropertyChanged, G_CALLBACK(service_property_changed_callback), this, NULL); When I add the signal I get the message: ** (process:23404): WARNING **: No marshaller for signature of signal 'PropertyChanged' Is the signature different than the documentation states? SignalsPropertyChanged(string name, variant value) This signal indicates a changed value of the given property. This signal is documented identically to the signal of the same name in the bluez stack, and the same code works there. Am I missing something basic here? TIA Tom ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
RE: Connecting to ieee8021x access point
Patrik, The login credentials are different for each person that attaches. There has to be a configuration file to describe the eap and phase2 scheme being used, but the first connection still prompts for the username and passphrase. Thanks, Tom -Original Message- From: connman [mailto:connman-boun...@connman.net] On Behalf Of Patrik Flykt Sent: Friday, September 12, 2014 5:58 AM To: connman@connman.net Subject: Re: Connecting to ieee8021x access point On Thu, 2014-09-11 at 18:58 +, Thomas Green wrote: All, I'm currently running connman 1.21. I'd upgrade if possible. Just looking at the release notes for newer releases I can discover quite a few fixes to DHCP for example. I am trying to connect to a ieee8021x access point. It never connects saying that the credentials that I'm supplying is incorrect. I've traced this down to __connman_service_set_passphrase where the service-immutable value is true, so it never sets the passphrase or attempts to connect. What, (and why) would the immutable value be set to true, service-immutable is set if the service is described in a configuration file. The service configuration file is supposed to contain all values needed and should therefore not be modifiable. Is the user name and passphrase different for all users of this ieee8021x AP? Or is the passphrase a one-time token that will change from one login to the next? Maybe we have forgot these kinds of passphrase schemes for the ieee8021x ones in combination with configuration files... Cheers, Patrik ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
Connecting to ieee8021x access point
All, I'm currently running connman 1.21. I am trying to connect to a ieee8021x access point. It never connects saying that the credentials that I'm supplying is incorrect. I've traced this down to __connman_service_set_passphrase where the service-immutable value is true, so it never sets the passphrase or attempts to connect. What, (and why) would the immutable value be set to true, and why would this prevent the passphrase to be set, and the connection attempt to proceed? Or, was this a problem that has been fixed in a later release? What, at this point would be the best way to proceed? Tom ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
ieee8021x connection issue
All,
I am trying to establish a connection with an AP that identifies as a ieee8021x
access point. When I issue the connect call to it, it does not make a request
to my agent for the username/passphrase (ie, it doesn't call the RequestInput
method), and returns with a GError of {domain = 78, code = 32, message =
0x41002360 Invalid arguments}. Now I can make a connection to an access
point utilizing an AP that is a managed_psk access point, and it also makes the
correct call to the RequestInput agent method. Why would it not make the
connect call correctly for the ieee801x but correctly for the managed_psk AP?
I'm running an unpatched version of 1.21
Tom
___
connman mailing list
connman@connman.net
https://lists.connman.net/mailman/listinfo/connman
RE: ieee8021x connection issue
Hate to reply to my own mail stupid mistake on my part. Hadn't set up the
configuration file for the ieee8021x connection. Sorry for the distraction.
Tom
-Original Message-
From: connman [mailto:connman-boun...@connman.net] On Behalf Of Thomas Green
Sent: Wednesday, August 06, 2014 9:31 AM
To: connman@connman.net
Subject: ieee8021x connection issue
All,
I am trying to establish a connection with an AP that identifies as a ieee8021x
access point. When I issue the connect call to it, it does not make a request
to my agent for the username/passphrase (ie, it doesn't call the RequestInput
method), and returns with a GError of {domain = 78, code = 32, message =
0x41002360 Invalid arguments}. Now I can make a connection to an access
point utilizing an AP that is a managed_psk access point, and it also makes the
correct call to the RequestInput agent method. Why would it not make the
connect call correctly for the ieee801x but correctly for the managed_psk AP?
I'm running an unpatched version of 1.21
Tom
___
connman mailing list
connman@connman.net
https://lists.connman.net/mailman/listinfo/connman
___
connman mailing list
connman@connman.net
https://lists.connman.net/mailman/listinfo/connman
IPv6 Addresses
I seem to be having a problem with IPv6. I am using the scripts supplied with
connman to set the IPv6 address method to 'auto'. This is a cap of what I did:
#ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:a0:0c:ed:00:35
inet addr:10.20.187.12 Bcast:10.20.187.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST DYNAMIC MTU:1500 Metric:1
RX packets:43488 errors:0 dropped:0 overruns:0 frame:0
TX packets:16410 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:44676304 (44.6 MB) TX bytes:1478906 (1.4 MB)
Interrupt:130 Memory:1000-1002
# ./set-ipv6-method ethernet_00a00ced0035_cable auto
Setting method auto for ethernet_00a00ced0035_cable
New IPv6.Configuration: {'Method': dbus.String(u'auto', variant_level=1)}
#ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:a0:0c:ed:00:35
inet addr:10.20.187.12 Bcast:10.20.187.255 Mask:255.255.255.0
inet6 addr: fe80::2a0:cff:feed:35/64 Scope:Link
UP BROADCAST RUNNING MULTICAST DYNAMIC MTU:1500 Metric:1
RX packets:43488 errors:0 dropped:0 overruns:0 frame:0
TX packets:16410 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:44676304 (44.6 MB) TX bytes:1478906 (1.4 MB)
Interrupt:130 Memory:1000-1002
# ./list-services
[ ethernet_00a00ced0035_cable ]
IPv6.Configuration = { Method=auto Privacy=disabled }
AutoConnect = true
Name = Wired
Nameservers = [ 10.20.35.16 192.168.250.16 192.168.253.16 ]
Provider = { }
Favorite = true
Domains.Configuration = [ ]
Timeservers.Configuration = [ ]
State = online
Proxy = { Method=direct }
Nameservers.Configuration = [ ]
IPv4 = { Netmask=255.255.255.0 Gateway=10.20.187.1 Method=dhcp
Address=10.20.187.12 }
Timeservers = [ 10.20.187.1 ]
IPv6 = { }
Domains = [ SORENSON.COM ]
Ethernet = { Interface=eth0 MTU=1500 Method=auto Address=00:A0:0C:ED:00:35 }
Security = [ ]
Proxy.Configuration = { }
Type = ethernet
Immutable = false
IPv4.Configuration = { Method=dhcp }
As you can see, list-services lists the IPv6.Configuration method as auto, but
does not list anything in the IPv6 dict, though ifconfig lists the address. Is
this not fully supported yet? I am running connmand version 1.20
Tom
___
connman mailing list
connman@connman.net
https://lists.connman.net/mailman/listinfo/connman
RE: Strange Enterprise bug
Thank you for letting me know. I will keep an eye on this one. Tom -Original Message- From: connman-boun...@connman.net [mailto:connman-boun...@connman.net] On Behalf Of Patrik Flykt Sent: Friday, October 11, 2013 5:04 AM To: connman@connman.net Subject: Re: Strange Enterprise bug On Tue, 2013-10-01 at 23:30 +, Thomas Green wrote: I am re-submitting this item from the tester I have here on site. I reported this before, and it was thought that the problem was with an older version of connman. I have now upgraded to 1.18, and my tester says that this is still an issue. His description is perhaps better than mine, so I will attach his email to me for clarity. I added this to JIRA so it's not forgotten, filed as https://01.org/jira/browse/CM-653 Cheers, Patrik ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
Strange Enterprise bug
I am re-submitting this item from the tester I have here on site. I reported this before, and it was thought that the problem was with an older version of connman. I have now upgraded to 1.18, and my tester says that this is still an issue. His description is perhaps better than mine, so I will attach his email to me for clarity. Tom From: Isaac Goodrich Sent: Thursday, September 12, 2013 2:20 PM To: Thomas Green Subject: Strange Enterprise bug When re-connecting to an Enterprise network after previously being connected to it, there is an occasional failure to re-connect. If you try to re-connect again, there is a prompt for credentials. If bad credentials are given, it appears as though connection was successful and the status shows online, but network connectivity is not present. 1. Successfully connect to Enterprise network 2. Disconnect 3. Re-connect 4. Repeat steps 2-3 until Operation aborted error occurs. Seems to occur when the re-connect is done too quickly after disconnecting. 5. Try to re-connect (this time, you are prompted for username and password) 6. Enter invalid credentials When this happens, there is no failure given and it appears as though it was successful. The status shows online. The problem is that there is not a connection. There is no IP address and DNS requests don't come back. At this point, if I disconnect from the network and re-connect, things are successful again and there is a connection. This means that the original good credentials, which were cached, are still being used on subsequent connection attempts during the session. I can't think of what would cause the problem on the connection attempt when entering bad credentials after an operation aborted error. The AP does not return a failure, so that seems to indicate that the cached good credentials are being sent, which also explains Connman not returning an error. Something causes Internet not to work in this scenario. My opinion is that to fix the issue, the cached credentials should be deleted after a failure to connect, so that the new credentials that are entered are the ones that get sent. Isaac Goodrich Software Engineer in Test - nVP Sorenson Communications CONFIDENTIALITY NOTICE. This e-mail transmission and any documents, files or previous e-mail messages attached to it, may contain confidential and proprietary information. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this message is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify me by e-mail at igoodr...@sorenson.commailto:gbeckm...@sorenson.com and destroy the original transmission and its attachments without reading them or saving them to disk. ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
RE: Calculating signal strength
It would be a wext based one. -Original Message- From: connman-boun...@connman.net [mailto:connman-boun...@connman.net] On Behalf Of Patrik Flykt Sent: Thursday, August 22, 2013 12:16 AM To: connman@connman.net Subject: Re: Calculating signal strength Hi, On Wed, 2013-08-21 at 15:15 +, Thomas Green wrote: bss-signal all seem to be actual signal strength values, ie, all of them in the range from 50 to 100, Which WiFi driver is this? Is it netlink or an old wext based one? Cheers, Patrik ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
RE: Calculating signal strength
Hey Patrik, For the use case that I've been experiencing is that the values returned in bss-signal all seem to be actual signal strength values, ie, all of them in the range from 50 to 100, so regardless of the signal strength, it always reports 100%. By not adding the value 120 to the signal strength, I get values that (roughly) match with what my phone reports to me. Tom -Original Message- From: connman-boun...@connman.net [mailto:connman-boun...@connman.net] On Behalf Of Patrik Flykt Sent: Wednesday, August 21, 2013 2:07 AM To: connman@connman.net Subject: Re: Calculating signal strength Hi, On Tue, 2013-08-20 at 20:31 +, Thomas Green wrote: In the function calculate_strength (in the file plugins/wifi.c, line 1736) the value returned is the maximum of 100, or 120 +g_supplicant_network_get_signal(supplicant_network). That indicates that anything with a signal of greater than (-20) will report a strength of 100. Is this supposed to be the case? The only explanation I have is that for all practical purposes any signal attenuation between 0 and -20 is a 100% good signal. This traces back to commit d665a37c4837e35741c14879140632d6c61f3d87 in 2009, it seems. Do you have a specific use case in mind? Should it just not report the value returned by g_supplicant_network_get_signal? The value returned there is just the value of network-signal, which is the stored value of bss-signal. If we'd want to be smart about signal strength, the strength should be reacted upon (== services sorted) and updated via Service D-Bus API to clients only after it has changed with 10 units or so from its previous value. Cheers, Patrik ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
connecting to ieee8021x
I'm having an interesting issue when connecting to an enterprise AP. When first connecting I'm prompted for the username and passphrase in the agent, and all works fine. If I then disconnect then try to re-connect, the connection fails the first attempt, then connects the second attempt. Every other connection attempt fails. I connect, disconnect, connect (fails), connect(succeeds), disconnect, connect(fails), connect(succeeds), and so on. If I let a -great- deal of time pass between the disconnect and the next connect attempt, it will work first attempt. I have wireshark traces of both a successful and unsuccessful connection attempt. Any idea what causes this behavior? Tom ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
Calculating signal strength
In the function calculate_strength (in the file plugins/wifi.c, line 1736) the value returned is the maximum of 100, or 120+g_supplicant_network_get_signal(supplicant_network). That indicates that anything with a signal of greater than (-20) will report a strength of 100. Is this supposed to be the case? Should it just not report the value returned by g_supplicant_network_get_signal? The value returned there is just the value of network-signal, which is the stored value of bss-signal. Tom ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
