Re: networkmanager fails to associate (ipw3945)
On Sat, 02/24/2007, Dan Williams wrote: > Right; so what we now need to know from everyone is: > > 1) what distro? > 2) what kernel version? > 3) what version of ipw3945 drivers? > 4) what version of the ieee80211 stack? distro: debian testing kernel: 2.6.18-3-686 #1 SMP ipw3945: 1.1.2dmpr ieee80211: 1.2.15 ipw3945 and ieee80211 modules are from the debian repository ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
On Fri, 02/23/2007, dragoran wrote: > as you can see in the thread there seems to be no soultion for it and > the discussion stopped :( > the only solution that I can tell you is to use wpa_supplicant directly, > networkmanager seems not to work with ipw3945 + wpa. NM works fine with my ipw3945 + wpa (debian on dell inspiron 6400) same processes running here NM-tool output: NetworkManager Tool State: connected - Device: eth2 NM Path: /org/freedesktop/NetworkManager/Devices/eth2 Type: 802.11 Wireless Driver:ipw3945 Active:yes HW Address:00:13:02:65:97:1E Capabilities: Supported: yes Speed: 54 Mb/s Wireless Settings Scanning:yes WEP Encryption: yes WPA Encryption: yes WPA2 Encryption: yes Wireless Networks (* = Current Network) CLS: Infrastructure Mode, Freq 0.000 MHz, Rate 54 Mb/s, Strength 58%, Encrypted (WEP) *Xenonet:Infrastructure Mode, Freq 0.000 MHz, Rate 62 Mb/s, Strength 93%, Encrypted (WPA) IP Settings: IP Address: 192.168.2.101 Subnet Mask: 255.255.255.0 Broadcast: 192.168.2.255 Gateway: 192.168.2.1 Primary DNS: 192.168.2.1 Secondary DNS: 0.0.0.0 - Device: eth0 NM Path: /org/freedesktop/NetworkManager/Devices/eth0 Type: Wired Driver:b44 Active:no HW Address:00:15:C5:13:51:A5 Capabilities: Supported: yes Carrier Detect: yes Speed: 10 Mb/s Wired Settings Hardware Link: no Did you uncomment your interfaces in /etc/network/interfaces? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Singe DES encryption should be enabled
Well, there are indeed such cases -> my university I was thinking about enabling this feature through a gconf entry. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Singe DES encryption should be enabled
We should enable single DES encryption mode. In this case, vpnc must be called using the --enable-1des flag. According to http://mail.gnome.org/archives/networkmanager-list/2006-September/msg00107.html this feature should be implemented using the gconf to determing whether of not to use this flag. I would like to implement this feature, but I'm not sure where in the program to read out the gconf and to transmit the data to the calling function. My first idea was to write it in gnome/applet/applet-dbus-vpn.c, where the gconf is read already. On the other hand, this would necessitate to extend the dbus message, which could lead to incompatibility between the networkmanager and the vpnc-daemon, couldn't it? My second idea was to read it in vpn-daemons/vpnc/src/nm-vpnc-service.c:nm_vpnc_start_vpnc_binary, but since the gconf isn't read in this file, it would mean code duplication and that libgconf would be linked to this binary and therefor growth of the bin size. I would like to know what the developers suggest. ___ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
RE: message 5 (wrong patch)
I accidentally mixed the patch with another thing I
was working on. Here's a clean version of it.
___
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.deIndex: nm-vpnc-service.c
===
RCS file: /cvs/gnome/NetworkManager/vpn-daemons/vpnc/src/nm-vpnc-service.c,v
retrieving revision 1.21
diff -u -r1.21 nm-vpnc-service.c
--- nm-vpnc-service.c 4 Dec 2006 20:59:26 - 1.21
+++ nm-vpnc-service.c 20 Feb 2007 23:01:27 -
@@ -52,6 +52,7 @@
{
"/usr/sbin/vpnc",
"/sbin/vpnc",
+ "/usr/local/sbin/vpnc",
NULL
};
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
vpnc plugin should look in /usr/local/sbin for binary
In case vpnc is compiled manually, it is often installed in /usr/local/sbin. Thus, the vpnc plugin should look for the binary in this directory as well. I have appended a trivial patch which provokes this. So far Olaf ___ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.deIndex: nm-vpnc-service.c === RCS file: /cvs/gnome/NetworkManager/vpn-daemons/vpnc/src/nm-vpnc-service.c,v retrieving revision 1.21 diff -r1.21 nm-vpnc-service.c 54a55 > "/usr/local/sbin", 356a358,359 > gbooleanenable_1des = false; > GConfClient *gconfclient; 376a380,383 > gconfclient = gconf_client_get_default (); > enable_1des = gconf_client_get_bool (gconfclient, > > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
