On 2011-08-06 15:29:04 -0400, Robert Blair Mason Jr. wrote: > Thanks for your help! I was finally able to get it to work with the > following, which I put into a script: > > /etc/init.d/wicd stop > ifconfig $IFACE down > iwconfig $IFACE essid $ESSID mode Ad-Hoc channel $CHANNEL > ifconfig $IFACE up $IPADDR > iwconfig $IFACE essid $ESSID mode Ad-Hoc channel $CHANNEL > route add default gw $DEFAULTGW $IFACE > > Adding google dns into resolv.conf allowed me to successfully get > internet. I now have a couple of questions: > > 1. Why do I have to call iwconfig twice?
I don't know. I just noticed that if I used only one of them, it didn't work (IIRC, ifconfig ... up ... fails without the first iwconfig, and ifconfig ... up ... resets iwconfig settings, somethink like that). > 2. Is wicd at fault in this case? If so, should I file a bug report? No, because I stop wicd first to avoid bad interactions between wicd (which can do things automatically) and this script: it is bad to have 2 different active methods to do a wifi connection at the same time. -- Vincent Lefèvre <vinc...@vinc17.net> - 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) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110808121905.ga11...@xvii.vinc17.org
