gmane.linux.network.networkmanager.devel

Re: Not able to connect from CDMA2000 Modem from Network Managerconnection

ezee — 2012-05-26T09:27:11

Hey Aleksander,

I am waiting for your important reply...:)

-Eshant

Aleksander Morgado-5 wrote:

Re: NM vlan config documentation ?

Weiping Pan — 2012-05-25T02:07:53

Yes.

So please prepare a ifcfg file and put it in 
/etc/sysconfig/network-scripts/.

The example of ifcfg-vlan43 is as followed:
(src/settings/plugins/ifcfg-rh/tests/network-scripts/ifcfg-test-vlan-interface)

     VLAN=yes
     TYPE=Vlan
     DEVICE=vlan43  or "DEVICE=eth9.43"
     PHYSDEV=eth9
     REORDER_HDR=1
     VLAN_FLAGS=GVRP,LOOSE_BINDING
     VLAN_INGRESS_PRIORITY_MAP=0:1,2:5
     VLAN_EGRESS_PRIORITY_MAP=12:3,14:7
     ONBOOT=yes
     BOOTPROTO=static
     IPADDR=192.168.43.149
     NETMASK=255.255.255.0

     And we try to make it compitable with the format used by initscripts,
     and there is no need to change anything in ifcfg-eth9.

thanks
Weiping Pan

NM vlan config documentation ?

Marc MAURICE — 2012-05-24T12:36:03

Hello all,

I would like to use some VLAN configuration with my NM 0.9.4.

However, it seems like the graphical interfaces do not support vlan 
config yet. So we have to do it in /etc/NetworkManager ?

Looking around on NM site and wiki, and the list archives, I did not 
find any Doc about how to configure VLAN connections.

I even tried to look in the source, but I'm not an expert.

Could you provide a sample config for VLAN config ? or I have to do it 
with dbus with some commands ?

Thanks in advance,
and for your work on NM!
Marc

Re: Strange issues in debian testing - persistent gsm connection

PongráczI — 2012-05-23T19:12:29

 

 

_______________________________________________
networkmanager-list mailing list
networkmanager-list< at >gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Little white window SECRET

Dan Williams — 2012-05-23T14:26:55

The things that ask for secrets are provided by the desktop
environments.  So there's one for GNOME Shell, one for GNOME classic,
one for KDE, and so forth.  For KDE it's kde-plasma-networkmanagement
and part of the KDE sources.

Dan

Strange issues in debian testing, no idea what's going on

PongráczI — 2012-05-23T13:07:23


Hi,

On my debian testing (i486) I run into issue with my modem + recent 0.5.2 MM + kernel 3.2.0-2-486

Modem stopped working, so, I made two logs using modem-manager.

1st case: cannot use the modem, even cannot see in devices list etc.: modem-manager.connection-lost.log

2nd case: I pull out the modem and plug back after some seconds, it get known, tried to connect but dropped the connection immediately. modem-manager.connection-lost_new_plug.log

3rd case: reboot, working well.

The attached messages.log contains the end of the 2nd case and a normal operation (boot, activated, everything working well at this moment).

In fact, I have no idea, what is going on and why these things happen. I did not see any segfault. Even, last night it was working all the night, but in the morning I had several issues. 

It is possible, the weather is not so good here nowadays, probably the mobile service provider kicks out from the network, I do not know.

Could somebody check the logs, maybe you have more experiences.

[PATCH 6/6] bridge: nmcli support

Thomas Graf — 2012-05-23T14:19:30

---
 cli/src/connections.c |   17 +++++++++++++++--
 cli/src/devices.c     |    5 +++++
 cli/src/settings.c    |   48 ++++++++++++++++++++++++++++++++++++++++++++++++
 cli/src/settings.h    |    2 ++
 4 files changed, 70 insertions(+), 2 deletions(-)

diff --git a/cli/src/connections.c b/cli/src/connections.c
index 2b4eb01..1c6fe53 100644
--- a/cli/src/connections.c
+++ b/cli/src/connections.c
< at >< at > -43,6 +43,7 < at >< at >
 #include <nm-device-olpc-mesh.h>
 #include <nm-device-infiniband.h>
 #include <nm-device-bond.h>
