tags 562267 wontfix thanks Hi Vincent,
On Saturday 26 December 2009 21:32:15, Vincent Lefevre wrote: > Even though I have an ad-hoc network stored in wireless-settings.conf, > wicd-client doesn't show it if the ESSID isn't currently used by one > of the machines. Fortunately my other machine doesn't have such a > problem, so that I can start the network on it first. But two machines > using wicd won't be able to connect to each other without re-creating > the network by clicking on Network -> Create an ad-hoc network (and > entering all the parameters again). I asked about this issue to upstream on IRC, and Adam Blackburn (CCed) replied that this is probably a difference in views about usage of ad-hoc networks. They mean it as a temporary connection between two hosts and, as such, shouldn't be listed in the list of available networks, when one is not already active. I personally believe this isn't a strong and definitive wontfix, Adam you're welcome to post your opinion. Upstream is pushing development for the 1.7 branch, so they're not really in the mood of adding anything new. As always, patches are welcome, and I'd be glad to evaluate any, if you have, but I don't want to diverge much from upstream (you know, maintainance burden :)). > So, after scanning the networks, wicd should be able to show *all* > ad-hoc networks stored in wireless-settings.conf (there could be an > option for that). What kind of option do you have in mind? Have a nice evening, David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 ----|---- http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
signature.asc
Description: This is a digitally signed message part.
