Re: Mysteries of NM
On Sat, 2011-02-26 at 15:09 +, Timothy Murphy wrote: I'm running NetworkManager on my Thinkpad T60 (Intel PRO/Wireless 3945ABG controller, iwl3945 driver) and it works fine under Fedora/KDE, but I find the user interface almost completely unintelligible. If I left click on the NM icon in the panel a window comes up with WLAN Interface on the left, and Connections on the right. (Rather annoyingly, there is no X at the top right-hand corner to close the window, one has to click again on the icon.) A number of APs (4) are listed on the right, including the one I am using. On the left, the Traffic box shows a number of moving spikes, distributed unevenly but approximately one every 10 seconds. I take it these are beacons of some kind from the APs? If I click on the Manage Connections button at the bottom of the window and then choose Wireless, my present connection is listed, but it says Last Used: Never. which I find puzzling. If I highlight this entry, and click on Scan, I see rather a nice map showing the APs previously listed, presumably showing the stronger signals nearer to the centre. (What, if anything, does the location around the circle mean?) I find it odd that this graphic only appears after I have chosen a specific connection; I would have thought it would be more logical to offer it when the APs were listed earlier. Are others puzzled by the NM interface, or am I being obtuse? I am mystified by your description of the interface. When I left click on the NM icon I get no Traffic Box, no Manage Connwections button, etc, etc and so forth. Is it that you are using knetworkmanager rather than Network Manager? -- === Many pages make a thick book. === Aaron Konstam telephone: (210) 656-0355 e-mail: akons...@sbcglobal.net ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager reason codes
On Thu, 2011-02-10 at 21:10 +, mike cloaked wrote: That is of course fine - but there are use cases where the two APs are both in one's own home - and both have the same ssid and that presents a problem - at least for me. Ok it is time to admit ignorance. I don't understand the scenario described above. What are the implications of having 2 APs in your house (meaning I assume that they have thew same wireless passed) but different bssids (presumably different Mac addresses for the AP cards). How would you specify using NM one AP over the other. Wouldn't only one connection entry show up on the NM access point list? -- === Murder is always a mistake -- one should never do anything one cannot talk about after dinner. -- Oscar Wilde, The Picture of Dorian Gray === Aaron Konstam telephone: (210) 656-0355 e-mail: akons...@sbcglobal.net ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
wilreless connection before login
A week or so ago I posted the following question: I have meant to follow up on this years ago but let it slip. But this came up recently on the fedora-list so I need to ask. It seems to me that several versions ago it was possible to have NM create a wireless connection on boot rather than only on login. Is this possible and if so how does one set this up? - From Marc Herbert I received the response Wild guess: did you try to configure it using system-config-network, and then pass it to NM using the ifcfg-rh plugin? http://live.gnome.org/NetworkManager/SystemSettings --- I used system-configure-network to re-configure the ifcfg-eth1 file and am using the ifcfg-rh plugin. I got no connection before boot although the ifcfg-eth1 file indicated the ONBOOT=yes option --- from Dan Williams I got the comment: You can also move connections between user and system with nm-connection-editor; look for the Available to all users checkbox in each connection's edit window. Checking that box makes it a system connection (thus available at boot time) as long as a plugin is enabled that allows writing of system connections. That wiki page should also talk about system settings plugins. Dan --- I tried that. I used nm-connection-editor to edit the entry for the AP I was using. Checked: the Available to all users checkbox. Then maybe I made a mistake by clicking activate. The result was the AP disappeared from the list of APs seen in the nm-applet, so that was no good. Would someone just tell me how to activate a wireless connection before logging in with clear instructions I can follow. I assume this is possible -- === Blessed is he who expects no gratitude, for he shall not be disappointed. -- W.C. Bennett === Aaron Konstam telephone: (210) 656-0355 e-mail: akons...@sbcglobal.net -- === What!? Me worry? -- Alfred E. Newman === Aaron Konstam telephone: (210) 656-0355 e-mail: akons...@sbcglobal.net ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
wirelesws connection before login
I have meant to follow up on this years ago but let it slip. But this came up recently on the fedora-list so I need to ask. It seems to me that several versions ago it was possible to have NM create a wireless connection on boot rather than only on login. Is this possible and if so how does one set this up? -- === It's a summons. What's a summons? It means summon's in trouble. -- Rocky and Bullwinkle === Aaron Konstam telephone: (210) 656-0355 e-mail: akons...@sbcglobal.net ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: debug tips
On Wed, 2009-06-03 at 10:55 +0100, Marc Herbert wrote: Aaron Konstam a écrit : On Mon, 2009-06-01 at 08:53 -0700, Daniel Fetchinson wrote: As I've said, but let me repeat it again, I do boot into run level 3. After logging in I start X manually via startx. We are having a giant miscommunication going on . What rl are you actually running at? No, there is no miscommunication, simply you just have to believe that it is possible to boot in runlevel 3 and then it is possible to start X manually via startx :) I believe it, if you will accept that running startx puts you in to rl5 not rl3. Huh? startx is changing the runlevel? That is some news. This is a semantic argument. rl3 does not support X, rl5 does. I have never actually checked this but I would be amazed if when one runs startx the system does not switch to rl5. But I guess I will have to try it or depend on the testimony of someone who runs startx. I have been amazed before. -- === Hofstadter's Law: It always takes longer than you expect, even when you take Hofstadter's Law into account. === Aaron Konstam telephone: (210) 656-0355 e-mail: akons...@sbcglobal.net ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: debug tips
On Wed, 2009-06-03 at 08:21 -0500, Aaron Konstam wrote: On Wed, 2009-06-03 at 10:55 +0100, Marc Herbert wrote: Aaron Konstam a écrit : On Mon, 2009-06-01 at 08:53 -0700, Daniel Fetchinson wrote: As I've said, but let me repeat it again, I do boot into run level 3. After logging in I start X manually via startx. We are having a giant miscommunication going on . What rl are you actually running at? No, there is no miscommunication, simply you just have to believe that it is possible to boot in runlevel 3 and then it is possible to start X manually via startx :) I believe it, if you will accept that running startx puts you in to rl5 not rl3. Huh? startx is changing the runlevel? That is some news. This is a semantic argument. rl3 does not support X, rl5 does. I have never actually checked this but I would be amazed if when one runs startx the system does not switch to rl5. But I guess I will have to try it or depend on the testimony of someone who runs startx. I have been amazed before. Well it is always good to be amazed at least once a day. I tried it. startx does not cause rl5 to be reported by runlevel. Howver, at least on my machine NM does not run the way it should. -- === memo, n.: An interoffice communication too often written more for the benefit of the person who sends it than the person who receives it. === Aaron Konstam telephone: (210) 656-0355 e-mail: akons...@sbcglobal.net ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: debug tips
On Wed, 2009-06-03 at 09:49 -0400, Dan Williams wrote: On Wed, 2009-06-03 at 08:40 -0500, Aaron Konstam wrote: On Wed, 2009-06-03 at 08:21 -0500, Aaron Konstam wrote: On Wed, 2009-06-03 at 10:55 +0100, Marc Herbert wrote: Aaron Konstam a écrit : On Mon, 2009-06-01 at 08:53 -0700, Daniel Fetchinson wrote: As I've said, but let me repeat it again, I do boot into run level 3. After logging in I start X manually via startx. We are having a giant miscommunication going on . What rl are you actually running at? No, there is no miscommunication, simply you just have to believe that it is possible to boot in runlevel 3 and then it is possible to start X manually via startx :) I believe it, if you will accept that running startx puts you in to rl5 not rl3. Huh? startx is changing the runlevel? That is some news. This is a semantic argument. rl3 does not support X, rl5 does. I have never actually checked this but I would be amazed if when one runs startx the system does not switch to rl5. But I guess I will have to try it or depend on the testimony of someone who runs startx. I have been amazed before. Well it is always good to be amazed at least once a day. I tried it. startx does not cause rl5 to be reported by runlevel. Howver, at least on my machine NM does not run the way it should. Does startx spawn the applet? I'm pretty sure it should, since I think startx just starts up the normal r5 session but of course doesn't switch to r5. It also depends on what levels you've got NM set to start at: chkconfig --list | grep NetworkManager should tell you that. Dan Well you are essentially correct . startx starts a normal r5 session but runlevel claims that the system is still at rl3. Which seems strange to me. However one thing that does not happen (on my machine at least) nm-applet does not start bringing up wireless. Maybe this should be expected that the wireless is not active but I suspect that I could start it by editing the proper connection. -- === There is nothing so easy but that it becomes difficult when you do it reluctantly. -- Publius Terentius Afer (Terence) === Aaron Konstam telephone: (210) 656-0355 e-mail: akons...@sbcglobal.net ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
[Fwd: Re: debug tips]-correction
Forwarded Message From: Aaron Konstam akons...@sbcglobal.net To: Dan Williams d...@redhat.com Cc: Marc Herbert marc.herb...@gmail.com, networkmanager-list@gnome.org Subject: Re: debug tips Date: Wed, 03 Jun 2009 15:42:53 -0500 On Wed, 2009-06-03 at 09:49 -0400, Dan Williams wrote: On Wed, 2009-06-03 at 08:40 -0500, Aaron Konstam wrote: On Wed, 2009-06-03 at 08:21 -0500, Aaron Konstam wrote: On Wed, 2009-06-03 at 10:55 +0100, Marc Herbert wrote: Aaron Konstam a écrit : On Mon, 2009-06-01 at 08:53 -0700, Daniel Fetchinson wrote: As I've said, but let me repeat it again, I do boot into run level 3. After logging in I start X manually via startx. We are having a giant miscommunication going on . What rl are you actually running at? No, there is no miscommunication, simply you just have to believe that it is possible to boot in runlevel 3 and then it is possible to start X manually via startx :) I believe it, if you will accept that running startx puts you in to rl5 not rl3. Huh? startx is changing the runlevel? That is some news. This is a semantic argument. rl3 does not support X, rl5 does. I have never actually checked this but I would be amazed if when one runs startx the system does not switch to rl5. But I guess I will have to try it or depend on the testimony of someone who runs startx. I have been amazed before. Well it is always good to be amazed at least once a day. I tried it. startx does not cause rl5 to be reported by runlevel. Howver, at least on my machine NM does not run the way it should. Does startx spawn the applet? I'm pretty sure it should, since I think startx just starts up the normal r5 session but of course doesn't switch to r5. It also depends on what levels you've got NM set to start at: chkconfig --list | grep NetworkManager should tell you that. Dan Well you are essentially correct . startx starts a normal r5 session but runlevel claims that the system is still at rl3. Which seems strange to me. However one thing that does not happen (on my machine at least) nm-applet does not start bringing up wireless. Maybe this should be expected that the wireless is not active but I expect that I could start it by editing the proper connection. I must make a correction. If I run startx as a simple user I can connect to my default\ wireless connection if I enter the keyring passwd. As long as the proper services are running rh3 vs. rl5 is irrelevant. -- === There is nothing so easy but that it becomes difficult when you do it reluctantly. -- Publius Terentius Afer (Terence) === Aaron Konstam telephone: (210) 656-0355 e-mail: akons...@sbcglobal.net ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: debug tips
On Sun, 2009-05-31 at 09:21 -0700, Daniel Fetchinson wrote: I'm trying to debug a 100% reproducable issue but don't really know where to look for clues. I have a Sony VAIO VGN-FZ240E, running 64bit Fedora 8. It happens with many wifi networks that when I boot everything goes fine, I can connect to the wifi network with nm-applet but as soon as I lose the connection I will never be able reconnect. The networks in question use pre-shared keys. If I reboot, everything will be fine again, I can connect using the password, but as soon as I lose connection the only way I can reconnect is by reboot. Instead of rebooting I tried manually restarting all network related services but that doesn't help. These are the services I restart in this order from /etc/rc3.d that I guess are relevant: service ip6tables restart service iptables restart service network restart NetworkManager and network are two different competitive systems to support networking. I don't say it would work but you should restart NetworkManager not network. Sure. But in /etc/rc3.d the order of the network related services is this: ip6tables iptables network NetworkManager NetworkManagerDispatcher Not on my machine. NetworkManager and network are not designed to run at the same time. It is not clear what NM would do in run level 3 without X. You certainly don't have a nm-applet running at rl 3 in any meaningful fashion. So I've tried stopping all 5 services and starting them in the above order, because they get started in the above order while booting. But already the third service, 'network', fails and wlan doesn't come up. If I nevertheless restart NetworkManager and NetworkManagerDispatcher I can see the wireless network in question in nm-applet but can not connect. I enter the pre-shared key password but it wouldn't connect, it just gives back the password window. Look you talk about rc3.d but if you are using nm-applet you can't be at run level 3 so what is in rc3.d is irrelevant. We are having a giant miscommunication going on . What rl are you actually running at? If I reboot though the above 5 services are started in the above order and everything works, wlan comes up and nm-applet can connect using the same pre-shared key password. So it seems to me that I need to do some additional steps manually to completely reproduce what is happening at boot time. It just seems impossible to me that I can not reproduce everything what is happening at boot time, without actually rebooting but doing the same things manually as root. Any ideas where should I be looking for clues? Thanks a lot, Daniel -- === Anyone can do any amount of work provided it isn't the work he is supposed to be doing at the moment. -- Robert Benchley === Aaron Konstam telephone: (210) 656-0355 e-mail: akons...@sbcglobal.net ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: debug tips
On Mon, 2009-06-01 at 08:53 -0700, Daniel Fetchinson wrote: I'm trying to debug a 100% reproducable issue but don't really know where to look for clues. I have a Sony VAIO VGN-FZ240E, running 64bit Fedora 8. It happens with many wifi networks that when I boot everything goes fine, I can connect to the wifi network with nm-applet but as soon as I lose the connection I will never be able reconnect. The networks in question use pre-shared keys. If I reboot, everything will be fine again, I can connect using the password, but as soon as I lose connection the only way I can reconnect is by reboot. Instead of rebooting I tried manually restarting all network related services but that doesn't help. These are the services I restart in this order from /etc/rc3.d that I guess are relevant: service ip6tables restart service iptables restart service network restart NetworkManager and network are two different competitive systems to support networking. I don't say it would work but you should restart NetworkManager not network. Sure. But in /etc/rc3.d the order of the network related services is this: ip6tables iptables network NetworkManager NetworkManagerDispatcher Not on my machine. NetworkManager and network are not designed to run at the same time. It is not clear what NM would do in run level 3 without X. You certainly don't have a nm-applet running at rl 3 in any meaningful fashion. I do boot in runlevel 3 and then start X manually with startx. After X is running nm-applet gets started as well. There is absolutely no problem here. So I've tried stopping all 5 services and starting them in the above order, because they get started in the above order while booting. But already the third service, 'network', fails and wlan doesn't come up. If I nevertheless restart NetworkManager and NetworkManagerDispatcher I can see the wireless network in question in nm-applet but can not connect. I enter the pre-shared key password but it wouldn't connect, it just gives back the password window. Look you talk about rc3.d but if you are using nm-applet you can't be at run level 3 so what is in rc3.d is irrelevant. As I've said, but let me repeat it again, I do boot into run level 3. After logging in I start X manually via startx. We are having a giant miscommunication going on . What rl are you actually running at? No, there is no miscommunication, simply you just have to believe that it is possible to boot in runlevel 3 and then it is possible to start X manually via startx :) I believe it, if you will accept that running startx puts you in to rl5 not rl3. Also that network and NM should not be run at the same time. If I reboot though the above 5 services are started in the above order and everything works, wlan comes up and nm-applet can connect using the same pre-shared key password. So it seems to me that I need to do some additional steps manually to completely reproduce what is happening at boot time. It just seems impossible to me that I can not reproduce everything what is happening at boot time, without actually rebooting but doing the same things manually as root. Any ideas where should I be looking for clues? -- === The idea is to die young as late as possible. -- Ashley Montague === Aaron Konstam telephone: (210) 656-0355 e-mail: akons...@sbcglobal.net ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: debug tips
On Sat, 2009-05-30 at 10:49 -0700, Daniel Fetchinson wrote: Hi folks, I'm trying to debug a 100% reproducable issue but don't really know where to look for clues. I have a Sony VAIO VGN-FZ240E, running 64bit Fedora 8. It happens with many wifi networks that when I boot everything goes fine, I can connect to the wifi network with nm-applet but as soon as I lose the connection I will never be able reconnect. The networks in question use pre-shared keys. If I reboot, everything will be fine again, I can connect using the password, but as soon as I lose connection the only way I can reconnect is by reboot. Instead of rebooting I tried manually restarting all network related services but that doesn't help. These are the services I restart in this order from /etc/rc3.d that I guess are relevant: service ip6tables restart service iptables restart service network restart NetworkManager and network are two different competitive systems to support networking. I don't say it would work but you should restart NetworkManager not network. The first two are fine, but 'service network restart' always fails bringing up wlan. When I reboot, wlan comes up okay though. And this is 100% reproducable. I have absolutely no clue what reboot does that I don't when manually starting the services. Also, I have no idea where to look for clues. Which log files to look at? Any other tips? Thanks very much, Daniel -- === Love isn't only blind, it's also deaf, dumb, and stupid. === Aaron Konstam telephone: (210) 656-0355 e-mail: akons...@sbcglobal.net ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager and RunLevel 3
On Thu, 2009-03-19 at 09:11 -0700, Geoffrey Leach wrote: I addressed this question to the NetworkManager list and received a couple of replies that I found to be quite educational. The topic appears on this list occasionally, so I thought it worthwhile to re- post here. The essence of what I discovered is that its not NetworkManager but nm- applet, which is a separate package, albeit from the same source. There is an analogous program available for RL3 There is no separate nm-applet package on Fedora that I can find. === Aaron Konstam telephone: (210) 656-0355 e-mail: akons...@sbcglobal.net ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: When will NM 0.7 be released ?
On Wed, 2008-10-15 at 18:58 -0400, Dan Williams wrote: On Tue, 2008-10-14 at 23:44 +0200, Mildred Ki'Lya wrote: Hi, Just a question, it seems anyone here forgot that the 0.7 version was not released. So unfortunately, because of that, it can't make its way to the packages of my distribution (ArchLinux). I know I can compile myself, but it's not that easy. I made several attempts which all failed. So the question: is releasing NM 0.7 planned, if it is, do you have an idea when? It's gonna happen by the end of the month or I'll hang myself. Dan How come the NM in Fedora 9 says its 0.7? -- === Talking much about oneself can also be a means to conceal oneself. -- Friedrich Nietzsche === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Storing the WEP key outside user's keyring
On Fri, 2008-10-03 at 15:55 -0400, Dan Williams wrote: On Fri, 2008-10-03 at 18:47 +0200, Marcin 'Qrczak' Kowalczyk wrote: 2008/10/3 Robert Piasek [EMAIL PROTECTED]: You can use keyfile plugin and define your system wide connection. That way NM will activate during boot. How do do that? Where is the documentation? There is a system settings service that will use the configuration from your /etc/network/interfaces file if it's configured correctly, and/or you can use the keyfile plugin for persistent connection storage as well. What constitutes configured correctly? Does Fedora have a ketfile plugin, and if so where do you get it and how is it used? I'd first try setting up /etc/network/interfaces in the normal Ubuntu way and if that fails, then Alexander should fix it :P Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list -- === I've been on this lonely road so long, Does anybody know where it goes, I remember last time the signs pointed home, A month ago. -- Carpenters, Road Ode === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
A belated question about 0.7
I thought that one of the capabilities of NM-0.7.. was to be able to bring up the network globally on the machine instead of having to loin as a user, Did that happen and I missed it. If that can be dons , how? -- === Who needs friends when you can sit alone in your room and drink? === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [Fwd: system wide settings again ^^]
On Tue, 2008-08-05 at 16:43 +0100, Robert Piasek wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Dan, This time I've got different question about system wide settings. Don't know if the problem is on my end or NM Makefile. The file: /usr/share/dbus-1/system-services/org.freedesktop.NetworkManagerSystemSettings.service contains entry: Exec=/usr/sbin/nm-system-settings --config /etc/NetworkManager/nm-system-settings.conf but after default installation I had no /etc/NetworkManager/nm-system-settings.conf file On my F9 machine the above file was created contining: [main] plugins=ifcfg-fedora So I've created /etc/NetworkManager/nm-system-settings.conf as follow: [main] plugins=keyfile When I tried to save the system wide settings I got another error (can't find it right now to link), but it was complaining that can't save the settings. As I found out later on, /etc/NetworkManager/system-connections/ didn't exist. NM tried to create it, but it created a FILE and die with an error. When I created the directory manually and saved the example file everything worked fine. Now my question is, does networkmanager create these files/folders by default during make install, or should it create when you try to save config file for the first time? I've checked files which are installed by my script (which generally runs make install): (linked only etc files): = [dir] /etc = [dir] /etc/dbus-1 = [dir] /etc/dbus-1/system.d |- [obj] /etc/dbus-1/system.d/NetworkManager.conf |- [obj] /etc/dbus-1/system.d/nm-dhcp-client.conf |- [obj] /etc/dbus-1/system.d/nm-dispatcher.conf |- [obj] /etc/dbus-1/system.d/nm-avahi-autoipd.conf |- [obj] /etc/dbus-1/system.d/nm-system-settings.conf = [dir] /etc/NetworkManager = [dir] /etc/NetworkManager/dispatcher.d = [dir] /etc/init.d |- [obj] /etc/init.d/NetworkManager I've also checked src/Makefile.am and there is only: rundir=$(localstatedir)/run/NetworkManager dispatcherdir=$(sysconfdir)/NetworkManager/dispatcher.d install-data-hook: ~ $(mkinstalldirs) -m 0700 $(DESTDIR)$(rundir) ~ $(mkinstalldirs) -m 0755 $(DESTDIR)$(dispatcherdir) CLEANFILES = $(BUILT_SOURCES) Should it be patched in NM or should distros come up with their own patches for it? Thanks, Rob -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJImHUQAAoJELvLB8ABrzqYVt8QAM00u+5pYysyjmZCpmoY9CB9 gswlLvULTDjj5wKToOVVBkTUQ/plfVOiwWwg58rnohFZjp3rtG2WWiJlHWPsumuU 2UZXlupo48fskuVJU6QpMn4yLPnkf9SwKsS/t9BCohM5mtECbQiSSAPnDKDchrS+ /nk0mmX560wFEcAdtveZlHYQ0msFc9hBVsigysagtLN1WFAzrU9U175V3GyCY4W4 Hu18s74TR1UOwB9kGT/reGhlmirEl7sIn5Uf1g5Fcl8GSPMuh4k5/AvRy25cqtZ5 xPsiKF7JgvReCz38dzFa7Q+L+hw6qdp7RU9gGdkJk+frASZYz0MIOVbig3B+sLCv eG20TBoDRG4hAey41sDdkQWn4WUw0vglSelaEMq3/UZCnalR+wP5Z4wIlnyNRrXy E0aUq+AsSykslgOjv5r/PxfP9mXnJJ5S2g092/c/9UgXuMzT8+UYIkBcIpf7XiKw i6xwdn5PRHVT5RcQgrTsLry+zgQlSsZwITuKg0BIZ7JoOMxdjCVCCN2LUX2le3Np +vzO412akAJXQjk52wh8YYwnS1a9H3++NZUqSSo9ZpzaEabXbPAnF+vyANHo45B5 NFrMBoTp/CO+yD20G3SXzTfDhAkVOsna1NM47PCxx//hlpV2mNefLfTCY0oIGkpV 2fv65bWBNJBQPoYgzR1A =1GnW -END PGP SIGNATURE- ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list -- === Take that, you hostile sons-of-bitches! -- James Coburn, in the finale of _The_President's_Analyst_ === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Problem with update of f7 for Network Manager.
This morning I was send a message about updating NetworkManager. The following rpms were updated on my f7 system: NetworkManager-glib -0.6.6-2.fc7.i386 NetworkManager-devel -0.6.6-2.fc7.i386 NetworkManager -0.6.6-2.fc7.i386 NetworkManager-gnome -0.6.6-2.fc7.i386 after the update NM no longer works properly. The connection is made but instead of seeing the vertical blue bars the arrow keeps circling. Do others with f7 see the same thing. How can I downgrade to the earlier version? What can be done otherwise? Why are devel rpms being downloaded? My development repo is disabled. -- Aaron Konstam [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Is this the way NM should work?
On Tue, 2008-05-13 at 16:05 -0400, Gene Czarcinski wrote: I have a laptop with both a working wireless interface and a working ethernet wired interface. Normally, I run wireless. On Fedora 9, if I plug into the wired interface, it is brought up also so I now have both the wired and wireless interfaces enabled. Fortunately, both interfaces are on the same (sub) network so routine does not get screwed up. This does not happen on Fedora 8. On Fedora 8, when I plug in the wired interface, the wireless interface is disabled and the wired interface is enabled. Conversely, when I unplug the wired interface, it is disabled and the wireless interface is enabled. The way things work under Fedora 8 is how I expect things to work. However, there may be good reasons for how things work in Fedora 9. What you discribe is a change between f6 and f9. -- === It takes all kinds to fill the freeways. -- Crazy Charlie === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: I might be asking for DHCP support, but I'm not sure
On Thu, 2008-05-08 at 14:04 -0400, Dan Williams wrote: On Wed, 2008-05-07 at 09:20 -0400, Matt Burkhardt wrote: Basically, I have three computers - two laptops and a server. They all hook up to my Linksys Wireless Router fine, but they get different IP addresses at different times. Right; this is normal for DHCP depending on which client requests addresses at which times. If your laptop requests an address before the desktop, the laptop will generally get the lower address. That is interesting because on my home network all machines get the same address no matter in which order they are turned on. -- === Revolution, n.: A form of government abroad. === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager should report killswitch state per device
On Sat, 2008-04-26 at 20:01 -0500, Larry Finger wrote: [EMAIL PROTECTED] wrote: On Thu, Apr 24, 2008 at 01:24:33PM -0400, Dan Williams wrote: Expected behavior. If you don't want to kill any wireless, don't flip the switch. I don't see real use-cases where you'd want to rfkill one card but not others; Here's a real use-case: on my wife's laptop, the integrated wifi is misfunctionning. (It sees network but can only intermitently connect to them. It just happened one day, I am sure it is an hardware problem on this four year old computer.) We bought an USB dongle to have a reliable wifi. It would be nice to stop the integrated card in order to save battery time. That was a real case, I can imagine other cases where the integrated device doesn't have the good protocols (maybe it doesn't do g or n wifi networks), doesn't have the correct range, doesn't have the correct MAC address to be accepted by the router, and where one would like to use an external wifi card without the first one sucking power. Well, anyway, it sure is'nt a priority... Why not blacklist the driver for the defunct device? Larry I have to ask. How do you blacklist a driver? === We have phasers, I vote we blast 'em! -- Bailey, The Corbomite Maneuver, stardate 1514.2 === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Is Ignore interfaces supported?
On Thu, 2008-04-24 at 11:45 +, Nick Byrne wrote: Hi list, I would like configure NM so that ignores my ethernet interfaces, is this possible? Thanks Nick Why would you want to do that? -- === There is never time to do it right, but always time to do it over. === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Clarification of key terminaology.
I am still unclear as to what is the difference between ASCII key and a passphrase? Can the latter have blanks in it or what? -- -- === Depart in pieces, i.e., split. === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Surprise - olpc sugar uses NM
I was surprised to see that the olpc running the sugar operating system runs NM. olpc (product of the one computer one child project) if MIT's Negroponte. The idea is to mass produce cheap computers for children in third world countries. The connection interface is interesting. It is a screen of colored dots each one a AP or a mesh connection, which is a connection to another olpc.It is more colorful than NM-applet. -- === Common sense is the most evenly distributed quantity in the world. Everyone thinks he has enough. -- Descartes, 1637 === Aaron Cost telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: 0.7 this year?
On Wed, 2007-12-12 at 15:17 -0500, Stuart D. Gathman wrote: On Tue, 11 Dec 2007, Bjoern Martensen wrote: how are the chances we might get our (desperately waiting) hands on NM 0.7 by the end of this year? maybe a christmas present? ;) I am running Fedora Core 8, and it has NM 0.7. Lo and behold, WPA works with NM! (It didn't work with NM 0.6 on EL5). So download the werewolf and enjoy. It worked on NM-0.6.5 -- === It'll be just like Beggars' Canyon back home. -- Luke Skywalker === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Proper WEP Code
On Tue, 2007-12-11 at 17:10 -0500, Dan Williams wrote: WEP ASCII passphrases are standardized, WEP104 passphrases are de-facto standard (some implemented hashing for 40-bit WEP keys, but that's not really standardized at all), and Apple uses a completely different hashing scheme for it's password. So no, WEP doesn't have a standardized passphrase-key hashing scheme. That's why you get 3 choices. WPA fixed this, where there is a standard for hashing a passphrase into a key, _plus_ they made it easy to differentiate a passphrase and a hex key, which is great because you can't do this with WEP, leading to people using what _look_ like hex keys as actual WEP passphrases. Dan I am sure you think the above explanation is clear but it is not to me. From what I have read the WEP pasphrase is the encryption key. and an ASCII passphrase is just a hex passphrase expressed in ASCII characters, What is the difference between a passphrase and a hex key and where does hashing come in for WEP? -- === You know that feeling when you're leaning back on a stool and it starts to tip over? Well, that's how I feel all the time. -- Steven Wright === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Proper WEP Code
On Sun, 2007-12-09 at 19:22 -0500, Dan Williams wrote: On Sun, 2007-12-09 at 15:48 -0600, Aaron Konstam wrote: On Mon, 2007-12-10 at 01:42 +1000, [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey everyone sorry to disturb you all but what is the proper way to put your wep code in hex into the nm-applet? So far i can't figure it out and it won't allow me to connect. This is my code (obviously without the stars): **:38:22:05:40:AB:**:EF:04:38:22:05:** Thanks in advance i tried googling it but i don't think i could think of the right combination of search phrase. NJ But the associated question do you really want to set the WEP encryption code in hex rather than in ASCII, which is another option. He needs to be sure he matches the setting used on the AP. It won't work if he uses the wrong type in the applet. That said, most APs don't use ASCII passphrases (it was an older lucent thing), so I'd expect it to be a hex key, most likely. Dan Dan, You may be right but all of the wireless APs distributed by ATT have ASCII WEP passwds that are annoyingly 10 rather then 13 ASCII characters. -- === Could I have a drug overdose? === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Proper WEP Code
On Mon, 2007-12-10 at 01:42 +1000, [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey everyone sorry to disturb you all but what is the proper way to put your wep code in hex into the nm-applet? So far i can't figure it out and it won't allow me to connect. This is my code (obviously without the stars): **:38:22:05:40:AB:**:EF:04:38:22:05:** Thanks in advance i tried googling it but i don't think i could think of the right combination of search phrase. NJ But the associated question do you really want to set the WEP encryption code in hex rather than in ASCII, which is another option. -- === It took me fifteen years to discover that I had no talent for writing, but I couldn't give it up because by that time I was too famous. -- Robert Benchley === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Fedora 8 and PEAP
On Mon, 2007-12-03 at 11:13 -0500, Yaakov Nemoy wrote: Hey List, Are there any known problems with Network Manager 0.7 and PEAP Networks? I seem to be having trouble connecting to my school's network, which has otherwise been rock solid in Fedora 7. What can I do to figure out if it's a bug, and file the appropriate report? -Yaakov I am currently able to connect to our Universities WPA/WPA2 service that uses PEAP. Is that what you wnat to do? However I am using NM-0.6.5 in F7. -- === Health is merely the slowest possible rate at which one can die. === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager keeps asking for secret phrase
On Wed, 2007-11-21 at 13:21 -0200, Matias Estrada wrote: so you say it doesn't ask for the PAM password every time you reboot ? mine keeps asking , so I went for nm-applet manual configuration. Now it doesn't show the signal strength :( My experience is that the keys are stored in the gnome-keyring and you are asked for a WEP key for example every time you logon. In NM-0.7 it is supposed to be possible to get a machine wide passwd rather than a user specific passwd but I don't know if that is operational yet. On Nov 15, 2007 6:27 AM, Henry Andrew [EMAIL PROTECTED] wrote: On Sat, 2007-11-10 at 14:48 +0200, Firas Swidan, PhD wrote: Hi, I am trying to connect to my WAP wireless network and NetworkManager keeps asking for the secret phrase without connecting. Is there anything specific that I need to do to stop this and make the connection? Thanks in advance, Firas. There is some confusion here. I suspect you mean WEP. If it is asking you for a secret phrase it means is is not open to anyone who connects. You need to know the (usually 40 bit or 104 bit) string that was set up on the AP. Note that 104 bits is 13 ASCII characters. Isn't it the case that the key for WEP or WPA is stored in the PAM keyring if you have PAM installed? I run Ubuntu (Gnome) so PAM is already installed, but if you run another distro/desktop and PAM isn't installed or configured then maybe it's not storing the WEP key? Once stored in PAM, then you only get asked for the PAM passphrase, but in the version of PAM supplied in Ubuntu 7.10 there is a checkbox in the passphrase dialog to always remember the PAM passphrase. --andrew ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list -- === It was a virgin forest, a place where the Hand of Man had never set foot. === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager keeps asking for secret phrase
On Sat, 2007-11-10 at 14:48 +0200, Firas Swidan, PhD wrote: Hi, I am trying to connect to my WAP wireless network and NetworkManager keeps asking for the secret phrase without connecting. Is there anything specific that I need to do to stop this and make the connection? Thanks in advance, Firas. There is some confusion here. I suspect you mean WEP. If it is asking you for a secret phrase it means is is not open to anyone who connects. You need to know the (usually 40 bit or 104 bit) string that was set up on the AP. Note that 104 bits is 13 ASCII characters. -- === You got to be very careful if you don't know where you're going, because you might not get there. -- Yogi Berra === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: killswitch messages flood syslog fixed
On Sun, 2007-11-11 at 12:26 -0500, walter neumann wrote: Sorry if this has already been said -- I couldn't find any search functionality for this list. There have been several messages complaining that killswitch error messages flood the syslog (especially on Dell machines that have no physical wlan killswitch, only the keyboard one). The following fixes the problem for me: run on startup hal-device --r dell_wlan_switch Well I tried this putting the line in rc.local on my Dell laptop. It seemed to reduce the: Nov 11 16:07:48 cyrus last message repeated 11 times messages but I am still not clear about what is going on, and why this formula helps things. === One has to look out for engineers -- they begin with sewing machines and end up with the atomic bomb. -- Marcel Pagnol === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Wireless Network Controller missing on PS3
On Fri, 2007-10-26 at 15:12 +0700, Carlos Andre Camargo wrote: Please, need your guidance to troubleshoot a problem Ii found here. I have installed a Ubuntu 7.04 on my PS3, and I am using NetworkManager Applet 0.6.4 but the system can not display my wireless card connection. Can you help me on this ? I think more details are needed on exactly what your are doing and what network related init.d scripts you are running. -- === ROMEO: Courage, man; the hurt cannot be much. MERCUTIO: No, 'tis not so deep as a well, nor so wide as a church-door; but 'tis enough, 'twill serve. === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Using LEAP, WPA-EAP and CCMP with NetworkManager
On Fri, 2007-09-21 at 17:46 -0400, Dan Williams wrote:
On Fri, 2007-09-21 at 15:26 -0500, Aaron Konstam wrote:
On Fri, 2007-09-21 at 22:03 +0200, Jan Vlug wrote:
I want to use NetworkManager to setup my wireless connection, however I
do not manage to get it working.
When using wpa_supplicant, I can connect to the wireless network by
using these settings:
network={
ssid=NAME
scan_ssid=1
key_mgmt=WPA-EAP
pairwise=CCMP
eap=LEAP
identity=me
password=secret
}
Is this configuration supported by the NetworkManager GUI?
I am using Fedora 7.
At the risk of being shot down choose in nm-applet Connect to Other
Wireless Network and a GUI will open up giving you a choice of LEAP, WPA
with PEAP , etc.
However , in my case the GUI for WPA with PEAP opened up automatically
when I chose the AP using that protocol.
I don't think there's a GUI option for LEAP as an eap method; it's
likely simple to add one though since it shouldn't require much behind
the scenes or in the UI at all. Seems pretty easy.
Dan
I am not sure what you mean. There are two different GUI based ways to get
LEAP authorization in NM. The first is an option in the default security
GUI as an alternative to WEP.
The second is in the Connect to Other Wireless Network GUI as a security
option as as an alternative to WEP and various WPA options.
However, Dan you know much more about NM than I do so I assume the problem
is in the phrase LEAP and an eap method whose meaning is not clear to me.
--
===
You are a very redundant person, that's what kind of person you are.
===
Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED]
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Using LEAP, WPA-EAP and CCMP with NetworkManager
On Fri, 2007-09-21 at 22:03 +0200, Jan Vlug wrote:
I want to use NetworkManager to setup my wireless connection, however I
do not manage to get it working.
When using wpa_supplicant, I can connect to the wireless network by
using these settings:
network={
ssid=NAME
scan_ssid=1
key_mgmt=WPA-EAP
pairwise=CCMP
eap=LEAP
identity=me
password=secret
}
Is this configuration supported by the NetworkManager GUI?
I am using Fedora 7.
At the risk of being shot down choose in nm-applet Connect to Other
Wireless Network and a GUI will open up giving you a choice of LEAP, WPA
with PEAP , etc.
However , in my case the GUI for WPA with PEAP opened up automatically
when I chose the AP using that protocol.
--
===
In Hollywood, all marriages are happy. It's trying to live together
afterwards that causes the problems. -- Shelley Winters
===
Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED]
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Explanation of killswitch related messages.
On Thu, 2007-09-20 at 22:15 +0200, MartinG wrote: On 9/20/07, Brian Millett [EMAIL PROTECTED] wrote: Aaron Konstam escribío: Well I reinstalled libsmbios but am still getting the killswitch messages in slightly different form: --Sep 19 17:58:08 cyrus yum: Updated: httpd.i386 2.2.6-1.fc7 Sep 19 17:58:13 cyrus NetworkManager: info Error getting killswitch power: org.freedesktop.Hal.Device.KillSwitch.NotSupported - dellWirelessCtl returned 4 Sep 19 17:58:44 cyrus last message repeated 5 times So now what? The dellWirelessCtl is part of the: # rpm -qf /usr/bin/dellWirelessCtl libsmbios-bin-0.13.10-1.fc7 package. I'm not sure I follow: I get the same kind of message, even though I have libsmbios-bin and libsmbios-libs installed (see my previous message in this same thread): # rpm -qf /usr/bin/dellWirelessCtl libsmbios-bin-0.13.10-1.fc7 Things got much clearer to me when I ran: dellWirelessCtl -i I found that most of the functionality of this program is not supported my BIOS. Maybe a new BIOS is needed. Run this program and see what you get. -- === Have you ever felt like a wounded cow halfway between an oven and a pasture? walking in a trance toward a pregnant seventeen-year-old housewife's two-day-old cookbook? -- Richard Brautigan === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Explanation of killswitch related messages.
On Wed, 2007-09-19 at 21:10 +0200, MartinG wrote: Similar problem here, on a Dell Latitude X1: # uname -a Linux x1 2.6.22.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686 i686 i386 GNU/Linux # cat /etc/rc.local #!/bin/sh touch /var/lock/subsys/local modprobe cpufreq-powersave modprobe dcdbas service haldaemon restart # lsmod|grep dcdbas dcdbas 12257 0 # tail /var/log/messages Sep 19 20:08:28 x1 NetworkManager: info Error getting killswitch power: org.freedesktop.Hal.Device.KillSwitch.NotSupported - Access type not supported Sep 19 20:09:04 x1 last message repeated 6 times Sep 19 20:10:10 x1 last message repeated 11 times ... # rpm -q libsmbios-bin (not installed) So I went ahead and installed it: # wget -q -O - http://linux.dell.com/repo/software/bootstrap.cgi | bash (what a stupid way to install a yum repo! Piping a web-page to bash... I actually saved the script, and had a brief look at it before I ran it.) Now I have really fouled UP: I have a dell Latitude D810 I installed the modprobe dcdbas I installed libsmbios using the wget above. /usr/bin/dellWirelessCtl --version produces no meaningfull result. /usr/bin/dellWirelessCtl does not exist. I have noting in BIOS that calls itself a killswitch but there is an option to turn wireless on and off using Fn-F2. I assume that is the software killswitch. I still get the killswitch related messages in /var/log/messages. Now I made a big mistake . I decided to re-install libsmbios . So I removed it and tried the wget method again to reinstall it. That did not work. I got a message this was already done and it will not be done again. So I haven't installed libsmbios and the errors are still there. What worries me is that somewhere along the line I got a message that libsmbios is needed by the haldaemon. Anny help out there? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Explanation of killswitch related messages.
Now I have really fouled UP: I have a dell Latitude D810 I installed the modprobe dcdbas I installed libsmbios using the wget above. /usr/bin/dellWirelessCtl --version produces no meaningfull result. /usr/bin/dellWirelessCtl does not exist. I have noting in BIOS that calls itself a killswitch but there is an option to turn wireless on and off using Fn-F2. I assume that is the software killswitch. I still get the killswitch related messages in /var/log/messages. Now I made a big mistake . I decided to re-install libsmbios . So I removed it and tried the wget method again to reinstall it. That did not work. I got a message this was already done and it will not be done again. So I haven't installed libsmbios and the errors are still there. What worries me is that somewhere along the line I got a message that libsmbios is needed by the haldaemon. Anny help out there? Well I reinstalled libsmbios but am still getting the killswitch messages in slightly different form: --Sep 19 17:58:08 cyrus yum: Updated: httpd.i386 2.2.6-1.fc7 Sep 19 17:58:13 cyrus NetworkManager: info Error getting killswitch power: org.freedesktop.Hal.Device.KillSwitch.NotSupported - dellWirelessCtl returned 4 Sep 19 17:58:44 cyrus last message repeated 5 times So now what? === Don't panic. === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Connecting to Wireless AP
On Wed, 2007-09-19 at 14:49 -0700, rajyalakshmi bommaraju wrote: Hi I am a new bie to linux. I have installed Network manager on ubuntu. Is there a way that I can make network manager connect to any wireless Ap through command line? I am looking for something similar to iwconfig. Thanks It is designed by gnome.org and is designed to run in a X environemt like gnome. nm-applet under gnome allows the connection. KDM has something similar. -- === Ignorance is never out of style. It was in fashion yesterday, it is the rage today, and it will set the pace tomorrow. -- Franklin K. Dane === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
I need some information.
Forwarded Message From: Aaron Konstam [EMAIL PROTECTED] To: Derek Atkins [EMAIL PROTECTED] Subject: Re: [ipw3945-devel] chaning mode only when interface down? Date: Sun, 05 Aug 2007 15:32:20 -0500 On Fri, 2007-08-03 at 11:10 -0400, Derek Atkins wrote: I think you are confusing a/b/g mode (which is _not_ the topic) with AP/STA/IBSS/monitor mode (which is the topic). Would someone take the trouble to explain what AP/STA/IBSS/monitor mode means? -- === There are only two kinds of men -- the dead and the deadly. -- Helen Rowland === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] -- === Our attitude with TCP/IP is, `Hey, we'll do it, but don't make a big system, because we can't fix it if it breaks -- nobody can.' TCP/IP is OK if you've got a little informal club, and it doesn't make any difference if it takes a while to fix it. -- Ken Olson, in Digital News, 1988 === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: LEAP, and other EAPs.
On Sun, 2007-07-15 at 09:14 -0400, Dan Williams wrote: On Fri, 2007-07-13 at 19:19 -0400, Darren Albers wrote: I think Cisco is just acknowledging the obvious and longstanding weaknesses in LEAP and is doing the right thing and advising their customers to move to PEAP which works the same from the users prospective. LEAP has been steadily going away for a long time, because there are well-known exploitable vulnerabilities (dictionary attacks on your password) that have been around for at least 3 or 4 years. LEAP hasn't been considered secure for a long time. Dynamic WEP with 802.1x is actually better, but only if you change your WEP key really often. LEAP also sucks because you can't know whether or not an AP supports it from the beacon, which is what WPA[2] fixes quite nicely. The above sort of misses several points. One does not have the power to decide what authorization method an access point supplier uses. I use LEAP because that is what the University I was contacting uses. Second, if NM advertises it supports LEAP it should support LEAP. Until last week it did not at least on Fedora 7. Third, I am now informed that NM supports PEAP and other EAPs. Does it? Has anyone actually tried it? I hope so. In addition this ability is pretty well hidden in the lists of options that nm-applet displays. I would probably not have found it if Darren Albers had showed me how. -- === It's not hard to admit errors that are [only] cosmetically wrong. -- J.K. Galbraith === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: LEAP, and other EAPs.
On Sun, 2007-07-15 at 13:20 -0400, Dan Williams wrote: Second, if NM advertises it supports LEAP it should support LEAP. Until last week it did not at least on Fedora 7. It did support it but a patch broke it, it wasn't caught since you can't test LEAP without Cisco AP's or a LEAP network which none of the dev's have access to. Third, I am now informed that NM supports PEAP and other EAPs. Does it? Has anyone actually tried it? I hope so. In addition this ability is pretty well hidden in the lists of options that nm-applet displays. I would probably not have found it if Darren Albers had showed me how. I have used PEAP and EAP-TLS successfully before. It isn't really hidden, it is under connect to other network If NM detects a network using EAP then the PEAP or EAP-TLS options are shown. If your network is not broadcasting and you need to select the options manually you will need to select connect to other network so I /think/ all the places you would need to find it are covered. As Dan stated in an earlier post LEAP was different because you can't tell if it is just a normal WEP network or a LEAP network. I don't think LEAP networks set the privacy bit (ie, the WEP bit) in the beacon, which means you can't tell between LEAP or unencrypted networks. That's the same with 802.1x+Dynamic WEP too. Dan Ok, I keep learning new things and that is good. -- === To err is human -- to blame it on a computer is even more so. === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
LEAP, the saga continues
After all this falderall to get LEAP working in NM I was informed today that CISCO is not sure it wants to ocntinue to support LEAP so people are going to PEAP or is it PEEP. Well as we know in computer things change fast. What a bummer. -- === Intolerance is the last defense of the insecure. === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Good News in LEAP-land
On Thu, 2007-07-12 at 12:38 -0400, Dan Williams wrote:
On Thu, 2007-07-12 at 16:36 +0100, Jon Escombe wrote:
Aaron Konstam wrote:
Well it looks like your patch for the LEAP authentication now works.
And it works as I predicted it should. That is, when you try to
reconnect to the access point the program asks you for your keyring
passwd and connects.
If you also want to avoid the prompt for your keyring password, have a
look at pam_keyring (RPM is in the Fedora repos), you'll still need to
edit one file by hand to make it seamless..
http://www.hekanetworks.com/index.php/publisher/articleview/frmArticleID/25/staticId/31/
Which leaves me with two questions:
1. Does any one want the new rpms that I have created? If so where
should I send them?
2. How does one decide whether a %patchN line should appear before the
tar -xjf %{SOURCE1}
line or after it in the .spec file?
Just patches to the gnome panel applet need to go after..
Anyway, Jon, thanks for your efforts to get this matter resolved. I can
now LEAP freely without bother.
Glad it sorted the issue for you..
Did the patch get bugzilla'd? My laptop drive crashed monday so I'm
still catching up somewhat
Dan
Not by me. I assume Jon will do it.
--
===
Necessity is the plea for every infringement of human freedom. It is the
argument of tyrants; it is the creed of slaves. -- William Pitt, 1783
===
Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED]
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Bad news on LEAP fix patch
On Wed, 2007-07-11 at 09:18 +0100, Jon Escombe wrote: - Aaron Konstam [EMAIL PROTECTED] wrote: I took the src rpm :NetworkManager-0.6.5-7.fc7.src.rpm and recompiled it using the LEAP patch NetworkManager-0.6.5-LEAP_passwd.patch developed by Jon Escombe. Nothing improved. The behavior is the same. Thinking about it, are you confident the patch applied ok? Did you build a new version of the RPM, applying the patch in the .spec file? Cheers, Jon. That is exactly what I did. In the spec file NetworkManager.spec I had the lines: Patch0: NetworkManager-0.6.4-startup-dhcdbd.patch Patch1: NetworkManager-0.6.5-fixup-internal-applet-build.patch Patch2: linkdebug.patch Patch3: NetworkManager-0.6.5-no-killswitch-fix.patch Patch4: NetworkManager-0.6.5-LEAP_passwd.patch And I added the NetworkManager-0.6.5-LEAP_passwd.patch file to the /usr/src/redhat/SOURCES directory. Then I recompiled the rpms by execuuting: rpmbuild -ba NetworkManager.spec Does that seem right? -- Aaron Konstam [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Bad news on LEAP fix patch
On Wed, 2007-07-11 at 18:06 +0100, Jon Escombe wrote: - Derek Atkins [EMAIL PROTECTED] wrote: Aaron Konstam [EMAIL PROTECTED] writes: That is exactly what I did. In the %prep section did you add the appropriate %patchN (where 'N' is the PatchN: you added here)? Well spotted, I'd missed that. Fingers crossed that was the missing piece and the patch is okay ;) Regards, Jon. Well that is right ,I blew it. I will make that change and try again. I assume the added line should be: %patch4 -p1 -b .LEAP_passwd Someone let me know if this is not correct. -- Aaron Konstam [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Bad news on LEAP fix patch - the story continues
On Wed, 2007-07-11 at 22:27 +0100, Jon Escombe wrote:
- Aaron Konstam [EMAIL PROTECTED] wrote:
On Wed, 2007-07-11 at 18:06 +0100, Jon Escombe wrote:
- Derek Atkins [EMAIL PROTECTED] wrote:
Aaron Konstam [EMAIL PROTECTED] writes:
That is exactly what I did.
In the %prep section did you add the appropriate %patchN (where 'N' is
the PatchN: you added here)?
Well spotted, I'd missed that.
Fingers crossed that was the missing piece and the patch is okay ;)
Regards,
Jon.
Well that is right ,I blew it. I will make that change and try again.
I assume the added line should be:
%patch4 -p1 -b .LEAP_passwd
Someone let me know if this is not correct.
Yep, that last parameter is just a suffix for a backup copy of the file, so
can be whatever you like..
The last spec file I have has the applet patches in a second section (just
underneath the tar command), you'll want to put this one there too..
Cheers,
Jon.
Now we are really getting into black magic. I changed the lines:
%prep
%setup -q
%patch0 -p1 -b .startup-dhcdbd
%patch2 -p1 -b .linkdebug
%patch3 -p1 -b .no-killswitch-fix
%patch4 -p1 -b .LEAP_passwd
# unpack the applet
tar -xjf %{SOURCE1}
%patch1 -p1 -b .buildfix
To:
%prep
%setup -q
%patch0 -p1 -b .startup-dhcdbd
%patch2 -p1 -b .linkdebug
%patch3 -p1 -b .no-killswitch-fix
# unpack the applet
tar -xjf %{SOURCE1}
%patch1 -p1 -b .buildfix
%patch4 -p1 -b .LEAP_passwd
and now executing rpmbuild -ba gives a successful compile.
Will someone confirm that this is ok and I can install the rpms
produced.?
--
===
I think the world is run by C students. -- Al McGuire
===
Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED]
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Solution to the LEAP problem
I said this before and I will say it again. The solution to get LEAP authorization to work seems simple: It should work like WEP authorization. When you sent up a WEP controlled access point you are asked to put in the access passsphrase then you are asked to enter the passwd for access to your gnome keyring. When you login after that you are asked for the passwd to your keyring and the access is authenticated by accessing the keyring and finding the passsphrase. With LEAP you are asked for a user name ans passwd. Then you are asked for the passwd of your keyring and the connection is made. When you login after that you should be asked for your keyring passwd just like the WEP case. But you are not so NM can't access your LEAP passwd from the keyring and the connection fails. Actually the passwd is retrieved but it can't be decrypted. I someone has a better idea I would be glad to hear it. I have been waiting for LEA to work properly foe over half a year. I realize I am am in the minority by using LEAP but I have no choice and I think this should be fixed.. -- === Your wise men don't know how it feels To be thick as a brick. -- Jethro Tull, Thick As A Brick === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: FR: NetworkManagerDispatcher should fireup scripts owned by any user.
On Sun, 2007-07-08 at 21:02 -0400, Hans Deragon wrote: Greetings. [ Resending with a less annoying title and non signed email; Please reply to this email instead to start a thread. My apologies ] I would like to propose a new feature. The NetworkManagerDispatcher should call any scripts found under NM_SCRIPT_DIR (currently hardcoded to '/etc/NetworkManager/dispatcher.d' directory), regardless of the owner. Currently, it only executes scripts owned by root. Scripts would be executed with the EUID set to the user owning the script. This would prevent a user to gain root privileges. But with this feature, users without any admin privileges could add their own scripts. For instance, they could set ssh tunnels when getting connected to a particular network. NM_SCRIPT_DIR would have the sticky bit set, like /tmp. From chmod man page: When the sticky bit is set on a directory, files in that directory may be unlinked or renamed only by the directory owner as well as by root or the file owner. Without the sticky bit, anyone able to write to the directory can delete or rename files. The sticky bit is commonly found on directories, such as /tmp, that are world-writable. Comments are welcomed. If my proposal is welcomed, I could give a try coding it and submit a patch. Instead of calling system() directly, a fork would be executed, and the child would perform a setuid() call prior calling system(). One advantage of forking is that the daemon would never freeze since only the children would call shell commands. Thus if a shell command loops indefinitely, the main daemon isn't affected. Best regards, Hans Deragon -- === Quidquid latine dictum sit, altum viditur. [Whatever is said in Latin sounds profound.] === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Networkmanager not connecting to known network
On Mon, 2007-07-09 at 10:23 -0400, Alex Janssen wrote: I have been reading the list and snooping around in the files trying to figure this out, but I'm not sure what I'm looking for. I know it is supposed to connect to a known network automatically. It does try but times out. Any help is appreciated. Thanks, Alex Is it a wired or wireless network it is timing out on? -- === Lazlo's Chinese Relativity Axiom: No matter how great your triumphs or how tragic your defeats -- approximately one billion Chinese couldn't care less. === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Temporary solution to NM LEAP glitch.
This is only for people who believe in kludgey solutions to annoying problems. As was decided, LEAP does not work in the current NM in the sense you can configure it and it will connect but never connect on further logins. A solution has been suggested Jon Escombe and eventually it will be included in the distribution. What can you do in the meantime? What I have done is the following. Created a script which removes the directory TrinityAP which represents the LEAP access point in my .gconf directory tree. The next time you can configure the LEAP connection from the beginning and connect; and go on your merry way. Before you log off you must remember to run the script, which completes the kludge solution to the problem. It works but be free to ignore it if you hate kludges. -- === Who goeth a-borrowing goeth a-sorrowing. -- Thomas Tusser === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: FR: NetworkManagerDispatcher should fireup scripts owned by any user.
On Sun, 2007-07-08 at 21:02 -0400, Hans Deragon wrote: Greetings. [ Resending with a less annoying title and non signed email; Please reply to this email instead to start a thread. My apologies ] I would like to propose a new feature. The NetworkManagerDispatcher should call any scripts found under NM_SCRIPT_DIR (currently hardcoded to '/etc/NetworkManager/dispatcher.d' directory), regardless of the owner. Currently, it only executes scripts owned by root. There is no such directory on my Fedora 7 machine. What version of Linux is being used? Scripts would be executed with the EUID set to the user owning the script. This would prevent a user to gain root privileges. But with this feature, users without any admin privileges could add their own scripts. For instance, they could set ssh tunnels when getting connected to a particular network. NM_SCRIPT_DIR would have the sticky bit set, like /tmp. From chmod man page: When the sticky bit is set on a directory, files in that directory may be unlinked or renamed only by the directory owner as well as by root or the file owner. Without the sticky bit, anyone able to write to the directory can delete or rename files. The sticky bit is commonly found on directories, such as /tmp, that are world-writable. Comments are welcomed. If my proposal is welcomed, I could give a try coding it and submit a patch. Instead of calling system() directly, a fork would be executed, and the child would perform a setuid() call prior calling system(). One advantage of forking is that the daemon would never freeze since only the children would call shell commands. Thus if a shell command loops indefinitely, the main daemon isn't affected. Best regards, Hans Deragon -- === First there was Dial-A-Prayer, then Dial-A-Recipe, and even Dial-A-Footballer. But the south-east Victorian town of Sale has produced one to top them all. Dial-A-Wombat. It all began early yesterday when Sale police received a telephone call: You won't believe this, and I'm not drunk, but there's a wombat in the phone booth outside the town hall, the caller said. Not firmly convinced about the caller's claim to sobriety, members of the constabulary drove to the scene, expecting to pick up a drunk. But there it was, an annoyed wombat, trapped in a telephone booth. The wombat, determined not to be had the better of again, threw its bulk into the fray. It was eventually lassoed and released in a nearby scrub. Then the officers received another message ... another wombat in another phone booth. There it was: *Another* angry wombat trapped in a telephone booth. The constables took the miffed marsupial into temporary custody and released it, too, in the scrub. But on their way back to the station they happened to pass another telephone booth, and -- you guessed it -- another imprisoned wombat. After some serious detective work, the lads in blue found a suspect, and after questioning, released him to be charged on summons. Their problem ... they cannot find a law against placing wombats in telephone booths. -- Newcastle Morning Herald, NSW Australia, Aug 1980. === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Leap authentication problem in NM.- once again
On Fri, 2007-07-06 at 09:28 +0100, Jon Escombe wrote: Hmm, that patch shouldn't have changed the logic for LEAP authentication.. Do we know what version was last working ok for Aaron (6.4 / 6.5)? Regards, Jon. Looking at the applet code, I'm suspicious that the 6.5 changes that broke some WPA2 configs have done the same to LEAP. So we might just need to extend that last patch to include LEAP networks. Aaron, does your LEAP passphrase get stored in the keyring or in gconf? You might need to install the gnome-keyring-manager to check the keyring. If it's in the keyring then I would expect it only to work when you enter all the information through the applet, but not when it re-connects? If this is the case then it is the issue above should be a simple fix... Regards, Jon Yes the passphrase gets stored in the gnome-keyring. The problem is exactly as you describe it. It last worked in the Unstable CVS version last September which was probably 6.4 -- === But Captain -- the engines can't take this much longer! === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
[Fwd: Re: Leap authentication problem in NM.- once again]
Forwarded Message From: Aaron Konstam [EMAIL PROTECTED] To: Dan Williams [EMAIL PROTECTED] Subject: Re: Leap authentication problem in NM.- once again Date: Fri, 06 Jul 2007 08:53:06 -0500 On Thu, 2007-07-05 at 22:49 -0400, Dan Williams wrote: On Thu, 2007-07-05 at 15:14 -0500, Aaron Konstam wrote: On Thu, 2007-07-05 at 13:23 -0400, Darren Albers wrote: On 7/5/07, Aaron Konstam [EMAIL PROTECTED] wrote: On Mon, 2007-07-02 at 15:18 -0500, Aaron Konstam wrote: I am using NetworkManager-0.6.5-6.fc7 on F7 but it is not working properly. When I set up a WEP authentication I am asked to enter the id number of the Access point then I am asked for a passwd phrase which when entered causes the connecton to be made. When I subsequently login I am asked for the passwd phrase; which when entered proceeds to make the connection. When I choose LEAP authentication I am asked for a login and passwd. Then I am asked for a passwd phrase (which I don't remember happening in earlier LEAP authentication.) The connection is then made. Subsequently when I login to the machine I am not asked for a passwd phrase and the NM-applet keeps searching endlessly for a connection. Something is wrong. Could someone either confirm that this is a error in the program or tell me how to make it work? I don't know why complex questions can get answered but simple ones do not, so let me try again. Is LEAP authentication using NM supposed to ask you for a password at the end of the configuration process? It is happening and it screws things up as described above. If you want a bugzilla I will file one. -- === Well, Jim, I'm not much of an actor either. === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] Probably because not many people who lurk here answering questions have used LEAP so they don't know the answer... Is the second request for a passphrase your keyring passphrase? Yes it is? Ok maybe it is time for a bugzilla. The developer of this capability must know how it is supposed to work, It used to work in an earlier NM version. My guess is that it was the patch that made WPA[2] Enterprise certificate stuff stop asking for passwords in applet-dbus-info.c, nmi_dbus_get_key_for_network(). That changed the password request logic, possibly for the worse with LEAP. What exactly are your LEAP options, just user and password, right? Dan I am asked for a user and passwd. Then I am asked for a passphrase. But no request ever appears on login asking me to enter the passphrase. It is frustrating I am sure for both of us. This used to work in the Unstable version last September. Should I post the syslog entries as Darren Albers asked for or is it time for a bugzilla? -- === A true artist will let his wife starve, his children go barefoot, his mother drudge for his living at seventy, sooner than work at anything but his art. -- Shaw === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] -- === Gort, klaatu nikto barada. -- The Day the Earth Stood Still === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Requested syslog for LEAP authenticatiln sequence
Attached is the syslog messages generated for my machine being attached to a hard wired connection to attempting to connect to an access point using LEAP authentication. I gzipped the file. Maybe I am naive but the problem seems clear. The system requests a key for TrinityAP the access point. It gets the key. Then determines that it is encrypted and it hasn't the key to decrypt it. One solution seems to me is to have the system at that poinnt ask the user to enter a key as it does in WEP authentication and once entered the connection is made. Alternately no passphrase cold be asked for in the set up of the LEAP authentication as NM used to do prevously. If anyone wants me to file a buzilla, I assume at [EMAIL PROTECTED], let me know and I will. One additional thing. What is the meaning of the line on the syslog: Jul 6 09:42:11 localhost NetworkManager: info Error getting killswitch power: org.freedesktop.Hal.Device.KillSwitch.NotSupported - Access type not supported and what can be done about it? -- === The qotc (quote of the con) was Liz's: My brain is paged out to my liver. === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] error2.gz Description: GNU Zip compressed data ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Leap authentication problem in NM.- once again
On Fri, 2007-07-06 at 15:24 +0100, Jon Escombe wrote: - Aaron Konstam [EMAIL PROTECTED] wrote: Looking at the applet code, I'm suspicious that the 6.5 changes that broke some WPA2 configs have done the same to LEAP. So we might just need to extend that last patch to include LEAP networks. Aaron, does your LEAP passphrase get stored in the keyring or in gconf? You might need to install the gnome-keyring-manager to check the keyring. If it's in the keyring then I would expect it only to work when you enter all the information through the applet, but not when it re-connects? If this is the case then it is the issue above should be a simple fix... Regards, Jon Yes the passphrase gets stored in the gnome-keyring. The problem is exactly as you describe it. It last worked in the Unstable CVS version last September which was probably 6.4 The attached patch should allow fetching the LEAP passphrase from the keyring. I'm assuming it's always stored there for LEAP networks and doesn't need a conditional check like the WPA2 case. Regards, Jon. How can I apply the patch and to What? NetworkManager? -- === Dying is a very dull, dreary affair. My advice to you is to have nothing whatever to do with it. -- W. Somerset Maughm, his last words === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Leap authentication problem in NM.- correection
On Fri, 2007-07-06 at 15:24 +0100, Jon Escombe wrote: - Aaron Konstam [EMAIL PROTECTED] wrote: Looking at the applet code, I'm suspicious that the 6.5 changes that broke some WPA2 configs have done the same to LEAP. So we might just need to extend that last patch to include LEAP networks. Aaron, does your LEAP passphrase get stored in the keyring or in gconf? You might need to install the gnome-keyring-manager to check the keyring. If it's in the keyring then I would expect it only to work when you enter all the information through the applet, but not when it re-connects? If this is the case then it is the issue above should be a simple fix... Regards, Jon Yes the passphrase gets stored in the gnome-keyring. The problem is exactly as you describe it. It last worked in the Unstable CVS version last September which was probably 6.4 htings are more complicated then I thought. The attached patch should allow fetching the LEAP passphrase from the keyring. I'm assuming it's always stored there for LEAP networks and doesn't need a conditional check like the WPA2 case. I have a correction on what I said earlier. It is clear that things are more complicated then I thought. When you configure LEAP authentication you are asked foe a user name, then a passwd and finally you are asked for a passphrase. What appears in the gnome keyring is the passwd not the passphrase. Previously in NM a passphrase was not asked for so I am not sure where it is stored. Probably the same place it is stored for the WEP configuration. I will try to file a bugzilla but it might not be today. -- === To err is human -- to blame it on a computer is even more so. === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Leap authentication problem in NM.- once again
On Mon, 2007-07-02 at 15:18 -0500, Aaron Konstam wrote: I am using NetworkManager-0.6.5-6.fc7 on F7 but it is not working properly. When I set up a WEP authentication I am asked to enter the id number of the Access point then I am asked for a passwd phrase which when entered causes the connecton to be made. When I subsequently login I am asked for the passwd phrase; which when entered proceeds to make the connection. When I choose LEAP authentication I am asked for a login and passwd. Then I am asked for a passwd phrase (which I don't remember happening in earlier LEAP authentication.) The connection is then made. Subsequently when I login to the machine I am not asked for a passwd phrase and the NM-applet keeps searching endlessly for a connection. Something is wrong. Could someone either confirm that this is a error in the program or tell me how to make it work? I don't know why complex questions can get answered but simple ones do not, so let me try again. Is LEAP authentication using NM supposed to ask you for a password at the end of the configuration process? It is happening and it screws things up as described above. If you want a bugzilla I will file one. -- === Well, Jim, I'm not much of an actor either. === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Leap authentication problem in NM.- once again
On Thu, 2007-07-05 at 13:23 -0400, Darren Albers wrote: On 7/5/07, Aaron Konstam [EMAIL PROTECTED] wrote: On Mon, 2007-07-02 at 15:18 -0500, Aaron Konstam wrote: I am using NetworkManager-0.6.5-6.fc7 on F7 but it is not working properly. When I set up a WEP authentication I am asked to enter the id number of the Access point then I am asked for a passwd phrase which when entered causes the connecton to be made. When I subsequently login I am asked for the passwd phrase; which when entered proceeds to make the connection. When I choose LEAP authentication I am asked for a login and passwd. Then I am asked for a passwd phrase (which I don't remember happening in earlier LEAP authentication.) The connection is then made. Subsequently when I login to the machine I am not asked for a passwd phrase and the NM-applet keeps searching endlessly for a connection. Something is wrong. Could someone either confirm that this is a error in the program or tell me how to make it work? I don't know why complex questions can get answered but simple ones do not, so let me try again. Is LEAP authentication using NM supposed to ask you for a password at the end of the configuration process? It is happening and it screws things up as described above. If you want a bugzilla I will file one. -- === Well, Jim, I'm not much of an actor either. === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] Probably because not many people who lurk here answering questions have used LEAP so they don't know the answer... Is the second request for a passphrase your keyring passphrase? Yes it is? Ok maybe it is time for a bugzilla. The developer of this capability must know how it is supposed to work, It used to work in an earlier NM version. -- === Live fast, die young, and leave a flat patch of fur on the highway! -- The Squirrels' Motto (The Hell's Angels of Nature) === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Leap authentication problem in NM.
I am using NetworkManager-0.6.5-6.fc7 on F7 but it is not working properly. When I set up a WEP authentication I am asked to enter the id number of the Access point then I am asked for a passwd phrase which when entered causes the connecton to be made. When I subsequently login I am asked for the passwd phrase; which when entered proceeds to make the connection. When I choose LEAP authentication I am asked for a login and passwd. Then I am asked for a passwd phrase (which I don't remember happening in earlier LEAP authentication.) The connection is then made. Subsequently when I login to the machine I am not asked for a passwd phrase and the NM-applet keeps searching endlessly for a connection. Something is wrong. Could someone either confirm that this is a error in the program or tell me how to make it work? -- Aaron Konstam [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Strange NetweorkManager behavior.
On Sat, 2007-06-23 at 21:20 +1200, Simon Geard wrote: On Fri, 2007-06-22 at 17:40 -0500, Aaron Konstam wrote: Has anyone else seen this. Sometimes when I am connected to a wireless access point using nm-applet and NetworkManager the system in F7 says I am connected to a wired network. Any comments out there? Seen something similar, not sure if it's related. I use a desktop machine connecting via wireless, never over ethernet. Normally, NM attempts to connect to wireless as soon as I log in, but on some occasions lately, it seems to think it's got a wired connection - nm-applet displays that icon, and it doesn't prompt for keyring password. It certainly doesn't have a wired connection - no cable is connected, and /sys/class/net/eth0/carrier reports 0. This is running NM 0.6.5 and nm-applet 0.6.5, both build from tarballs on an LFS system. I've been running those for a while though - the only things that have changed that might affect NM are a) rebuilding NM with the patch for Atheros signal strength, and b) upgrading kernel from 2.6.20.7 to to 2.6.21.5. Simon. You are obviously not using F7 so I can't comment this similarity. -- === Not every question deserves an answer. === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Strange NetweorkManager behavior.
Has anyone else seen this. Sometimes when I am connected to a wireless access point using nm-applet and NetworkManager the system in F7 says I am connected to a wired network. Any comments out there? -- -- === Hello... IRON CURTAIN? Send over a SAUSAGE PIZZA! World War III? No thanks! === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Weird nm-applet behavior.
On Sun, 2007-03-25 at 09:42 +0200, dragoran wrote: I can confirm that this works fine with 0.6.4 but not with 0.6.5 so its not a driver issue. Has 0.6.5 been released? I thought it had not. Does 0.6.5 have LEAP authentication, and where can it be found? -- Aaron Konstam [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Weird nm-applet behavior.
What is described below has happened to me at least twice. I asked about it on this list and got no real assistance. Can anyone guess why this would happen? The person who posted below was using FC6 and I was was using FC5 if that is important. 2/ NetworkManager has started to claim that it has successfully connected to a wired network. This is weird as the computer isn't connected to a wired network. All network access is through a PCI wireless card. Still works fine. It just thinks it's the wrong kind of network. ^ -- Aaron Konstam [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Incorrect symbol dispalyed for wrelwss connection.
On Sat, 2007-03-17 at 13:25 -0400, Dan Williams wrote: On Sat, 2007-03-17 at 09:50 -0500, Aaron Konstam wrote: What does this mean or indicate. Suddenly at home when NM makes a connection with wireless access point instead of the vertical bars t displays the wired connection symbol and when you put the courser on the symbol it says wired connection. Only thong that seems relevant is the kernel was upgraded to:2.6.20-1.2300.fc5 This is FC5 and the connection works. Do you have anything plugged into your Ethernet port? What's the value of /sys/class/net/ethX/carrier when you _don't_ have anything plugged in (replace ethX with the name of your wired device). Dan This stopped happening as soundingly as it started. Nothing was plugged into the Ethernet port at the time. When or if it happens again I will try the test you suggest. For now I just will stay confused. -- === Education is the process of casting false pearls before real swine. -- Irwin Edman === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Incorrect symbol dispalyed for wrelwss connection.
What does this mean or indicate. Suddenly at home when NM makes a connection with wireless access point instead of the vertical bars t displays the wired connection symbol and when you put the courser on the symbol it says wired connection. Only thong that seems relevant is the kernel was upgraded to:2.6.20-1.2300.fc5 This is FC5 and the connection works. What is going on. -- Aaron Konstam [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Clarification on SVN storage of NetworkManager versions
Am I to conclude that the NetwoprkManager source is now stored in a Subversion database rather than CVI. How does one download a binary version of NetworkManager from the SVN database? -- === Yow! Are we laid back yet? === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
A question of how connection proceeds.
I have been having trouble with an access point that is Leap authenticated. What sees form the applet display is an circular arrow continuing to precess and then finally a connection signaled by vertical bars. What is happening in the connecton process when the arrow precesses and what event causes the vertical bar to appear? I ask because the arrow precesses but the vertical bar does not appear. Sometimes the connection is made to a different access point and sometimes the whole process fails irrevocably in the sense no access point can be connected to. -- Aaron Konstam [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
[Fwd: failure of NETWORKMANAGER_)^_$_RELEASE ond FC5]
In order to get LEAP authentication I installed the unstable version of NetworkManager from the CVS on Sept 4. This worked well for a whale but in November (possibly affected by a security patch installed on the system) Leap authentication was spotty. So I downloaded NETWORKMANAGER_0.6_4_Release on Dec 26. I compiles it successfully but just installed it today. It failed to work in the following sense. The nm-applet was launched automatically and I was asked for the password on the access point. Immediately thereafter the connection failed leaving the well known symbol on the upper panel of my desktop and I could not revive it of make it try again to connect. I immediately reinstalled the unstable version which worked. Now what can I do to get you the details that would allow you to debug the reason for failure. This product has always just worked out of the box on FC5 so I ma stumped. What can I do to pin point the reasons for failure? -- === Are [Linux users] lemmings collectively jumping off of the cliff of reliable, well-engineered commercial software? (By Matt Welsh) === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: A couple of minor issues with NM
On Fri, 2006-12-22 at 19:42 -0500, Darren Albers wrote: No. It always tries to connect to a network I very seldom use. Are both open network or is one WEP and the other open? I /think/ that Network Manager will not automatically connect to an unencrypted network but I am not certain since I rarely use an unencrypted networks since I got my Aircard. In my environment NM allows me to connect to both WEP encripted networks and open networks with problem. -- === f u cn rd ths, itn tyg h myxbl cd. === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
[Fwd: Re: Status of NM with LEAP authentication feature.]
Forwarded Message From: Aaron Konstam [EMAIL PROTECTED] To: Dan Williams [EMAIL PROTECTED] Subject: Re: Status of NM with LEAP authentication feature. Date: Sun, 15 Oct 2006 08:59:36 -0500 On Sat, 2006-10-14 at 10:41 -0400, Dan Williams wrote: ___ I hate to be the only idiot on the list. I downloaded the NetworkManager source from the CVS database close to a month ago. I compiled it and installed the compiled code. This version of NM works in out universities wireless system that uses LEAP authentication. So why are we still patching to get this capability. If you downloaded from HEAD, then the LEAP patch was applied in July. For the STABLE branch, the LEAP patch has not been applied. Distributions are using the STABLE branch, because, of course, it's stable. Dan Look let me give you some background. I will soon get my 50th year in computer technology. When I started in this field there were no transistors or certainly no wireless communication. 7 years ago I finished 38 years of teaching Computer Science at the college level. In the last years of teaching I taught the course of Computer Communication and Networking, so I am not a complete ignoramus on the subject, but again wireless communication when I retired was in its infancy. During the time I was involved with teaching the technology of managing large computer software projects CVS was not in use. I am trying to catch up as fast as I time but there is a lot to catch up on. So your answer might be go learn about CVS!, and I can sympathize with that answer. However here is the problem. When I execute the commands: cvs -d :pserver:[EMAIL PROTECTED]:/cvs/gnome login cvs -d :pserver:[EMAIL PROTECTED]:/cvs/gnome co NetworkManager I seem to be getting what is at the CVS HEAD. I haven't a clue how I get what is at CVS STABLE. Could you enlighten me? -- === Any given program, when running, is obsolete. === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] -- === The molars, I'm sure, will be all right, the molars can take care of themselves, the old man said, no longer to me. But what will become of the bicuspids? -- The Old Man and his Bridge === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: As a point of reference.
Sometime at the end of the suummer I installed the version of NM that does LEAP authentication. It worked for 2 months and this week it stopped working consistantly. I reinstalled the version I had installed before and it is working better. Would installing the current HEAD version in the CVS database be usefull at this point? -- Aaron Konstam [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: network manager cannot connect to hex network
On Sun, 2006-10-15 at 16:15 -0700, colin williams wrote: I'm having trouble with network manager. When I choose to connect to a network and type in the hex key the connect button never lights up. I can manually connect to the network using iwconfig and the key. Anybody have a work around? One thing I would do is not use a hex key (I assume yo mean a WEP key). I would use a 13 character ASCII key. -- === You're at Witt's End. === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Status of NM with LEAP authentication feature.
On Sat, 2006-10-14 at 01:53 -0300, Thiago Bauermann wrote: 2006/10/13, Thiago Bauermann [EMAIL PROTECTED]: 2006/10/12, Dan Williams [EMAIL PROTECTED]: On Wed, 2006-10-11 at 16:10 -0500, Aaron Konstam wrote: Up to now I have been using NM with LEAP authentication on my FC5 machine. To do this I had to download the source from the CVS repository and compile. Will this version of NM be ever be ready as an RPM? In FC6 maybe? Somebody could backport the patch... hint hint :) It's pretty self-contained. I have just downloaded the source tarball for NM 0.6.4 and applied the LEAP patch to it. Amasingly enough, the only reject is in src/Makefile.am, which is trivial to fix. NM compiled and ran correctly. Unfortunately, I don't have a LEAP network around right now, so I can't confirm that it connects to it, but I think it would. At least NM does all the steps it should and sends wpa_supplicant the correct config for a LEAP network... Ok, just to confirm: the LEAP patch works without problems on 0.6.x versions of NM (I'm using it right now on NM 0.6.3! :-) ). Attached is a patch which applies cleanly to 0.6.x . -- []'s Thiago Jung Bauermann ___ I hate to be the only idiot on the list. I downloaded the NetworkManager source from the CVS database close to a month ago. I compiled it and installed the compiled code. This version of NM works in out universities wireless system that uses LEAP authentication. So why are we still patching to get this capability. -- Aaron Konstam [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Question about NM icon]
- On Wed, 2006-10-11 at 19:19 +0200, Tomasz Torcz wrote: On Tue, Oct 10, 2006 at 11:56:59AM -0700, Joshua L. Phillips wrote: My University uses the same setup. Just click on the NM icon, select to connect to a new network, select WPA2 Enterprise, and just enter the SSID and your identity/password. It should take care of the rest. (Works for me anyways...) I have to ask this. In FC4 and FC5 there is no NM icon that I can find. Where is this located and up to now I have connected without needing it using nm-applet? Am I missing someting important? -- === grep me no patterns and I'll tell you no lines. === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Status of NM with LEAP authentication feature.
Up to now I have been using NM with LEAP authentication on my FC5 machine. To do this I had to download the source from the CVS repository and compile. Will this version of NM be ever be ready as an RPM? In FC6 maybe? -- Aaron Konstam [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: A problem compiling NetworkManager.
On Tue, 2006-08-29 at 12:39 -0500, Steev Klimaszewski wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan Williams wrote: On Sun, 2006-08-27 at 08:34 -0500, Aaron Konstam wrote: On Fri, 2006-08-25 at 16:44 -0500, Steev Klimaszewski wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aaron Konstam wrote: snippage Glad to hear you got further. I am not sure about LEAP support, but if you are building from CVS, then I guess you should have it, but someone more familiar with CVS would have a better answer for you (I am simply a packager for Gentoo, no commit access.) As to the dbus-glib-1 - that is either dbus-0.60+ or dbus-0.91+dbus-glib-0.71 hth Well I have dbus-061 installed as well as dbus-glib-0.61. So now what am I to do? I really would like some direction on compiling this NetworkManager from the CVS. Are you still getting the same error about automake macros? Note that if you don't have dbus = 0.90 you'll have to: s/dbus_connection_close/dbus_connection_disconnect/ Dan Actually, pretty sure dbus_connection_close was added in dbus .34... Was some discussion about that last night because of needing to patch a few things to work with dbus .91 on Gentoo. I am not sure what the above means where do you use: s/dbus_connection_close/dbus_connection_disconnect/ The dbus error is the one that is holding me up right now. Is it a matter that this compileing only works on Gentoo. Others reporting that htey suceeded in the compiling using the same method. So I am mystified. -- Aaron Konstam [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: A problem compiling NetworkManager.
On Fri, 2006-08-25 at 16:44 -0500, Steev Klimaszewski wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aaron Konstam wrote: snippage Glad to hear you got further. I am not sure about LEAP support, but if you are building from CVS, then I guess you should have it, but someone more familiar with CVS would have a better answer for you (I am simply a packager for Gentoo, no commit access.) As to the dbus-glib-1 - that is either dbus-0.60+ or dbus-0.91+dbus-glib-0.71 hth Well I have dbus-061 installed as well as dbus-glib-0.61. So now what am I to do? I really would like some direction on compiling this NetworkManager from the CVS. -- Aaron Konstam [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: A problem compiling NetworkManager.
On Fri, 2006-08-25 at 09:23 -0400, Matthew Saltzman wrote: On Thu, 24 Aug 2006, Aaron Konstam wrote: Here during the autogen.sh step I get these errors: Checking for required M4 macros... libtool.m4 not found glib-gettext.m4 not found Checking for forbidden M4 macros... ***Error***: some autoconf macros required to build NetworkManager were not found in your aclocal path, or some forbidden macros were found. Perhaps you need to adjust your ACLOCAL_FLAGS? What is the correct proceedure to fix these errors and procede? I appologize if the problem has been well discussed before and I missed it. $ rpm -qf `locate libtool.m4` libtool-1.5.22-2.3 $ rpm -qf `locate glib-gettext.m4`ell you weere half right Well you were half right. glib2-devel was notinstalled. Things got further but I was stopped in my tracks by the error message: Package requirements not met: dbus-glib-1 = 0.60 Now that is a puzzle since I can't find that program anywhere except for a site that cannot be reached. At least for FC5. One more thing is this NetworkManager I am trying to produce the one that has LEAP support? Otherwise I am wasting my time. -- Aaron Konstam [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: A problem compiling NetworkManager.
On Thu, 2006-08-24 at 16:17 -0500, Aaron Konstam wrote: On Thu, 2006-08-24 at 16:23 -0400, Darren Albers wrote: I think you need to install automake automake-1.9..6-2 is installed. I guess I could try to update it. Sorry , but here top posting seemed appropriate. On 8/24/06, Aaron Konstam [EMAIL PROTECTED] wrote: I am probably doing something really stupid but I have to ask. I am trying to compile NetworkManager from the CVS repository using instructions found on : http://www.gnome.org/projects/NetworkManager/developers/ The first thing is compile gnome-common using the following instructions: cvs -d :server:[EMAIL PROTECTED]:/cvs/gnome login cvs -d :pserver:[EMAIL PROTECTED]:/cvs/gnome co gnome-common cd gnome-common ./autogen.sh --prefix=/usr cd macros2 make make install Now we get to compiling and installing NetworkManager. THe isntructions were : cvs -d :pserver:[EMAIL PROTECTED]:/cvs/gnome login cvs -d :pserver:[EMAIL PROTECTED]:/cvs/gnome co NetworkManager cd NetworkManager ./autogen.sh --prefix=/usr --sysconfdir=/etc --localstatedir=/var make make install Here during the autogen.sh step I get these errors: Checking for required M4 macros... libtool.m4 not found glib-gettext.m4 not found Checking for forbidden M4 macros... ***Error***: some autoconf macros required to build NetworkManager were not found in your aclocal path, or some forbidden macros were found. Perhaps you need to adjust your ACLOCAL_FLAGS? What is the correct proceedure to fix these errors and procede? I appologize if the problem has been well discussed before and I missed it. -- === YOU!! Give me the CUTEST, PINKEST, most charming little VICTORIAN DOLLHOUSE you can find!! An make it SNAPPY!! === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list -- === And if California slides into the ocean, Like the mystics and statistics say it will. I predict this motel will be standing, Until I've paid my bill. -- Warren Zevon, Desperados Under the Eaves === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] -- === Injustice anywhere is a threat to justice everywhere. -- Martin Luther King, Jr. === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: A problem compiling NetworkManager.
On Thu, 2006-08-24 at 16:38 -0500, Aaron Konstam wrote: On Thu, 2006-08-24 at 16:17 -0500, Aaron Konstam wrote: On Thu, 2006-08-24 at 16:23 -0400, Darren Albers wrote: I think you need to install automake automake-1.9..6-2 is installed. I guess I could try to update it. Sorry , but here top posting seemed appropriate. I also apologize for duplicate messages because of my confusion. Any further ideas on what to do? On 8/24/06, Aaron Konstam [EMAIL PROTECTED] wrote: I am probably doing something really stupid but I have to ask. I am trying to compile NetworkManager from the CVS repository using instructions found on : http://www.gnome.org/projects/NetworkManager/developers/ The first thing is compile gnome-common using the following instructions: cvs -d :server:[EMAIL PROTECTED]:/cvs/gnome login cvs -d :pserver:[EMAIL PROTECTED]:/cvs/gnome co gnome-common cd gnome-common ./autogen.sh --prefix=/usr cd macros2 make make install Now we get to compiling and installing NetworkManager. THe isntructions were : cvs -d :pserver:[EMAIL PROTECTED]:/cvs/gnome login cvs -d :pserver:[EMAIL PROTECTED]:/cvs/gnome co NetworkManager cd NetworkManager ./autogen.sh --prefix=/usr --sysconfdir=/etc --localstatedir=/var make make install Here during the autogen.sh step I get these errors: Checking for required M4 macros... libtool.m4 not found glib-gettext.m4 not found Checking for forbidden M4 macros... ***Error***: some autoconf macros required to build NetworkManager were not found in your aclocal path, or some forbidden macros were found. Perhaps you need to adjust your ACLOCAL_FLAGS? What is the correct proceedure to fix these errors and procede? I appologize if the problem has been well discussed before and I missed it. -- === YOU!! Give me the CUTEST, PINKEST, most charming little VICTORIAN DOLLHOUSE you can find!! An make it SNAPPY!! === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list -- === And if California slides into the ocean, Like the mystics and statistics say it will. I predict this motel will be standing, Until I've paid my bill. -- Warren Zevon, Desperados Under the Eaves === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] -- === Injustice anywhere is a threat to justice everywhere. -- Martin Luther King, Jr. === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list -- === Some men love truth so much that they seem to be in continual fear lest she should catch a cold on overexposure. -- Samuel Butler === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Website Broken
On Tue, 2006-07-25 at 22:44 -0400, Paul Dugas wrote: Header is okay for me but the text in the Flexible, Extendable, Open paragraphs is floating over, not wrapping around the screenshot image. See attached. I'm running FireFox-1.5.0.4 on updated Fedora Code 5. Paul This is happening to me also but not all the time. -- Aaron Konstam [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Website Broken - additional info
On Wed, 2006-07-26 at 08:41 -0500, Aaron Konstam wrote: On Tue, 2006-07-25 at 22:44 -0400, Paul Dugas wrote: Header is okay for me but the text in the Flexible, Extendable, Open paragraphs is floating over, not wrapping around the screenshot image. See attached. I'm running FireFox-1.5.0.4 on updated Fedora Code 5. Paul This is happening to me also but not all the time. It happens to me with firefox but not konqueror. So it must be a firefox problem in some sense. -- Aaron Konstam [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Website Broken
On Wed, 2006-07-26 at 23:12 +0200, Dominik Sandjaja wrote: Hello, Am Mittwoch, den 26.07.2006, 13:15 -0500 schrieb Jason Martens: Darren Albers wrote: It /seems/ to look ok to me... What browser are you using? Sorry, wasn't paying attention. Here's a screenshot of what it looks like in my browser, which says it is Firefox/1.5.0.4 (Debian-1.5.dfsg+1.5.0.4-1). the Administrators-page looks like this: http://dadadom.de/images/screenshot.png on my browser (Firefox 1.5.0.4, FC5). So it's definitely not a Debian-only-problem ;) Dominik I am getting the same behavior in FC5 so I agree it is not a Debian problem alone. === Were these parsnips CORRECTLY MARINATED in TACO SAUCE? === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [PATCH] LEAP support in NetworkManager
On Thu, 2006-07-13 at 13:07 -0400, Dan Williams wrote: On Fri, 2006-07-07 at 20:32 -0300, Thiago Bauermann wrote: Hi folks, This is a patch which adds LEAP support to NetworkManager. It has two issues which I am aware of, but it's most definetly usable (and useful!). I am interested in the LEAP support but I am unclear where to find the NM that contains it. Is it one of the distributions of source code you can get from the NetworkManager home site? If so which is it? -- Aaron Konstam [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
wpa_supplicant
I am having a hard time filding wpa_supplicant. I downloaded a source for it but when I compiled it I got the error that SCARD_S_SUCCESS was undeclared. Any help out there? Aaron Konstam [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Subscribing to lost
It has happened again. No matter how I try I cannot resubscribe to the list. Could someone on help me? -- Aaron Konstam [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
A reconsideration of the list reply configuration.
When I am wrong I an wrong. I have been thinking about it. Despite what
red hat lists do I think that return to message sender is the best
configuration of this list.
With appropriate e-mail clients we can then:
1. reply to the poster of the message. [reply]
2. reply to the list alone {reply to list]
3. reply to both [reply all]
The only bad thing is that some mail clients [mutt for example] do not
have these three options but you can fake it if your clever.
--
Aaron Konstam [EMAIL PROTECTED]
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
mailman list manager has a misconfiguration.
I don't know if my comment about the misconfiguration of this list got lost in shuffle. But unlike most mailman lists this list is not configured to have postings include a reply to: option pointing to the list itself rather than to the sender of the post. -- === The worst cliques are those which consist of one man. -- G.B. Shaw === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: mailman list manager has a misconfiguration.
On Sat, 2006-05-13 at 10:47 -0400, Gene Heskett wrote: Aaron Konstam wrote: I don't know if my comment about the misconfiguration of this list got lost in shuffle. But unlike most mailman lists this list is not configured to have postings include a reply to: option pointing to the list itself rather than to the sender of the post. -- I've been advised by someone on this list that this list does it correctly and the rest of the world is wrong, but frankly Aaron I detest having to bomb both your mailbox and the list by using reply to all in order for my reply to go to the list. It should default to the list, and only include your private address if I 'reply all'. This is one of the reasons I don't think I have a 'reply to:' set here. I of course agree with you. -- Aaron Konstam [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: A comment on NetworkManager
On Fri, 2006-05-12 at 10:39 -0500, Gene Heskett wrote: Garry Williams wrote: On 5/11/06, Gene Heskett [EMAIL PROTECTED] wrote: p.roediger wrote: Aaron Konstam schrieb: On Thu, 2006-05-11 at 02:48 +0200, Peter Roediger wrote: [snip] So when is it going to be made compatible with kde I run FC5 (updated from FC4) on a Sony Vaio FS640/W. (This uses the Intel ipw2200 wireless adapter.) I decided to use KDE (after years with Gnome) about two months ago. nm-applet will run in KDE just fine. I added /usr/libexec/gnome-settings-daemon /usr/bin/gnome-keyring-daemon to my start-up list. All works as expected here with one minor exception: The nm-applet icon occasionally disappears from the panel, leaving a blank spot where it used to be. If I unplug or plug in my wired Ethernet cable, nm-applet still notifies me that the change has occurred. I can restore the icon by manually killing and restarting nm-applet. It will also spontaneously reappear. I haven't figured why this happens. I intend to give KNetworkManager a try when I get some time, but I have all NM functionality now with KDE and without KNetworkManager. What is this nm_applet people are talking about? I don't believe its installed on this FC5 system. It is vry habdy for scanning available access points. You should install it if it is not installed. It is part of the : -- NetworkManager-gnome-0.5.1-1.FC4.4 rpm ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: A comment on NetworkManager
On Thu, 2006-05-11 at 02:48 +0200, Peter Roediger wrote: Hi everyone, I thought I should write a little -personal- comment on what I think about the current implementation of NetworkManager and, more importantly, its design goals. First of all, I'm very pleased to see that there is some effort going on to make a linux desktop more user-friendly in terms of network usage and managing more than one network device in more than one (wireless) network. So far, NetworkManager looks to me like a very good approach to it, though it has some, in my view, major shortcomings which I'd like to address in this mail. 1.) Wireless networks list. There is no Search for wireless networks or Refresh wireless networks list button/option in the applet. While this seems to be convenient in the first place it turns out to be not in some cases. Consider this: Many laptops nowadays feature an LED that shows the status of the wireless connection ( e.g. flashing when it's not connected, etc.). Thus people will naturally switch the wireless network off when it's not needed. Then, they might disconnect their wired LAN at one point and go to some place that is supplied by a wireless network. Now, they turn on their wireless network card by a hardware switch and...they have to wait. They have to wait until NM will update the list. Which will take some time. The average user will not understand this behavior. But the average user would understand an option mentioned above. It's easy. Easier than a WEP key. Or something else: You walk around in a foreign city in order to find a hotspot to logon to. There is a desperate need to update the list immediately. It's simply crucial. I must be pretty confused. I use my wireless at home and at work and nm-applet shows me immediately the wireless access points that are available. 2.) The configuration issue. In my view NetworkManager is one of the most intransparent linux applications out there. There's no Documentation (correct me if I'm wrong), there is no configuration file easily accessible and there are weird things going on with resolv.conf. How is it configured? How can I change the DNS server without violating # generated by NetworkManager, do not edit!? Do I have to use a special program. In answer to part of point two, it is the DHCP server that supplies the addresses of the DNS servers not NM ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
WEP vs WPA
I must be losing something is the WEP vs wpa discussion. wpa is supposed to be more secure than WEP, However currently my WEP access at home is secured by a 13 character (128 bit) passwd. In addition there the keyring string. That seems pretty secure to me. Could someone explain why this security is so compromisable that the added trouble of wpa is worth doing? -- Aaron Konstam [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Help I am stuck in limbo
I obviously unsubscribed from the list but nothing I do will allow me to subscribe again. What can I do? -- Aaron Konstam [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