+#include <nm-device-bridge.h>
 #include <nm-device-vlan.h>
 #include <nm-remote-settings.h>
 #include <nm-vpn-connection.h>
< at >< at > -94,6 +95,7 < at >< at > static NmcOutputField nmc_fields_settings_names[] = {
 SETTING_FIELD (NM_SETTING_BOND_SETTING_NAME, 0),                  /* 17 */
 SETTING_FIELD (NM_SETTING_VLAN_SETTING_NAME, 0),                  /* 18 */
 SETTING_FIELD (NM_SETTING_ADSL_SETTING_NAME, 0),                  /* 19 */
+SETTING_FIELD (NM_SETTING_BRIDGE_SETTING_NAME, 0),                /* 20 */
 {NU

[PATCH 2/6] bridge: API to to create, delete, attach,and detach bridges

Thomas Graf — 2012-05-23T14:19:26

Provides functions to create and delete bridging devices and
to attach/detach slaves from bridging devices.

It currently relies on the ioctl() kernel interface. The long
term goal is to use the netlink interface for this.
---
 src/nm-system.c |  247 ++++++++++++++++++++++++++++++++++++++++++++++++++++++-
 src/nm-system.h |   13 +++
 2 files changed, 259 insertions(+), 1 deletions(-)

diff --git a/src/nm-system.c b/src/nm-system.c
index 6a35997..a0e7275 100644
--- a/src/nm-system.c
+++ b/src/nm-system.c
< at >< at > -15,7 +15,7 < at >< at >
  * with this program; if not, write to the Free Software Foundation, Inc.,
  * 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
  *
- * Copyright (C) 2004 - 2010 Red Hat, Inc.
+ * Copyright (C) 2004 - 2012 Red Hat, Inc.
  * Copyright (C) 2005 - 2008 Novell, Inc.
  * Copyright (C) 1996 - 1997 Yoichi Hariguchi <yoichi< at >fore.com>
  * Copyright (C) January, 1998 Sergei Viznyuk <sv< at >phystech.com>
< at >< at > -44,6 +44,7 < at >< at >
 #include <linux/if.h>
 #include <linux/sockios.h>
 #include <linux/if_bo

[PATCH 5/6] bridge: add bridge device type

Thomas Graf — 2012-05-23T14:19:29

This adds a new device type 'bridge'. Kernel devices are created
on demand.
---
 docs/libnm-glib/libnm-glib-docs.xml |    1 +
 docs/libnm-glib/libnm-glib.types    |    2 +
 include/NetworkManager.h            |    4 +
 introspection/Makefile.am           |    1 +
 introspection/all.xml.in            |    1 +
 introspection/nm-device-bridge.xml  |   27 ++
 introspection/nm-device.xml         |    5 +
 libnm-glib/Makefile.am              |    2 +
 libnm-glib/libnm-glib.ver           |    6 +
 libnm-glib/nm-device-bridge.c       |  301 +++++++++++++++++++
 libnm-glib/nm-device-bridge.h       |   82 +++++
 libnm-glib/nm-device.c              |    3 +
 src/Makefile.am                     |    6 +
 src/nm-device-bridge.c              |  560 +++++++++++++++++++++++++++++++++++
 src/nm-device-bridge.h              |   65 ++++
 src/nm-device-wired.c               |    3 +
 src/nm-manager.c                    |   28 ++-
 src/nm-udev-manager.c               |    3 +
 18 files changed, 1097 insertions(+), 3 deletions(-)

[PATCH 4/6] bridge: support bridging slaves

Thomas Graf — 2012-05-23T14:19:28

Allows to attach any connection to a bridge using the BRIDGE= key.
IP configuration is optional for bridge components but not
prohibited. Test case included.
---
 src/settings/plugins/ifcfg-rh/reader.c             |   52 +++----
 .../plugins/ifcfg-rh/tests/test-ifcfg-rh.c         |  155 +++++++++++++++++++-
 src/settings/plugins/ifcfg-rh/utils.c              |    5 +-
 src/settings/plugins/ifcfg-rh/writer.c             |    2 +
 4 files changed, 175 insertions(+), 39 deletions(-)

diff --git a/src/settings/plugins/ifcfg-rh/reader.c b/src/settings/plugins/ifcfg-rh/reader.c
index 8d490bf..2ea63ea 100644
--- a/src/settings/plugins/ifcfg-rh/reader.c
+++ b/src/settings/plugins/ifcfg-rh/reader.c
< at >< at > -169,6 +169,24 < at >< at > make_connection_setting (const char *file,
 g_object_set (s_con, NM_SETTING_CONNECTION_ZONE, zone, NULL);
 g_free (zone);
 
+value = svGetValue (ifcfg, "BRIDGE", FALSE);
+if (value) {
+const char *bridge;
+
+if ((bridge = nm_setting_connection_get_master (s_con))) {
+PLUGIN_WARN (IFCFG_PLUGI

[PATCH 3/6] bridge: add bridging settings class (NMSettingBridge)

Thomas Graf — 2012-05-23T14:19:27

Support to read/write bridging ifcfg files and convert it to
a NMSettingBridge. Test case included as well.
---
 docs/api/generate-settings-spec.c                  |    2 +
 docs/libnm-util/libnm-util-docs.sgml               |    1 +
 libnm-util/Makefile.am                             |    2 +
 libnm-util/libnm-util.ver                          |   13 +
 libnm-util/nm-connection.c                         |   25 +-
 libnm-util/nm-connection.h                         |    2 +
 libnm-util/nm-setting-bridge.c                     |  557 ++++++++++++++++++++
 libnm-util/nm-setting-bridge.h                     |  105 ++++
 src/settings/plugins/ifcfg-rh/reader.c             |  134 +++++-
 .../plugins/ifcfg-rh/tests/test-ifcfg-rh.c         |  172 ++++++-
 src/settings/plugins/ifcfg-rh/writer.c             |   53 ++
 11 files changed, 1060 insertions(+), 6 deletions(-)
 create mode 100644 libnm-util/nm-setting-bridge.c
 create mode 100644 libnm-util/nm-setting-bridge.h

diff --git a/docs/api/generate-settings-spec.c b

[PATCH 1/6] utils: Move dev_valid_name() to libnm-utils and make itpublic

Thomas Graf — 2012-05-23T14:19:25

The bridging code needs it as well.
---
 libnm-util/libnm-util.ver    |    1 +
 libnm-util/nm-setting-bond.c |   27 +--------------------------
 libnm-util/nm-utils.c        |   30 ++++++++++++++++++++++++++++++
 libnm-util/nm-utils.h        |    2 ++
 4 files changed, 34 insertions(+), 26 deletions(-)

diff --git a/libnm-util/libnm-util.ver b/libnm-util/libnm-util.ver
index 9eec05c..d8850a5 100644
--- a/libnm-util/libnm-util.ver
+++ b/libnm-util/libnm-util.ver
< at >< at > -499,6 +499,7 < at >< at > global:
 nm_utils_hwaddr_len;
 nm_utils_hwaddr_ntoa;
 nm_utils_hwaddr_type;
+nm_utils_iface_valid_name;
 nm_utils_init;
 nm_utils_ip4_addresses_from_gvalue;
 nm_utils_ip4_addresses_to_gvalue;
diff --git a/libnm-util/nm-setting-bond.c b/libnm-util/nm-setting-bond.c
index fe874ab..fef6870 100644
--- a/libnm-util/nm-setting-bond.c
+++ b/libnm-util/nm-setting-bond.c
< at >< at > -329,31 +329,6 < at >< at > nm_setting_bond_get_option_default (NMSettingBond *setting, const char *name)
 g_assert_not_reached ();
 }
 
-/*
- * This function is a 1:1 cop

[PATCH 0/6] Bridging support v2

Thomas Graf — 2012-05-23T14:19:24

This series of patches adds bridging support to NM.

Thomas Graf (6):
  utils: Move dev_valid_name() to libnm-utils and make it public
  bridge: API to to create, delete, attach, and detach bridges
  bridge: add bridging settings class (NMSettingBridge)
  bridge: support bridging slaves
  bridge: add bridge device type
  bridge: nmcli support

 cli/src/connections.c                              |   17 +-
 cli/src/devices.c                                  |    5 +
 cli/src/settings.c                                 |   48 ++
 cli/src/settings.h                                 |    2 +
 docs/api/generate-settings-spec.c                  |    2 +
 docs/libnm-glib/libnm-glib-docs.xml                |    1 +
 docs/libnm-glib/libnm-glib.types                   |    2 +
 docs/libnm-util/libnm-util-docs.sgml               |    1 +
 include/NetworkManager.h                           |    4 +
 introspection/Makefile.am                          |    1 +
 introspection/all.xml.in                           |    1 +
 int

Re: Little white window SECRET

Brian Morrison — 2012-05-23T11:31:21

On Wed, 23 May 2012 13:02:03 +0200
Timothy Murphy <gayleard< at >eircom.net> wrote:


Ah, I didn't realise that you couldn't, I thought you were saying that
the window was very small and didn't allow you to see what was entered.


I am not currently using NM but back in the dim and distant past I used
it for WiFi on my laptop, I did occasionally get a similar window, I
think it was used by the GNOME key storage program rather than directly
by NM. 


See above.


I'd guess that this could be a problem in your wireless driver rather
than directly in NM itself, but I'm not the best person to ask about it.

Perhaps someone else could comment if you add in a bit more information
about which hardware you have and which driver versions you're using. I
think it's known that some wireless drivers are less solid than others,
but it's probably also AP dependent too. WiFi standards are, well, not
actually standards at all, the WiFi Alliance testing is more like a set
of interoperability tests with 'gold' APs and hence it's p

Re: Little white window SECRET

Timothy Murphy — 2012-05-23T11:02:03


As I said, it does not allow any input into the window,
even if I click "show password",
which is in fact the only thing I can do in the window.

Do you see this "Secret" window?
If so, does it accept input?

Who provides this window, incidentally?
Is it NM?

I'm afraid this incident highlighted for me
how bad NM is when it doesn't work.
(I emphasize that this is only 5% or less of the time.
95% of the time it works fine.)
But when it is not working, I get out my Android phone
(Samsung Galaxy S2) and see if that has a network connection,
so I'll know if the fault actually lies with my WiFi router,
or with dhcpd on my server.
(These are rarely the case.)

The point is, I've never known my Android to have any problems
with WiFi, anywhere.
It lists the access points it sees (as does NM),
and if I click on one it asks me for the password
if that is required, and that is it.
I can go from one location to another,
and it seems to have no problem,
while NM appears to find a change of location very challenging.

Re: Little white window SECRET

Brian Morrison — 2012-05-23T09:12:43

On Wed, 23 May 2012 11:02 +0200
Timothy Murphy <gayleard< at >eircom.net> wrote:


It wants the password, or phrase, for your wireless connection whether
it is Wi-Fi or some other flavour.

You should be able to type in the field, it may not show the whole
string entered, but it should be there. Cut and paste would probably
help if you have your password/phrase/key somewhere accessible.

Little white window SECRET

Timothy Murphy — 2012-05-23T09:02:00

Every now and again NM stops working,
and a little window appears in the middle of the screen
(in fact in the middle of all virtual desktops
on my Fedora-16/KDE laptop).
The window is entitled Secret,
and it has a space to enter a password.
But in fact it is impossible to write in the space provided,
even if one clicks "Show password".

I don't know what password is wanted, even if I could enter one.

I find the only thing to do when this happens is to reboot the laptop.
NM usually works OK after the reboot.

Best way to keep alive mobile connection + openvpn?

PongráczI — 2012-05-23T07:16:02

Dear Guys,

We try to make a system, based on debian testing with MM 0.5.2, which is able to provide the following:

 
it connect automatically to the mobile broadband network using ZTE or Huawei usb modems,
 
it reconnects in any case, when the modem or the provider drops the connection,
 
it builds up the openvpn channel via the mobile broadband when ppp0 interface is available and working well
 
it can make it without any user interaction
 
note: there is gnome, but lightdm, fluxbox, policykit, network-manager, modem-manager, nm-applet, nmcli. Minimal system.


As I can see at this moment, we have to write our own control script, which controls at this moment only the 2G/3G connection:

 
checks gsm device is ready/available
 
checks the wwan is on or turn it on
 
nm-applet setup contains auto-connect for the connection


As in the last few days I found some strange issues with the stability of the mobile connection, I wonder how others solve this kind of problem?

Do you have any solution, recommendatio

Re: [PATCH v2] Re: Change the state of iface from disconnected toconnected using nmcli

Jirka Klimes — 2012-05-22T16:46:49

Commited:
e0329b4 libnm-glib: add 'autoconnect' property for devices
d1cbeeb core: authenticate Set() D-Bus call for NMDevice "Autoconnect" 
property
6d9338f core: add "Autoconnect" property to NMDevice

Jirka

[PATCH 4/4] Add switches to the Applet menu

Niv Sardi — 2012-05-21T23:03:48

this is actually quite a bigger change, we factorize a bit of code adding the menu to the function (though it's not strictly necesary), we give a callback to toggle the device state,
note that the callback is unimplemented for bt and wired.

Signed-off-by: Niv Sardi <xaiki< at >debian.org>
---
 src/applet-device-bt.c    |   12 +++--
 src/applet-device-cdma.c  |   15 ++++--
 src/applet-device-gsm.c   |   15 ++++--
 src/applet-device-wifi.c  |   16 ++++--
 src/applet-device-wimax.c |   15 ++++--
 src/applet-device-wired.c |   12 +++--
 src/applet.c              |  119 +++++++++++++++++++++++++++++++++++++++++++--
 src/applet.h              |   10 ++--
 8 files changed, 178 insertions(+), 36 deletions(-)

diff --git a/src/applet-device-bt.c b/src/applet-device-bt.c
index 4f1cac2..cbba5b9 100644
--- a/src/applet-device-bt.c
+++ b/src/applet-device-bt.c
< at >< at > -129,6 +129,12 < at >< at > add_connection_items (NMDevice *device,
 }
 }
 
+static gboolean
+bt_toggle (GtkWidget *sw, gpointer user_data)
+{
+g_log (G_LOG_DOMAIN, G_LOG_LEV

[PATCH 3/4] move creation ofapplet_menu_item_create_device_item_helper to it's own helper

Niv Sardi — 2012-05-21T23:03:47

this is going to be used to be able to make a more complex widget there, you should have guessed by the name it's going to be a switch

Signed-off-by: Niv Sardi <xaiki< at >debian.org>
---
 src/applet.c |   28 ++++++++++++++++++++++++++--
 1 file changed, 26 insertions(+), 2 deletions(-)

diff --git a/src/applet.c b/src/applet.c
index 6081a71..7b3a97b 100644
--- a/src/applet.c
+++ b/src/applet.c
< at >< at > -613,6 +613,30 < at >< at > applet_menu_item_activate_helper (NMDevice *device,
 }
 }
 
+GtkWidget *
+applet_menu_create_switch_item_helper (NMApplet  *applet,
+   GtkWidget *label,
+   GtkWidget *swbox)
+{
+GtkWidget *menu_item = gtk_image_menu_item_new ();
+#if GTK_CHECK_VERSION(3,1,6)
+GtkWidget *box = gtk_box_new (GTK_ORIENTATION_HORIZONTAL, 0);
+#else
+GtkWidget *box = gtk_hbox_new (FALSE, 0);
+#endif
+
+gtk_box_pack_start (GTK_BOX (box), label, TRUE, TRUE, 0);
+if (swbox)
+gtk_box_pack_start (GTK_BOX (box), swbox, FALSE, FALSE, 0);
+
+g_object_set (G_OBJECT (menu_item),
+              "child", b