WiFi on my Thinkpad T60 has stopped working recently. I'm running Fedora-15/KDE.
When I hover over the NetworkManager icon in the panel I read "Disconnected Wireless disabled in software"
I'm wondering who gives this message, and what it means?
My WiFi card is Intel/PRO 3945ABG The driver seems to be iwl3945.
I might mention that WiFi works fine on this machine under Windows XP.
Do you have the driver installed?
iwl3945-firmware.noarch
Your e-mail seems to suggest that it was working earlier, but you did not indicate what, if anything, you changed?
Ranjan
On Fri, 16 Sep 2011 16:55:38 -0500 Timothy Murphy gayleard@eircom.net wrote:
WiFi on my Thinkpad T60 has stopped working recently. I'm running Fedora-15/KDE.
When I hover over the NetworkManager icon in the panel I read "Disconnected Wireless disabled in software"
I'm wondering who gives this message, and what it means?
My WiFi card is Intel/PRO 3945ABG The driver seems to be iwl3945.
I might mention that WiFi works fine on this machine under Windows XP.
-- Timothy Murphy e-mail: gayleard /at/ eircom.net tel: +353-86-2336090, +353-1-2842366 s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Ranjan Maitra wrote:
Do you have the driver installed?
iwl3945-firmware.noarch
Your e-mail seems to suggest that it was working earlier, but you did not indicate what, if anything, you changed?
WiFi on my Thinkpad T60 has stopped working recently. I'm running Fedora-15/KDE.
When I hover over the NetworkManager icon in the panel I read "Disconnected Wireless disabled in software"
I should have said that I discovered the cause of the problem: NetworkManager had written "WirelessEnabled=false" in /var/lib/NetworkManager/NetworkManager.state for some reason; and re-booting did not change this entry.
Also I noticed that /var/log/messages did contain an entry about this: ----------------------------------- Sep 16 23:32:32 blanche NetworkManager[730]: <info> WiFi enabled by radio killswitch; disabled by state file -----------------------------------
But how many people would know what the "state file" is? (I certainly didn't.) Why not say "by the file /var/lib/NetworkManager/NetworkManager.state"?
You asked what I had changed. The answer is that my ADSL line stopped working (Telecom Italia) and I had been using an "Onda MC833UP" broadband dongle (a nightmare under Fedora/NM but quite usable under Windows XP).
This caused NM to modify or create files all over the place, including deleting everything in /etc/resolv.conf . This is a habit of NM that I don't understand - I cannot think of any circumstances where an empty resolv.conf would be better than one containing something, however silly NM might think it was.
On Sat, 2011-09-17 at 12:55 +0200, Timothy Murphy wrote:
Ranjan Maitra wrote:
Do you have the driver installed?
iwl3945-firmware.noarch
Your e-mail seems to suggest that it was working earlier, but you did not indicate what, if anything, you changed?
WiFi on my Thinkpad T60 has stopped working recently. I'm running Fedora-15/KDE.
When I hover over the NetworkManager icon in the panel I read "Disconnected Wireless disabled in software"
I should have said that I discovered the cause of the problem: NetworkManager had written "WirelessEnabled=false" in /var/lib/NetworkManager/NetworkManager.state for some reason; and re-booting did not change this entry.
Also I noticed that /var/log/messages did contain an entry about this:
Sep 16 23:32:32 blanche NetworkManager[730]: <info> WiFi enabled by radio killswitch; disabled by state file
But how many people would know what the "state file" is? (I certainly didn't.) Why not say "by the file /var/lib/NetworkManager/NetworkManager.state"?
You asked what I had changed. The answer is that my ADSL line stopped working (Telecom Italia) and I had been using an "Onda MC833UP" broadband dongle (a nightmare under Fedora/NM but quite usable under Windows XP).
This caused NM to modify or create files all over the place, including deleting everything in /etc/resolv.conf . This is a habit of NM that I don't understand - I cannot think of any circumstances where an empty resolv.conf would be better than one containing something, however silly NM might think it was.
---- on the other hand, if you don't have any configured network adaptor, the content of /etc/resolv.conf is entirely irrelevant and when you do configure a network adaptor, the contents of /etc/resolv.conf become relevant. If you get an IP address automatically (ie DHCP-client), then it is configured automatically. If you enter an IP address manually, you will need to enter dns server addresses manually since the ones you choose are indeed relevant to the newly configured IP address.
Craig
Craig White wrote:
This caused NM to modify or create files all over the place, including deleting everything in /etc/resolv.conf . This is a habit of NM that I don't understand - I cannot think of any circumstances where an empty resolv.conf would be better than one containing something, however silly NM might think it was.
on the other hand, if you don't have any configured network adaptor, the content of /etc/resolv.conf is entirely irrelevant and when you do configure a network adaptor, the contents of /etc/resolv.conf become relevant. If you get an IP address automatically (ie DHCP-client), then it is configured automatically. If you enter an IP address manually, you will need to enter dns server addresses manually since the ones you choose are indeed relevant to the newly configured IP address.
I have found many times that I am not connected to the internet on my laptop BECAUSE NM has deleted the entries in /etc/resolv.conf , and that when I install the proper entries (I keep them in /etc/resolv.conf.opendns for this purpose) I am immediately connected. (I do not need to enter my IP address manually.)
I repeat: I simple don't understand why NM deletes the entries in /etc/resolv.conf . How could this possibly help me? In my opinion, any entries in resolv.conf are better than none.
I recently had the experience that NM deleted the HWADDR address in /etc/sysconfig/network-scripts/ifcfg-wlan0 . Why?
I find the logic of NM completely incomprehensible, and I haven't found any simple explanation of it anywhere.
What exactly is its train of thought if it sees a single AP visible? Wouldn't any normal person try to connect to that? And if it found some key was needed, why not just ask for it? More or less what Windows does, in fact.
Recently, a new nightmare has occurred; a window comes up called Secret, or something like that, with a space for a password, in which it is impossible to write. Admittedly closing the window does not seem to leave matters any worse than before.
To put it bluntly, NM is very bad if there is a problem. It does not give any helpful advice, and the entries in /var/log/messages are more or less meaningless, eg "deactivating device (reason: 2)".
On Sat, 2011-09-17 at 15:15 +0200, Timothy Murphy wrote:
Craig White wrote:
This caused NM to modify or create files all over the place, including deleting everything in /etc/resolv.conf . This is a habit of NM that I don't understand - I cannot think of any circumstances where an empty resolv.conf would be better than one containing something, however silly NM might think it was.
on the other hand, if you don't have any configured network adaptor, the content of /etc/resolv.conf is entirely irrelevant and when you do configure a network adaptor, the contents of /etc/resolv.conf become relevant. If you get an IP address automatically (ie DHCP-client), then it is configured automatically. If you enter an IP address manually, you will need to enter dns server addresses manually since the ones you choose are indeed relevant to the newly configured IP address.
I have found many times that I am not connected to the internet on my laptop BECAUSE NM has deleted the entries in /etc/resolv.conf , and that when I install the proper entries (I keep them in /etc/resolv.conf.opendns for this purpose) I am immediately connected. (I do not need to enter my IP address manually.)
---- If NM deletes the contents of /etc/resolv.conf WHILE you have a network device that is functional, that would be a bug and you should report it. ----
I repeat: I simple don't understand why NM deletes the entries in /etc/resolv.conf . How could this possibly help me? In my opinion, any entries in resolv.conf are better than none.
I recently had the experience that NM deleted the HWADDR address in /etc/sysconfig/network-scripts/ifcfg-wlan0 . Why?
---- HWADDR might have changed - that's not really a problem anyway. ----
I find the logic of NM completely incomprehensible, and I haven't found any simple explanation of it anywhere.
---- Feel free to contribute documentation ----
What exactly is its train of thought if it sees a single AP visible? Wouldn't any normal person try to connect to that? And if it found some key was needed, why not just ask for it? More or less what Windows does, in fact.
---- always seemed to work well enough for my laptop but it did require that I interact with the 'widget' (whatever it is called in KDE) that listed available wireless networks and allowed me to instigate a connection. In a general sense, I think Windows automatically joining a wireless network is a real security concern but I suspect that at some point, there will be enough users who just want things to work automatically and are incapable of applying their needs to an interface. ----
Recently, a new nightmare has occurred; a window comes up called Secret, or something like that, with a space for a password, in which it is impossible to write. Admittedly closing the window does not seem to leave matters any worse than before.
---- haven't a clue what you are getting at here ----
To put it bluntly, NM is very bad if there is a problem. It does not give any helpful advice, and the entries in /var/log/messages are more or less meaningless, eg "deactivating device (reason: 2)".
---- yeah but things were much worse before NM so either make bug reports for the behaviors you believe are wrong/problematic, suffer or use another OS because those really are you choices. Whining to the list may prove to be sufficiently cathartic for you to continue on suffering I suppose.
Craig
Craig White wrote:
I have found many times that I am not connected to the internet on my laptop BECAUSE NM has deleted the entries in /etc/resolv.conf , and that when I install the proper entries (I keep them in /etc/resolv.conf.opendns for this purpose) I am immediately connected. (I do not need to enter my IP address manually.)
If NM deletes the contents of /etc/resolv.conf WHILE you have a network device that is functional, that would be a bug and you should report it.
I'm not sure exactly what you mean by functional. Eg last night I was on my laptop in my bed-room, which may be near the limiting distance from my WiFi router. I guess the laptop lost connection, and when it came back I found resolv.conf had been gutted. So the device was not functional (briefly) in the sense that it had lost the connection.
I recently had the experience that NM deleted the HWADDR address in /etc/sysconfig/network-scripts/ifcfg-wlan0 . Why?
HWADDR might have changed - that's not really a problem anyway.
Can the HWADDR of a device change in the real world? I imagine it might in the virtual world, but I'm not into that sort of thing.
When you say it isn't really a problem, does dhcpd have another way of recognising the device? I see NM (maybe dhclient?) has taken to writing a UUID in ifcfg-* , I'm not sure why as I don't think my dhcpd server knows anything about it.
In my case, I put the HWADDR back, and probably had to restore resolv.conf, and the connection came back, but I don't know which change was responsible.
I find the logic of NM completely incomprehensible, and I haven't found any simple explanation of it anywhere.
Feel free to contribute documentation
I genuinely don't know NM's modus operandi, so any documentation written by me would be completely useless, in fact worse than useless, dangerous.
All I know is that if NM stops working there are about 6 things I can do - look at resolv.conf, look at /var/log/messages, look at ifcfg-wlan0, look at lsmod, google "Fedora NM <card> <driver>", google <last NM message in /var/log/messages>. One of these usually gives a hint.
What exactly is its train of thought if it sees a single AP visible? Wouldn't any normal person try to connect to that? And if it found some key was needed, why not just ask for it? More or less what Windows does, in fact.
always seemed to work well enough for my laptop but it did require that I interact with the 'widget' (whatever it is called in KDE) that listed available wireless networks and allowed me to instigate a connection.
I'm not sure what you mean by "instigate a connection". If I right-click on the slightly odd NM icon (like the sound icon rotated 90%) then I can go to Network Management Settings (where I also get to less directly if I left click on the icon). Very occasionally - maybe one time in twenty - I actually see a label "Connect" which I can click. But usually there is no action I can take apart from editing the data which in fact is never necessary.
The only action I've found likely to work at this point is re-booting.
In a general sense, I think Windows automatically joining a wireless network is a real security concern but I suspect that at some point, there will be enough users who just want things to work automatically and are incapable of applying their needs to an interface.
I wouldn't mind in the slightest if NM gave me a choice of APs, and asked me to click the one I want. But it doesn't tell me anything, even though "iwlist scan" tells me there is an AP staring in its face.
Recently, a new nightmare has occurred; a window comes up called Secret, or something like that, with a space for a password, in which it is impossible to write. Admittedly closing the window does not seem to leave matters any worse than before.
haven't a clue what you are getting at here
I've never seen it before. It is a small window entitled Secret which appears in the middle of the screen, with a space denoted "Password" in which I cannot in fact write. (I wouldn't know what to write even if I could.) I take it that it has something to do with NM, since I know NM is very fond of the word "secret". This phenomenon has only occurred about 5 times, in the last day or two, so I assume it comes from a new version of NM, or possibly some other application. Has no-one else seen this?
To put it bluntly, NM is very bad if there is a problem. It does not give any helpful advice, and the entries in /var/log/messages are more or less meaningless, eg "deactivating device (reason: 2)".
yeah but things were much worse before NM so either make bug reports for the behaviors you believe are wrong/problematic, suffer or use another OS because those really are you choices. Whining to the list may prove to be sufficiently cathartic for you to continue on suffering I suppose.
I agree that the network service under Fedora was even worse. I have actually communicated with Dan Williams on occasion, and he has always gone out of his way to help, or try to help. But I've always had the impression that he has his own way of doing things, and is not very open to suggestion. Eg I suggested some time ago that "reason: 3" is not very helpful in an error or warning message, but his response was to tell me where I could find what it means.
Incidentally, system-config-network seems to have become completely useless. It comes up with a blue screen, with 2 apparent options in the middle: Device configuration, and DNS configuration. The first only lists em1, my ethernet controller, which I am not using. And as far as I can see, there is no change I could make even if I wanted to.
And there seem no entries in the f-menu allowing me to run something like a GUI version of system-config-network, as there used to be.
Timothy Murphy <gayleard <at> eircom.net> writes:
...
Recently, a new nightmare has occurred; a window comes up called Secret, or something like that, with a space for a password, in which it is impossible to write. Admittedly closing the window does not seem to leave matters any worse than before.
haven't a clue what you are getting at here
I've never seen it before. It is a small window entitled Secret which appears in the middle of the screen, with a space denoted "Password" in which I cannot in fact write. (I wouldn't know what to write even if I could.) I take it that it has something to do with NM, since I know NM is very fond of the word "secret". This phenomenon has only occurred about 5 times, in the last day or two, so I assume it comes from a new version of NM, or possibly some other application. Has no-one else seen this? ...
You can determine who is the owner (application) of that "password" window.
I can not remember it now, but it was inquired on Fedora users or testers list some time ago regarding how to do it. Search for it.
JB
On Sat, 2011-09-17 at 23:09 +0200, Timothy Murphy wrote:
Craig White wrote:
I have found many times that I am not connected to the internet on my laptop BECAUSE NM has deleted the entries in /etc/resolv.conf , and that when I install the proper entries (I keep them in /etc/resolv.conf.opendns for this purpose) I am immediately connected. (I do not need to enter my IP address manually.)
If NM deletes the contents of /etc/resolv.conf WHILE you have a network device that is functional, that would be a bug and you should report it.
I'm not sure exactly what you mean by functional. Eg last night I was on my laptop in my bed-room, which may be near the limiting distance from my WiFi router. I guess the laptop lost connection, and when it came back I found resolv.conf had been gutted. So the device was not functional (briefly) in the sense that it had lost the connection.
---- at the point you lost connection, NM dutifully released the configuration info obtained from the connection and thus removed the contents in /etc/resolv.conf that it put there. Some might call that being a good housekeeper. After the device re-established a connection (satisfied authentication requirements & obtained an IP address from DHCP server) /etc/resolv.conf should automatically be repopulated. Seems to me that you sometimes are confused by a lack of understanding how the process occurs and start flailing about for an answer. ----
I recently had the experience that NM deleted the HWADDR address in /etc/sysconfig/network-scripts/ifcfg-wlan0 . Why?
HWADDR might have changed - that's not really a problem anyway.
Can the HWADDR of a device change in the real world? I imagine it might in the virtual world, but I'm not into that sort of thing.
When you say it isn't really a problem, does dhcpd have another way of recognising the device? I see NM (maybe dhclient?) has taken to writing a UUID in ifcfg-* , I'm not sure why as I don't think my dhcpd server knows anything about it.
In my case, I put the HWADDR back, and probably had to restore resolv.conf, and the connection came back, but I don't know which change was responsible.
---- I actually wouldn't think that either of those actions had a single thing to do with whether your 'connection' came back. It's possible that the HWADDR could but ifcfg-XXXX should function fine with or without a HWADDR and if the HWADDR is wrong, it won't function properly. ----
All I know is that if NM stops working there are about 6 things I can do - look at resolv.conf, look at /var/log/messages, look at ifcfg-wlan0, look at lsmod, google "Fedora NM <card> <driver>", google <last NM message in /var/log/messages>. One of these usually gives a hint.
---- I gather that NM never actually stops working but rather you have a configured interface that doesn't do what you expect it to do. ----
I'm not sure what you mean by "instigate a connection". If I right-click on the slightly odd NM icon (like the sound icon rotated 90%) then I can go to Network Management Settings (where I also get to less directly if I left click on the icon). Very occasionally - maybe one time in twenty - I actually see a label "Connect" which I can click. But usually there is no action I can take apart from editing the data which in fact is never necessary.
---- icon is supposed to represent the pretty much standard image of 'wireless'
right click on this icon to get a list of options. One of them is likely to offer to scan for available wireless networks. It also might list available wireless networks and thus would allow you to choose to connect to an available wireless network that you hadn't previously indicated to connect to 'automatically' This isn't rocket science and is similar to actions required to use wireless networking on a Macintosh or Windows system. ----
The only action I've found likely to work at this point is re-booting.
---- I suspect that you resort to rebooting because you have never checked your options by right clicking the wireless icon in the system panel. If it works for you... great. ----
I wouldn't mind in the slightest if NM gave me a choice of APs, and asked me to click the one I want. But it doesn't tell me anything, even though "iwlist scan" tells me there is an AP staring in its face.
---- see my explanation above - the GUI way to run 'iwlist scan' ----
Incidentally, system-config-network seems to have become completely useless. It comes up with a blue screen, with 2 apparent options in the middle: Device configuration, and DNS configuration. The first only lists em1, my ethernet controller, which I am not using. And as far as I can see, there is no change I could make even if I wanted to.
And there seem no entries in the f-menu allowing me to run something like a GUI version of system-config-network, as there used to be.
---- system-config-network is for 'network' not 'NetworkManager' and thus should not be used on systems using NetworkManager. It will only confuse things for the computer and for the user.
On the fly wireless configuration is entirely dependent upon NetworkManager and the wireless 'widget' in the system tray should provide all of the functionality you need. I don't know why you haven't figured this out already or even gotten that info from whoever you referred to as being knowledgeable but really... it's there, it works well and should do everything you need. If not, you should file a bug report.
Craig
Craig White wrote:
right click on this [NM] icon to get a list of options.
I'm right clicking on the icon now. It lists 3 items: Network Management Settings Panel Options Remove this Network Management
One of them is likely to offer to scan for available wireless networks. It also might list available wireless networks and thus would allow you to choose to connect to an available wireless network that you hadn't previously indicated to connect to 'automatically' This isn't rocket science and is similar to actions required to use wireless networking on a Macintosh or Windows system.
Sorry, nothing like that appears on my Fedora-15/KDE system. If I click on Network Management Settings I get a window entitled Network Connections which gives information on my current connection. If I highlight this connection I get the basic data, SSID, MTU, etc. As far as I can see, the only options I have are to change these, which I don't need or want to.
The only action I've found likely to work at this point is re-booting.
I suspect that you resort to rebooting because you have never checked your options by right clicking the wireless icon in the system panel. If it works for you... great.
As I have explained, right-clicking does not have the effects you describe. What you say should happen is exactly what I would like to happen.
see my explanation above - the GUI way to run 'iwlist scan'
Unfortunately, the only way I have found to run "iwlist scan" is "iwlist scan".
On the fly wireless configuration is entirely dependent upon NetworkManager and the wireless 'widget' in the system tray should provide all of the functionality you need. I don't know why you haven't figured this out already
because it doesn't correspond to what I see on my laptop
or even gotten that info from whoever you referred to as being knowledgeable but really... it's there, it works well and should do everything you need. If not, you should file a bug report.
The simplest explanation would seem to be that I am missing some package. But I included all relevant groups when installing F-15. ----------------------------------- [tim@blanche ~]$ sudo grep -i net /var/log/yum.log May 26 14:00:13 Installed: netpbm-10.47.26-2.fc15.i686 May 26 14:00:16 Installed: netpbm-progs-10.47.26-2.fc15.i686 May 28 11:37:55 Updated: 1:NetworkManager- glib-0.8.999-3.git20110526.fc15.i686 May 28 11:37:58 Updated: 1:NetworkManager-0.8.999-3.git20110526.fc15.i686 Jun 03 14:23:02 Updated: 1:NetworkManager- glib-0.8.9997-1.git20110531.fc15.i686 Jun 03 14:24:27 Updated: 1:NetworkManager-0.8.9997-1.git20110531.fc15.i686 Jun 03 14:24:28 Updated: evolution-NetworkManager-3.0.2-1.fc15.i686 Jun 10 22:05:05 Updated: 1:NetworkManager- glib-0.8.9997-2.git20110531.fc15.i686 Jun 10 22:05:07 Updated: 1:NetworkManager-0.8.9997-2.git20110531.fc15.i686 Jun 10 22:05:43 Updated: evolution-NetworkManager-3.0.2-2.fc15.i686 Jun 16 23:27:28 Updated: net-tools-1.60-117.fc15.i686 Jun 17 23:54:11 Installed: libnet-1.1.5-2.fc15.i686 Jun 22 21:59:52 Updated: 1:kde-plasma- networkmanagement-0.9-0.47.20110323.fc15.1.i686 Jun 22 21:59:53 Updated: 1:kde-plasma-networkmanagement- libs-0.9-0.47.20110323.fc15.1.i686 Jun 22 22:01:33 Updated: 1:kde-plasma-networkmanagement- openvpn-0.9-0.47.20110323.fc15.1.i686 Jun 22 22:01:33 Updated: 1:kde-plasma-networkmanagement- vpnc-0.9-0.47.20110323.fc15.1.i686 Jun 22 22:01:33 Updated: 1:kde-plasma-networkmanagement- pptp-0.9-0.47.20110323.fc15.1.i686 Jun 26 01:30:25 Updated: 1:NetworkManager- glib-0.8.9997-4.git20110620.fc15.i686 Jun 26 01:31:01 Updated: 1:NetworkManager-0.8.9997-4.git20110620.fc15.i686 Jul 01 12:20:32 Updated: 1:kde-plasma- networkmanagement-0.9-0.53.20110616git.nm09.fc15.i686 Jul 01 12:20:34 Updated: 1:kde-plasma-networkmanagement- libs-0.9-0.53.20110616git.nm09.fc15.i686 Jul 01 12:20:44 Updated: 1:kde-plasma-networkmanagement- pptp-0.9-0.53.20110616git.nm09.fc15.i686 Jul 01 12:20:44 Updated: 1:kde-plasma-networkmanagement- openvpn-0.9-0.53.20110616git.nm09.fc15.i686 Jul 01 12:20:45 Updated: 1:kde-plasma-networkmanagement- vpnc-0.9-0.53.20110616git.nm09.fc15.i686 Jul 03 12:09:06 Updated: evolution-NetworkManager-3.0.2-3.fc15.i686 Jul 07 13:49:08 Updated: 1:NetworkManager- glib-0.8.9997-5.git20110702.fc15.i686 Jul 07 13:49:10 Updated: 1:NetworkManager-0.8.9997-5.git20110702.fc15.i686 Jul 19 12:12:24 Updated: 7:kdenetwork-libs-4.6.5-1.fc15.i686 Jul 19 12:13:16 Updated: 7:kdenetwork-4.6.5-1.fc15.i686 Jul 22 22:40:45 Updated: perl-Net-DNS-SEC-0.16-6.fc15.noarch Jul 25 11:57:27 Updated: 1:telnet-0.17-51.fc15.i686 Aug 03 13:09:51 Updated: 1:NetworkManager- glib-0.8.9997-6.git20110721.fc15.i686 Aug 03 13:11:18 Updated: 1:NetworkManager-0.8.9997-6.git20110721.fc15.i686 Aug 03 13:11:41 Updated: 1:NetworkManager- vpnc-0.8.999-3.git20110721.fc15.i686 Aug 03 13:11:59 Updated: 1:NetworkManager- openvpn-0.8.9997-2.git20110721.fc15.i686 Aug 03 13:12:02 Updated: 1:NetworkManager- pptp-0.8.999-2.git20110721.fc15.i686 Aug 10 01:45:29 Installed: perl-Net-FTP-AutoReconnect-0.3-3.fc15.noarch Aug 10 01:45:30 Installed: perl-Net-FTP-RetrHandle-0.2-3.fc15.noarch Aug 10 01:46:48 Updated: perl-NetPacket-1.2.0-1.fc15.noarch Aug 10 09:59:08 Updated: perl-Net-SSLGlue-0.8-1.fc15.noarch Aug 28 14:31:54 Updated: perl-Net-Amazon-0.60-1.fc15.noarch Aug 28 14:32:23 Updated: 1:kde-plasma-networkmanagement- libs-0.9-0.54.20110812git.nm09.fc15.i686 Aug 28 14:32:25 Updated: 1:kde-plasma- networkmanagement-0.9-0.54.20110812git.nm09.fc15.i686 Aug 28 14:32:25 Updated: 1:kde-plasma-networkmanagement- vpnc-0.9-0.54.20110812git.nm09.fc15.i686 Aug 28 14:32:26 Updated: 1:kde-plasma-networkmanagement- pptp-0.9-0.54.20110812git.nm09.fc15.i686 Aug 28 14:32:26 Updated: 1:kde-plasma-networkmanagement- openvpn-0.9-0.54.20110812git.nm09.fc15.i686 Sep 09 12:31:28 Updated: evolution-NetworkManager-3.0.3-1.fc15.i686 Sep 16 11:34:19 Updated: 1:NetworkManager-glib-0.9.0-1.fc15.i686 Sep 16 11:35:03 Updated: perl-Net-Telnet-Cisco-1.10-7.fc15.noarch Sep 16 11:35:20 Updated: 1:NetworkManager-0.9.0-1.fc15.i686 Sep 16 11:36:07 Updated: 1:NetworkManager-vpnc-0.9.0-1.fc15.i686 Sep 16 11:36:10 Updated: 1:NetworkManager-openvpn-0.9.0-1.fc15.i686 Sep 16 11:36:13 Updated: NetworkManager-openconnect-0.9.0-1.fc15.i686 Sep 16 11:36:17 Updated: 1:NetworkManager-pptp-0.9.0-1.fc15.i686 Sep 16 11:36:26 Updated: netcf-libs-0.1.9-1.fc15.i686 ----------------------------------- (I've deleted a large number of perl-Net-* packages, as I assume these are not relevant.)
Is there something obvious I am missing?
On Sun, 2011-09-18 at 02:17 +0200, Timothy Murphy wrote:
Craig White wrote:
right click on this [NM] icon to get a list of options.
I'm right clicking on the icon now. It lists 3 items: Network Management Settings Panel Options Remove this Network Management
---- My netbook is still F14 (KDE)
Sorry, it was a standard (left) click System tray => WLAN interface (widget)
Choose the appropriate WLAN interface (you probably only have 1 but you could conceivably have more than 1) and then on the right side, you can pick from the available Wireless LAN's.
Couldn't be any simpler.
Perhaps you are looking at the wrong widget
Craig
Craig White wrote:
right click on this [NM] icon to get a list of options.
...
Sorry, it was a standard (left) click System tray => WLAN interface (widget)
OK, now I'm left clicking on the icon. I get a window with 2 halves, entitled Interfaces and Connections. I'm connected at the moment. The left half-window says WLAN Interface Connected to wlan0 The right half-window says Connections wlan0 and down the bottom Show More Manage Connections If I click Show More it just changes to Show Less but has no other effect. If I click on Manage Connections I get the same window that I got when right-clicking on the icon. If I left-click on wlan0 the connection is broken for a second, "Connected to wlan0" in the left half-window changes to "Configuring interface", then "Setting network address" and then "Connected to wlan0" again.
OK, this is fine; but I don't see any of the goodies you mention. There is no option to scan for APs, nor is there a list of available APs (as provided by "iwlist scan", which incidentally shows 2 APs, including the one I am using)
More to the point, if I am not connected for some reason, the two window-halves are empty, and there is no action offered to me to correct the problem as far as I can see.
Choose the appropriate WLAN interface (you probably only have 1 but you could conceivably have more than 1) and then on the right side, you can pick from the available Wireless LAN's.
Couldn't be any simpler.
I think you should consider the possibility that I don't see what you see. Are you using KDE or Gnome?
Perhaps you are looking at the wrong widget
I don't think so; I have 13 widgets in my panel, including 5 hidden ones. Only one has any connection with wifi.
On Sun, 2011-09-18 at 13:36 +0200, Timothy Murphy wrote:
Craig White wrote:
right click on this [NM] icon to get a list of options.
...
Sorry, it was a standard (left) click System tray => WLAN interface (widget)
OK, now I'm left clicking on the icon. I get a window with 2 halves, entitled Interfaces and Connections. I'm connected at the moment. The left half-window says WLAN Interface Connected to wlan0 The right half-window says Connections wlan0 and down the bottom Show More Manage Connections If I click Show More it just changes to Show Less but has no other effect. If I click on Manage Connections I get the same window that I got when right-clicking on the icon. If I left-click on wlan0 the connection is broken for a second, "Connected to wlan0" in the left half-window changes to "Configuring interface", then "Setting network address" and then "Connected to wlan0" again.
OK, this is fine; but I don't see any of the goodies you mention. There is no option to scan for APs, nor is there a list of available APs (as provided by "iwlist scan", which incidentally shows 2 APs, including the one I am using)
More to the point, if I am not connected for some reason, the two window-halves are empty, and there is no action offered to me to correct the problem as far as I can see.
---- seems as if your manual configuration attempts are interfering with the GUI since at the point where you left-click on wlan0, it should do the equivalent to a iwlist scan command and list the available wireless networks (whether AP's or Ad-Hoc) - at least it does for me.
Craig
Craig White wrote:
seems as if your manual configuration attempts are interfering with the GUI since at the point where you left-click on wlan0, it should do the equivalent to a iwlist scan command and list the available wireless networks (whether AP's or Ad-Hoc) - at least it does for me.
As I said, the effect of left-clicking on the NM icon, and then left-clicking on wlan0, is to re-start the connection.
I don't see how anything I've done could possibly affect the GUI. (All I did at one point was to put the opendns entries in resolv.conf .)
There is another oddity in my NM: the time of "Last use" given if I go to Manage Connections seems to be random. Sometimes it says Never, even if I am using it at that moment. At the moment it say One minute, at other times it says No minutes.
According to "NetworkManager --version" I'm running NM-0.9.0-1.fc15.
You didn't say if you were using KDE or Gnome (or something else). I have the impression kdenetwork used to give more information, but that doesn't seem to be the case any longer.
On 9/17/11 9:15 AM, Timothy Murphy wrote:
Craig White wrote:
This caused NM to modify or create files all over the place, including deleting everything in /etc/resolv.conf . This is a habit of NM that I don't understand - I cannot think of any circumstances where an empty resolv.conf would be better than one containing something, however silly NM might think it was.
on the other hand, if you don't have any configured network adaptor, the content of /etc/resolv.conf is entirely irrelevant and when you do configure a network adaptor, the contents of /etc/resolv.conf become relevant. If you get an IP address automatically (ie DHCP-client), then it is configured automatically. If you enter an IP address manually, you will need to enter dns server addresses manually since the ones you choose are indeed relevant to the newly configured IP address.
I have found many times that I am not connected to the internet on my laptop BECAUSE NM has deleted the entries in /etc/resolv.conf , and that when I install the proper entries (I keep them in /etc/resolv.conf.opendns for this purpose) I am immediately connected. (I do not need to enter my IP address manually.)
I repeat: I simple don't understand why NM deletes the entries in /etc/resolv.conf .
if you apply chattr +i /etc/resolv.conf it will prevent the file from being overwritten by dhcpd
How could this possibly help me? In my opinion, any entries in resolv.conf are better than none.
I recently had the experience that NM deleted the HWADDR address in /etc/sysconfig/network-scripts/ifcfg-wlan0 . Why?
I find the logic of NM completely incomprehensible, and I haven't found any simple explanation of it anywhere.
What exactly is its train of thought if it sees a single AP visible? Wouldn't any normal person try to connect to that? And if it found some key was needed, why not just ask for it? More or less what Windows does, in fact.
Recently, a new nightmare has occurred; a window comes up called Secret, or something like that, with a space for a password, in which it is impossible to write. Admittedly closing the window does not seem to leave matters any worse than before.
To put it bluntly, NM is very bad if there is a problem. It does not give any helpful advice, and the entries in /var/log/messages are more or less meaningless, eg "deactivating device (reason: 2)".
Glad you found out the issue.
Anyway, I must add Fedora 15's Gnome-Shell's NM interface is buggy, use the old one when things are going bad, http://www.spinics.net/linux/fedora/fedora-users/msg403101.html . That interface clearly has the option of enabling and disabling Wireless.
And, if anything else fails, use `rfkill' to check what is disabled (must be installed first).
(IMO, info on how to revert to the old nm-applet should be referenced on http://fedoraproject.org/wiki/Common_F15_bugs#General_buggy_or_missing_funct...)
Timothy Murphy wrote:
WiFi on my Thinkpad T60 has stopped working recently. I'm running Fedora-15/KDE.
When I hover over the NetworkManager icon in the panel I read "Disconnected Wireless disabled in software"
I discovered the cause of the problem: NetworkManager had written "WirelessEnabled=false" in /var/lib/NetworkManager/NetworkManager.state for some reason; and re-booting did not change this entry.
Timothy Murphy <gayleard <at> eircom.net> writes:
WiFi on my Thinkpad T60 has stopped working recently. I'm running Fedora-15/KDE.
When I hover over the NetworkManager icon in the panel I read "Disconnected Wireless disabled in software"
I'm wondering who gives this message, and what it means?
My WiFi card is Intel/PRO 3945ABG The driver seems to be iwl3945.
I might mention that WiFi works fine on this machine under Windows XP.
Some points to consider (mainly who could modify or interfere with /etc/resolv.conf):
- dhclient $ apropos dhclient dhclient (8) - Dynamic Host Configuration Protocol Client dhclient-script (8) - DHCP client network configuration script dhclient.conf (5) - DHCP client configuration file dhclient.leases (5) - DHCP client lease database
Note: dhclient.conf has options (prepend, etc) to modify /etc/resolv.conf, usually found in a config file under /etc dir. # find /etc -iname "*dhclient*"
- zeroconf Basically avahi package. http://en.wikipedia.org/wiki/Avahi_%28software%29 Usually it changes kernel routing table if installed ($ route -n), etc. It also manipulates DNS (DNS service discovery). I am not on KDE, but I see KDE-specific package for zeroconf: $ yum info kdnssd-avahi
JB
-
Christina Salls -
Craig White -
JB -
Pedro Francisco -
Ranjan Maitra -
Timothy Murphy