Data Center Bridging build
... nm-dcb.c: In function '_dcb_setup': nm-dcb.c:211:3: error: format not a string literal and no format arguments [-Werror=format-security] success = do_helper (iface, DCBTOOL, run_func, user_data, error, s->str); ^ nm-dcb.c: In function '_dcb_cleanup': nm-dcb.c:245:3: error: format not a string literal and no format arguments [-Werror=format-security] if (!do_helper (iface, DCBTOOL, run_func, user_data, success ? error : NULL, *iter)) ^ cc1: all warnings being treated as errors ... poma ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
libgsystem as a git submodule, not system wide
Why the 'libgsystem' is used as a git submodule, and not via the system wide setup - 'libgsystem/devel'? I suppose this is the git way to acquire the source code to build a local tarball, git clone git://anongit.freedesktop.org/NetworkManager/NetworkManager cd NetworkManager/ git submodule init git submodule update ./autogen.sh cd ../ tar ... Perhaps this is the reason, however it is still a mystery why are snapshots created with a blank 'libgsystem/'!? poma [1] http://cgit.freedesktop.org/NetworkManager/NetworkManager/ ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
"server.conf" ignore-carrier=* Bonding/Bridge DHCP
'NetworkManager-config-server', /etc/NetworkManager/conf.d/00-server.conf ... # Ignore the carrier (cable plugged in) state when attempting to # activate static-IP connections. ignore-carrier=* This option tends to break the Bonding andor Bridge DHCP setups. Is it a bug, or a feature? poma ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm_device_disconnect
Thanks for the answer, Is there an other way ? Because I want the adhoc network to stop as soon as possible. Plus I do not do anything in the disconnect callback, so I fear that it is just my callback that is called when the adhoc network is disconnected (by somebody else or by the fact that the network is not available anymore) and then that this not the function for my purpose. Well, well, what I am looking for is the function that is called when in a GUI the user hit the disconnect button... So it exists somewhere, but maybe it is not in a public API ? -- Manuel On 04/01/2014 08:16 PM, Dan Winship wrote: On 04/01/2014 01:18 PM, Manuel Yguel wrote: however in the include directory of libnm-glib the file nm-device.h contains only the following function: void nm_device_disconnect (NMDevice *device, NMDeviceDeactivateFn callback, gpointer user_data); I tried to use the last one with a dummy callback function and with a pointer to a NMClient object but it did not disconnect the network. Thanks for any hint or pointer. A libnm-glib method that takes a callback is most likely asynchronous. So you need to call nm_device_disconnect() and then run the main loop until the callback gets called. -- Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm_device_disconnect
On 04/01/2014 01:18 PM, Manuel Yguel wrote: > however in the include directory of libnm-glib the file nm-device.h > contains only the following function: >void nm_device_disconnect (NMDevice *device, > NMDeviceDeactivateFn callback, gpointer user_data); > > I tried to use the last one with a dummy callback function and with a > pointer to a NMClient object but it did not disconnect the network. > > Thanks for any hint or pointer. A libnm-glib method that takes a callback is most likely asynchronous. So you need to call nm_device_disconnect() and then run the main loop until the callback gets called. -- Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
nm_device_disconnect
Hi, I am using libnm-glib version 0.9.4.0-0ubuntu4.3 on ubuntu 12.04 precise pangolin. I would like to time the delay of activation of an adhoc network and I would like to do statistics: creating an adhoc network with a pc, scan and connect with an other, log the different times and repeat. So far I am able to create the adhoc network, scan and connect. I am stuck at the repeat part since I would like to disconnect the network but I do not find how to proceed. It seems that there exists a nm_device_disconnect function with the following prototype: gboolean nm_device_disconnect (NMDevice *device, GError **error); in the source of the NetworkManager however in the include directory of libnm-glib the file nm-device.h contains only the following function: void nm_device_disconnect (NMDevice *device, NMDeviceDeactivateFn callback, gpointer user_data); I tried to use the last one with a dummy callback function and with a pointer to a NMClient object but it did not disconnect the network. Thanks for any hint or pointer. -- Manuel ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: RFC: Improving Ref-Settings.html
On Thu, 2014-03-27 at 13:55 -0500, Justin Brown wrote: > I have recently been working with setting up NetworkManager with > keyfiles and struggled to understand > https://developer.gnome.org/NetworkManager/unstable/ref-settings.html#idp7510624. > To that end, I have some suggestions for a newcomer, although one who > is well-versed in Linux networking. These are great suggestions and they make me think we actually want to create separate documentation for 'keyfile' instead of using the settings reference. It can still be auto-generated from the code documentation (which is great for us since it reduces duplication) but we'll want to override certain settings to make better documentation. Also, we'll probably want to generate manpages too. Dan > * Include a "data type" section before "configuration settings." > Basically just explain the data types and how to type them. Strings > are straightforward, but even things that are simple to programmers > like uint32 are likely confusing to users. The case-sensitivity of > booleans should be defined. Arrays are probably the most confusing. > The documentation is not clear about whether brackets should be used > around the array, what the valid separations are, and if strings need > quotes around them. > > For example, I initially tried this when I saw the data types: > > address1=[192.168.1.2, 24, 192.168.1.1] > > This change should still allow easy use of the current documentation > generation tools since it would just be a static block before the > dynamic content. > > > * Add a description for each table. Many of the tables are easy to > understand like ipv4 and bluetooth. Some are less clear like > bridge-port. It would be nice if there was a short description for > each table, even if some are painfully obvious. I did a brief look at > how the documentation strings are specified in libnm-util/. For the > most part, it looks like all of nm-setting-*.c files have a decent > SECTION description. They would need to be rewritten a little for user > documentation, but that seems like an easy way to expose more > information to users. > > > * Clarify complex data types. This likely applies to many different > types, but I encountered it with ipv4->addresses. I call this a > complex data type, because each address is an array of length two. > (Note the documentation says 3-array, which doesn't reflect the recent > changes.) The first element is an address with a subnet mask. The > documentation should more clearly specify to use a slash and subnet. > Again, I only experienced this problem with this key, but I'm sure > that it exists in many other keys. > > > * Reconcile "method" between ipv4 and ipv6. It used to be that > method=ignore worked for both. Sometime in the past 6 months or so, > ignore has been replaced with "disabled" but only for ipv4. Either > term is fine, but they should be the same. > > > Thanks, > Justin > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > https://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: pppd: Terminating connection due to lack of activity.
On Tue, 2014-04-01 at 09:30 +0200, Aleksander Morgado wrote: > Hey hey, > > Is there any good reason why when launching pppd, for e.g. a mobile > connection, we don't use "idle 0" by default? Otherwise pppd will > suicide after 10 mins (default) of inactivity in the channel: > > Apr 01 01:22:38 pppd[23180]: Terminating connection due to lack of activity. > Apr 01 01:22:38 pppd[23180]: Connect time 10.1 minutes. > Apr 01 01:22:38 pppd[23180]: Sent 0 bytes, received 84 bytes. > > ... even if those 84 bytes are actually some activity... Not that I can think of. We should probably fix that :) Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
pppd: Terminating connection due to lack of activity.
Hey hey, Is there any good reason why when launching pppd, for e.g. a mobile connection, we don't use "idle 0" by default? Otherwise pppd will suicide after 10 mins (default) of inactivity in the channel: Apr 01 01:22:38 pppd[23180]: Terminating connection due to lack of activity. Apr 01 01:22:38 pppd[23180]: Connect time 10.1 minutes. Apr 01 01:22:38 pppd[23180]: Sent 0 bytes, received 84 bytes. ... even if those 84 bytes are actually some activity... Cheers! -- Aleksander https://aleksander.es ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
