Paul Fox @ 2005-12-23 (Friday), 08:25 (-0500) > > > does your script work if "someplace" contains spaces? can > > > /etc/network/interfaces deal with that syntax? a quick look > > > at your diff makes me think that it won't. > > > > The problem here is that ifupdown does not allow spaces in interface > > names. If one needs to connect to SSIDs containing spaces, one could > > either use its BSSID or a mapping script. > > > > One could argue a mapping script should always be used, but I like the > > simplicity of having wpasupplicant just working after installing it. > > but only "just works" for you. :-)
No, "just works" as in functional upon installation for anyone. On my computer it now works because all the configuration and reading I had to do. My intentions with trying to fix this bug report is to save others from having to do more work than really needed. Thinking more of it, splitting the action script into a simpler action script and a mapping script would probably be the way to go. That way everything could just work with networks that do not need special configuration, and those that do require that can simply be made functional without having two configuration interfaces doing the same thing. > one solution is to do something like that done by "iwgetid --scheme", > which compresses out all non-alphanumerics from the SSID, so that > it can be used for purposes such as this. i suspect this could > be done quite simply in your script by a small sed or tr command. My first question is what characters are actually allowed in an interface name? Would it be safe to assume it is limited to [A-Za-z0-0]? Simply removing not allowed characters would be trivial, but it would be even better transcoding them in some way. Any ideas on a working one liner? > but this only works for known nets -- not for the corner coffee shop, > whose SSID you don't know in advance. Complicated networks will always require some grade of manual configuration, but that configuration should be as easy as possible to perform. I would expect any coffee shop network to be usable with only a dhcp client, thus not needing any configuration at all. (The ones I have encountered have all been either completely open or requiering a one time password that can't be automated anyway) > another, possibly more complete solution, would be for > wpa_supplicant to allow configuring an "id" string along with the > network when it is described in wpa_supplicant.conf. this > identity (which could default to the SSID) would be passed to the > wpa_cli as an argument along with the connect/disconnect event. > the identity string, since it would be specified by the user in > the wpa_supplicant config, is guaranteed to be useful in a simple > ifup management script such as yours. (i.e., the id i specified > in my wpa_supplicant.conf file whould match a mapping name in > /etc/network/interfaces. it would be the key that links the two > config files.) Such changes to wpa_supplicant.conf can't really be motivated when it is simple enough to archive the same result without them, I think. -- /Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
