Date: Mon, 17 Mar 2008 12:17:55 -0700 From: Sam Leffler <sam@freebsd.org> To: "Alphons \"Fonz\" van Werven" <a.j.werven@student.utwente.nl> Cc: knowtree@aloha.com, freebsd-mobile@freebsd.org Subject: Re: ifconfig, wifi, and DHCP Message-ID: <47DEC3E3.8010900@freebsd.org> In-Reply-To: <47DEC0F0.5090100@student.utwente.nl> References: <200803170751.m2H7pMQW020344@yoda.pixi.com> <47DEC0F0.5090100@student.utwente.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Alphons "Fonz" van Werven wrote:
> knowtree@aloha.com wrote:
>
>> ifconfig_wi0="dhcp ssid Oz"
> [snip]
>> Can I use this quoted phrase when I invoke ifconfig manually? I see ssid
>> documented on the man page for ifconfig, but not dhcp.
>
> It's not ifconfig that calls DHCP, it's the network startup script
> /etc/rc.d/netif. It's also this script that reads rc.conf, not ifconfig.
>
> You can either call that script (which will call ifconfig AND DHCP for
> you)
> or call BOTH ifconfig and DHCP manually.
>
> In the former case:
> # /etc/rc.d/netif start
> should bring up the network.
>
> In the latter case:
> # ifconfig wi0 up
> should bring up the network,
> # ifconfig wi0 ssid Oz (plus any additional arguments)
> should get you associated to the network and then
> # dhclient wi0
> should get you an IP address.
>
> The ifconfig invokations can usually be combined into one, but if you
> don't
> call the netif script you'll have to invoke DHCP manually.
Actually, the problem is in the wi driver; it isn't properly integrated
with the 802.11 layer so devd isn't receiving the necessary events to
trigger starting dhclient. Noone seems to care about the driver and
it's hard to get worked up about 5 year old cards when a new one that
does 11g can be had for US$20.
Sam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47DEC3E3.8010900>