Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
You can try increasing the timeout for dhclient in /etc/dhcp3/dhclient.conf. I've seen issues in the with dhclient timing out too early when using wpa_supplication on 802.1x wired networks. On Thu, Apr 28, 2011 at 9:53 AM, <johnmalloy-Wuw85uim5zDR7s880joybQ at public.gmane.org> wrote: > > I reinstalled both wpasupplicant and dhcp3-client. > > We are still not getting an ip address. > > It seems the wpasupplicant is taking too long to connect to the wireless access point and the dhclient is not working. > > If I run it manually, it works. > > Are there any other web sites/listservs for this issue? > > here is my /etc/rc.local file: > > > #!/bin/sh -e > # > # rc.local > # > # This script is executed at the end of each multiuser runlevel. > # Make sure that the script will "exit 0" on success or any other > # value on error. > # > # In order to enable or disable this script just change the execution > # bits. > # > # By default this script does nothing. > > /etc/opt/elo-ser/setup/elorc start > echo "/sbin/wpa_supplicant -ira0 -c/etc/wpa_supplicant/ra0.conf -d 2>&1 > /var/log/wpa_supplicant.ra0 "|/usr/bin/at now > sleep 180 > #echo "/sbin/dhclient -d -pf /var/run/dhclient-ra0.pid -lf /var/lib/dhcp3/dhclient-ra0.lease -sf /usr/local/scripts/dhclient-exit-hooks ra0 2>&1 > /var/log/dhclient.ra0"|at now > > > John Malloy > > johnmalloy AT comcast DOT net > > ----- Original Message ----- > From: "Tom Metro" <tmetro-blu-5a1Jt6qxUNc at public.gmane.org> > To: johnmalloy-Wuw85uim5zDR7s880joybQ at public.gmane.org > Cc: "L-blu" <discuss-mNDKBlG2WHs at public.gmane.org> > Sent: Wednesday, April 27, 2011 10:38:45 PM > Subject: Re: wireless configuration > > johnmalloy-Wuw85uim5zDR7s880joybQ at public.gmane.org wrote: >> Ubuntu 10.04 >> I have inherited someone else's config. > > Hmmm...unless you think the dhclient setup is usefully customized, you > might try the easy fix (after backing up /etc): > > sudo aptitude reinstall dhcp3-client > sudo aptitude reinstall wpasupplicant > > which might resolve the problem, if it is being caused by a missing hook > script. > > A quick browse suggests that /etc/network/if-up.d/wpasupplicant gets > called - probably on a pre-up event. It does it's thing, then does an > ifup. It then looks like Network Manager plays a role in triggering > dhclient, so you should probably review settings in there too. > > -Tom > > -- > Tom Metro > Venture Logic, Newton, MA, USA > "Enterprise solutions through open source." > Professional Profile: http://tmetro.venturelogic.com/ > _______________________________________________ > Discuss mailing list > Discuss-mNDKBlG2WHs at public.gmane.org > http://lists.blu.org/mailman/listinfo/discuss >
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |