Hi Jiajia, > >> Using git 6fc258703, I can use set-passhprase and select-netwok to > >> associate a WEP network. However I found that the ConnMan/Dhclient > >> can not assign the IP automatically. I am running it on Ubuntu > >> System. > > > > my test system is running Ubuntu 8.10 and that works fine. However > > with WEP you have to be 100% sure you enter the right key. If it is > > wrong, it will still associate, but then DHCP will fail. > > > > I have another problem here. Set-passphrase uses the default key index 1. How > could I associate a WEP network with other key index, for example, key[2], > key[3] or key[4]?
you don't. We just only use key[1]. What do you wanna do with the other key sets? That is useless stuff from the good old WEP times. It is a broken design anyway. > Using set-passphrase and select-network, I am able to associate a WPA-PSK > network as well. But I still fail to associate a WPA-EAP network because not > knowing the method of setting WPA certs. Could you give me any hint? The WPA-Enterprise support is currently not implemented. So while wpa_supplicant supports it, there is no method to set the certs or username/password combination to make this work. This needs extra work since we have to design a proper security framework around this. So when using pre-shared keys (PSK) it really makes no sense to protect these with your life. They are clear text to begin with, but for the certs or username/password combination that is different. These are really personal details. And don't get confused with WPA-Personal and WPA-Enterprise from the wording. The WPA-Enterprise has the personal details that are worth protecting :) Regards Marcel _______________________________________________ connman mailing list [email protected] https://lists.moblin.org/mailman/listinfo/connman
