Re: wpa_supplicant before dhcpcd

[David Young <dyoung%pobox.com@localhost>]

On Mon, Aug 18, 2008 at 01:44:44PM -0400, matthew sporleder wrote:
> On Mon, Aug 18, 2008 at 12:33 PM, Roy Marples <roy%marples.name@localhost> 
> wrote:
> > On Fri, 2008-08-15 at 15:09 +0200, Joerg Sonnenberger wrote:
> >> On Thu, Aug 14, 2008 at 09:15:58PM -0400, matthew sporleder wrote:
> >> > How do I convince wpa_supplicant to start before dhcpcd?  My rc.conf
> >> > looks like this:
> >>
> >> If you don't mind it connecting to open wireless networks, you can just
> >> let it wait. It should get a new lease once wpa_supplicant decided on
> >> the network to use.
> >>
> >> In fact, it might be a good idea to hook up wpa_supplicant in a similiar
> >> way as dhcpcd, since it is too per-interface.
> >
> > You may wish to consider shipping a default /etc/wpa_suppliant.conf
> > which looks like so
> >
> > # This is a network block that connects to any unsecured access point.
> > # We give it a low priority so any defined blocks are preferred.
> > network={
> >        key_mgmt=NONE
> >        priority=-9999999
> > }
> >
> > And this in defualts/rc.conf
> > wpa_supplicant_args="-B -c /etc/wpa_supplicant.conf"
> >
> > Then the user could do this in /etc/rc.conf
> > ifconfig_iwi0="wpa dhcp"
> >
> > And would get the same defaults as if not using wpa (wpa_supplicant)
> > which would be to connect to best unsecured network.
> >
> 
> 
> I like the idea of saying wpa in the same line as dhcp if we're going
> that direction for per-interface configs.  However, I would prefer it
> if simply added any "wpa" flagged interfaces to the -i argument of
> wpa_supplicant.

I am comfortable with this direction in principle, but not in the
implementation details.

Let us use a more generic keyword than 'wpa', such as 'auth', 'authenc',
or 'crypto'.

These ifconfig_xxN keywords ought to be decoupled from the implementation.
Let ifconfig_xxN=dhcp activate on interface xxN either dhclient,
dhcpcd, or whichever daemon is the DHCP client today.  After rc(8)
sources each /etc/rc.d/${name}, let it run '${name}_kw_dhcp xxN' to
rewrite the environment.  (For example, dhclient_kw_dhcp() may add xxN
to the end of the dhclient_flags var.)  Likewise, ifconfig_xxN=auth may
activate either wpa_supplicant or, say, open1x.

Dave

-- 
David Young             OJC Technologies
dyoung%ojctech.com@localhost      Urbana, IL * (217) 278-3933 ext 24