Re: 4.6-RELEASE and Aironet DHCP

Doug Ambrisko <[email protected]>
Newsgroups gmane.os.freebsd.devel.mobile
Message-ID <[email protected]>
Aron Silverton writes:
| Hi all,
| 
| I'm not sure what I am doing wrong, but I have a 4.6-RELEASE notebook 
| with an Aironet 350 that I can't seem to configure via DHCP.  Static 
| configuration works fine.  I am on a network using LEAP and I am able to 
| authenticate without any problems.  I seem to receive information from 
| the DHCP server as I have a /var/db/dhclient.leases, but my an0 
| interface does not configure an address.  If I run dhclient an0, the 
| best that I get is inet 0.0.0.0 netmask 0xFF00000000 . . .  I do get a 
| populated /etc/resolv.conf.
| 
| In my rc.conf, I have:
| 
| pccard_enable="YES"
| pccard_ifconfig="DHCP" (I have tried both with and without this.)
| ifconfig_an0="DHCP"
| 
| My SSID is currently set in rc.conf.local but I'll move it to 
| start_if.an0 later.
| 
| After logging in, I do the following:
| 
| ancontrol -i an0 -L <user_name>
| <password>
| 
| One time the interface took the IP address, but I can't figure out why. 
|   After trying another dhclient an0 to see what would happen, I lost the 
| address and haven't gotten it back.

Hmm, you don't say how the SSID is set in rc.conf.local.  You have some
ordering problems.  Setting pccard_ifconfig=DHCP is going to make dhclient
fire off before you get to logon via LEAP.  This is the order you need
to do things:
	set the SSID
	logon via LEAP
	dhclient
otherwise things could go bad due to dhclient getting upset that it never
gets a lease back.  Starting another dhclient while the other one is 
hanging around doesn't work.  I'd suggest taking pccard_ifconfig out
of /etc/rc.conf and do everything by hand initially and then probably 
make a script to do the right thing.  Doing the LEAP logon after the fact
is going to result in trouble.

Doug A.

To Unsubscribe: send mail to [email protected]
with "unsubscribe freebsd-mobile" in the body of the message
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.