Re: Wireless silently disconnects?
if (nm_device_802_11_wireless_get_mode (self) == mode)
return TRUE;
This is true, but if nm_device_802_11_wireless_get_mode
(self) is IW_MODE_AUTO and mode is IW_MODE_INFRA, condition is
false because device mode is changed.
This patch work fine for me and all changes are needed
--- NetworkManager-0.5.2/src/nm-device-802-11-wireless.c
2006-02-21 11:39:33.0 +0100
+++ /root/Desktop/nm-device-802-11-wireless.c 2006-03-03
13:55:08.0 +0100
@@ -1808,7 +1808,10 @@
/* Must be in infrastructure mode during scan, otherwise
we don't get a full
* list of scan results. Scanning doesn't work well in
Ad-Hoc mode :(
*/
- nm_device_802_11_wireless_set_mode (self,
IW_MODE_INFRA);
+
+ if (nm_device_802_11_wireless_get_mode (self) ==
IW_MODE_ADHOC) {
+ nm_device_802_11_wireless_set_mode (self,
IW_MODE_INFRA);
+ }
nm_device_802_11_wireless_set_frequency (self, 0);
wrq.u.data.pointer = NULL;
@@ -2282,13 +2285,27 @@
const char *iface = nm_device_get_iface (NM_DEVICE (self));
gbooleansuccess = FALSE;
int tries = 0;
+ char * driver;
if (!(ctrl = wpa_ctrl_open (WPA_SUPPLICANT_GLOBAL_SOCKET,
NM_RUN_DIR)))
goto exit;
+ if (!strcmp (nm_device_get_driver (NM_DEVICE (self)),
ndiswrapper)) {
+ driver= g_malloc(sizeof(char)*(strlen(ndiswrapper)+1));
+ driver= strcpy(driver, ndiswrapper);
+ }
+ else if (!strcmp (nm_device_get_driver (NM_DEVICE (self)),
ath_pci)) {
+ driver= g_malloc(sizeof(char)*(strlen(madwifi)+1));
+ driver= strcpy(driver, madwifi);
+ }
+ else {
+ driver= g_malloc(sizeof(char)*(strlen(wext)+1));
+ driver= strcpy(driver, wext);
+ }
+
/* wpa_cli -g/var/run/wpa_supplicant-global interface_add
eth1 wext /var/run/wpa_supplicant */
if (!nm_utils_supplicant_request_with_check (ctrl, OK,
__func__, NULL,
- INTERFACE_ADD %s\t\twext\t
WPA_SUPPLICANT_CONTROL_SOCKET
\t, iface))
+ INTERFACE_ADD %s\t\t%s\t WPA_SUPPLICANT_CONTROL_SOCKET
\t, iface, driver))
goto exit;
wpa_ctrl_close (ctrl);
@@ -2308,6 +2325,7 @@
success = TRUE;
exit:
+ g_free (driver);
return success;
}
On Thu, 2006-03-02 at 10:15 -0500, Dan Williams wrote:
On Thu, 2006-03-02 at 10:03 -0500, Robert Love wrote:
On Thu, 2006-03-02 at 09:49 -0500, Dan Williams wrote:
So which hunk of this patch seems to fix the problem?
The first part
for the set_mode, or the second part passing the
ndiswrapper driver to
wpa_supplicant?
The first hunk. I just checked a variant into CVS.
The reason this hunk exists is really for just adhoc. Same
for the
frequency set to 0, I think. If you want to move both of
them into
if (orig_mode == IW_MODE_ADHOC)
block just above, that would be fine. I initially observed
with prism54
cards that adhoc mode pretty much didn't work at all unless
the mode was
infrastructure and the bitrate was unlocked.
Unfortunately, the bitrate
had to be locked during normal adhoc operation, otherwise
you never got
any traffic. Now that our custom adhoc setup code is gone,
I think we
can remove that bitrate unlock line.
Note that NM only supports two modes right now, INFRA and
ADHOC. The
other mode is MASTER, and of course we don't do that yet.
On second look, your commit is fine. I forgot that if
wpa_supplicant
sets up the stuff, we need to switch it back anyway.
However, there's another problem... The code for set_mode
already
checks to see what the mode was, and if you request to set
the mode that
the card is in already, it just returns without doing anything:
if (nm_device_802_11_wireless_get_mode (self) == mode)
return TRUE;
So I'm not sure what your commit fixes? It's more likely
that the
driver here dislikes the frequency set, and that we should
only unlock
the frequency when the card is in ad-hoc mode.
Candidate patch attached, does this fix the issue?
Dan
nm-ndiswrapper2.patch
Description: application/data
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
small patch for DBUS 0.60
Hi,
The recent change to libnm_glib.c to fix various problems with DBUS
calls have broken things for people with older versions of DBUS. In
particular, the function dbus_bus_get_private() seems to have been
introduced in DBUS 0.60, and so doesnt work for people with older
versions (I have a version of FC4, updated to DBUS 0.50 via the nrpms
repository at www.nrpms.net). There is some configurey magic to work
out the DBUS version, and that allows DBUS 0.50, but the build then
fails.
As I see it (as a very limited hacker) there are 2 ways round this.
1) Only allow DBUS = 0.60
2) Check the DBUS version, and use the appropriate DBUS function. The
attached patch does this, and is sent on a strictly works-for-me basis.
Cheers,
James.
patch below - apologies in advance for the line wrapping ...
diff -rup NetworkManager-0.5.1.cvs20060302/gnome/libnm_glib/libnm_glib.c
NetworkManager-0.5.1/gnome/libnm_glib/libnm_glib.c
--- NetworkManager-0.5.1.cvs20060302/gnome/libnm_glib/libnm_glib.c
2006-02-22 15:52:30.0 +
+++ NetworkManager-0.5.1/gnome/libnm_glib/libnm_glib.c 2006-03-03
12:35:54.0 +
@@ -295,7 +295,11 @@ libnm_glib_dbus_init (gpointer *user_dat
DBusErrorerror;
dbus_error_init (error);
+#if (DBUS_VERSION_MAJOR == 0) (DBUS_VERSION_MINOR = 60)
connection = dbus_bus_get_private (DBUS_BUS_SYSTEM, error);
+#else
+ connection = dbus_bus_get (DBUS_BUS_SYSTEM, error);
+#endif
if (dbus_error_is_set (error))
{
fprintf (stderr, %s: error, %s raised:\n %s\n\n,
__func__, error.name, error.message);
James Begley
--
Telephone +354-575-2039
Marine Research Institute,
Skulagata 4, P.O. Box 1390,
121 Reykjavik, Iceland.
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
spanish translation
Added translation of notify messages, Where have I to send it so that it is including? P.D. - My english is very bad but I translate english to spanish good. es.po Description: application/data ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Wireless silently disconnects?
On Fri, 2006-03-03 at 13:56 +0100, [EMAIL PROTECTED] wrote:
This patch work fine for me and all changes are needed
Alright, thanks.
Dan, what do you think? It seems the real issue is that ndiswrapper
doesn't want to be out of IW_MODE_AUTO, not that the set_mode()
operation itself is costly.
+ if (!strcmp (nm_device_get_driver (NM_DEVICE (self)),
ndiswrapper)) {
+ driver= g_malloc(sizeof(char)*(strlen(ndiswrapper)+1));
+ driver= strcpy(driver, ndiswrapper);
+ }
+ else if (!strcmp (nm_device_get_driver (NM_DEVICE (self)),
ath_pci)) {
+ driver= g_malloc(sizeof(char)*(strlen(madwifi)+1));
+ driver= strcpy(driver, madwifi);
+ }
+ else {
+ driver= g_malloc(sizeof(char)*(strlen(wext)+1));
+ driver= strcpy(driver, wext);
+ }
+
aj2r, just as an FYI, you don't need dynamic allocations here.
const char *driver = madwifi;
is sufficient. As it stands, this code allocates both a static
character array and a dynamic one. Just a tip ;-)
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Wireless silently disconnects?
aj2r, just as an FYI, you don't need dynamic allocations here. const char *driver = madwifi; is sufficient. As it stands, this code allocates both a static character array and a dynamic one. Just a tip ;-) Robert Love Ok, thanks. But later you don't make driver=ndiswrapper because you are using non reserved memory, no? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Wireless silently disconnects?
On Fri, 2006-03-03 at 16:17 +0100, [EMAIL PROTECTED] wrote: Ok, thanks. But later you don't make driver=ndiswrapper because you are using non reserved memory, no? I am not sure what you mean? This is okay (and preferred): const char *driver; if (foo) driver = cat; else if (bar) driver = dog; else driver = fox; And you do not free it. Robert Love ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
wireless driver workarounds
Attached patch is a collection of workarounds for madwifi, orinoco, and
ndiswrapper that I have worked on or that have been posted to this list.
We are probably not going to merge any of this. If NM does not work for
you but works with this patch, we would like to know.
Robert Love
Index: src/nm-device-802-11-wireless.c
===
RCS file: /cvs/gnome/NetworkManager/src/nm-device-802-11-wireless.c,v
retrieving revision 1.59
diff -u -r1.59 nm-device-802-11-wireless.c
--- src/nm-device-802-11-wireless.c 2 Mar 2006 23:01:33 - 1.59
+++ src/nm-device-802-11-wireless.c 3 Mar 2006 15:19:13 -
@@ -1834,14 +1834,16 @@
/* Must be in infrastructure mode during scan, otherwise we don't get a full
* list of scan results. Scanning doesn't work well in Ad-Hoc mode :(
- */
- nm_device_802_11_wireless_set_mode (self, IW_MODE_INFRA);
-
- /* We only unlock the frequency if the card is in adhoc mode, in case it is
- * a costly operation for the driver.
+ *
+ * We only set the mode and unlock the frequency if the card is in adhoc mode,
+ * in case doing so is a costly operation for the driver or the driver prefers
+ * IW_MODE_AUTO.
*/
if (orig_mode == IW_MODE_ADHOC)
+ {
+nm_device_802_11_wireless_set_mode (self, IW_MODE_INFRA);
nm_device_802_11_wireless_set_frequency (self, 0);
+ }
wrq.u.data.pointer = NULL;
wrq.u.data.flags = 0;
@@ -2415,13 +2417,28 @@
const char * iface = nm_device_get_iface (NM_DEVICE (self));
gboolean success = FALSE;
inttries = 0;
+ const char * wpa_driver;
+ const char * kernel_driver;
if (!(ctrl = wpa_ctrl_open (WPA_SUPPLICANT_GLOBAL_SOCKET, NM_RUN_DIR)))
goto exit;
+ kernel_driver = nm_device_get_driver (NM_DEVICE (self));
+
+ /*
+ * We want to work with the generic wext wpa_supplicant driver, but some kernel drivers
+ * are just utter junk. For those losers, we use a specific wpa_supplicant driver.
+ */
+ if (!strcmp (kernel_driver, ath_pci))
+ wpa_driver = madwifi;
+ else if (!strcmp (kernel_driver, ndiswrapper))
+ wpa_driver = ndiswrapper;
+ else
+ wpa_driver = wext;
+
/* wpa_cli -g/var/run/wpa_supplicant-global interface_add eth1 wext /var/run/wpa_supplicant */
if (!nm_utils_supplicant_request_with_check (ctrl, OK, __func__, NULL,
- INTERFACE_ADD %s\t\twext\t WPA_SUPPLICANT_CONTROL_SOCKET \t, iface))
+ INTERFACE_ADD %s\t\t%s\t WPA_SUPPLICANT_CONTROL_SOCKET \t, iface, wpa_driver))
goto exit;
wpa_ctrl_close (ctrl);
@@ -2457,7 +2474,8 @@
struct wpa_ctrl * ctrl;
gboolean user_created;
char * hex_essid;
- char * ap_scan = AP_SCAN 1;
+ const char * ap_scan;
+ const char * kernel_driver;
g_return_val_if_fail (self != NULL, FALSE);
g_return_val_if_fail (req != NULL, FALSE);
@@ -2468,14 +2486,25 @@
ctrl = self-priv-supplicant.ctrl;
g_assert (ctrl);
- /* Ad-Hoc and non-broadcasting networks need AP_SCAN 2 */
user_created = nm_ap_get_user_created (ap);
- if (!nm_ap_get_broadcast (ap) || user_created)
+ kernel_driver = nm_device_get_driver (NM_DEVICE (self));
+
+ /*
+ * We want to use AP_SCAN 1, which tells wpa_supplicant to perform scanning. This seems
+ * to work better with some drivers. But we want AP_SCAN 2, telling wpa_supplicant that
+ * we will do our own scanning, if
+ *
+ * - The driver is orinoco_cs. It chokes on AP_SCAN 1.
+ * - The AP is non-broadcast or Ad-Hoc. Unless the driver is madwifi.
+ */
+ if (!strcmp (kernel_driver, orinoco_cs))
ap_scan = AP_SCAN 2;
+ else if ((!nm_ap_get_broadcast (ap) || user_created) strcmp (kernel_driver, ath_pci))
+ ap_scan = AP_SCAN 2;
+ else
+ ap_scan = AP_SCAN 1;
- /* Tell wpa_supplicant that we'll do the scanning */
- if (!nm_utils_supplicant_request_with_check (ctrl, OK, __func__, NULL,
- ap_scan))
+ if (!nm_utils_supplicant_request_with_check (ctrl, OK, __func__, NULL, ap_scan))
goto out;
/* Standard network setup info */
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: wireless driver workarounds
Modified patch to work with gentopia-overlay, and some small change nmwirelessdriverworkaroundsrml-aj2r.patch Description: application/data ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: small patch for DBUS 0.60
On Fri, 2006-03-03 at 13:33 +, James Begley wrote: As I see it (as a very limited hacker) there are 2 ways round this. 1) Only allow DBUS = 0.60 2) Check the DBUS version, and use the appropriate DBUS function. The attached patch does this, and is sent on a strictly works-for-me basis. I actually would prefer to just require DBUS 0.60, although your patch is a viable option, too. By and by, I don't see where we require 0.50, though. Dan, opinions? Robert Love ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: wireless driver workarounds
Once upon a time, Robert Love [EMAIL PROTECTED] said: Attached patch is a collection of workarounds for madwifi, orinoco, and ndiswrapper that I have worked on or that have been posted to this list. We are probably not going to merge any of this. If NM does not work for you but works with this patch, we would like to know. I'm using: - Fedora rawhide (up to date as of today) - the latest madwifi-ng snapshot plus the patch from this list to set the capabilities for WPA - NetworkManager-0.5.1-18.cvs.20060302 plus your patch WPA is not working. I had WPA working a couple of weeks ago, but updating something broke it and it hasn't worked since. -- Chris Adams [EMAIL PROTECTED] Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: small patch for DBUS 0.60
On Fri, 2006-03-03 at 12:21 -0500, Robert Love wrote: On Fri, 2006-03-03 at 13:33 +, James Begley wrote: As I see it (as a very limited hacker) there are 2 ways round this. 1) Only allow DBUS = 0.60 2) Check the DBUS version, and use the appropriate DBUS function. The attached patch does this, and is sent on a strictly works-for-me basis. I actually would prefer to just require DBUS 0.60, although your patch is a viable option, too. By and by, I don't see where we require 0.50, though. Dan, opinions? Not particularly, but I think I'd rather require dbus 0.60 too. While the patch does preserve the old behavior, the old behavior was clearly broken. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: wireless driver workarounds
On Fri, 2006-03-03 at 12:04 -0600, Chris Adams wrote: Once upon a time, Robert Love [EMAIL PROTECTED] said: Attached patch is a collection of workarounds for madwifi, orinoco, and ndiswrapper that I have worked on or that have been posted to this list. We are probably not going to merge any of this. If NM does not work for you but works with this patch, we would like to know. I'm using: - Fedora rawhide (up to date as of today) - the latest madwifi-ng snapshot plus the patch from this list to set the capabilities for WPA - NetworkManager-0.5.1-18.cvs.20060302 plus your patch WPA is not working. I had WPA working a couple of weeks ago, but updating something broke it and it hasn't worked since. Any chance you could whip up a wpa_supplicant config file for your network situation, and use wpa_supplicant standalone (without NetworkManager)? Make sure to use -ddd to get the maximum logging information. the command should go something like this: /usr/sbin/wpa_supplicant -ddd -iath0 -c/etc/wpa_supplicant.conf -Dmadwifi If that fails, then it's 95% likely a madwifi-ng bug and something they broke recently. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: small patch for DBUS 0.60
On Fri, 2006-03-03 at 13:31 -0500, Dan Williams wrote: On Fri, 2006-03-03 at 12:21 -0500, Robert Love wrote: On Fri, 2006-03-03 at 13:33 +, James Begley wrote: As I see it (as a very limited hacker) there are 2 ways round this. 1) Only allow DBUS = 0.60 2) Check the DBUS version, and use the appropriate DBUS function. The attached patch does this, and is sent on a strictly works-for-me basis. I actually would prefer to just require DBUS 0.60, although your patch is a viable option, too. By and by, I don't see where we require 0.50, though. Dan, opinions? Not particularly, but I think I'd rather require dbus 0.60 too. While the patch does preserve the old behavior, the old behavior was clearly broken. Fair enough. The only reason I hacked this patch together was to delay/avoid the need to upgrade DBUS to version 0.6x, since a simple rpmbuild --rebuild of the rawhide DBUS source rpm fails on my machine. I figured it would be easier, and less pain in the short term, to change NM to use the older version of DBUS, than figure out why DBUS doesnt compile. Cheers, James. James Begley -- Telephone +354-575-2039 Marine Research Institute, Skulagata 4, P.O. Box 1390, 121 Reykjavik, Iceland. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: small patch for DBUS 0.60
On Fri, 2006-03-03 at 13:31 -0500, Dan Williams wrote: Not particularly, but I think I'd rather require dbus 0.60 too. While the patch does preserve the old behavior, the old behavior was clearly broken. I bumped our requirement from 0.22 (!) to 0.60. Robert Love ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: wireless driver workarounds
Robert, That patch allowed me to use NetworkManager with MadWifi! I am running the following: wpa_supplicant 0.5.1 CVS Checkout 03/03/06 Madwifi-ng SVN 1458 patched with Dan's patch NetworkManager CVS from 03/03/06 with your patches Previously I could never get my madwifi card to connect. The past month of the Mad-wifi dev list and their bug tracker show no issues or discussions related to Network-Manager. Should I post a bug or have they already been contacted about Dan's patch and WEXT support and have decided to not implement it? Thanks, Darren On 3/3/06, Robert Love [EMAIL PROTECTED] wrote: Attached patch is a collection of workarounds for madwifi, orinoco, and ndiswrapper that I have worked on or that have been posted to this list. We are probably not going to merge any of this. If NM does not work for you but works with this patch, we would like to know. Robert Love ___ 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
Re: wireless driver workarounds
* Robert Love [EMAIL PROTECTED] [2006-03-03 11:00]: Attached patch is a collection of workarounds for madwifi, orinoco, and ndiswrapper that I have worked on or that have been posted to this list. We are probably not going to merge any of this. If NM does not work for you but works with this patch, we would like to know. Robert Love Still works for me. -Brian ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
vpnc and nm-applet
A couple of things I've noticed: Under KDE nm-applets icon isn't always fully initilized. Often times it's there but not there. Meaning that a space is being comsumed in the notification area but there's nothing there that responds to clicks. Killing nm-applet and restaring it usually takes care of this. I think I also managed to make it appear once by hiding the panel and the exposing it, but that hasn't been repeatable. Secondly, I got the vpnc plugin to appear to work. The tun device gets created and it has the right IP address. What didn't happen is that the DNS and route information didn't get processed. How can I make that happen? Does NM even try to make use of /etc/vpnc/vpnc-script (or equivilent)? -Brian ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Stop removing localhost from /etc/hosts
On Fri, 2006-03-03 at 21:06 -0500, Neal Becker wrote: Why is nm removing 127.0.0.1 localhost from /etc/hosts? Please don't do that. This causes a lot of problems. What distribution and version? AFAIK, NM doesn't touch /etc/hosts... It would more likely be a dhcp client or distro-specific scripts. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: vpnc and nm-applet
On Fri, 2006-03-03 at 21:20 -0500, Brian Magnuson wrote: A couple of things I've noticed: Under KDE nm-applets icon isn't always fully initilized. Often times it's there but not there. Meaning that a space is being comsumed in the notification area but there's nothing there that responds to clicks. Killing nm-applet and restaring it usually takes care of this. I think I also managed to make it appear once by hiding the panel and the exposing it, but that hasn't been repeatable. Secondly, I got the vpnc plugin to appear to work. The tun device gets created and it has the right IP address. What didn't happen is that the DNS and route information didn't get processed. How can I make that happen? Does NM even try to make use of /etc/vpnc/vpnc-script (or equivilent)? Nope. NM executes nm-vpnc-service, which itself executes vpnc directly. NM tells vpnc to use a different script, nm-vpnc-service-helper, that passes the tunnel's information back to NM. a) run NetworkManager with --no-daemon b) as root, run nm-vpnc-service c) try to connect the vpn d) grab the logs from both NM and nm-vpnc-service and attach them to a mail Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
ANNOUNCE: NetworkManager 0.6 Release
We are pleased to announce the release of NetworkManager 0.6. This is the new stable branch of NetworkManager. Not that there's really been a stable branch before :) NetworkManager is a desktop agnostic network connection manager, targeted mainly at mobile laptop users. It's aim is to make networking painless. More information on the project is available here: http://www.gnome.org/projects/NetworkManager/ --- The NetworkManager Team Notable Improvements * WPA/WPA2 Personal and Enterprise support * Two new VPN services; openvpn and pptp * Better distro interaction * Dial-up support * Bug fixes all around See the NEWS file for a comprehensive list of changes for this and past versions. Requirements * Linux kernel 2.6.12 or higher * dhcdbd (http://people.redhat.com/~jvdias/dhcdbd/) * dbus 0.6 (http://www.freedesktop.org/wiki/Software/dbus) * hal 0.5 or higher (http://www.freedesktop.org/wiki/Software/hal) * wpa_supplicant 0.4.8 or higher (http://hostap.epitest.fi/wpa_supplicant/) * glib 2.6 or higher (http://www.gtk.org/) How To Get It = NetworkManager is available for most Linux distributions in that distribution's native package format. Please check your distribution's software updates for NetworkManager 0.6, and if it's not available, request it. Otherwise, you may get NetworkManager 0.6 from gnome.org CVS using the RELEASE_0_6_0 CVS tag. See more detailed build directions here: http://www.gnome.org/projects/NetworkManager/developers/ What's Next === We anticipate releasing the next version of NetworkManager some time in 2006. We hope to address most, if not all, of the annoyances and most requested features for this next release. The current to-do list is maintained here: http://live.gnome.org/NetworkManagerToDo ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
