It seems I have knetworkmanager and NetworkManager* installed, which may well be why I have problems. In the systemtray I have an icon that looks like an unplugged RJ45 cable, which tells me that the network is not available. Nonsense, of course. Left or Right-click on it tells me that network management is disabled.
NetworkManager-gnome never seemed to work on this laptop, so I'd like to try knetworkmanager. Can you give me some hints with regard to sorting this out? Thanks
Anne
On 03/07/2010 06:24 PM, Anne Wilson wrote:
It seems I have knetworkmanager and NetworkManager* installed, which may well be why I have problems. In the systemtray I have an icon that looks like an unplugged RJ45 cable, which tells me that the network is not available. Nonsense, of course. Left or Right-click on it tells me that network management is disabled.
NetworkManager-gnome never seemed to work on this laptop, so I'd like to try knetworkmanager. Can you give me some hints with regard to sorting this out? Thanks
Anne
kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
in system-config-network make sure that your interface is managed by NM, and in system-config-services make sure that NM is started and network is not.
On Sunday 07 March 2010 16:42:57 Aioanei Rares wrote:
On 03/07/2010 06:24 PM, Anne Wilson wrote:
It seems I have knetworkmanager and NetworkManager* installed, which may well be why I have problems. In the systemtray I have an icon that looks like an unplugged RJ45 cable, which tells me that the network is not available. Nonsense, of course. Left or Right-click on it tells me that network management is disabled.
NetworkManager-gnome never seemed to work on this laptop, so I'd like to try knetworkmanager. Can you give me some hints with regard to sorting this out? Thanks
Anne
kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
in system-config-network make sure that your interface is managed by NM, and in system-config-services make sure that NM is started and network is not.
Yes, I've checked and all those settings are correct.
Anne
If I am not mistaken,, you have either knetworkmanager or NetworkManager-gnome installed, not both.
Correct me if I'm wrong, and how does this affect systems where both KDE and Gnome are installed?
However, I am not able to get a wireless network connection established with knetworkmanager. It works fine for wired.
See bugzilla #570947.
On Sunday 07 March 2010 19:02:43 Petrus de Calguarium wrote:
If I am not mistaken,, you have either knetworkmanager or NetworkManager-gnome installed, not both.
That seems likely. However, I'm not sure whether there would be any side- effects from removing NetworkManager-gnome. Anyway, I've taken the bit between the teeth and removed it. I guess it will need a reboot to make the change read, but I can't do that just now. I'll do it as soon as I can.
Correct me if I'm wrong, and how does this affect systems where both KDE and Gnome are installed?
I would have thought that either should work with both, since the libraries for both are installed, but that's guesswork.
However, I am not able to get a wireless network connection established with knetworkmanager. It works fine for wired.
See bugzilla #570947.
Well I know that I can't get one on this laptop whenever I'm working here. I suspect telephone wireless interference. If I can get knetworkmanager to look promising I'll give it a try in a place that I know has a better chance.
Anne
Anne Wilson wrote:
I'm not sure whether there would be any side- effects from removing NetworkManager-gnome.
There ought not to be. I initially installed from the kde-live cd and NetworkManager-gnome is not on on the disk, only knetworkmanager.
I hope this isn't why I cannot connect wirelessly with knetworkmanager :-) Hopefully, Kevin comes up with something soon, re. my bz report.
On Sun, Mar 7, 2010 at 8:02 PM, Petrus de Calguarium kwhiskerz@gmail.com wrote:
If I am not mistaken,, you have either knetworkmanager or NetworkManager-gnome installed, not both.
You can have both installed without a problem. If you have both you get a warning (get asked?) from knetworkmanager that another applet is running and if you want to use it or not in the future. So, one is always working.
On Sun, Mar 7, 2010 at 8:02 PM, Petrus de Calguarium
kwhiskerz@gmail.com wrote:
If I am not mistaken,, you have either knetworkmanager or NetworkManager-gnome installed, not both.
You can have both installed without a problem. If you have both you get a warning (get asked?) from knetworkmanager that another applet is running and if you want to use it or not in the future. So, one is always working.
Hi,
Aren't both knetworkmanager and NetworkManager-gnome more or less front-ends to NetworkManager? So if the network doesn't work, it has to be NetworkManager that didn't detect the network-card, or did set up the interface wrongly. Are there any error messages in /var/log/messages?
Martin Kho
On 03/08/2010 07:21 AM, Martin Kho wrote:
On Sun, Mar 7, 2010 at 8:02 PM, Petrus de Calguarium
kwhiskerz@gmail.com wrote:
If I am not mistaken,, you have either knetworkmanager or NetworkManager-gnome installed, not both.
You can have both installed without a problem. If you have both you get a warning (get asked?) from knetworkmanager that another applet is running and if you want to use it or not in the future. So, one is always working.
Hi,
Aren't both knetworkmanager and NetworkManager-gnome more or less front-ends to NetworkManager?
Yes.
So if the network doesn't work, it has to be NetworkManager
that didn't detect the network-card, or did set up the interface wrongly.
Not really. I recently had a case where knetworkmanger would just not connect to a WPA2 access point (tried 3 or 4 times) but nm-applet connected up on the first try.
Are
there any error messages in /var/log/messages?
Martin Kho _______________________________________________ kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
Hi, First time I am posting here! I had exactly the same problem as Anne. Sometimes, knetworkmanager tells me a that network management is disabled while everything looks properly configured in the system settings. this what I do when this happens : 1. Kill knetworkmanager 2. launch nm-applet (Indeed, I have to keep it installed for such cases !) 3. On the system-tray icon, *right*-click and I think that you will the check box "Enable networking" that is unchecked. Check it. The point is that I cannot find any equivalent of this checkbox in knetworkmanager. (Of course,I checked before that network and NetworkManager are enabled at startup !) 4. nm-applet should work fine now, but you can kill it and relaunch knetworkmanager, which should also work.
Hope it helps,
Ben
On Mon, Mar 8, 2010 at 12:21 PM, Martin Kho lists.kho@gmail.com wrote:
On Sun, Mar 7, 2010 at 8:02 PM, Petrus de Calguarium
kwhiskerz@gmail.com wrote:
If I am not mistaken,, you have either knetworkmanager or NetworkManager-gnome installed, not both.
You can have both installed without a problem. If you have both you get a warning (get asked?) from knetworkmanager that another applet is running and if you want to use it or not in the future. So, one is always working.
Hi,
Aren't both knetworkmanager and NetworkManager-gnome more or less front-ends to NetworkManager? So if the network doesn't work, it has to be NetworkManager that didn't detect the network-card, or did set up the interface wrongly. Are there any error messages in /var/log/messages?
Martin Kho _______________________________________________ kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
2010/3/8 Benjamin HAAS haas.benjamin@gmail.com:
2. launch nm-applet (Indeed, I have to keep it installed for such cases !)
You can also install and use 'cnetworkmanager' for such cases. It's CLI and works very well.
On Mon, Mar 8, 2010 at 12:45 PM, Thomas Janssen thomasj@fedoraproject.orgwrote:
2010/3/8 Benjamin HAAS haas.benjamin@gmail.com:
- launch nm-applet (Indeed, I have to keep it installed for such cases
!)
You can also install and use 'cnetworkmanager' for such cases. It's
CLI and works very well.
I could try it. But in any case, this does not solve the root problem : How comes that, sometimes, the network is "disabled" (by the way, /var/log/message is dumb about that) ? I still have no clue about that ... And how comes that knetworkmanager cannot control that if the gnome backend and cnetworkmanager can?
Ben.
-- LG Thomas
Dubium sapientiae initium _______________________________________________ kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
2010/3/8 Benjamin HAAS haas.benjamin@gmail.com:
On Mon, Mar 8, 2010 at 12:45 PM, Thomas Janssen thomasj@fedoraproject.org wrote:
2010/3/8 Benjamin HAAS haas.benjamin@gmail.com:
2. launch nm-applet (Indeed, I have to keep it installed for such cases !)
You can also install and use 'cnetworkmanager' for such cases. It's
CLI and works very well.
I could try it. But in any case, this does not solve the root problem : How comes that, sometimes, the network is "disabled" (by the way, /var/log/message is dumb about that) ? I still have no clue about that ... And how comes that knetworkmanager cannot control that if the gnome backend and cnetworkmanager can?
Well, IMO, knetworkmanager is the ugly little brother of NetworkManager-gnome. It lacks some love. I still use nm-applet and be happy, even it's written in a different toolkit. Though i'm waiting to get the (for me it was perfectly working, not for others) plasmoid back.
On Monday 08 March 2010 11:21:21 Martin Kho wrote:
On Sun, Mar 7, 2010 at 8:02 PM, Petrus de Calguarium
kwhiskerz@gmail.com wrote:
If I am not mistaken,, you have either knetworkmanager or NetworkManager-gnome installed, not both.
You can have both installed without a problem. If you have both you get a warning (get asked?) from knetworkmanager that another applet is running and if you want to use it or not in the future. So, one is always working.
Hi,
Aren't both knetworkmanager and NetworkManager-gnome more or less front-ends to NetworkManager? So if the network doesn't work, it has to be NetworkManager that didn't detect the network-card, or did set up the interface wrongly. Are there any error messages in /var/log/messages?
Messages appeared to be saying that the cabled connection was OK, but the wireless connection was disabled by 'killswitch'. Since the hardware switch is in a position where it can get knocked off, I played around with it until Messages accepted that it is on. However, when I got the authentication dialog there is no entry possibility for WPA! This is definitely a regression. I've had WPA with knetworkmanager before, I'm sure.
Oddly enough, ifconfig says it has an ipv6 address, but no ipv4 address. Meanwhile, the icon on the systray still tells me that the network is disabled.
Anne
On Monday 08 March 2010 11:21:21 Martin Kho wrote:
On Sun, Mar 7, 2010 at 8:02 PM, Petrus de Calguarium
kwhiskerz@gmail.com wrote:
If I am not mistaken,, you have either knetworkmanager or NetworkManager-gnome installed, not both.
You can have both installed without a problem. If you have both you get a warning (get asked?) from knetworkmanager that another applet is running and if you want to use it or not in the future. So, one is always working.
Hi,
Aren't both knetworkmanager and NetworkManager-gnome more or less front-ends to NetworkManager? So if the network doesn't work, it has to be NetworkManager that didn't detect the network-card, or did set up the interface wrongly. Are there any error messages in /var/log/messages?
Messages appeared to be saying that the cabled connection was OK, but the wireless connection was disabled by 'killswitch'. Since the hardware switch is in a position where it can get knocked off, I played around with it until Messages accepted that it is on. However, when I got the authentication dialog there is no entry possibility for WPA! This is definitely a regression. I've had WPA with knetworkmanager before, I'm sure.
Oddly enough, ifconfig says it has an ipv6 address, but no ipv4 address. Meanwhile, the icon on the systray still tells me that the network is disabled.
Hi Anne,
Just a silly question. You don't - still - have the kde-plasma version of knetworkmanager installed?
Martin Kho
Anne
On Monday 08 March 2010 13:14:19 Martin Kho wrote:
On Monday 08 March 2010 11:21:21 Martin Kho wrote:
On Sun, Mar 7, 2010 at 8:02 PM, Petrus de Calguarium
kwhiskerz@gmail.com wrote:
If I am not mistaken,, you have either knetworkmanager or NetworkManager-gnome installed, not both.
You can have both installed without a problem. If you have both you get a warning (get asked?) from knetworkmanager that another applet is running and if you want to use it or not in the future. So, one is always working.
Hi,
Aren't both knetworkmanager and NetworkManager-gnome more or less front-ends to NetworkManager? So if the network doesn't work, it has to be NetworkManager that didn't detect the network-card, or did set up the interface wrongly. Are there any error messages in /var/log/messages?
Messages appeared to be saying that the cabled connection was OK, but the wireless connection was disabled by 'killswitch'. Since the hardware switch is in a position where it can get knocked off, I played around with it until Messages accepted that it is on. However, when I got the authentication dialog there is no entry possibility for WPA! This is definitely a regression. I've had WPA with knetworkmanager before, I'm sure.
Oddly enough, ifconfig says it has an ipv6 address, but no ipv4 address. Meanwhile, the icon on the systray still tells me that the network is disabled.
Hi Anne,
Just a silly question. You don't - still - have the kde-plasma version of knetworkmanager installed?
Seems that I do. I installed it and never got around to sorting it out. I think that maybe the tray icon I'm complaining about is from that. OK - so removed the plasma object - the icon remains. I'll try a reboot in a moment to see whether the network activates properly. Funny, though, in the past I've always been able to see the cabled connection even if the wireless one wasn't available.
In desperation I installed every tool I could see to help troubleshoot this. wlassistant tells me "Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory CONNECTION FAILED". If things don't work after the reboot I'll see whether it's still getting that message.
Anne
On Monday 08 March 2010 13:37:42 Anne Wilson wrote:
On Monday 08 March 2010 13:14:19 Martin Kho wrote:
On Monday 08 March 2010 11:21:21 Martin Kho wrote:
On Sun, Mar 7, 2010 at 8:02 PM, Petrus de Calguarium
kwhiskerz@gmail.com wrote:
If I am not mistaken,, you have either knetworkmanager or NetworkManager-gnome installed, not both.
You can have both installed without a problem. If you have both you get a warning (get asked?) from knetworkmanager that another applet is running and if you want to use it or not in the future. So, one is always working.
Hi,
Aren't both knetworkmanager and NetworkManager-gnome more or less front-ends to NetworkManager? So if the network doesn't work, it has to be NetworkManager that didn't detect the network-card, or did set up the interface wrongly. Are there any error messages in /var/log/messages?
Messages appeared to be saying that the cabled connection was OK, but the wireless connection was disabled by 'killswitch'. Since the hardware switch is in a position where it can get knocked off, I played around with it until Messages accepted that it is on. However, when I got the authentication dialog there is no entry possibility for WPA! This is definitely a regression. I've had WPA with knetworkmanager before, I'm sure.
Oddly enough, ifconfig says it has an ipv6 address, but no ipv4 address. Meanwhile, the icon on the systray still tells me that the network is disabled.
Hi Anne,
Just a silly question. You don't - still - have the kde-plasma version of knetworkmanager installed?
Seems that I do. I installed it and never got around to sorting it out. I think that maybe the tray icon I'm complaining about is from that. OK - so removed the plasma object - the icon remains. I'll try a reboot in a moment to see whether the network activates properly. Funny, though, in the past I've always been able to see the cabled connection even if the wireless one wasn't available.
In desperation I installed every tool I could see to help troubleshoot this. wlassistant tells me "Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory CONNECTION FAILED". If things don't work after the reboot I'll see whether it's still getting that message.
And after a reboot, same icon, same 'Network Management disabled' message and same dialog that doesn't allow WPA-PSK. That dialog looks a lot like the one we used to have 2-3 years ago :-(
wlassistant tells me
==>stderr: Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory Using wpa_supplicant driver: wext WPA client started. Waiting for status... ==>stderr: Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory CONNECTION FAILED. disconnect: /sbin/iwconfig eth0 mode managed key off ap off essid off
Anne
On Monday 08 March 2010 13:37:42 Anne Wilson wrote:
On Monday 08 March 2010 13:14:19 Martin Kho wrote:
On Monday 08 March 2010 11:21:21 Martin Kho wrote:
On Sun, Mar 7, 2010 at 8:02 PM, Petrus de Calguarium
kwhiskerz@gmail.com wrote: > If I am not mistaken,, you have either > knetworkmanager or NetworkManager-gnome > installed, not both.
You can have both installed without a problem. If you have both you get a warning (get asked?) from knetworkmanager that another applet is running and if you want to use it or not in the future. So, one is always working.
Hi,
Aren't both knetworkmanager and NetworkManager-gnome more or less front-ends to NetworkManager? So if the network doesn't work, it has to be NetworkManager that didn't detect the network-card, or did set up the interface wrongly. Are there any error messages in /var/log/messages?
Messages appeared to be saying that the cabled connection was OK, but the wireless connection was disabled by 'killswitch'. Since the hardware switch is in a position where it can get knocked off, I played around with it until Messages accepted that it is on. However, when I got the authentication dialog there is no entry possibility for WPA! This is definitely a regression. I've had WPA with knetworkmanager before, I'm sure.
Oddly enough, ifconfig says it has an ipv6 address, but no ipv4 address. Meanwhile, the icon on the systray still tells me that the network is disabled.
Hi Anne,
Just a silly question. You don't - still - have the kde-plasma version of knetworkmanager installed?
Seems that I do. I installed it and never got around to sorting it out. I think that maybe the tray icon I'm complaining about is from that. OK
- so removed the plasma object - the icon remains. I'll try a reboot in
a moment to see whether the network activates properly. Funny, though, in the past I've always been able to see the cabled connection even if the wireless one wasn't available.
In desperation I installed every tool I could see to help troubleshoot this. wlassistant tells me "Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory CONNECTION FAILED". If things don't work after the reboot I'll see whether it's still getting that message.
And after a reboot, same icon, same 'Network Management disabled' message and same dialog that doesn't allow WPA-PSK. That dialog looks a lot like the one we used to have 2-3 years ago :-(
wlassistant tells me
==>stderr: Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory Using wpa_supplicant driver: wext WPA client started. Waiting for status... ==>stderr: Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory CONNECTION FAILED. disconnect: /sbin/iwconfig eth0 mode managed key off ap off essid off
Anne
Another silly question :-) You have wpa_supplicant running?
Martin Kho
btw: old dialog? I have installed: knetworkmanager-(libs-)0.9-0.12.20100220.fc12.x86_64 NetworkManager-(glib-)0.7.998-2.git20100106.fc12.x86_64
On Monday 08 March 2010 14:07:10 Martin Kho wrote:
Another silly question :-) You have wpa_supplicant running?
It's installed - I checked that. I never had to do anything special before to get it running - have I missed something?
Anne
2010/3/8 Anne Wilson cannewilson@googlemail.com:
On Monday 08 March 2010 13:14:19 Martin Kho wrote:
On Monday 08 March 2010 11:21:21 Martin Kho wrote:
On Sun, Mar 7, 2010 at 8:02 PM, Petrus de Calguarium
kwhiskerz@gmail.com wrote:
If I am not mistaken,, you have either knetworkmanager or NetworkManager-gnome installed, not both.
You can have both installed without a problem. If you have both you get a warning (get asked?) from knetworkmanager that another applet is running and if you want to use it or not in the future. So, one is always working.
Hi,
Aren't both knetworkmanager and NetworkManager-gnome more or less front-ends to NetworkManager? So if the network doesn't work, it has to be NetworkManager that didn't detect the network-card, or did set up the interface wrongly. Are there any error messages in /var/log/messages?
Messages appeared to be saying that the cabled connection was OK, but the wireless connection was disabled by 'killswitch'. Since the hardware switch is in a position where it can get knocked off, I played around with it until Messages accepted that it is on. However, when I got the authentication dialog there is no entry possibility for WPA! This is definitely a regression. I've had WPA with knetworkmanager before, I'm sure.
Oddly enough, ifconfig says it has an ipv6 address, but no ipv4 address. Meanwhile, the icon on the systray still tells me that the network is disabled.
Hi Anne,
Just a silly question. You don't - still - have the kde-plasma version of knetworkmanager installed?
Seems that I do. I installed it and never got around to sorting it out. I think that maybe the tray icon I'm complaining about is from that. OK - so removed the plasma object - the icon remains. I'll try a reboot in a moment to see whether the network activates properly. Funny, though, in the past I've always been able to see the cabled connection even if the wireless one wasn't available.
The networkmanagemnt plasmoid does right now nothing except popup a message that it's deprecated in favor of the systray applet. Doesn't matter if it's installed or not. I guess the worst thing that could happen is that it makes plasma-desktop crash. Well, that would actually be bad ;)
In desperation I installed every tool I could see to help troubleshoot this. wlassistant tells me "Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory CONNECTION FAILED". If things don't work after the reboot I'll see whether it's still getting that message.
Do try the NetoworkManager-gnome (nm-applet). I had a different problem, not solvable with knetworkmanager, but with nm-applet.
2010/3/8 Anne Wilson cannewilson@googlemail.com:
On Monday 08 March 2010 13:14:19 Martin Kho wrote:
On Monday 08 March 2010 11:21:21 Martin Kho wrote:
On Sun, Mar 7, 2010 at 8:02 PM, Petrus de Calguarium
kwhiskerz@gmail.com wrote: > If I am not mistaken,, you have either > knetworkmanager or NetworkManager-gnome > installed, not both.
You can have both installed without a problem. If you have both you get a warning (get asked?) from knetworkmanager that another applet is running and if you want to use it or not in the future. So, one is always working.
Hi,
Aren't both knetworkmanager and NetworkManager-gnome more or less front-ends to NetworkManager? So if the network doesn't work, it has to be NetworkManager that didn't detect the network-card, or did set up the interface wrongly. Are there any error messages in /var/log/messages?
Messages appeared to be saying that the cabled connection was OK, but the wireless connection was disabled by 'killswitch'. Since the hardware switch is in a position where it can get knocked off, I played around with it until Messages accepted that it is on. However, when I got the authentication dialog there is no entry possibility for WPA! This is definitely a regression. I've had WPA with knetworkmanager before, I'm sure.
Oddly enough, ifconfig says it has an ipv6 address, but no ipv4 address. Meanwhile, the icon on the systray still tells me that the network is disabled.
Hi Anne,
Just a silly question. You don't - still - have the kde-plasma version of knetworkmanager installed?
Seems that I do. I installed it and never got around to sorting it out. I think that maybe the tray icon I'm complaining about is from that. OK - so removed the plasma object - the icon remains. I'll try a reboot in a moment to see whether the network activates properly. Funny, though, in the past I've always been able to see the cabled connection even if the wireless one wasn't available.
The networkmanagemnt plasmoid does right now nothing except popup a message that it's deprecated in favor of the systray applet. Doesn't matter if it's installed or not. I guess the worst thing that could happen is that it makes plasma-desktop crash. Well, that would actually be bad ;)
Hi,
I'm not sure if you're right here if I read Will Stephenson's post under point b), see [1]
Martin Kho
[1] http://mail.kde.org/pipermail/kde-networkmanager/2009-November/000480.html
In desperation I installed every tool I could see to help troubleshoot this. wlassistant tells me "Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory CONNECTION FAILED". If things don't work after the reboot I'll see whether it's still getting that message.
Do try the NetoworkManager-gnome (nm-applet). I had a different problem, not solvable with knetworkmanager, but with nm-applet.
On Mon, Mar 8, 2010 at 4:04 PM, Martin Kho lists.kho@gmail.com wrote:
2010/3/8 Anne Wilson cannewilson@googlemail.com:
On Monday 08 March 2010 13:14:19 Martin Kho wrote:
On Monday 08 March 2010 11:21:21 Martin Kho wrote:
> On Sun, Mar 7, 2010 at 8:02 PM, Petrus de Calguarium > > kwhiskerz@gmail.com wrote: > > If I am not mistaken,, you have either > > knetworkmanager or NetworkManager-gnome > > installed, not both. > > You can have both installed without a problem. If you have both > you get a warning (get asked?) from knetworkmanager that another > applet is running and if you want to use it or not in the future. > So, one is always working.
Hi,
Aren't both knetworkmanager and NetworkManager-gnome more or less front-ends to NetworkManager? So if the network doesn't work, it has to be NetworkManager that didn't detect the network-card, or did set up the interface wrongly. Are there any error messages in /var/log/messages?
Messages appeared to be saying that the cabled connection was OK, but the wireless connection was disabled by 'killswitch'. Since the hardware switch is in a position where it can get knocked off, I played around with it until Messages accepted that it is on. However, when I got the authentication dialog there is no entry possibility for WPA! This is definitely a regression. I've had WPA with knetworkmanager before, I'm sure.
Oddly enough, ifconfig says it has an ipv6 address, but no ipv4 address. Meanwhile, the icon on the systray still tells me that the network is disabled.
Hi Anne,
Just a silly question. You don't - still - have the kde-plasma version of knetworkmanager installed?
Seems that I do. I installed it and never got around to sorting it out. I think that maybe the tray icon I'm complaining about is from that. OK - so removed the plasma object - the icon remains. I'll try a reboot in a moment to see whether the network activates properly. Funny, though, in the past I've always been able to see the cabled connection even if the wireless one wasn't available.
The networkmanagemnt plasmoid does right now nothing except popup a message that it's deprecated in favor of the systray applet. Doesn't matter if it's installed or not. I guess the worst thing that could happen is that it makes plasma-desktop crash. Well, that would actually be bad ;)
Hi,
I'm not sure if you're right here if I read Will Stephenson's post under point b), see [1]
Hi,
well, i have no idea about Kubuntu ;) But i speak out of experience. I had the plasmoid. I have both frontends installed, the gnome and the kde one (using the gnome one) and cnetworkmanager. Yes, you can run only one at the same time. But the plasmoid i had did nothing except that popup (of course after it got deprecated for now). Could of course be that my brain serves bad here and i had to de-install it. Will try it later with some time again.
On Monday 08 March 2010 14:37:47 Thomas Janssen wrote:
Do try the NetoworkManager-gnome (nm-applet). I had a different problem, not solvable with knetworkmanager, but with nm-applet.
I could try it again, but of course the reason I was trying knetwork manager was because NetworkManager-gnome wasn't working. Still, it's worth a try, since I tried to change over before the 4.4.1 update. I'll report back.
Anne
On Monday 08 March 2010 15:55:45 Anne Wilson wrote:
On Monday 08 March 2010 14:37:47 Thomas Janssen wrote:
Do try the NetoworkManager-gnome (nm-applet). I had a different problem, not solvable with knetworkmanager, but with nm-applet.
I could try it again, but of course the reason I was trying knetwork manager was because NetworkManager-gnome wasn't working. Still, it's worth a try, since I tried to change over before the 4.4.1 update. I'll report back.
Is there no way of restarting things like this, without rebooting? It's beginning to feel like windows! AIUI the command 'service network restart' can't be used if NetworkManager-gnome is to control it. Is that right?
Anne
On 03/08/2010 12:06 PM, Anne Wilson wrote:
On Monday 08 March 2010 15:55:45 Anne Wilson wrote:
On Monday 08 March 2010 14:37:47 Thomas Janssen wrote:
Do try the NetoworkManager-gnome (nm-applet). I had a different problem, not solvable with knetworkmanager, but with nm-applet.
I could try it again, but of course the reason I was trying knetwork manager was because NetworkManager-gnome wasn't working. Still, it's worth a try, since I tried to change over before the 4.4.1 update. I'll report back.
Is there no way of restarting things like this, without rebooting? It's beginning to feel like windows! AIUI the command 'service network restart' can't be used if NetworkManager-gnome is to control it. Is that right?
service NetworkManager restart
Anne
kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
On Monday 08 March 2010 16:09:44 Patrick Boutilier wrote:
On 03/08/2010 12:06 PM, Anne Wilson wrote:
On Monday 08 March 2010 15:55:45 Anne Wilson wrote:
On Monday 08 March 2010 14:37:47 Thomas Janssen wrote:
Do try the NetoworkManager-gnome (nm-applet). I had a different problem, not solvable with knetworkmanager, but with nm-applet.
I could try it again, but of course the reason I was trying knetwork manager was because NetworkManager-gnome wasn't working. Still, it's worth a try, since I tried to change over before the 4.4.1 update. I'll report back.
Is there no way of restarting things like this, without rebooting? It's beginning to feel like windows! AIUI the command 'service network restart' can't be used if NetworkManager-gnome is to control it. Is that right?
service NetworkManager restart
service NetworkManager restart Stopping NetworkManager daemon: [ OK ] Setting network parameters... [ OK ] Starting NetworkManager daemon: [ OK ] [root@anne-laptop ~]# ifup eth0
Determining IP information for eth0...dhclient(6296) is already running - exiting.
This version of ISC DHCP is based on the release available on ftp.isc.org. Features have been added and other changes have been made to the base software release in order to make it work better with this distribution.
Please report for this software via the Red Hat Bugzilla site: http://bugzilla.redhat.com
exiting. failed.
I think I'm beaten.
Just one thought - I have no idea why, but on this laptop eth0 is defined as the wireless interface and eth1 is the cabled one. I didn't do this - the setup did - but I'm beginning to wonder whether it's relevant.
Anne
On 03/08/2010 12:17 PM, Anne Wilson wrote:
On Monday 08 March 2010 16:09:44 Patrick Boutilier wrote:
On 03/08/2010 12:06 PM, Anne Wilson wrote:
On Monday 08 March 2010 15:55:45 Anne Wilson wrote:
On Monday 08 March 2010 14:37:47 Thomas Janssen wrote:
Do try the NetoworkManager-gnome (nm-applet). I had a different problem, not solvable with knetworkmanager, but with nm-applet.
I could try it again, but of course the reason I was trying knetwork manager was because NetworkManager-gnome wasn't working. Still, it's worth a try, since I tried to change over before the 4.4.1 update. I'll report back.
Is there no way of restarting things like this, without rebooting? It's beginning to feel like windows! AIUI the command 'service network restart' can't be used if NetworkManager-gnome is to control it. Is that right?
service NetworkManager restart
service NetworkManager restart Stopping NetworkManager daemon: [ OK ] Setting network parameters... [ OK ] Starting NetworkManager daemon: [ OK ] [root@anne-laptop ~]# ifup eth0
Determining IP information for eth0...dhclient(6296) is already running - exiting.
This version of ISC DHCP is based on the release available on ftp.isc.org. Features have been added and other changes have been made to the base software release in order to make it work better with this distribution.
Please report for this software via the Red Hat Bugzilla site: http://bugzilla.redhat.com
exiting. failed.
I think I'm beaten.
service NetworkManager stop killall dhclient service NetworkManager start
Just one thought - I have no idea why, but on this laptop eth0 is defined as the wireless interface and eth1 is the cabled one. I didn't do this - the setup did - but I'm beginning to wonder whether it's relevant.
Anne
kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
On Monday 08 March 2010 16:20:47 Patrick Boutilier wrote:
service NetworkManager stop killall dhclient service NetworkManager start
Exactly the same error messages when running ifiup eth0.
Anne
On Monday 08 March 2010 17:41:49 Anne Wilson wrote:
On Monday 08 March 2010 16:20:47 Patrick Boutilier wrote:
service NetworkManager stop killall dhclient service NetworkManager start
Exactly the same error messages when running ifiup eth0.
Is ifup necessary with NetworkManager? I thought it's a friend of network.
Anne
On Monday 08 March 2010 16:49:15 Martin Kho wrote:
On Monday 08 March 2010 17:41:49 Anne Wilson wrote:
On Monday 08 March 2010 16:20:47 Patrick Boutilier wrote:
service NetworkManager stop killall dhclient service NetworkManager start
Exactly the same error messages when running ifiup eth0.
Is ifup necessary with NetworkManager? I thought it's a friend of network.
it shouldn't be necessary, but since it's not running it seemed sensible to try ifup
Anne
On 03/08/2010 12:41 PM, Anne Wilson wrote:
On Monday 08 March 2010 16:20:47 Patrick Boutilier wrote:
service NetworkManager stop killall dhclient service NetworkManager start
Exactly the same error messages when running ifiup eth0.
Oh, I didn't notice that you ran ifup . dhclient would have been spawned by NetworkManager so it make sense you get that error since dhclient is already running.
Anne
kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
On Monday 08 March 2010 17:17:51 Anne Wilson wrote:
On Monday 08 March 2010 16:09:44 Patrick Boutilier wrote:
On 03/08/2010 12:06 PM, Anne Wilson wrote:
On Monday 08 March 2010 15:55:45 Anne Wilson wrote:
On Monday 08 March 2010 14:37:47 Thomas Janssen wrote:
Do try the NetoworkManager-gnome (nm-applet). I had a different problem, not solvable with knetworkmanager, but with nm-applet.
I could try it again, but of course the reason I was trying knetwork manager was because NetworkManager-gnome wasn't working. Still, it's worth a try, since I tried to change over before the 4.4.1 update. I'll report back.
Is there no way of restarting things like this, without rebooting? It's beginning to feel like windows! AIUI the command 'service network restart' can't be used if NetworkManager-gnome is to control it. Is that right?
service NetworkManager restart
service NetworkManager restart Stopping NetworkManager daemon: [ OK ] Setting network parameters... [ OK ] Starting NetworkManager daemon: [ OK ] [root@anne-laptop ~]# ifup eth0
Determining IP information for eth0...dhclient(6296) is already running - exiting.
This version of ISC DHCP is based on the release available on ftp.isc.org. Features have been added and other changes have been made to the base software release in order to make it work better with this distribution.
Please report for this software via the Red Hat Bugzilla site: http://bugzilla.redhat.com
exiting. failed.
I think I'm beaten.
Just one thought - I have no idea why, but on this laptop eth0 is defined as the wireless interface and eth1 is the cabled one. I didn't do this - the setup did - but I'm beginning to wonder whether it's relevant.
What have in /etc/sysconfig/network-scripts/ifcfg-eth[0,1]? Do they exist?
Anne
On Monday 08 March 2010 16:36:25 Martin Kho wrote:
On Monday 08 March 2010 17:17:51 Anne Wilson wrote:
On Monday 08 March 2010 16:09:44 Patrick Boutilier wrote:
On 03/08/2010 12:06 PM, Anne Wilson wrote:
On Monday 08 March 2010 15:55:45 Anne Wilson wrote:
On Monday 08 March 2010 14:37:47 Thomas Janssen wrote:
Do try the NetoworkManager-gnome (nm-applet). I had a different problem, not solvable with knetworkmanager, but with nm-applet.
I could try it again, but of course the reason I was trying knetwork manager was because NetworkManager-gnome wasn't working. Still, it's worth a try, since I tried to change over before the 4.4.1 update. I'll report back.
Is there no way of restarting things like this, without rebooting? It's beginning to feel like windows! AIUI the command 'service network restart' can't be used if NetworkManager-gnome is to control it. Is that right?
service NetworkManager restart
service NetworkManager restart Stopping NetworkManager daemon: [ OK ] Setting network parameters... [ OK ] Starting NetworkManager daemon: [ OK ] [root@anne-laptop ~]# ifup eth0
Determining IP information for eth0...dhclient(6296) is already running - exiting.
This version of ISC DHCP is based on the release available on ftp.isc.org. Features have been added and other changes have been made to the base software release in order to make it work better with this distribution.
Please report for this software via the Red Hat Bugzilla site: http://bugzilla.redhat.com
exiting.
failed.
I think I'm beaten.
Just one thought - I have no idea why, but on this laptop eth0 is defined as the wireless interface and eth1 is the cabled one. I didn't do this - the setup did - but I'm beginning to wonder whether it's relevant.
What have in /etc/sysconfig/network-scripts/ifcfg-eth[0,1]? Do they exist?
Experimenting in system-config-network I changed eth0 to wlan0, but ifup wlan0 gives the same errors.
ifcfg-wlan0 # Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection DEVICE=eth0 BOOTPROTO=dhcp HWADDR=xx:xx:xx:xx:xx:xx ONBOOT=yes DNS2=212.23.3.100 TYPE=Wireless DNS1=192.168.0.1 NM_CONTROLLED=yes USERCTL=yes PEERDNS=yes IPV6INIT=yes MODE=Managed RATE=auto ESSID= CHANNEL=
(the firmware is installed)
ifcfg-eth1 # Broadcom Corporation NetXtreme BCM5788 Gigabit Ethernet DEVICE=eth1 BOOTPROTO=dhcp HWADDR=xx:xx:xx:xx:xx:xx ONBOOT=yes TYPE=Ethernet IPV6INIT=no USERCTL=no
Anne
On Monday 08 March 2010 17:53:44 Anne Wilson wrote:
On Monday 08 March 2010 16:36:25 Martin Kho wrote:
On Monday 08 March 2010 17:17:51 Anne Wilson wrote:
On Monday 08 March 2010 16:09:44 Patrick Boutilier wrote:
On 03/08/2010 12:06 PM, Anne Wilson wrote:
On Monday 08 March 2010 15:55:45 Anne Wilson wrote:
On Monday 08 March 2010 14:37:47 Thomas Janssen wrote: > Do try the NetoworkManager-gnome (nm-applet). I had a different > problem, not solvable with knetworkmanager, but with nm-applet.
I could try it again, but of course the reason I was trying knetwork manager was because NetworkManager-gnome wasn't working. Still, it's worth a try, since I tried to change over before the 4.4.1 update. I'll report back.
Is there no way of restarting things like this, without rebooting? It's beginning to feel like windows! AIUI the command 'service network restart' can't be used if NetworkManager-gnome is to control it. Is that right?
service NetworkManager restart
service NetworkManager restart Stopping NetworkManager daemon: [ OK ] Setting network parameters... [ OK ] Starting NetworkManager daemon: [ OK ] [root@anne-laptop ~]# ifup eth0
Determining IP information for eth0...dhclient(6296) is already running
- exiting.
This version of ISC DHCP is based on the release available on ftp.isc.org. Features have been added and other changes have been made to the base software release in order to make it work better with this distribution.
Please report for this software via the Red Hat Bugzilla site: http://bugzilla.redhat.com
exiting.
failed.
I think I'm beaten.
Just one thought - I have no idea why, but on this laptop eth0 is defined as the wireless interface and eth1 is the cabled one. I didn't do this - the setup did - but I'm beginning to wonder whether it's relevant.
What have in /etc/sysconfig/network-scripts/ifcfg-eth[0,1]? Do they exist?
Experimenting in system-config-network I changed eth0 to wlan0, but ifup wlan0 gives the same errors.
Running system-config-network sets up network not NetworkManager. In my config for eth0 I only have:
"# Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller DEVICE=eth0 HWADDR=00:18:F3:8A:F3:D6"
The rest is set up by NetworkManager. In /var/lib/dhclient/dhclient-<big number>-eth[0,1].lease you'll find the find the set up info.
ifcfg-wlan0 # Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection DEVICE=eth0 BOOTPROTO=dhcp HWADDR=xx:xx:xx:xx:xx:xx ONBOOT=yes DNS2=212.23.3.100 TYPE=Wireless DNS1=192.168.0.1 NM_CONTROLLED=yes USERCTL=yes PEERDNS=yes IPV6INIT=yes MODE=Managed RATE=auto ESSID= CHANNEL=
(the firmware is installed)
ifcfg-eth1 # Broadcom Corporation NetXtreme BCM5788 Gigabit Ethernet DEVICE=eth1 BOOTPROTO=dhcp HWADDR=xx:xx:xx:xx:xx:xx ONBOOT=yes TYPE=Ethernet IPV6INIT=no USERCTL=no
Anne
On Monday 08 March 2010 18:15:06 Martin Kho wrote:
On Monday 08 March 2010 17:53:44 Anne Wilson wrote:
On Monday 08 March 2010 16:36:25 Martin Kho wrote:
On Monday 08 March 2010 17:17:51 Anne Wilson wrote:
On Monday 08 March 2010 16:09:44 Patrick Boutilier wrote:
On 03/08/2010 12:06 PM, Anne Wilson wrote:
On Monday 08 March 2010 15:55:45 Anne Wilson wrote: > On Monday 08 March 2010 14:37:47 Thomas Janssen wrote: >> Do try the NetoworkManager-gnome (nm-applet). I had a different >> problem, not solvable with knetworkmanager, but with nm-applet. > > I could try it again, but of course the reason I was trying > knetwork manager was because NetworkManager-gnome wasn't > working. > > Still, it's worth a try, since I tried to change over before > the > > 4.4.1 update. I'll report back.
Is there no way of restarting things like this, without rebooting? It's beginning to feel like windows! AIUI the command 'service network restart' can't be used if NetworkManager-gnome is to control it. Is that right?
service NetworkManager restart
service NetworkManager restart Stopping NetworkManager daemon: [ OK ] Setting network parameters... [ OK ] Starting NetworkManager daemon: [ OK ] [root@anne-laptop ~]# ifup eth0
Determining IP information for eth0...dhclient(6296) is already running - exiting.
This version of ISC DHCP is based on the release available on ftp.isc.org. Features have been added and other changes have been made to the base software release in order to make it work better with this distribution.
Please report for this software via the Red Hat Bugzilla site: http://bugzilla.redhat.com
exiting.
failed.
I think I'm beaten.
Just one thought - I have no idea why, but on this laptop eth0 is defined as the wireless interface and eth1 is the cabled one. I didn't do this - the setup did - but I'm beginning to wonder whether it's relevant.
What have in /etc/sysconfig/network-scripts/ifcfg-eth[0,1]? Do they exist?
Experimenting in system-config-network I changed eth0 to wlan0, but ifup wlan0 gives the same errors.
Running system-config-network sets up network not NetworkManager.
My formulation is not good: Better is - I think - NetworkManager doesn't need system-config-network to set up the network, network does.
In my config for eth0 I only have:
"# Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller DEVICE=eth0 HWADDR=00:18:F3:8A:F3:D6"
The rest is set up by NetworkManager. In /var/lib/dhclient/dhclient-<big number>-eth[0,1].lease you'll find the find the set up info.
ifcfg-wlan0 # Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection DEVICE=eth0 BOOTPROTO=dhcp HWADDR=xx:xx:xx:xx:xx:xx ONBOOT=yes DNS2=212.23.3.100 TYPE=Wireless DNS1=192.168.0.1 NM_CONTROLLED=yes USERCTL=yes PEERDNS=yes IPV6INIT=yes MODE=Managed RATE=auto ESSID= CHANNEL=
(the firmware is installed)
ifcfg-eth1 # Broadcom Corporation NetXtreme BCM5788 Gigabit Ethernet DEVICE=eth1 BOOTPROTO=dhcp HWADDR=xx:xx:xx:xx:xx:xx ONBOOT=yes TYPE=Ethernet IPV6INIT=no USERCTL=no
Anne
On Monday 08 March 2010 17:17:51 Anne Wilson wrote:
On Monday 08 March 2010 16:09:44 Patrick Boutilier wrote:
On 03/08/2010 12:06 PM, Anne Wilson wrote:
On Monday 08 March 2010 15:55:45 Anne Wilson wrote:
On Monday 08 March 2010 14:37:47 Thomas Janssen wrote:
Do try the NetoworkManager-gnome (nm-applet). I had a different problem, not solvable with knetworkmanager, but with nm-applet.
I could try it again, but of course the reason I was trying knetwork manager was because NetworkManager-gnome wasn't working. Still, it's worth a try, since I tried to change over before the 4.4.1 update. I'll report back.
Is there no way of restarting things like this, without rebooting? It's beginning to feel like windows! AIUI the command 'service network restart' can't be used if NetworkManager-gnome is to control it. Is that right?
service NetworkManager restart
service NetworkManager restart Stopping NetworkManager daemon: [ OK ] Setting network parameters... [ OK ] Starting NetworkManager daemon: [ OK ] [root@anne-laptop ~]# ifup eth0
Determining IP information for eth0...dhclient(6296) is already running - exiting.
This version of ISC DHCP is based on the release available on ftp.isc.org. Features have been added and other changes have been made to the base software release in order to make it work better with this distribution.
Please report for this software via the Red Hat Bugzilla site: http://bugzilla.redhat.com
exiting. failed.
I think I'm beaten.
Just one thought - I have no idea why, but on this laptop eth0 is defined as the wireless interface and eth1 is the cabled one. I didn't do this - the setup did - but I'm beginning to wonder whether it's relevant.
... and you're sure your kernel-module is loaded? The right one?
Anne
On Monday 08 March 2010 16:40:00 Martin Kho wrote:
... and you're sure your kernel-module is loaded? The right one?
ipw2200 firmware? yes, I'm sure that it's installed.
Anne
On 03/08/2010 12:55 PM, Anne Wilson wrote:
On Monday 08 March 2010 16:40:00 Martin Kho wrote:
... and you're sure your kernel-module is loaded? The right one?
ipw2200 firmware? yes, I'm sure that it's installed.
What does iwconfig show?
Anne
kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
On Monday 08 March 2010 17:00:56 Patrick Boutilier wrote:
On 03/08/2010 12:55 PM, Anne Wilson wrote:
On Monday 08 March 2010 16:40:00 Martin Kho wrote:
... and you're sure your kernel-module is loaded? The right one?
ipw2200 firmware? yes, I'm sure that it's installed.
What does iwconfig show?
eth0 IEEE 802.11g ESSID:"Lydgate2" Nickname:"anne-laptop.lydgate.net" Mode:Managed Frequency:2.422 GHz Access Point: 0xx:xx:xx:xx:xx:xx Bit Rate:54 Mb/s Tx-Power=20 dBm Sensitivity=8/0 Retry limit:7 RTS thr:off Fragment thr:off Encryption key: long string Security mode:open #should be WPA-PSK Power Management:off Link Quality=99/100 Signal level=-22 dBm Noise level=-92 dBm Rx invalid nwid:0 Rx invalid crypt:11 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Note that it says eth0, not wlan0. I'll copy the ifcfg to eth0 and see if that makes any difference.
Anne
On 03/08/2010 01:14 PM, Anne Wilson wrote:
On Monday 08 March 2010 17:00:56 Patrick Boutilier wrote:
On 03/08/2010 12:55 PM, Anne Wilson wrote:
On Monday 08 March 2010 16:40:00 Martin Kho wrote:
... and you're sure your kernel-module is loaded? The right one?
ipw2200 firmware? yes, I'm sure that it's installed.
What does iwconfig show?
eth0 IEEE 802.11g ESSID:"Lydgate2" Nickname:"anne-laptop.lydgate.net" Mode:Managed Frequency:2.422 GHz Access Point: 0xx:xx:xx:xx:xx:xx Bit Rate:54 Mb/s Tx-Power=20 dBm Sensitivity=8/0 Retry limit:7 RTS thr:off Fragment thr:off Encryption key: long string Security mode:open #should be WPA-PSK Power Management:off Link Quality=99/100 Signal level=-22 dBm Noise level=-92 dBm Rx invalid nwid:0 Rx invalid crypt:11 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Note that it says eth0, not wlan0. I'll copy the ifcfg to eth0 and see if that makes any difference.
Encryption key: long string Security mode:open #should be WPA-PSK
That looks to me like you are using WEP.
Mine on WPA2 looks like:
Encryption key:off Power Management:off
NetworkManager actually handles the keys:
NetworkManager: <info> Activation (wlan0/wireless): connection 'GGGGG' has security, and secrets exist. No new secrets needed. NetworkManager: <info> Config: added 'ssid' value 'GGGGG' NetworkManager: <info> Config: added 'scan_ssid' value '1' NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-PSK' NetworkManager: <info> Config: added 'psk' value '<omitted>'
Anne
kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
On Monday 08 March 2010 17:42:20 Patrick Boutilier wrote:
On 03/08/2010 01:14 PM, Anne Wilson wrote:
On Monday 08 March 2010 17:00:56 Patrick Boutilier wrote:
On 03/08/2010 12:55 PM, Anne Wilson wrote:
On Monday 08 March 2010 16:40:00 Martin Kho wrote:
... and you're sure your kernel-module is loaded? The right one?
ipw2200 firmware? yes, I'm sure that it's installed.
What does iwconfig show?
eth0 IEEE 802.11g ESSID:"Lydgate2" Nickname:"anne-laptop.lydgate.net"
Mode:Managed Frequency:2.422 GHz Access Point: 0xx:xx:xx:xx:xx:xx Bit Rate:54 Mb/s Tx-Power=20 dBm Sensitivity=8/0 Retry limit:7 RTS thr:off Fragment thr:off Encryption key: long string Security mode:open #should be WPA-PSK Power Management:off Link Quality=99/100 Signal level=-22 dBm Noise level=-92 dBm Rx invalid nwid:0 Rx invalid crypt:11 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0Note that it says eth0, not wlan0. I'll copy the ifcfg to eth0 and see if that makes any difference.
Encryption key: long string Security mode:open #should be WPA-PSK
That looks to me like you are using WEP.
Mine on WPA2 looks like:
Encryption key:off Power Management:off
NetworkManager actually handles the keys:
NetworkManager: <info> Activation (wlan0/wireless): connection 'GGGGG' has security, and secrets exist. No new secrets needed. NetworkManager: <info> Config: added 'ssid' value 'GGGGG' NetworkManager: <info> Config: added 'scan_ssid' value '1' NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-PSK' NetworkManager: <info> Config: added 'psk' value '<omitted>'
I've been using WPA-PSK for years, and the router is definitely set to use WPA-PSK. It's all very puzzling. I don't understand why I'm only being offered the possiblity of WEP - I've never used it - ever.
Anne
On Monday 08 March 2010 17:42:20 Patrick Boutilier wrote:
Encryption key: long string Security mode:open #should be WPA-PSK
That looks to me like you are using WEP.
Mine on WPA2 looks like:
This router is not young enough to have WPA2 - but WPA1 should work fine.
Encryption key:off Power Management:off
Decision made. I'm leaving it for tonight. I probably won't have time tomorrow, but then I'll get out the netbook. I use that for roaming, so it has connected with various public (open) networks. I'll see if I can copy configurations from there.
Anne
2010/3/8 Anne Wilson cannewilson@googlemail.com:
On Monday 08 March 2010 15:55:45 Anne Wilson wrote:
On Monday 08 March 2010 14:37:47 Thomas Janssen wrote:
Do try the NetoworkManager-gnome (nm-applet). I had a different problem, not solvable with knetworkmanager, but with nm-applet.
I could try it again, but of course the reason I was trying knetwork manager was because NetworkManager-gnome wasn't working. Still, it's worth a try, since I tried to change over before the 4.4.1 update. I'll report back.
Is there no way of restarting things like this, without rebooting? It's beginning to feel like windows! AIUI the command 'service network restart' can't be used if NetworkManager-gnome is to control it. Is that right?
service NetworkManager restart
2010/3/8 Anne Wilson cannewilson@googlemail.com:
On Monday 08 March 2010 15:55:45 Anne Wilson wrote:
On Monday 08 March 2010 14:37:47 Thomas Janssen wrote:
Do try the NetoworkManager-gnome (nm-applet). I had a different problem, not solvable with knetworkmanager, but with nm-applet.
I could try it again, but of course the reason I was trying knetwork manager was because NetworkManager-gnome wasn't working. Still, it's worth a try, since I tried to change over before the 4.4.1 update. I'll report back.
Is there no way of restarting things like this, without rebooting? It's beginning to feel like windows! AIUI the command 'service network restart' can't be used if NetworkManager-gnome is to control it. Is that right?
Oh and by the way, network service should be off IIRC.
On Monday 08 March 2010 16:11:44 Thomas Janssen wrote:
Oh and by the way, network service should be off IIRC.
It is.
Anne
Anne Wilson wrote:
It seems I have knetworkmanager and NetworkManager* installed, which may well be why I have problems. In the systemtray I have an icon that looks like an unplugged RJ45 cable, which tells me that the network is not available. Nonsense, of course. Left or Right-click on it tells me that network management is disabled.
NetworkManager-gnome never seemed to work on this laptop, so I'd like to try knetworkmanager. Can you give me some hints with regard to sorting this out? Thanks
One thing to mention: nm-applet has a check box for "Enable networking". knetworkmanager doesn't have this, and in fact, if networkmanager ever gets into the state where it thinks "Enable networking" isn't, then knetworkmanager doesn't work (ie, it runs, but nothing happens and nothing appears in the system tray). See also,
https://bugs.kde.org/show_bug.cgi?id=223030
-- Rex
-
Anne Wilson -
Benjamin HAAS -
Kevin Kofler -
Martin Kho -
Patrick Boutilier -
Petrus de Calguarium -
Rares Aioanei -
Rex Dieter -
Thomas Janssen