Activating wireless card at boot
Scot L. Harris
webid at cfl.rr.com
Sat Feb 5 17:49:31 UTC 2005
On Sat, 2005-02-05 at 12:08, jim lawrence wrote:
> On Sat, 05 Feb 2005 11:56:27 -0500, Scot L. Harris <webid at cfl.rr.com> wrote:
> > On Sat, 2005-02-05 at 11:37, jim lawrence wrote:
> > > As of now, I'm not 100% sure you can use Nm with Static IP addresses.
> > > If your AP was the last connection NM made, it will default to that AP
> > > the next time NM runs. to force your AP , click the radar, then
> > > choose "Other Network" and type in your Network name and then the
> > > HEX key if you use one.
> >
> > Will give that a try.
> >
> > It still seems that there is a problem when not using NetworkManager.
> > If/when I get that new motherboard with the built in wireless I can see
> > this being a bigger issue. In that case I want to use a static IP
> > address (do that for all servers/desktops on the local LAN). And the
> > fact that wireless does not seem to work without NetworkManager would be
> > a big issue.
> >
>
> You should be able to connect without using NM at all. Using the
> Wireless-tools which were installed with Fedora,
> iwlist scan
> iwconfig eth1 essid <networkname> key <hexkey to connect>
> ifup eth1
>
> these 3 commands should get you connected. or alternativly, try this page
> http://www.fedoranews.org/contributors/jim_lawrence/securewireless/
>
So using the original network management tools won't work anymore?
Talking about the System Settings --> Network tool in the menu.
But like the OP on this thread, what is keeping the wireless interface
from starting and connecting at boot time?
--
Scot L. Harris
webid at cfl.rr.com
You can't take it with you -- especially when crossing a state line.
More information about the fedora-list
mailing list