there's no way to graphically configure wifi to be automatically loaded at startup

[Virginie Quesnay]

I've my wifi card correctly configured (it works fine when it's launched by
"admin-network" or by "ifup ath0").
It wasn't automatically launched during the boot.
I've found (after litle help from mailing list) a solution that works well.
I've edited /etc/network/interfaces where there are some configuration info for
my network card. Right above the line that says "iface ath0 inet ...", I've
added a line that says "auto ath0".

Now the wifi works fine and is automatically loaded during boot.

But I've found nothing that can do the same thing in network-admin.

--
system :
hoary (up to date)
wifi card : 0000:02:02.0 Ethernet controller: Atheros Communications, Inc.
AR5211 802.11ab NIC (rev 01)
computer : IBM T40P

[Virginie Quesnay (virginie-quesnay)]

*** Bug 13100 has been marked as a duplicate of this bug. ***

[Sebastien Bacher (seb128)]

I'm a bit puzzled at the moment about the network-admin behaviour and startup
flags. Here the interfaces are automatically started.
There is a bug about having an option to not start them: bug #12899
and one another about the "auto" parameter: bug #12115

The current behaviour should be "auto is put when the device is activated and
removed when it's not" (which seems to be broken).
I'm not sure that's an ideal situation because some people want to boot without
a network connection and activate it sometime without changing the booting
paramaters ...

[Sebastien Bacher (seb128)]

do you still have the issue ? #5724 which is about the auto parameter is fixed
now, I'm not sure if that's the same issue

[Virginie Quesnay (virginie-quesnay)]

(In reply to comment #3)
> do you still have the issue ?
I've not tried a lot if the "auto" parameter is automaticaly writen in the
config file. But I've tried to desactive the eth0 network interface and for this
one the "auto" parameter is not removed.

> #5724 which is about the auto parameter is fixed now, I'm not sure if that's
the same issue
Yes it's the same but the first was not exact : it wasn't a problem with the
wifi loading but with the configuration saving. In order that people can find
the bug report if they have the same issue, I've made a new bug report marked
the 6745 as a duplicate of this bug, and closed the first one.

[Thomas Hood (jdthood)]

(In reply to comment #4)

Hi. Sorry, but after reading the log I am confused. Can you please
state again what the outstanding problems are?

[Martin Bergner (martin-bergner)]

I know, that this is possible with breezy and dapper since I'm doing this myself.