----- Forwarded message from Thorsten Sauter <[EMAIL PROTECTED]> -----
From: Thorsten Sauter <[EMAIL PROTECTED]>
Reply-To: Thorsten Sauter <[EMAIL PROTECTED]>
Subject: Re: Bug#221533: install fails - "couldn't download exim4"
Date: Sat, 27 Dec 2003 02:56:16 +0100
To: [EMAIL PROTECTED], debian-boot <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.4i
* Martin Michlmayr <[EMAIL PROTECTED]> [2003-12-26 12:33]:
| * Gaudenz Steinlin <[EMAIL PROTECTED]> [2003-11-20 11:10]:
| > > It found my wired ethernet controller, but not my Airport card.
| > As soon as there is a kernel module for the ariport card on the
| > installer image, we can test if this solves the problem or if we have to
| > add something more to support airport.
|
| The airport driver is included in
| nic-modules-2.4.22-powerpc-di_0.20_powerpc.udeb now. Joe, can you try
| a new daily build in a few days?
if we have support for aiport (and maybe other wifi cards), doesn't a
"wlancfg" udeb make sense?
This package should basicly ask for the following options and then
configure the wirless card based on these answers _before_ any network
configuration is done.
- network
- station/nick name
- encryption key
If we include such a package, then we need an udeb from the
wireless-tools package also.
Bye
Thorsten
----- End forwarded message -----
----- Forwarded message from Joey Hess <[EMAIL PROTECTED]> -----
From: Joey Hess <[EMAIL PROTECTED]>
Subject: Re: Bug#221533: install fails - "couldn't download exim4"
Date: Fri, 26 Dec 2003 23:13:27 -0500
To: [EMAIL PROTECTED], debian-boot <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.4i
Thorsten Sauter wrote:
> if we have support for aiport (and maybe other wifi cards), doesn't a
> "wlancfg" udeb make sense?
>
> This package should basicly ask for the following options and then
> configure the wirless card based on these answers _before_ any network
> configuration is done.
>
> - network
> - station/nick name
> - encryption key
>
> If we include such a package, then we need an udeb from the
> wireless-tools package also.
I looked at it a week ago, and concluded that to be a robust wifi
configurator, it would need to be part of netcfg. Here is my rough
design document:
- wifi config should happen after netcfg has chosen an interface, but
before the dhcp
- in low priority, should let wifi be configured
- in high priority, should see if there is an AP, and if so, use it with no
config
- should allow configuration of:
ad-hoc or AP
WEP key entry (ugh)
ad-hoc channel, essid
for AP, get a list of access points (how? at least dummy code with
AP and signal)
prompt with a question that asks which AP to use, with a manual
entry at the bottom to let the user enter the essid;
after the manual entry, see if an AP was found using that
essid, else show an error and back to list
- if dhcp or whatever fails, should be the option to go back and
reconfigure wifi, in case that was the problem
Instead of making there be 3 choices (retry dhcp, config static,
reconfig wifi), how about changing netcfg/dhcp_retry to jump back to
the start of netcfg (interface choice). This way, if you choose the
wrong interface, you can also rectify that, and you get to
configure wifi again too.
- after network config is done, need to write wifi info to interfaces file
Can this be made standalone, or how does it integrate with netcfg?
Probably the latter.
--
see shy jo
----- End forwarded message -----
--
Martin Michlmayr
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
