Open apinter opened 9 years ago
@asquared Would adding a password field to pass along to wpa_supplicant will be sufficient here? It wouldn't seem to me to be that simple...
It looks like the key_mgmt option needs to be set to WPA-PSK and the option for the password is then called "psk", not "password".
I would also advocate for making this a new class of connection, perhaps a subclass of WirelessConnection, or an object that plugs into WirelessConnection. There are many different kinds of wireless authentication that might be in use in a Concerto deployment, so we want to factor this in a way that allows new methods to be added easily.
For reference, here's the man page for wpa_supplicant.conf: http://manpages.ubuntu.com/manpages/hardy/man5/wpa_supplicant.conf.5.html
Guys, the question is not exactly about wpa_suppilcant, I know how to configure it, was just posting a silly example (was lazy to copy from my vm, sorry). The problem what I have unfortunately is that I'm not able to define a variable to the password field on the GUI which would pass the input to the wpa_supplicant eventually. Think it would be awesome to have a function like that.
Hi Guys,
Started to play around with Concerto a few days ago, it is awesome, but noticed that it can, but out of the box can't connect to encrypted wireless networks (wpa personal) so I added a field in ../application/views/netsettings.erb which is fine and tried to add an instance variable in ../lib/bandshell/netconfig.rb @pwas:
class WirelessConnection def initialize(args={}) @ssid = args['ssid'] || '' @interface_name = args['interface_name'] if args['interface_name'] @wpa_config_file = '/tmp/wpa_supplicant.concerto.conf' @pwas = args['pwas'] || '' end
This clearly not working, can you please advise where can I set this variable to make sense?
Thanks in advance!