Re: Will it work under Fedora Core 5?
On Wednesday 29 March 2006 11:27, jim lawrence wrote: I did a fresh instal of FC5 and was connect with my wireless in 2 minutes after loading the firmware for my wireless device. What exactly did you do in that 2 minutes? Are you running KDE, or Gnome, or something else? What is your wireless device? -- Timothy Murphy e-mail (80k only): tim /at/ birdsnest.maths.tcd.ie tel: +353-86-2336090, +353-1-2842366 s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
What exactly are the aims of NM?
I wonder if the aims and hopes of the NM developers are documented anywhere? Is it hoped that it will work with all wireless devices for which there is a Linux driver (including ndiswrapper)? Or will it only work for cards, etc, with certain properties - eg ability to go into Monitor mode - which are not actually necessary in order to run under Linux? I have an Orinoco classic Gold PCMCIA card (in fact several of them, including ones in USB and PCI adapters), and I have never been able to get NM to work with them. Also is it intended that NM should work with KDE? I installed FC-5 with KDE, started NetworkManager and NetworkManagerDispatcher, and as far as I could see nothing at all happened. I should say that I am quite happy to wait, if it is intended that NM will work with my setup sooner or later. -- Timothy Murphy e-mail (80k only): tim /at/ birdsnest.maths.tcd.ie tel: +353-86-2336090, +353-1-2842366 s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: What exactly are the aims of NM?
On Wed, 29 Mar 2006 13:53:44 +0100, Timothy Murphy wrote I wonder if the aims and hopes of the NM developers are documented anywhere? Is it hoped that it will work with all wireless devices for which there is a Linux driver (including ndiswrapper)? I haven't seen much of the stuff behind the scenes on NM, but the adapters that support WE (Wireless Extensions) have worked for me good enough. Specially the IPW one's. Or will it only work for cards, etc, with certain properties - eg ability to go into Monitor mode - which are not actually necessary in order to run under Linux? Why would you want rfmon for NM? I haven't seen something that uses that. I have an Orinoco classic Gold PCMCIA card (in fact several of them, including ones in USB and PCI adapters), and I have never been able to get NM to work with them. Have you ever googled to see if anyone else has asked about this? Maybe there is people that have it working and it is only you. Also is it intended that NM should work with KDE? I don't know much of the Linux thinking, but this is a gnome mailing list. Never the less. google for KNetworkManager. I read something about it. I installed FC-5 with KDE, started NetworkManager and NetworkManagerDispatcher, and as far as I could see nothing at all happened. I should say that I am quite happy to wait, if it is intended that NM will work with my setup sooner or later. It is an incredible tool so far. And I would try not to send my phone numbers, and contact information on emails. .Alejandro -- Timothy Murphy ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
configuration for DHCP client to use
Where do you configure which dhcp client to use for NetworkManager? dist is SUSE 10.0... /etc/sysconfig/network/dhcp?? If so, why doesn't the /var/log/dhclient-script reflect the change when I set the client to yes? I'm failing to get a valid DHCP address. Thx. Wendell ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: What exactly are the aims of NM?
On Wednesday 29 March 2006 14:51, Alejandro Bonilla wrote: I wonder if the aims and hopes of the NM developers are documented anywhere? Is it hoped that it will work with all wireless devices for which there is a Linux driver (including ndiswrapper)? I haven't seen much of the stuff behind the scenes on NM, but the adapters that support WE (Wireless Extensions) have worked for me good enough. Specially the IPW one's. So it works for you, as I am sure it does for many others, but it doesn't work for me (Fedora-5 with KDE). My question - which you don't seem to have read - was not whether it works for some people, but if it is intended that it should work for everyone who has a wireless device working under Linux. I have an Orinoco classic Gold PCMCIA card (in fact several of them, including ones in USB and PCI adapters), and I have never been able to get NM to work with them. Have you ever googled to see if anyone else has asked about this? Maybe there is people that have it working and it is only you. I have asked exactly that question on this list, and have not heard from anyone who has this fairly common card working under NM. Also is it intended that NM should work with KDE? I don't know much of the Linux thinking, but this is a gnome mailing list. What exactly does that mean? Are you saying that NetworkManager is not intended to run under KDE? Or that it is, but if you are running KDE you should not write to this list? Never the less. google for KNetworkManager. I read something about it. I don't think that is available under Fedora-5, which I am running. It is an incredible tool so far. I always amazes me when someone writes saying that their ABC video adaptor does not work under some version of Linux, and someone writes back to say that their XYZ adaptor is working fine, as though that is some kind of answer to the query. -- Timothy Murphy e-mail (80k only): tim /at/ birdsnest.maths.tcd.ie tel: +353-86-2336090, +353-1-2842366 s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: What exactly are the aims of NM?
This is answered here: http://live.gnome.org/NetworkManagerHardware The Orinco card does not seem to support the latest wireless extensions that are needed for NM to talk to the card to do WPA but it does do unencrypted and WEP Robert Love posted a patch that enables this but it is not part of the mainline NM since the authors did not want to have to support 10 different drivers and are focusing all their efforts on WEXT compliance. The patch is availabe here: http://mail.gnome.org/archives/networkmanager-list/2006-March/msg00068.html ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: What exactly are the aims of NM?
On 3/29/06, Timothy Murphy [EMAIL PROTECTED] wrote: On Wednesday 29 March 2006 14:51, Alejandro Bonilla wrote: I wonder if the aims and hopes of the NM developers are documented anywhere? Is it hoped that it will work with all wireless devices for which there is a Linux driver (including ndiswrapper)? I haven't seen much of the stuff behind the scenes on NM, but the adapters that support WE (Wireless Extensions) have worked for me good enough. Specially the IPW one's. So it works for you, as I am sure it does for many others, but it doesn't work for me (Fedora-5 with KDE). I am not trying to make this a flamewar so don't take this as such, but he did answer your question, NM supports cards that properly support the latest WEXT standard for example the IPW cards. My previous email contains another link that lists specific hardware support that you may find usefull. Regarding KNetworkManager, there was a post here by the author of that applet and I think he is hosting it on the KDE SVN repository. If you search the list archives for the past 2 weeks you should see it and that can help you find it. I think if you install your standard distro's NetworkManager package and then the KNetworkManager applet you should be good to go but I run Gnome so I have never tried it. If it works for you please let the list know. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: What exactly are the aims of NM?
Hi Timothy, On Wed, 2006-03-29 at 13:53 +0100, Timothy Murphy wrote: Also is it intended that NM should work with KDE? The NetworkManager daemon itself does not depend on a specific desktop environment. Up to my knowledge there are currently two graphical front-ends available: nm-applet using GTK/GNOME libraries and KNetworkManager using Qt/KDE libraries. However, both should run fine within any desktop environment -- as long as you have an application running which provides a system tray which is compliant to the freedesktop.org system tray spec [1]. I doubt that there are Fedora packages of KNetworkManager available yet, but a volunteering packager already contacted me. Timo [1] http://freedesktop.org/Standards/systemtray-spec ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Will it work under Fedora Core 5?
On Wed, 2006-03-29 at 07:53 +0200, Trond Husø wrote: Hi list, Fedora Core 5 has just been released, and I might concider upgrading from FC4. But before I do, I need to know if some of my favorite programs works. One of these are Network Manager. So: Does it work under FC5? We ship it and it works. It's not started by default, nor is nm-applet running by default. -- Peter ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
problem starting nm-applet
Just compiled NetworkManager-0.6.2 on SUSE 10.0 ...went fine. Note that I'm using dbus-0.35.2 not 0.60. Q1: Is this mandatory? Q2: After installing the package, and I startup the NetworkManager and Dispatcher daemons...come up fine. As a normal user, try launching the nm-applet, and this is what appears to stdout: ** (nm-applet:7196): CRITICAL **: network_device_is_wired: assertion `dev != NULL' failed ** (nm-applet:7196): CRITICAL **: network_device_is_wireless: assertion `dev != NULL' failed ** (nm-applet:7196): CRITICAL **: nma_get_connected_icon: assertion `dev != NULL' failed ** (nm-applet:7196): CRITICAL **: network_device_is_wired: assertion `dev != NULL' failed ** (nm-applet:7196): CRITICAL **: network_device_is_wireless: assertion `dev != NULL' failed What is going on? I did the touch /var/log/console/USER and chown'ed it to the user to avoid the pam issue on SUSE. Still no tickie-no-workie. Any thoughts on why? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: What exactly are the aims of NM?
Timothy Murphy wrote: Also is it intended that NM should work with KDE? I installed FC-5 with KDE, started NetworkManager and NetworkManagerDispatcher, and as far as I could see nothing at all happened. I don't know if it is intended or not, but NM works fine in KDE (I am using an up to date FC4 - I have yet to try FC5). In addition to running both the NetworkManager and NetworkManagerDispatcher services, you will need to manually start NetworkManagerInfo which should display an applet in your panel's tray. There may be other ways of doing this in KDE, but that's what I have to do with the version I'm using [1]. However, since it sounds like (from what others have said in reply so far) your card is not (yet) supported, you will have little to no functionality in the NM applet. [1] I can't upgrade to the latest NM because it requires a newer DBUS which requires a newer Glibc - and you know how messy that can get ;-). So I figure I'll get all that less painfully with FC5. -- Best Regards, ~DJA. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
[patch] OpenVPN helper server crash
Hi,
I have been using the ubuntu 0.6.1 packages (really nice btw!), and have
compiled up the openvpn service, however it the helper program just
crashed for me when using it.
The attached patch fixes the crash - it appears as though I don't have a
ptp address so it was crashing when trying to convert a null string to
an ip address.
Crispin
Index: nm-openvpn-service-openvpn-helper.c
===
RCS file: /cvs/gnome/NetworkManager/vpn-daemons/openvpn/src/nm-openvpn-service-openvpn-helper.c,v
retrieving revision 1.6
diff -u -u -8 -p -r1.6 nm-openvpn-service-openvpn-helper.c
--- nm-openvpn-service-openvpn-helper.c 16 Jan 2006 22:58:12 - 1.6
+++ nm-openvpn-service-openvpn-helper.c 29 Mar 2006 22:06:49 -
@@ -170,17 +170,17 @@ send_config_info (DBusConnection *con,
}
if (! ipstr_to_uint32 (str_ip4_address, uint_ip4_address) ) {
nm_warning (nm-openvpn-service-openvpn-helper didn't receive a valid Internal IP4 Address from openvpn.);
send_config_error (con, IP4 Address);
goto out;
}
- if (! ipstr_to_uint32 (str_ip4_ptpaddr, uint_ip4_ptpaddr) ) {
+ if (str_ip4_ptpaddr ! ipstr_to_uint32 (str_ip4_ptpaddr, uint_ip4_ptpaddr) ) {
nm_warning (nm-openvpn-service-openvpn-helper didn't receive a valid PtP IP4 Address from openvpn.);
send_config_error (con, IP4 PtP Address);
goto out;
}
if (strlen (str_ip4_netmask) 0) {
ipstr_to_uint32 (str_ip4_netmask, uint_ip4_netmask);
}
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Will it work under Fedora Core 5?
On 3/29/06, Peter Jones [EMAIL PROTECTED] wrote: On Wed, 2006-03-29 at 07:53 +0200, Trond Husø wrote: Hi list, Fedora Core 5 has just been released, and I might concider upgrading from FC4. But before I do, I need to know if some of my favorite programs works. One of these are Network Manager. So: Does it work under FC5? We ship it and it works. It's not started by default, nor is nm-applet running by default. -- Peter ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list 2 minute wireless installed ipw2200 FW from source forge rmmod ipw2200 modprobe ipw2200 started NM Connect to my AP Here is the directions I wrote for others http://easylinux.info/wiki/Fedora_fc5#how_to_get_wireless_working_Intel_IPW2200_b.2Cg -- Registered Linux User: #376813 www.fedorajim.homelinux.com ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Will it work under Fedora Core 5?
2 minute wireless installed ipw2200 FW from source forge rmmod ipw2200 modprobe ipw2200 Just curious, what kinda access point is that? WPA-PSK or WPA enterprise? oh and from the instructions on the link: --- mkdir tmp mv ~/Desktop/*-2.4.tgz ~/tmp tar -zxvf ipw2200-fw-2.4.tgz cp * /lib/firmware rmmod ipw2200 modprobe ipw2200 iwconfig --- you mite want to add a cd tmp or two in there before someone copies there home directory to /lib/firmware. Eli ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Question on NetworkManager
Hello all, I been trying to understand how NetworkManager work. Here are my status on my laptop. Dell XPS M140 (Laptop)Intel Pentium M Processor 750 (1.86GHz/2MB Cache/533MHz FSB)Genuine Windows XP Media Center Edition 2005 1GB Shared DDR2 SDRAM 2 Dimms100GB 5400rpm Hard Drive Integrated Intel Graphics Media Accelerator 900 Intel Corporation Pro/Wireless 2200BG (rev 05) Running FC4 Kernel - 2.6.15-1.1833_FC4NetworkManager NetworkManager-0.5.1-1.FC4.4NetworkManager-gnome-0.5.1-1.FC4.4I also have the most current drivers and firmware for my wireless card ipw2200-firmware-2.4-7.atipw2200-kmdl-2.6.15-1.1833_FC4-1.1.0-40.rhfc4.atipw2200-1.1.0-40.rhfc4.atieee80211-kmdl-2.6.15-1.1833_FC4-1.1.12-9.rhfc4.atI did iwconfig and got this. lo no wireless extensions.eth0 no wireless extensions.eth1 radio off ESSID:off/any Nickname:localhost.localdomainMode:Managed Channel:0 Access Point: 00:00:00:00:00:00Bit Rate=0 kb/s Tx-Power=off Retry limit:7 RTS thr:off Fragment thr:offEncryption key:offPower Management:offLink Quality:0 Signal level:0 Noise level:0Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0Tx excessive retries:0 Invalid misc:179 MisItsed beacon:0 sit0 no wireless extensions.I then did a ALT + F2 and type in NetworkManagerInfoRight when I ran that I seen a icon appear on the top right hand corner it looks like a cord or something.. I have attach a picture of it. It's right next to the icon that is crossed out. Can you tell me what that is? When I right click on it I see Wireless Enable and it's checked. Can you tell me what I'm doing wrong? From reading things around the board I should be seeing bars not a cord... one thing though I have my cat 5 cable plug in right now I don't know if that makes a difference. Once I disconnect the cat 5 cable it's gets crossed out. Any kind of help would be nice or instrustion for FC4[Malachai] http://forums.fedoraforum.org/attachment.php?attachmentid=7610 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Question on NetworkManager
Hello ;-) wrote: Hello all, I been trying to understand how NetworkManager work. Here are my status on my laptop. Running FC4 Kernel - 2.6.15-1.1833_FC4 NetworkManager NetworkManager-0.5.1-1.FC4.4 NetworkManager-gnome-0.5.1-1.FC4.4 I did iwconfig and got this. eth1 radio off ESSID:off/any Nickname:localhost.localdomain Mode:Managed Channel:0 Access Point: 00:00:00:00:00:00 Bit Rate=0 kb/s Tx-Power=off Retry limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:179 MisItsed beacon:0 This looks good. The driver seems to be working ok. When I right click on it I see Wireless Enable and it's checked. Not sure about this. Is your wireless card enabled? Can you tell me what I'm doing wrong? From reading things around the board I should be seeing bars not a cord... one thing though I have my cat 5 cable plug in right now I don't know if that makes a difference. Once I disconnect the cat 5 cable it's gets crossed out. Unplug the wired connection. Click the NetworkManager icon and select Create New Wireless Network. Enter the details for your Access Point. All being well it should connect. Plug the wired connection back in to swap back to it. Simple. Have fun. Rob ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Will it work under Fedora Core 5?
On 3/29/06, Eli Criffield [EMAIL PROTECTED] wrote: 2 minute wireless installed ipw2200 FW from source forge rmmod ipw2200 modprobe ipw2200 Just curious, what kinda access point is that? WPA-PSK or WPA enterprise? oh and from the instructions on the link: --- mkdir tmp mv ~/Desktop/*-2.4.tgz ~/tmp tar -zxvf ipw2200-fw-2.4.tgz cp * /lib/firmware rmmod ipw2200 modprobe ipw2200 iwconfig --- you mite want to add a cd tmp or two in there before someone copies there home directory to /lib/firmware. Eli Thanks ! fixed it -- Registered Linux User: #376813 www.fedorajim.homelinux.com ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
change the gnome keyring manager password
as the title states... How can I change the gnome keyring manager password ?? -- Registered Linux User: #376813 www.fedorajim.homelinux.com ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: change the gnome keyring manager password
And how do you set it to have no password ? On 3/29/06, jim lawrence [EMAIL PROTECTED] wrote: as the title states... How can I change the gnome keyring manager password ?? -- Registered Linux User: #376813 www.fedorajim.homelinux.com ___ 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
current cvs errors on compile
I was able to compile older CVS versions, mainly the version Taged D2006.03.03.15.00.00 with Robert's patch for working with madwifi (and other cards). But with ubuntu dapper updated today (03/29/06) I get this error on compile. gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../.. -I../../include -I../../utils -I../../src -I../../src/named-manager -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DDBUS_VERSION_MAJOR=0 -DDBUS_VERSION_MINOR=60 -DDBUS_VERSION_MICRO=0 -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/hal -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -g -Wall -DDBUS_API_SUBJECT_TO_CHANGE -DG_DISABLE_DEPRECATED -DBINDIR=\/usr/bin\ -DDATADIR=\/usr/share\ -DSYSCONFDIR=\/etc\ -Wall -Werror -std=gnu89 -g -O2 -Wshadow -Wmissing-declarations -Wmissing-prototypes -Wdeclaration-after-statement -Wfloat-equal -Wno-unused-parameter -Wno-sign-compare -MT libvpn_manager_la-nm-vpn-connection.lo -MD -MP -MF .deps/libvpn_manager_la-nm-vpn-connection.Tpo -c nm-vpn-connection.c -fPIC -DPIC -o .libs/libvpn_manager_la-nm-vpn-connection.o cc1: warnings being treated as errors In file included from ../../src/NetworkManagerMain.h:28, from ../../src/NetworkManagerDbusUtils.h:31, from nm-dbus-vpn.h:25, from nm-vpn-connection.c:25: /usr/include/hal/libhal.h:309: warning: declaration of 'index' shadows a global declaration /usr/include/string.h:304: warning: shadowed declaration is here make[3]: *** [libvpn_manager_la-nm-vpn-connection.lo] Error 1 make[3]: Leaving directory `/home/ecriffield/wpa/NetworkManager/src/vpn-manager'make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/ecriffield/wpa/NetworkManager/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/ecriffield/wpa/NetworkManager' make: *** [all] Error 2 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
cooperative scanning patch
Hi,
Here's a reworked patch that makes use of the netlink/wireless event
stuff from about a month ago. It's got a few features:
* Notices driver-provided scan completion events and pulls from them
* Uses wpa_supplicant for scanning when a wireless connection is active
* Works around older drivers that don't send scan completion events
* Doesn't block waiting for scan results
Please test it out (against HEAD) and see if it works for you.
I've noticed one fairly large issue though... wpa_supplicant seems to
get its link state confused and doesn't reconnect. I don't know if this
is due to the driver not sending reconnect events or whether
wpa_supplicant is just dumb. It doesn't appear that wpa_supplicant has
much special logic to 'fake' a connection through a scan, which sucks
for us. More investigation is certainly needed.
Dan
Index: src/nm-device-802-11-wireless.c
===
RCS file: /cvs/gnome/NetworkManager/src/nm-device-802-11-wireless.c,v
retrieving revision 1.66
diff -u -r1.66 nm-device-802-11-wireless.c
--- src/nm-device-802-11-wireless.c 8 Mar 2006 14:45:14 - 1.66
+++ src/nm-device-802-11-wireless.c 30 Mar 2006 04:12:11 -
@@ -73,10 +73,12 @@
gint8 num_freqs;
double freqs[IW_MAX_FREQUENCIES];
- GMutex * scan_mutex;
+ gboolean scanning;
NMAccessPointList * ap_list;
guint8 scan_interval; /* seconds */
guint32 last_scan;
+ GSource * scan_timeout;
+ GSource * pending_scan;
struct _Supplicant supplicant;
@@ -97,25 +99,21 @@
guint32 results_len;
} NMWirelessScanResults;
-typedef struct
-{
- NMDevice80211Wireless * dev;
- gboolean force;
-} NMWirelessScanCB;
-
static void nm_device_802_11_wireless_ap_list_clear (NMDevice80211Wireless *self);
static gboolean nm_device_802_11_wireless_scan (gpointer user_data);
+static void cancel_scan_results_timeout (NMDevice80211Wireless *self);
+
+static void cancel_pending_scan (NMDevice80211Wireless *self);
+
+static void request_and_convert_scan_results (NMDevice80211Wireless *self);
+
static gboolean process_scan_results (NMDevice80211Wireless *dev,
const guint8 *res_buf,
guint32 res_buf_len);
-
-static gboolean get_scan_results (NMDevice80211Wireless *dev,
- NMSock *sk,
- guint8 **out_res_buf,
- guint32 *data_len);
+static void schedule_scan (NMDevice80211Wireless *self);
static int wireless_qual_to_percent (const struct iw_quality *qual,
const struct iw_quality *max_qual,
@@ -140,7 +138,7 @@
char *data,
int data_len,
NMDevice80211Wireless *self);
-
+
static guint nm_wireless_scan_interval_to_seconds (NMWirelessScanInterval interval)
{
guint seconds;
@@ -263,9 +261,7 @@
NMSock *sk;
NmNetlinkMonitor * monitor;
- self-priv-scan_mutex = g_mutex_new ();
- nm_register_mutex_desc (self-priv-scan_mutex, Scan Mutex);
-
+ self-priv-scanning = FALSE;
self-priv-ap_list = nm_ap_list_new (NETWORK_TYPE_DEVICE);
app_data = nm_device_get_app_data (NM_DEVICE (self));
@@ -395,7 +391,10 @@
}
break;
case SIOCGIWSCAN:
-/* Got some scan results */
+nm_info ((%s) got scan results wireless event., nm_device_get_iface (NM_DEVICE (self)));
+cancel_scan_results_timeout (self);
+request_and_convert_scan_results (self);
+schedule_scan (self);
break;
}
pos += iwe-len;
@@ -475,16 +474,11 @@
/* Start the scanning timeout for devices that can do scanning */
if (nm_device_get_capabilities (dev) NM_DEVICE_CAP_WIRELESS_SCAN)
{
- NMWirelessScanCB * scan_cb;
-
- scan_cb = g_malloc0 (sizeof (NMWirelessScanCB));
- scan_cb-dev = self;
- scan_cb-force = TRUE;
-
- source = g_idle_source_new ();
- g_source_set_callback (source, nm_device_802_11_wireless_scan, scan_cb, NULL);
- source_id = g_source_attach (source, nm_device_get_main_context (dev));
- g_source_unref (source);
+ self-priv-pending_scan = g_idle_source_new ();
+ g_source_set_callback (self-priv-pending_scan,
+nm_device_802_11_wireless_scan, self, NULL);
+ source_id = g_source_attach (self-priv-pending_scan,
+nm_device_get_main_context (dev));
}
/* Peridoically update link status and signal strength */
@@ -616,8 +610,11 @@
{
gboolean have_link = FALSE;
- /* Checking hardware's ESSID during a scan is doesn't work. */
- nm_lock_mutex (self-priv-scan_mutex, __func__);
+ /* Fake a link if we're scanning, we'll drop it later
+ * if it's really dead.
+ */
+ if (self-priv-scanning)
+ return TRUE;
if (is_associated (self))
{
@@ -631,8 +628,6 @@
}
}
- nm_unlock_mutex
Re: current cvs errors on compile
On Wed, 2006-03-29 at 22:24 -0600, Eli Criffield wrote: I was able to compile older CVS versions, mainly the version Taged D2006.03.03.15.00.00 with Robert's patch for working with madwifi (and other cards). But with ubuntu dapper updated today (03/29/06) I get this error on compile. gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../.. -I../../include -I../../utils -I../../src -I../../src/named-manager -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DDBUS_VERSION_MAJOR=0 -DDBUS_VERSION_MINOR=60 -DDBUS_VERSION_MICRO=0 -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/hal -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -g -Wall -DDBUS_API_SUBJECT_TO_CHANGE -DG_DISABLE_DEPRECATED -DBINDIR=\/usr/bin\ -DDATADIR=\/usr/share\ -DSYSCONFDIR=\/etc\ -Wall -Werror -std=gnu89 -g -O2 -Wshadow -Wmissing-declarations -Wmissing-prototypes -Wdeclaration-after-statement -Wfloat-equal -Wno-unused-parameter -Wno-sign-compare -MT libvpn_manager_la-nm-vpn-connection.lo -MD -MP -MF .deps/libvpn_manager_la-nm-vpn-connection.Tpo -c nm-vpn-connection.c -fPIC -DPIC -o .libs/libvpn_manager_la-nm-vpn-connection.o cc1: warnings being treated as errors In file included from ../../src/NetworkManagerMain.h:28, from ../../src/NetworkManagerDbusUtils.h:31, from nm-dbus-vpn.h:25, from nm-vpn-connection.c:25: /usr/include/hal/libhal.h:309: warning: declaration of 'index' shadows a global declaration /usr/include/string.h:304: warning: shadowed declaration is here make[3]: *** [libvpn_manager_la-nm-vpn-connection.lo] Error 1 make[3]: Leaving directory `/home/ecriffield/wpa/NetworkManager/src/vpn-manager'make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/ecriffield/wpa/NetworkManager/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/ecriffield/wpa/NetworkManager' make: *** [all] Error 2 Needs to be fixed in your distribution's copy of HAL... Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: What exactly are the aims of NM?
On Wed, 2006-03-29 at 13:53 +0100, Timothy Murphy wrote: I wonder if the aims and hopes of the NM developers are documented anywhere? Various places, including the NM website under Developers/Design Goals, and in various emails to this mailing list. For example, from March 12, 2006: As we continue to develop NetworkManager, we're going to build it out to support more use cases. NM was originally developed for just one targetted use case; that of laptop and mobile users. The goal is to build to support more cases, but still make laptop and mobile cases drop-dead simple. Is it hoped that it will work with all wireless devices for which there is a Linux driver (including ndiswrapper)? Yes, if ndiswrapper supports WEXT, which it appears to. The latest version in CVS appears to support WEXT-19 for WPA, which is quite nice. It means we don't need to special-case ndiswrapper. Or will it only work for cards, etc, with certain properties - eg ability to go into Monitor mode - which are not actually necessary in order to run under Linux? Monitor mode is not needed. Any card/driver that supports WEXT should work; but note that many drivers have little quirks that have to be fixed up along the way before they will _reliably_ work with wpa_supplicant and NetworkManager. For these we need debug logs. I have an Orinoco classic Gold PCMCIA card (in fact several of them, including ones in USB and PCI adapters), and I have never been able to get NM to work with them. That should be supported, though in recent kernels I've had problems with that card. Robert Love posted a patch to wpa_supplicant a bit ago that should have fixed that little incompatibility. Note that you have to make sure that only _one_ driver out of hostap/orinoco binds to your card... if both bind to it, nothing good happens. That's a Linux issue though, and not unique to NM. Put blacklist hostap_cs in your /etc/modprobe.d/blacklist file. Also is it intended that NM should work with KDE? Yes, NM itself is desktop-agnostic. If you want a native KDE applet, look for KNetworkManager. It is not yet packaged in Fedora. As you've described your setup (FC5 + orinoco + KDE), it appears that NM should work for you in principle. There may, however, be bugs that we need to work through. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
no WEP networks
Hello, I just installed FC5 with NetworkManager 0.6 It shows and allows me to connect to my unsecured network. But it does not even list the 5 other secured networks around me that my other machines can see and connect to. Maybe it does not show encrypted networks? Any ideas? -Jono ___Get the FREE email that has everyone talking at http://www.mail2world.com Unlimited Email Storage POP3 Calendar SMS Translator Much More!___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
