Just upgraded from Fedora 8 to 13 this morning, the network manager is well, different to say the least. I was able to get my wireless nic to work easily in F8, but I don't think it was detected in the netmanager, so I went to the command line. This is the output from my attemp.

[root@StormhostIBM sephiroth]# iwconfig eth1 Mode Managed
[root@StormhostIBM sephiroth]# iwconfig eth1 ESSID Honeypot
[root@StormhostIBM sephiroth]# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

irda0 no wireless extensions.

eth1 IEEE 802.11abg Mode:Managed Channel:0
Access Point: Not-Associated Bit Rate:0 kb/s Tx-Power=20 dBm
Sensitivity=8/0
Retry limit:7 RTS thrff Fragment thrff
Encryption keyff
Power Managementff
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

[root@StormhostIBM sephiroth]# ifup eth1
Error org.freedesktop.NetworkManagerSettings.InvalidConnection: ifcfg file '/etc/sysconfig/network-scripts/ifcfg-eth1' unknown
Error org.freedesktop.NetworkManagerSettings.InvalidConnection: ifcfg file '/etc/sysconfig/network-scripts/ifcfg-eth1' unknown
RTNETLINK answers: File exists
Error org.freedesktop.NetworkManagerSettings.InvalidConnection: ifcfg file '/etc/sysconfig/network-scripts/ifcfg-eth1' unknown
Error org.freedesktop.NetworkManagerSettings.InvalidConnection: ifcfg file '/etc/sysconfig/network-scripts/ifcfg-eth1' unknown
[root@StormhostIBM sephiroth]#

What am I doing wrong?

this is just strange. So After trying again and again, I made some kind of progress, and at some point ended up with my wired connection (eth0) not working so I restarted and bam, the wireless is working but the wired isnt detected...

In Fedora go into Administration > Network Configuration and see wether the box for eth0 is checked, Controlled by NetworkManager ?

Typically (I'm sure there are exceptions) the wireless is recognized as wlanx whereas the wired interface is recognized as ethy (where x and y are small integers). When installing Fedora, I do not try to configure the network; Fedora defaults to NetworkManager, the nm-applet runs in my X session, and I right-click on the little icon in the system tray on the panel, make sure the Enable Networking and Enable Wireless boxes are checked, then select my network from among the options offered. Obviously, YMMV

Sorry about the late reply, but anyway,the thing is, in F13, there is no "Network Manager" under Admin. I have to right click on the network connections icon on the panel on the right of the screen. That is one thing that is so annoying, the functionallity is being improved(support for more devices, etc.), but they are changing other things as well.

fedora moved from the old default "network" daemon to the new "network manager" daemon
see mjm's page
http://www.mjmwired.net/resources/mjm-fedora-f13.html
and services
http://www.mjmwired.net/resources/mjm-services-f13.html
user guide
http://docs.fedoraproject.org/en-US/...ide/index.html
and " connecting to the net "
http://docs.fedoraproject.org/en-US/..._Internet.html
the solution is and has been in the docs
please read them .

1 members found this post helpful.

Rather then posting afresh, I've been having these errors too

@JohnVV: thanks for the links so system-config-network is out and nm-connection-applet is in it's place

Docs on Fedora's network stuff always seem to be closely guarded secrets, or else in superabundance, so it's like joining the Civil Service. Network config files patterned on muttrc would be great (Most options, and comments inline).

Having read the docs, I still have an issue. I have /etc/sysconfig/network-scripts/ifcfg-eth0 simply set to 'ONBOOT=no"; /etc/rc.d/init.d/network is not executable. NetworkManager is starting. I seem to have a problem with wlan config as this exchange doesn't make sense

My device is a broadcom 4312. Other distros run it comfortably (Like slack-13.1 which I am in now. Does NetworkManager work on runlevel 3 without starting X? I can't even get things going when I do boot X. But if I plug in a cable, and run 'dhcpcd eth0' away it goes on that.

Thanks for any ideas.

Check is NetworkManager is set to run on desired runlevel (chkconfig). make sure that EITHER NetworkManager OR network are starting on boot. Both services have their on network profile management, those ifcfg files are just on default profile.

For some Broadcom radios you need ndiswrapper package to install a driver.

Read Fedora Documentation for more info about Fedora.

What a pile of trouble! I'm going, and online in of all things, fedora!
I sorted these problems. Thanks for your suggestions.
1. Firmware was wrong - Broadcom chips nearly all run on b43 module & wext driver. Mine does.
2. Selinux went nazi over /etc/sysconfig/network, which it called a 'file_t' and pointed out it is used by NetworkManager. I resisted the strong urge to give selinux the middle finger and took the long way around. What is a file_t?

I am left with these problems:
a. When I connect, it scrubs /etc/resolv.conf, and leaves a note there to put DNS1 & DNS2 in /etc/syscionfig/network-scripts/ifcfg-* . I did. It still scrubs the resolv.conf and leaves the same note there.

b. When I leave connection to NetworkManager it fails. From the log
So I got online with
service networkmanager stop
pkill wpa_supplicant
wpa_supplicant [options] && iwconfig [options]
dhclient wlan0

c. Any time the NetworkManager applet is touched, it starts looking for some key. I know what is in the key file (wlan0-keys) but it just rejects it.

Do they do this stuff to irritate people. Am I like the unicorn because I edit the file in vim instead of some gui?

How far are you from the wireless router, I have the same problem when I have my PC downstairs and router up stairs , It keeps showing problems with key and keeps asking for correct key.

If I take the PC back up stairs near router it connects first time every time.

That could happen if signal is so weak that Notebook is not able to send WPA key properly, so router rejects it because transmit errors.

I am less than 6 feet (2 metres) from the wireless router. All this works flawlessly in Slackware. It's just the Fedora install is giving me hassle.

Then wireless driver, or other part of software, in Fedora is not good. Compare Slackware and Fedora versions of related driver an software. I installed RHEL 6.0 Beta (2) (based on Fedora 12) on my notebook, and connection is much worse then on CentOS 5 on the same notebook. I have Atheros radio.

On CentOS 5 I use driver from aTrpms, so I am going to look for aTrpms driver for RHEL 6 kernel to see if I can get better wireless connection.

It isn't a strength thing here, or quality of signal. NetworkManager is not connecting, and faultfinding is very difficult because I have to grok some labyrinthine script. If I give it the middle finger, and connect manually, I'm fine. Selinux turning on me only makes a bad situation worse, but life has a habit of being like that.

FEATURE REQUEST: pack /etc/sysconfig/network.sample full of every valid option, and comments on setting them
NetworkManager uses that, doesn't it?

BUGFIX: Get rid of those innaccurate notices telling me to put DNS1 & 2 in /etc/sysconfig/ifcfg-*, and replace them with notices on how things should be done.