Re: one time passwords

2007-03-24 Thread Denis Leroy
David Braun wrote:
  Hi,
 
  Network Manager doesn't handle one time passwords on VPN connections
  too well. I'm not too familiar with the various VPNs but Cisco uses
  two passwords, a user and a group password. In my case the user
  password comes from a token card and is only good once. NM very nicely
  saves both in the keyring. The problem is that it re-uses the user
  password when I start a new session. This always fails. Is there any
  way to save only the group password and not the user password?

Hi David,

I wrote a patch to fix this. It's available here:

http://bugzilla.gnome.org/show_bug.cgi?id=363918

CVS gatekeepers, any words on merging this patch in ?

-denis

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


problem applying Atheros patch

2007-03-24 Thread Patton Echols
Some time ago I wrote the list about using Network Manager with atheros 
/ madwifi driver and the signal strength reporting problem with the 
driver.  Even though it is not supposed to make a difference, NM 
periodically drops connection and I have been told that others in this 
position have seen better results after patching. 

Last time I posted, I was pointed to the patches posted here:
http://mail.gnome.org/archives/networkmanager-list/2006-January/msg00141.html

Since I'm kind of a Noob, it took me a while to fine out what I'm supposed to 
do with a patch. 

I am using Network Manager on Ubuntu 6.10 (Edgy) with Atheros chipset.  NM 
version is 0.6.3.

At the point of applying the patch, i get the following output from the patch 
command:

[EMAIL PROTECTED]:~/NetworkManager/network-manager-0.6.3$ patch -p0   
atheros.patch
patching file src/nm-device-802-11-wireless.c
Hunk #1 succeeded at 117 (offset -4 lines).
Hunk #2 succeeded at 1152 (offset 134 lines).
Hunk #3 succeeded at 1248 (offset 134 lines).
Hunk #4 FAILED at 1308.
Hunk #5 succeeded at 3309 with fuzz 1 (offset 114 lines).
1 out of 5 hunks FAILED -- saving rejects to file 
src/nm-device-802-11-wireless.c.rej

===

And here is the contents of file src/nm-device-802-11-wireless.c.rej

***
*** 1306,1312 
  #endif
  if (iw_get_stats (nm_dev_sock_get_fd (sk), iface, stats, 
range, has_range) == 0)
  {
- percent = wireless_qual_to_percent (stats.qual, (const 
iwqual *)(self-priv-max_qual),
  (const iwqual *)(self-priv-avg_qual));
  }
  nm_dev_sock_close (sk);
--- 1308,1314 
  #endif
  if (iw_get_stats (nm_dev_sock_get_fd (sk), iface, stats, 
range, has_range) == 0)
  {
+ percent = wireless_qual_to_percent (NM_DEVICE (self), 
stats.qual, (const iwqual *)(self-priv-max_qual),
  (const iwqual *)(self-priv-avg_qual));
  }
  nm_dev_sock_close (sk);

I stopped at this point.  I really don't want to carry on building the code if 
the patch won't work.  Any 
thoughts?  

Thanks for all thoughts,

Patton





___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Weird nm-applet behavior.

2007-03-24 Thread Aaron Konstam
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


NetworkManager and rtl8180 on debian etch

2007-03-24 Thread David L. Emerson
I'm trying to get NetworkManager-kde working with my wireless card
(Linksys WPC11 v.4 / rtl8180 chipset)

knetworkmanager can now detect the card, scan for networks, and prompt 
for a wep key if needed.  However, when trying to connect to any 
wireless network (encrypted or not) it stalls at 28%:
Activation Stage: Configuring device.

Here's a paste of dmesg:

IEEE802.11: Associating with belkin54g
IEEE802.11: Stopping scan
IEEE802.11: Sending authentication request
IEEE802.11: Received authentication response
IEEE802.11: Sending association request
IEEE802.11: Received association response
IEEE802.11: Successfully associated
rtl8180: Joining the BSS
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

...after about a minute, it resets the card and repeats the above.

The card+driver work ok, and can connect to unencrypted and 
wep-encrypted networks, using debian's /etc/network/interfaces and 
ifconfig.

(I commented out most of /etc/network/interfaces (except loopback lo) so 
that NetworkManager can work on debian;  I read somewhere that debian 
modified networkmanager so as not to touch interfaces listed 
in /etc/network/interfaces -- and indeed, prior to doing the 
commenting, networkmanager could not see the interfaces at all)

If it's relevant: I'm using kernel 2.6.18, with the (free) rtl-wifi 
driver.  I recently wrote a Debian entry for their FAQ:
http://rtl-wifi.sourceforge.net/wiki/FAQ#Debian

Thanks!
~David.


___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list