Re: ad-hoc wifi - network unreachable
On 2011-08-08 08:12:07 +0300, Volkan YAZICI wrote:
> On Sat, 06 Aug 2011 15:29:04 -0400, "Robert Blair Mason Jr." writes:
> > 1. Why do I have to call iwconfig twice?
> Because wicd overwrites it somehow?
No, wicd (the daemon) is stopped at that time.
> > 2. Is wicd at fault in this case? If so, should I file a bug report?
> If you can do it manually and wicd cannot by default, then, yes, you
> should, IMHO.
FYI, I use this script to connect to the same ad-hoc network, while
with wicd, it is necessary to re-enter all the connection parameters
at each connection, unless the ESSID is already visible (which isn't
the case if I want to start the network on my Debian machine first).
Unfortunately upstream doesn't want to fix this problem:
Vincent Lefèvre <firstname.lastname@example.org> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)