Re: NetworkManager tutorials?



On Thursday 20 April 2006 08:47, Aaron Konstam wrote:
On Thu, 2006-04-20 at 00:42 -0400, Gene Heskett wrote:
Greetings;

Subject...Is there such a thing? I've browsed the limited docs
installed on FC5, without finding anything that tells me how to
configure it. All I know is that if I start those 2 daemons, I have
to manually restart the network to restore service, and
that /etc/NetworkManager is an empty directory.

--

Could you explain what you mean by restarting the network since that
may not be correct.

As in 'service network restart'

Starting the NM daemon apparently takes me offline.

I note at the bottom of the redhat link that it says broadcom stuff
doesn't work, presumably because its ndiswrappered.

I know that ndiswrapper generated some pretty vociferous condemnations
from the GPL defenders, but it there's no other way to do it, what are
we the users to do. We're hardly in a position to demand GPL chipsets
in the lappy's we buy, particularly when they are so intertwined in FCC
regulations that are specifically designed to keep us from hacking
these 'software radios' to do illegal things. IMO thats unforch, but
its a fact of life and we should learn to deal with it after we realize
all the mewling in the world isn't going to change the regulatory
agencies stance on this even if broadcom were of a mind to gpl their
drivers.

Is there any hope that this will be addressed and NM made to work with
an ndiswrappered chipset eventually?

======================================================================
= Don't drink when you drive -- you might hit a bump and spill it.
=====================================================================
:-)
== Aaron Konstam telephone: (210) 656-0355 e-mail:
akonstam@xxxxxxxxxxxxx

--
Cheers, Gene
People having trouble with vz bouncing email to me should add the word
'online' between the 'verizon', and the dot which bypasses vz's
stupid bounce rules. I do use spamassassin too. :-)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2006 by Maurice Eugene Heskett, all rights reserved.

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list



Relevant Pages

  • Re: NetworkManager tutorials?
    ... Could you explain what you mean by restarting the network since that ... I know that ndiswrapper generated some pretty vociferous condemnations from the GPL defenders, but it there's no other way to do it, what are we the users to do. ... but its a fact of life and we should learn to deal with it after we realize all the mewling in the world isn't going to change the regulatory agencies stance on this even if broadcom were of a mind to gpl their drivers. ...
    (Fedora)
  • Re: Broadcom wifi card needs reboot to set essid
    ... been using ndiswrapper with the bcmwl5 driver for over a year now. ... reboot, sometimes 2-3 times, to get it to change to the new essid so I ... will also restart the broadcom network card. ...
    (Debian-User)
  • Re: Cant connect to the internet
    ... In the Startup tab, ... Click OK and restart your computer. ... I ran the Network Diagnostics on the laptop. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Boot time extremely long
    ... Rebooting did not show me any messages and even with restart disabled, ... Here are the error and warning events. ... Your computer was not able to renew its address from the network ... I had previously checked the event viewer and found that the ati ...
    (microsoft.public.windowsxp.perform_maintain)
  • Re: Wireless interface fails to initialize fully; still need to get DHCP manually
    ... # This file describes the network interfaces available on your system ... ndiswrapper -i bcmwl5.inf in the directory where that file resides (I ... The cause was that PCMCIA services are started in the boot / startup sequence AFTER networking is set up, so at the time the startup procedure is trying to connect to your network PCMCIA services are not running. ... The boot sequence will only attempt to initialise interfaces that have the auto keyword defined in /etc/interfaces. ...
    (Debian-User)