Re: NetworkManager 0.7.1 Success with CDC ACM Modem
Hi! > > And now when NetworkManager implements needed > > autodetection bits, everything Just Works(tm)! > > Excellent! Probably due to the modem prober. What exactly > do you mean by "the needed autodetection bits"? Umm, I think I meant the modem prober :-) I was looking for a correct term and noticed "autodetection" improvement in the RPM changelog. Cheers! ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Sierra Modem Problem
Hi, I am having this problem and would like to know what exact text change is needed so that I can add it to the file. Also, I've seen this fix list the location of the file in "etc/hal/fdi/information/modems.fdi" vs "/usr/share/hal/fdi/information/10freedesktop/". Which is correct? Thanks. Message: 4 Date: Tue, 10 Mar 2009 10:08:11 -0700 From: Chetan Karia Subject: Supporting new Sierra CDMA modems. To: networkmanager-l...@gnome..org Message-ID: <521673c40903101008y3634b54cjcbfb73cb47082...@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Hi, I am an employee of Sierra wireless USA. I was testing network manager on Ubuntu 8.10. I found that all Sierra CDMA modems worked well with network manager except our two new products which were not detected by Network Manager. On investigating further I discovered its just matter of adding the Vendor ID and Product ID of our new devices to the file "10-modem.fdi" under the directory "/usr/share/hal/fdi/information/10freedesktop/". Once I edit this file and add the VID/PID's the Network Manager detects the devices and connects to CDMA network. I wanted to know the procedure to officially add the VID/PID's of new Sierra device to 10-modem.fdi file, so that I do not have to edit it manually. Your help will be much appreciated. Thanks, Chetan -- Message: 5 Date: Tue, 10 Mar 2009 18:12:38 +0100 From: Rapha?l Jacquot Subject: Re: Supporting new Sierra CDMA modems. To: networkmanager-list@gnome.org Message-ID: <20090310171238.gf11...@sxpert.org> Content-Type: text/plain; charset=us-ascii On Tue, Mar 10, 2009 at 10:08:11AM -0700, Chetan Karia wrote: > Hi, > > I am an employee of Sierra wireless USA. I was testing network manager > on Ubuntu 8.10. I found that all Sierra CDMA modems worked well with > network manager except our two new products which were not detected by > Network Manager. On investigating further I discovered its just matter > of adding the Vendor ID and Product ID of our new devices to the file > "10-modem.fdi" under the directory > "/usr/share/hal/fdi/information/10freedesktop/". Once I edit this file > and add the VID/PID's the Network Manager detects the devices and > connects to CDMA network. I wanted to know the procedure to officially > add the VID/PID's of new Sierra device to 10-modem.fdi file, so that I > do not have to edit it manually. > > Your help will be much appreciated. you should contact the Udev people linux-hotp...@vger.kernel.org > Thanks, > Chetan > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list -- Message: 6 Date: Tue, 10 Mar 2009 18:50:37 +0100 From: Alexander Sack Subject: Re: Supporting new Sierra CDMA modems. To: Chetan Karia Cc: networkmanager-list@gnome.org Message-ID: <20090310175037.gh29...@jwsdot.com> Content-Type: text/plain; charset=us-ascii Hi, On Tue, Mar 10, 2009 at 10:08:11AM -0700, Chetan Karia wrote: > Hi, > > I am an employee of Sierra wireless USA. I was testing network manager > on Ubuntu 8.10. I found that all Sierra CDMA modems worked well with > network manager except our two new products which were not detected by > Network Manager. On investigating further I discovered its just matter > of adding the Vendor ID and Product ID of our new devices to the file > "10-modem.fdi" under the directory > "/usr/share/hal/fdi/information/10freedesktop/". Once I edit this file > and add the VID/PID's the Network Manager detects the devices and > connects to CDMA network. I wanted to know the procedure to officially > add the VID/PID's of new Sierra device to 10-modem.fdi file, so that I > do not have to edit it manually. Please provide info on the exact pieces required. One way to move foward would be to file a bug with that info against hal-info [1] package in launchpad. We (ubuntu) takes care that info submitted there regularly gets committed upstream. [1] - https://bugs.launchpad.net/ubuntu/+source/hal-info/+filebug - Alexander -- Message: 7 Date: Tue, 10 Mar 2009 14:58:51 -0400 From: Chuck Anderson Subject: Forcing a BSSID, unchecking "Connect automatically" doesn't work To: networkmanager-list@gnome.org Message-ID: <20090310185851.go10...@angus.ind.wpi.edu> Content-Type: text/plain; charset=us-ascii I'm trying to force a specific BSSID (testing 802.11n in fact) but NetworkManager keeps trying to associate to the other BSSID's (APs) on the same ESSID. In fact, it popped up with a dialog to set up the encryption settings, etc. (WPA TLS) because it couldn't use the connection profile that I forced the BSSID on. So I let it create another Auto profile, set up the encryption, and then unchecked the "Connect automatically"...but guess what? It still connects automatically. How do I force NetworkManage
Fw: DBus interface clarification part2
> On Mon, 2009-03-09 at 04:09 -0700, Kevron Rees wrote:
> > > Answering myself, since I got no response here, ActivateConnection
> > > requires
> > that the connection you want to activate has been connected to in the past.
> >
> Am
> > I correct on this? You basically have to get the connection object from
> > the
> > org.freedesktop.NetworkManagerSettings ListConnections() method. From that
> > list, you have to find the specific connection to use. You do so by
> > looking
> in
> > that path and the org.freedesktop.NetworkManagerSettings.Connection
> > interface
> > using the "GetSettings()" method.
> > >
> > > Correct me if i'm wrong, but if this is a new access point, you cannot
> connect
> > to it via dbus? Wouldn't a simpler:
> > >
> > > ActivateConnection(o: device, o: specific_object_to_connect_to)
> >
> > I responded on Saturday:
> >
> > http://mail.gnome.org/archives/networkmanager-list/2009-March/msg00082.html
> >
> > Let me know if you have any further questions!
> >
> > Dan
>
Thanks Dan! I didn't see the reply on Saturday. My mistake. Your example is
very helpful. Is it possible to use a blank path ("/") as the connection if
this is a new connection and no settings are available yet?
Thanks again
Kev
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
force nm to use a connection
hello, I'm looking for info to force nm to use a connection instead of "Auto eth0". I explain : at home I need a static IP, with special DNS, ... So, I created a connection called `home` with those parameters. Works fine when I activated it manually. When I'm outside, I need `auto eth0`. How can I tell nm "when I'm at home, connect me via `home`, even if connect me via `auto eth0` ? I try to pla with "automatic connection" but of course, if I put `home` as auto, and `auto eth0` as no-auto, when I'm outside, `home` is up. And inversement. Thank for show me the way. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager 0.7.1 Success with CDC ACM Modem
On Mon, 2009-03-09 at 15:18 -0700, Daniel Qarras wrote: > Dan, World, > > I'm thrilled to report that after just upgrading to 0.7.0.99-1 on Fedora 10, > NetworkManager is now able to establish connections by using my Nokia 6021 > connected to a laptop with Nokia CA-42 cable - with zero configuration! > "Woo!" :-) > > FWIW, background information: Nokia CA-42 shows up as a CDC ACM modem. The > tricky part was that these kind of cables can support both GSM and CDMA > models. HAL become aware of CDC ACM modems on 2008-05-05: > > http://cgit.freedesktop.org/hal-info/commit/?id=739f2cc5cf151c7454b8573d80a0173787527808 > > And now when NetworkManager implements needed autodetection bits, everything > Just Works(tm)! > > I'm attaching parts of syslog after booting the system while my home wireless > access point was turned off and creating a connection via Nokia CA-42/Nokia > 6021. Excellent! Probably due to the modem prober. What exactly do you mean by "the needed autodetection bits"? Dan > Thanks! > > > > > ___ hal mailing list > h...@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/hal ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Feature request: Blacklist BSSID or MAC address
Our campus wireless network has several dozen access points scattered around campus. From where I sit in my office, I can see about a dozen or so. Frequently, NM (or the driver) selects an AP with a relatively weak signal (to the point of being unusable), even though I sit across the hall from a much stronger one. I don't want to bind the configuration to a single BSSID, because I do move around the campus and I want to be able to connect wherever I am. But I do want to blacklist the weak APs near my office, so I don't have to force reassociation (which seems to require power-cycling my wireless interface). I don't see a way to do that in the pull-down Edit Connections menu. Is it possible to add such a feature? Or should I be asking for something else to deal with this issue? (For example, is it a driver bug?) Thanks. -- Matthew Saltzman Clemson University Math Sciences mjs AT clemson DOT edu http://www.math.clemson.edu/~mjs ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Shutting down specific device
Is there a bit of scripting magic where I can force a specific network device to shut down? We have a device that when it is powered down via external switch, Network Manager handles it but sees a state change to FAILED so it is marked as invalid. I'd like to be able to tell Network Manager that it should be disconnected so it is handled more gracefully. I've started playing with dbus-send but so far can only manage to use the sleep and wake commands successfully. Drew ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Forcing a BSSID, unchecking "Connect automatically" doesn't work
I'm trying to force a specific BSSID (testing 802.11n in fact) but NetworkManager keeps trying to associate to the other BSSID's (APs) on the same ESSID. In fact, it popped up with a dialog to set up the encryption settings, etc. (WPA TLS) because it couldn't use the connection profile that I forced the BSSID on. So I let it create another Auto profile, set up the encryption, and then unchecked the "Connect automatically"...but guess what? It still connects automatically. How do I force NetworkManager to ignore all BSSID's for a specific ESSID, except for the one I want? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Supporting new Sierra CDMA modems.
Hi, On Tue, Mar 10, 2009 at 10:08:11AM -0700, Chetan Karia wrote: > Hi, > > I am an employee of Sierra wireless USA. I was testing network manager > on Ubuntu 8.10. I found that all Sierra CDMA modems worked well with > network manager except our two new products which were not detected by > Network Manager. On investigating further I discovered its just matter > of adding the Vendor ID and Product ID of our new devices to the file > "10-modem.fdi" under the directory > "/usr/share/hal/fdi/information/10freedesktop/". Once I edit this file > and add the VID/PID's the Network Manager detects the devices and > connects to CDMA network. I wanted to know the procedure to officially > add the VID/PID's of new Sierra device to 10-modem.fdi file, so that I > do not have to edit it manually. Please provide info on the exact pieces required. One way to move foward would be to file a bug with that info against hal-info [1] package in launchpad. We (ubuntu) takes care that info submitted there regularly gets committed upstream. [1] - https://bugs.launchpad.net/ubuntu/+source/hal-info/+filebug - Alexander ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Supporting new Sierra CDMA modems.
On Tue, Mar 10, 2009 at 10:08:11AM -0700, Chetan Karia wrote: > Hi, > > I am an employee of Sierra wireless USA. I was testing network manager > on Ubuntu 8.10. I found that all Sierra CDMA modems worked well with > network manager except our two new products which were not detected by > Network Manager. On investigating further I discovered its just matter > of adding the Vendor ID and Product ID of our new devices to the file > "10-modem.fdi" under the directory > "/usr/share/hal/fdi/information/10freedesktop/". Once I edit this file > and add the VID/PID's the Network Manager detects the devices and > connects to CDMA network. I wanted to know the procedure to officially > add the VID/PID's of new Sierra device to 10-modem.fdi file, so that I > do not have to edit it manually. > > Your help will be much appreciated. you should contact the Udev people linux-hotp...@vger.kernel.org > Thanks, > Chetan > ___ > 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
Supporting new Sierra CDMA modems.
Hi, I am an employee of Sierra wireless USA. I was testing network manager on Ubuntu 8.10. I found that all Sierra CDMA modems worked well with network manager except our two new products which were not detected by Network Manager. On investigating further I discovered its just matter of adding the Vendor ID and Product ID of our new devices to the file "10-modem.fdi" under the directory "/usr/share/hal/fdi/information/10freedesktop/". Once I edit this file and add the VID/PID's the Network Manager detects the devices and connects to CDMA network. I wanted to know the procedure to officially add the VID/PID's of new Sierra device to 10-modem.fdi file, so that I do not have to edit it manually. Your help will be much appreciated. Thanks, Chetan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: How to suppress pop-up window when device is inserted ?
--On Tuesday, March 10, 2009 13:00:12 +0100 Christopher Lang wrote: ¦ for example under Ubuntu 8.10, which uses nm-applet, there is a pop-up ¦ whenever a 3G or similar GSM device is plugged in. Interesting... I'm also using Ubununtu 8.10 with standard NM, and I don't get any popup with my 3G modem. OTOH even though I have the MB connection set for auto-connect, it very rarely does so, so I suspect NM doesn't detect the modem plugin event properly anyway. Even so, I've never seen a popup even when it has managed to auto-connect. Not sure if that's any help ... :( ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
[PATCH] properly honor "actions" capability as announced by running notification daemon
patch against 0.7.1 rc3
=== modified file 'src/applet.c'
--- a/src/applet.c 2009-02-18 16:48:04 +
+++ b/src/applet.c 2009-03-10 13:36:00 +
@@ -65,16 +65,17 @@
#include "applet-device-gsm.h"
#include "applet-device-cdma.h"
#include "applet-dialogs.h"
#include "vpn-password-dialog.h"
#include "applet-dbus-manager.h"
#include "utils.h"
#include "gconf-helpers.h"
+#define NOTIFY_CAPS_ACTIONS_KEY "actions"
G_DEFINE_TYPE(NMApplet, nma, G_TYPE_OBJECT)
static NMActiveConnection *
applet_get_best_activating_connection (NMApplet *applet, NMDevice **device)
{
NMActiveConnection *best = NULL;
NMDevice *best_dev = NULL;
@@ -391,17 +392,17 @@ applet_do_notify (NMApplet *applet,
notify = notify_notification_new (summary, message,
icon ? icon : GTK_STOCK_NETWORK,
NULL);
applet->notification = notify;
notify_notification_attach_to_status_icon (notify, applet->status_icon);
notify_notification_set_urgency (notify, urgency);
notify_notification_set_timeout (notify, NOTIFY_EXPIRES_DEFAULT);
- if (action1) {
+ if (applet->notify_with_actions && action1) {
notify_notification_add_action (notify, action1, action1_label,
action1_cb, action1_user_data,
NULL);
}
if (!notify_notification_show (notify, &error)) {
g_warning ("Failed to show notification: %s", error->message);
g_error_free (error);
}
@@ -2472,16 +2473,17 @@ applet_pre_keyring_callback (gpointer us
static GObject *
constructor (GType type,
guint n_props,
GObjectConstructParam *construct_props)
{
NMApplet *applet;
AppletDBusManager *dbus_mgr;
+ GList *server_caps;
applet = NM_APPLET (G_OBJECT_CLASS (nma_parent_class)->constructor
(type, n_props, construct_props));
g_set_application_name (_("NetworkManager Applet"));
gtk_window_set_default_icon_name (GTK_STOCK_NETWORK);
applet->glade_file = g_build_filename (GLADEDIR, "applet.glade", NULL);
if (!applet->glade_file || !g_file_test (applet->glade_file,
G_FILE_TEST_IS_REGULAR)) {
@@ -2502,16 +2504,25 @@ constructor (GType type,
/* Load pixmaps and create applet widgets */
if (!setup_widgets (applet))
goto error;
nma_icons_init (applet);
if (!notify_is_initted ())
notify_init ("NetworkManager");
+ server_caps = notify_get_server_caps();
+ if (g_list_find (server_caps, NOTIFY_CAPS_ACTIONS_KEY))
+ applet->notify_with_actions = TRUE;
+ else
+ applet->notify_with_actions = FALSE;
+
+ g_list_foreach (server_caps, (GFunc) g_free, NULL);
+ g_list_free (server_caps);
+
dbus_mgr = applet_dbus_manager_get ();
if (dbus_mgr == NULL) {
nm_warning ("Couldn't initialize the D-Bus manager.");
g_object_unref (applet);
return NULL;
}
applet->dbus_settings = (NMDBusSettings *) nm_dbus_settings_system_new
(applet_dbus_manager_get_connection (dbus_mgr));
=== modified file 'src/applet.h'
--- a/src/applet.h 2009-02-18 16:29:49 +
+++ b/src/applet.h 2009-03-10 13:36:13 +
@@ -138,16 +138,17 @@ typedef struct
guint networking_enabled_toggled_id;
GtkWidget * wifi_enabled_item;
guint wifi_enabled_toggled_id;
GtkWidget * info_menu_item;
GtkWidget * connections_menu_item;
GladeXML * info_dialog_xml;
NotifyNotification* notification;
+ gbooleannotify_with_actions;
} NMApplet;
struct NMADeviceClass {
NMConnection * (*new_auto_connection) (NMDevice *device,
NMApplet *applet,
gpointer user_data);
- Alexander
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
[PATCH] Re: How to suppress pop-up window when device is inserted ?
On Tue, Mar 10, 2009 at 01:00:12PM +0100, Christopher Lang wrote: > > Hi, > > for example under Ubuntu 8.10, which uses nm-applet, there is a pop-up > whenever a 3G or similar GSM device is plugged in. > > Is there a way to switch that off or suppress it? > > Interesting would be also to understand, do I have to tell the nm-applet > somehow not to display the pop-up or is there a way I can tell NetworkManager > to leave some devices alone (maybe through dbus)? > > Or, is there a way to tell NM not to report it, still allowing manual config > when the user chooses to? This requires a patch to not add actions if there is no action support. Forgot to submit it ... will come in a minute .. - Alexander ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
How to suppress pop-up window when device is inserted ?
Hi, for example under Ubuntu 8.10, which uses nm-applet, there is a pop-up whenever a 3G or similar GSM device is plugged in. Is there a way to switch that off or suppress it? Interesting would be also to understand, do I have to tell the nm-applet somehow not to display the pop-up or is there a way I can tell NetworkManager to leave some devices alone (maybe through dbus)? Or, is there a way to tell NM not to report it, still allowing manual config when the user chooses to? many thanks, Chris http://www.acurana.de/ ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM 0.7.1 rc3 oddness with 3G USB device
On Mon, Mar 9, 2009 at 21:05, Dan Williams wrote: > Mobile broadband capabilities are detected with udev capabilities now > too, but the problem here is that nothing reports which channel is the > control channel and which isn't. That information need to go into the > driver somewhere like it does for 'hso' type devices. I don't know; > maybe asac is right and we do need to prefer HAL over udev at least for > 0.7.1. I agree with asac then. With any modem other than HSO, you have no idea from probing which port is the control port and which just accepts AT commands. With HAL, while things are fragile and require manual updates, there's at least a chance it works. Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
