Re: Requested syslog for LEAP authenticatiln sequence
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aaron Konstam wrote: > On Fri, 2007-07-06 at 14:36 -0400, Ryan Novosielski wrote: >> Apologies for being unclear -- I meant the killswitch problem. >> >> A little foggy today. :) >> >> =R >> >> Ryan Novosielski wrote: >>> This was answered just today -- take a look at the mailing list. >>> >>> =R > Well you are correct that this was discussed on the list today. But I am > not sure there was a answer I understand: > 1. What is a killswitch? > 2. What am I going to do with the patch if it shows up? Something that your laptop or desktop apparently does not have -- to disable wireless. My Latitude D620 has a sliding switch. As I understand it, the D810 had a function key combo that would turn it on and off (not sure if this counts as a killswitch -- think so). Support made it into NM recently I think (though there has not been a new release recently, so I'm not really sure about that). As for what to do with the patch, I suppose you patch the NetworkManager source or wait for the new release, like anything else. Please keep replies on list. =R - -- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer III |$&| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGjuvImb+gadEcsb4RAgcDAJwPrN2M/Hh1SjMCQGWuyjRifRw2UQCgzDZ7 y5C2i88Pg7sjEU1iFBKRXjY= =+8rx -END PGP SIGNATURE- begin:vcard fn:Ryan Novosielski n:Novosielski;Ryan org:UMDNJ;IST/AST adr;dom:MSB C630;;185 South Orange Avenue;Newark;NJ;07103 email;internet:[EMAIL PROTECTED] title:Systems Programmer III tel;work:(973) 972-0922 tel;fax:(973) 972-7412 tel;pager:(866) 20-UMDNJ x-mozilla-html:FALSE version:2.1 end:vcard ___ 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 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
gnome network manager doesn't check dial-up status --> no vpn possible
Hi there, I'm trying the gnome network manager for the first time these days, and so far I can say that things work quite easily and without much config-hassling. There is just one issue at the moment I have with the gnome network manager. I need wireless with WPA (this works), I need dial-up for my UMTS/GMS PCMCIA-Datacard (this works, too), and I need VPN-client functionality (works like a charm with vpnc in connection with the plugin for the network manager). The problem is using dial-up and VPN *together*. It's just not possible - the network manager is not offering me connecting via VPN if I'm in the Internet via the Datacard. It works, if I'm wired or wirelessly (802.11b/g) connected. I think the real problem is that the tool is not aware of the actual status of the dial-up connection and because of this the tool can't show it to the user. This also has a big consequence/drawback - as the tool doesn't know about the status of the connection, the icon above is shown as "not connected" --> and then you also can't start a VPN-connection! This is really a broken design of the tool. A common use-case is the following: I'm travelling with my laptop and have a UMTS/GSM PCMCIA-Datacard with me. I connect to the Internet (with the dial Up functionality of network-manager) and then want to start VPN to establish a secure tunnel to my company. I can't do that, because network-manager doesn't let me start VPN (it's greyed out), because it doesn't know about the dial-up status and thinks it's not connected. If I were at a wireless-hotspot, network-manager does check the status and offers me to connect via VPN (works perfectly, by the way). Perhaps I'll find a workaround by using some scripts to manually start the VPN-connection, but I would rather like to see this fixed. If i can help/test/do anything (except programming, which I can't), I'll gladly do it. Best Regards, airflow ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Requested syslog for LEAP authenticatiln sequence
Aaron Konstam wrote: > 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. > Am pretty confident the patch I posted today will fix this... Regards, Jon. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
More on NM killing eth0
Here is the /var/log/message again. This is what /var/log/messages tells me: Jul 5 08:08:02 localhost kernel: sdc: sdc1 Jul 5 08:08:04 localhost hald: mounted /dev/sdc1 on behalf of uid 500 This was me, user 500 mounting a USB 2 GByte flash card. Jul 5 08:08:41 localhost hald: unmounted /dev/sdc1 from '/media/disk' on behalf of uid 500 Here 40 seconds later I unmounted the thing. Jul 5 08:17:45 localhost NetworkManager: nm_signal_handler(): Caught si gnal 15, shutting down normally. Here 9 minutes after I unmounted the flash card NetworkManager gets the shut down signal 15. Jul 5 08:17:45 localhost NetworkManager: Caught terminiation signal Here it verifies it got the signal 15 Jul 5 08:17:45 localhost NetworkManager: Deactivating device eth0. Here is where the Internet died. Jul 5 08:17:45 localhost dhclient: DHCPRELEASE on eth0 to 192.168.0.1 port 67 Jul 5 08:17:46 localhost avahi-daemon[2409]: Withdrawing address record for 192 .168.0.2 on eth0. Here I was trying to ping and connect to the DSL Modem. Of course it didn't work. Jul 5 08:17:46 localhost avahi-daemon[2409]: Leaving mDNS multicast group on in terface eth0.IPv4 with address 192.168.0.2. Jul 5 08:17:46 localhost avahi-daemon[2409]: Interface eth0.IPv4 no longer rele vant for mDNS. Jul 5 08:17:46 localhost avahi-daemon[2409]: Withdrawing address record for fe8 0::250:2cff:fea8:69f3 on eth0. Jul 5 08:17:46 localhost avahi-daemon[2409]: Leaving mD The avahi-daemon I know nothing about. Hope this might help. If anyone wants me to try to repeat the problem I will be glad to do so. Karl Larsen ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Requested syslog for LEAP authenticatiln sequence
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Apologies for being unclear -- I meant the killswitch problem. A little foggy today. :) =R Ryan Novosielski wrote: > This was answered just today -- take a look at the mailing list. > > =R > > Aaron Konstam wrote: >> 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: 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] > > >> > >> ___ >> 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 - -- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer III |$&| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGjovGmb+gadEcsb4RAgTkAKDUxa2U7gt2jZNkIlJvlZcuGBX84wCfaBiS jrNh7pShW0UrbCC93kKYrV4= =JzC/ -END PGP SIGNATURE- ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Requested syslog for LEAP authenticatiln sequence
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This was answered just today -- take a look at the mailing list. =R Aaron Konstam wrote: > 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: 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] > > > > > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list - -- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer III |$&| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGjoo+mb+gadEcsb4RAtXqAKCZxRbCWhFIwASQeVrwz2Bmi4pwKwCfZr5h Z07Y5JmppmuTWTrhWi0uWeQ= =P3Ra -END PGP SIGNATURE- ___ 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: 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
- "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.
diff -urN NetworkManager-0.6.5/nm-applet-0.6.5/src/applet-dbus-info.c NetworkManager-0.6.5.new/nm-applet-0.6.5/src/applet-dbus-info.c
--- NetworkManager-0.6.5/nm-applet-0.6.5/src/applet-dbus-info.c 2007-06-07 17:44:06.0 +0100
+++ NetworkManager-0.6.5.new/nm-applet-0.6.5/src/applet-dbus-info.c 2007-07-06 15:11:16.0 +0100
@@ -193,9 +193,7 @@
}
/* Hack: 802.1x passwords are not stored in the keyring */
- if (!new_key &&
- ((we_cipher == NM_AUTH_TYPE_WPA_EAP && !have_priv_key_file) ||
- we_cipher == NM_AUTH_TYPE_LEAP))
+ if (!new_key && (we_cipher == NM_AUTH_TYPE_WPA_EAP && !have_priv_key_file))
{
NMGConfWSO *gconf_wso;
gconf_wso = nm_gconf_wso_new_deserialize_gconf (applet->gconf_client,
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Possible Bug
I by accident loaded NM on this computer which has only one source of the Internet from eth0. It was working fine and no problems until about 8AM when it appeared the Internet had failed. I could not get Google on my web browser. A hint I missed was that when I tried to reach my DSL modem with a call of 192.168.0.1 it failed. I know now it failed because eth0 was turned off by NM. This is what /var/log/messages tells me: Jul 5 08:08:02 localhost kernel: sdc: sdc1 Jul 5 08:08:04 localhost hald: mounted /dev/sdc1 on behalf of uid 500 Jul 5 08:08:41 localhost hald: unmounted /dev/sdc1 from '/media/disk' on behalf of uid 500 Jul 5 08:17:45 localhost NetworkManager: nm_signal_handler(): Caught si gnal 15, shutting down normally. Jul 5 08:17:45 localhost NetworkManager: Caught terminiation signal Jul 5 08:17:45 localhost NetworkManager: Deactivating device eth0. Jul 5 08:17:45 localhost dhclient: DHCPRELEASE on eth0 to 192.168.0.1 port 67 Jul 5 08:17:46 localhost avahi-daemon[2409]: Withdrawing address record for 192 .168.0.2 on eth0. Jul 5 08:17:46 localhost avahi-daemon[2409]: Leaving mDNS multicast group on in terface eth0.IPv4 with address 192.168.0.2. Jul 5 08:17:46 localhost avahi-daemon[2409]: Interface eth0.IPv4 no longer rele vant for mDNS. Jul 5 08:17:46 localhost avahi-daemon[2409]: Withdrawing address record for fe8 0::250:2cff:fea8:69f3 on eth0. Jul 5 08:17:46 localhost avahi-daemon[2409]: Leaving mD When a computer with just one source of Internet has that turned off by NM it is a serious Bug I think. Your better at reading the messages and perhaps you can find a reason I missed. Karl ___ 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
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
Re: NM stopped 'spinning'
Quoting Dan Williams <[EMAIL PROTECTED]>: > Trunk/0.7 aren't quite ready for general use yet. There are still > missing pieces that various people are working on. It worked reasonably good on 2.6.20 (there I had the spinning). The only problem I noticed, which I noticed on both .20 and .22 is that I loose the network quite often. And very often it require the key again (this is true on 0.9.30 to). It's just a matter of requesting the network again, but ten seconds later, I loose it again (ad finitum). I couldn't get 0.9.30 to compile on 2.6.22, but that's ok. There where other problems with that kernel, so I gone back to .20 and there everything seems stable. Thanx for the help, much appreciated. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Leap authentication problem in NM.- once again
> 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 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
AP selection process
hi. how does the ap selection process work? at home i'm using wpa on my ap, but nm always connects to an ap without encryption first. i have to manually switch to my ap, which is a bit annoying. isn't there some magic that prefers encrypted networks over unencrypted? -- pelle smime.p7s Description: S/MIME cryptographic signature ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Leap authentication problem in NM.- once again
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 > > 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. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
