Re: Libnm async functions and GMainLoop

On Thu, 2016-03-17 at 11:01 +0100, Thomas Haller wrote: > On Wed, 2016-03-16 at 16:03 -0700, Aaron Zinghini wrote: > > > > When using async functions such as > > "nm_client_activate_connection_async" I am not getting the supplied > > callback being called. Do I need to have a GMainLoop setup for

Re: NetworkManager 1.1.90 : nm-exported-object.c:293:nm_exported_object_class_add_interface: assertion failed: (object_property != NULL)

814] [mm-port- > serial.c:1294] > _close_internal(): (ttyUSB2) device open count is 1 (close) > ModemManager[2805]: [1457951711.157924] [mm-port- > serial.c:1237] > mm_port_serial_open(): (ttyUSB2) device open count is 2 (open) > ModemManager[2805]: [1457951711.158883] [m

Re: nmcli radio off connected to ModemManager power state low

On Mon, 2016-03-14 at 09:40 -0500, Dan Williams wrote: > On Sun, 2016-03-13 at 18:23 +0100, c.lobr...@gmail.com wrote: > > > > I'm sorry, I think I explained myself wrong. > > > > CFUN=4 is ok for radio off, I wanted to say that some plugins might > > n

Re: nmcli radio off connected to ModemManager power state low

On Sun, 2016-03-13 at 18:23 +0100, c.lobr...@gmail.com wrote: > I'm sorry, I think I explained myself wrong. > > CFUN=4 is ok for radio off, I wanted to say that some plugins might > not  > use CFUN=4 for "power low". > In Telit modem, as example, I might use CFUN=5 "mobile full  > functionality

Re: nmcli radio off connected to ModemManager power state low

On Sun, 2016-03-13 at 12:26 +0100, Aleksander Morgado wrote: > On Sun, Mar 13, 2016 at 10:28 AM, Carlo Lobrano > wrote: > > > > > > thank you, it is more clear now. I will check in my system for > > rfkill. > > One more question, do you think it will be feasible for NM to

Re: nmcli c does not list modem device

On Mon, 2016-03-14 at 15:55 +0200, matti kaasinen wrote: > In fact there are two more messages preceding those ones I mentioned > before, but I guess they have nothing to do with this problem. I'll > get > following messages, if I have MM running from boot: > > src/nm-udev-manager.c:568]

Re: NetworkManager 1.1.90 : nm-exported-object.c:293:nm_exported_object_class_add_interface: assertion failed: (object_property != NULL)

, it is.  But notice how it doesn't actually come as a response to the AT^SCFG=? request, but only when ModemManager sends the next request. Dan > > > > > On Fri, Mar 11, 2016 at 6:59 AM, Dan Williams <d...@redhat.com> > wrote: > > > > > On Thu, 2016-03

Re: nmcli radio off connected to ModemManager power state low

On Fri, 2016-03-11 at 14:49 +0100, Carlo Lobrano wrote: > Hello everybody, > > making some changes in ModemManager "set power state", I observed > that setting > setting a radio interface to OFF with nmcli, the ModemManager power > state > triggered is the LOW one, while I expected it to be the

Re: NetworkManager 1.1.90 : nm-exported-object.c:293:nm_exported_object_class_add_interface: assertion failed: (object_property != NULL)

g_log(): (ttyUSB2): <-- '^SCFG: > > > > "Audio/Loop",("0","1")^SCFG: "Call/ECC",("0"- > > > > "255")^SCFG: > > > > "Call/Speech/Codec",("0","1")^SCFG: > > > > "GPRS/Auth

Re: NetworkManager 1.1.90 : nm-exported-object.c:293:nm_exported_object_class_add_interface: assertion failed: (object_property != NULL)

ot;URC/Ringline/ActiveTime",("0","1","2","keep")OK< > LF>+CGDCONT: > (1-16,101-116),"IP",,,(0),(0-4)OK' > ModemManager[2738]:   [946691988.701381] [mm-iface- > modem.c:3984] > load_supported_ip_families_ready(): couldn't load S

Re: NetworkManager 1.1.90 : nm-exported-object.c:293:nm_exported_object_class_add_interface: assertion failed: (object_property != NULL)

wn/OnIgnition",("on","off")^SCFG: > "Radio/Band",("4-108","0-1")^SCFG: > "Radio/NWSM",("0","1","2")^SCFG: > "Radio/OutputPowerReduction",("4"-"8")^SCFG: > "Se

Re: NetworkManager 1.1.90 : nm-exported-object.c:293:nm_exported_object_class_add_interface: assertion failed: (object_property != NULL)

On Thu, 2016-03-10 at 10:24 -0800, Ali Nematollahi wrote: > Hi Thomas > > Thanks! This is much better...here is the output from start to > finish: > mmcli -m 0 > > /org/freedesktop/ModemManager1/Modem/0 (device id > '2ea06a44171a29335a8b7f781e0f9559bc24976d') >   - >  

Re: NetworkManager dispatchers

t;  |  DNS: none >   - >   IPv6 configuration |   method: 'unknown' > > > > Does it not mean that I am already connected?? If I bring up PPPD > manually > I could ping and I can wget at this point. > > > O

Re: Bonding wifi and wired

On Tue, 2016-03-08 at 10:50 +0100, Thomas Haller wrote: > On Mon, 2016-03-07 at 23:34 -0500, Nikolay Martynov wrote: > > > > Hi. > > > >   I just wanted to reach out to ask what's NetworkManager team's > > position on allowing bonding of wifi and wired interface? Are there > > any plans to

Re: NetworkManager dispatchers

ppp ifname ppp0 apn > > > > > internet.com > > > > > Connection 'ppp' (af71d0c7-bbbd-4d4e-941e-a2581dc86a2e) > > > > > successfully > > > > > added. > > > > > > > > > > root/usr/local/etc/NetworkManager/system-connections# nmcli > > > > > con up

Re: nm-pppd-plugin does not start

On Fri, 2016-03-04 at 17:17 +0200, matti kaasinen wrote: > 2016-03-04 13:50 GMT+02:00 matti kaasinen : > > > > > Good point, ppp is not enabled! Option seems to be --enable-ppp. > > I'll try > > > > > > it. This NDISDUP seemp pretty problematic. In fact I found MM > >

Re: NetworkManager dispatchers

compatible with connection 'radio'. > > > Can someone tell me what I'm not doing right? I want to have my PPP0 > interface come up everytime the radio is connected. When I do it > manually > through pppd call it works beautifully but I can't get it to work > with > NM

Re: [PATCH 1/1] import: ignore file encoding for ovpn configuration file

On Wed, 2016-03-02 at 12:53 +0100, Thomas Haller wrote: > Openvpn treats ovpn files as ASCII configuration file and > does not care about a specific certain encoding. As such, > only encodings that are an extension of ASCII can work at > all (like iso8859-* or utf8). > > We should not try to

Re: NetworkManager dispatchers

yWwanConnection > type=gsm > > [ipv4] > method=auto > > [gsm] > number=*99# > apn=mnet.bell.ca.ioe > > > restarted NM, did the same thing, no difference. > > Any documentation for 0.9.4.0 that I can use to figure this out? Can > someone help me with

Backport th/supplicant-manager-fix-ref-count-rh1298007 to 1.0?

Thomas, Do you think it's worth backporting th/supplicant-manager-fix-ref- count-rh1298007 to nm-1-0?  I was just looking at https://bugzilla.redh at.com/show_bug.cgi?id=1241198 and maybe that branch fixes the bug there.  The only other plausible reason would be memory corruption.  But 1.0 would

Re: NetworkManager dispatchers

On Fri, 2016-02-26 at 10:50 -0800, Ali Nematollahi wrote: > Thanks! > > How to I enable "service called NetworkManager-dispatcher or > nm-dispatcher"? When I search for "dispatcher" in my filesystem only > these > come up: > /etc/NetworkManager/dispatcher.d >

[PATCH] libnm-glib/libnm/vpn: fix handling of ConnectInteractive() failure (rh #1298732)

If the plugin supports interactive mode, but the VPN binary (like vpnc or openvpn) doesn't support it, then the plugin should return NM_VPN_PLUGIN_ERROR_INTERACTIVE_NOT_SUPPORTED from its connect_interactive() hook.  This lets NetworkManager know to fall back to plain Connect(). Since this

[PATCH] wifi: ignore monitor interfaces

If a monitor interface is created, NM will grab that interface and change it to station mode. That's not very nice. diff --git a/src/devices/wifi/nm-wifi-factory.c b/src/devices/wifi/nm-wifi-factory.c index 1c8ca47..2d5f8fa 100644 --- a/src/devices/wifi/nm-wifi-factory.c +++

Re: Problems with gobi 4000 connecting via QMI

On Mon, 2016-02-22 at 20:05 +0100, Harald Jung wrote: > Hi, > > a firmware update fixes the problem: > The update did not work with windows 10-64bit, but with windows 7- > 32bit. > > Firmware Update: > http://h20564.www2.hp.com/hpsc/swd/public/detail?sp4ts.oid=5405133 > ItemId=ob_152395_1=4060 

Re: nm-1-2 blocker cleanup

On Mon, 2016-02-22 at 12:27 +0100, Lubomir Rintel wrote: > Hi, > > with the 1.2 release approaching, we need to decide on which bugs set > for 1.2  > milestone need to block the release. No new features should remain in > the list, > only things that absolutely need to be fixed before the release

Re: Problems with gobi 4000 connecting via QMI

On Fri, 2016-02-12 at 13:10 +0100, Harald Jung wrote: > Hi, > > i was able to establish a connection via qmicli, but still not with  > NetworkManager/ModemManager, maybe this information can help to > solve  > the problem: Good info actually; perhaps it's the IPv6 requests.  If you set IPv6

Re: [PATCH 1/1] all/trivial: rename STRLEN() macro to NM_STRLEN()

On Fri, 2016-02-12 at 12:34 +0100, Thomas Haller wrote: > We should not have defines/macros in header files without a nm/NM > prefix. > STRLEN() was one of the few offendors. > --- LGTM. Dan >  clients/cli/settings.c|  8 ++--- >  libnm-core/nm-keyfile-reader.c

Re: [PATCH 1/1] shared: add nm_streq() and nm_streq0() macro

On Fri, 2016-02-12 at 12:34 +0100, Thomas Haller wrote: > Using strcmp() to test for string equality is a well known pattern. > However the inverse logic still hurts my brain every single time, > especially in more complex expressions. > > nm_streq() should be preferred over strcmp(). And there

Re: [PATCH] wifi: allow autoconnect on AP/AdHoc mode connections with manual IP configuration

On Thu, 2016-02-11 at 13:21 +0100, Thomas Haller wrote: > On Mon, 2016-02-08 at 17:03 -0600, Dan Williams wrote: > > The existing checks assumed that all AP/AdHoc connections would use > > the > > shared IP method.  But what we really want to check for here is > > wheth

Re: NM ignores knobs regarding ipv6

On Tue, 2016-02-09 at 19:21 +0100, Olaf Hering wrote: > On Fri, Feb 05, Dan Williams wrote: > > > Can you grab some NM log output?  the NetworkManager openvpn plugin > > does have support for IPv6, but we need to figure out if: > > > > 1) NM or NM-openvpn is somehow

Re: IP configuration is useless with openvpn

On Wed, 2016-02-10 at 17:16 +0100, Anthony Bourguignon wrote: > Hi, > > My OpenVPN provider gives ipv6 connectivity. The IP configuration is > not pushed to client by the server. So, when I connect to the vpn, > the > openvpn plugin send no ipv6 configuration to network manager : > >   

Re: Problems with gobi 4000 connecting via QMI

between when the PIN unlocks and the connection attempt occurs? Also, any chance you can connect to the AT port with minicom and run "AT+CGDCONT?" for me? Dan > Harald > > Am 08.02.2016 um 17:32 schrieb Dan Williams: > > On Mon, 2016-02-08 at 14:51 +0100, Harald Jung

Re: Problems with gobi 4000 connecting via QMI

gt; when another SIM is used, the messages are "user request" oder > > "none", nm-applet gives a messages > > Creating object path > > '/org/freedesktop/NetworkManager/ActiveConnection/1" failed in nm > > -glib. > > But I have no log

Re: WPA2-Enterprise and server certificate verification

On Mon, 2016-02-08 at 12:09 +0100, Christian Hesse wrote: > Hello everybody, > > when networkmanager connects to a WPA/WPA2-Enterprise secured notwork > it can > check the validity of the server certificate against a CA > certificate. > > Connecting to the authentication server does not include

Re: WPA2-Enterprise and server certificate verification

On Mon, 2016-02-08 at 21:35 +0100, Christian Hesse wrote: > Christian Hesse on Mon, 2016/02/08 21:23: > > > Yes, it's come up recently on bugzilla.gnome.org too and it > > > should > > > likely get added > > > > Ah, nice. Do you have a link for the bug? I did not find it... > >

[PATCH] wifi: allow autoconnect on AP/AdHoc mode connections with manual IP configuration

The existing checks assumed that all AP/AdHoc connections would use the shared IP method. But what we really want to check for here is whether the connection is AP/AdHoc. Leave the existing 'shared' check for backwards compatibility. Also move the check above the timestamp check, since the user

Re: NM ignores knobs regarding ipv6

On Fri, 2016-02-05 at 16:49 +0100, Olaf Hering wrote: > On Fri, Feb 05, Thomas Haller wrote: > > > On Fri, 2016-02-05 at 09:01 +0100, Olaf Hering wrote: > > > The openvpn connection I have been using for months just gained > > > support for ipv6. A few months ago I already set ipv6 to > > >

Re: regarding creating a new interface

On Wed, 2016-02-03 at 17:29 +0530, abhash jain wrote: > Hi All, > i want to create a new interface and assign it to new NIC. but while > getting an ip through bootp i am getting following error. can someone > please help me? > > root@n7k-xb37-pc7 ~]# ifup eth2 -i > Active connection state:

Re: [PATCH] simplify blob handling

On Wed, 2016-02-03 at 11:21 +0100, Thomas Haller wrote: > On Wed, 2016-02-03 at 10:40 +0100, Matthias Berndt wrote: > > Hi Thomas, > > Hi Matthias, > > (CC-ing mailing list) > > > > > I didn't look at it very closely, but I'd suggest using more > > conservative > > permissions for the

Re: How to deal with unsupported wpa_supplicant parameters?

On Fri, 2016-01-29 at 18:00 -0500, Eloy Paris wrote: > Hi Dan, > > On Thu, Jan 28, 2016 at 12:21:24PM -0600, Dan Williams wrote: > > > On Thu, 2016-01-28 at 17:58 +0100, Toby wrote: > > > I fully understand that this specific TLS1.2 issue is temporary > &g

Re: Changing the dnsmasq options for a shared wifi access point?

On Sat, 2016-01-30 at 17:15 +, Ashley Collins wrote: > Hello, > > I have set up an access point connection to share my Ubuntu 15.10 > laptop's > network via wifi. I works really well and I can connect Android and > other > devices to it. > > I would like to change the default route given out

Re: networkmanager starts infinite number of VPN daemons

On Fri, 2016-01-29 at 23:44 +0100, Adrian Freihofer wrote: > Hi Thomas > > Thank you for taking care about this issue. > With my current setup I'm able to reproduce this. Unfortunately I > cannot use NetworkManager 1.2. I'm working on a cross compiled > Embedded System (based on Yocto). I guess

Re: How to deal with unsupported wpa_supplicant parameters?

On Thu, 2016-01-28 at 09:50 +0100, Toby wrote: > Hi, > due to a delay in the upgrade of our corporate radius servers, I > temporarily need to deactivate TLSv1.2 in phase1 of WPA2/EAP-PEAP, to > bypass a conflict with wpa_supplicant >=2.4. (known issue) > In wpa_supplicant.conf this would require a

Re: How to deal with unsupported wpa_supplicant parameters?

plement), but it looks like > this > is not the case. > Toby > Am 28.01.2016 17:25 schrieb "Dan Williams" <d...@redhat.com>: > > > On Thu, 2016-01-28 at 09:50 +0100, Toby wrote: > > > Hi, > > > due to a delay in the upgrade of our corporat

Re: [PATCH v2] dns: clean up error paths in dns-manager

On Mon, 2016-01-25 at 22:59 +0100, Beniamino Galvani wrote: > On Mon, Jan 25, 2016 at 12:59:22PM -0600, Dan Williams wrote: > > From 2370f508df8400b424fec032f8314cea97fdbaef Mon Sep 17 00:00:00 > > 2001 > > From: Dan Williams <d...@redhat.com> > > Date: Wed, 20 Ja

[PATCH v2] platform: ignore permanent MAC addresses of all ones (FF:FF:FF:FF:FF:FF)

Drivers are stupid, and just like the platform ignores an all zeros permanent address, so should it ignore all ones. NetworkManager[509]: [1453743778.854919] [devices/nm-device.c:8885] nm_device_update_hw_address(): [0x190370] (eth0): hardware address now 86:18:52:xx:xx:xx NetworkManager[509]:

[PATCH] wwan: retry connect on some errors and save them for log messages

First, cb751012a2f4b8ef236eab2a7c65687c99205806 mistakenly converted the act_stage_context_step() in connect_ready() to connect_context_clear() instead of connect_context_step(). This would cause the IP Type retry logic to fail and no further types to be tried. It also throws away the

Re: [PATCH v2] platform: ignore permanent MAC addresses of all ones (FF:FF:FF:FF:FF:FF)

be rejected too. There are also some older drivers that used special addresses to indicate some states that we used to ignore as well. But I think we need to allow LAA if the device reports it :( Dan > On Tue, Jan 26, 2016 at 11:33:49AM -0600, Dan Williams wrote: > > Drivers are stupid, a

Re: [PATCH 1/1] configure.ac: fix LIBNM_GLIB_CFLAGS in configure.ac

On Sat, 2016-01-23 at 19:07 +0100, Thomas Haller wrote: > We want to specify the min/max version requirements for libnm-gtk > (the > user of libnm-glib), not for libnm-glib itself. > > Fixes: a0d4d15ed22fff2ed856ca6291812e96374afc94 > >

[PATCH v2] dns: clean up error paths in dns-manager

>From 2370f508df8400b424fec032f8314cea97fdbaef Mon Sep 17 00:00:00 2001 From: Dan Williams <d...@redhat.com> Date: Wed, 20 Jan 2016 13:52:59 -0600 Subject: [PATCH] dns: clean up error paths in dns-manager Specifically for resolvconf, if the write succeeded, but the pclose() failed er

[PATCH] platform: ignore permanent MAC addresses of all ones (FF:FF:FF:FF:FF:FF)

Drivers are stupid, and just like the platform ignores an all zeros permanent address, so should it ignore all ones. NetworkManager[509]: [1453743778.854919] [devices/nm-device.c:8885] nm_device_update_hw_address(): [0x190370] (eth0): hardware address now 86:18:52:xx:xx:xx NetworkManager[509]:

Re: How to create a simple tap0 interface using nmcli

On Mon, 2016-01-25 at 12:21 +, Vincent Fortier wrote: > Thnx. So lets say I previously created a bridge interface and linked > in my > eth0: > $ nmcli connection show > $ nmcli connection delete > $ nmcli connection add type bridge \ > ifname br0 con-name br0 > $

Re: [PATCH] editor: don't show connections for missing device plugins

On Fri, 2016-01-22 at 21:52 +0300, Mikhail Efremov wrote: > On Fri, 22 Jan 2016 21:51:08 +0300 Mikhail Efremov wrote: > > If device plugin is missing (e.g. not installed) then no use > > to show a connection of this type in the list of connections: > > it can't be used anyway. > > --- > >

Re: networkmanager starts infinite number of VPN daemons

On Fri, 2016-01-22 at 15:24 +0100, Thomas Haller wrote: > On Fri, 2016-01-22 at 14:48 +0100, Adrian Freihofer wrote: > > Hi, > > > > Setup an OpenVPN connection with NetworkManager 1.0.10 is not > > always painless... I ended up with a setup where an > > infinite number of openvpn daemons tried

[PATCH] dns: clean up error paths in dns-manager

Specifically for resolvconf, if the write succeeded, but the pclose() failed error would be left NULL and SR_ERROR would be returned, which caused a crash in nm_dns_manager_end_updates(). --- src/dns-manager/nm-dns-manager.c | 126 ++- 1 file changed, 58

[Fwd: RFP: NetworkManager-openconnect - A Feature Request setting group in vpn config]

Forwarded Message From: Riku Meskanen <riku.h.meska...@jyu.fi> To: Dan Williams <d...@redhat.com>, David Zeuthen <dav...@redhat.com>, David Woodhouse <dw...@infradead.org> Subject: RFP: NetworkManager-openconnect - A Feature Request setting group in vpn

Re: NM attempts connecting to nonexistent AP

On Thu, 2015-12-24 at 17:38 -0600, Robby Workman wrote: > On Thu, 11 Sep 2014 16:47:45 -0500 > Dan Williams <d...@redhat.com> wrote: > > > On Wed, 2014-09-10 at 22:53 -0500, Robby Workman wrote: > > > Summary: when resuming from sleep, NM attempts to connect to an

Re: How do I tell NetworkManager a device is actually wired and not wireless?

On Tue, 2015-12-29 at 13:25 -0800, Steven Stewart-Gallus wrote: > Hello, > > I using CentOS 7 and have a D-Link dwa-130 (revision E) device that > shows up with a name like enp0s4f1u7. NetworkManager seems to think > the > device is wired and not wireless which prevents me from connecting. >

Re: RPi-2 Arch multiple modems

On Sun, 2015-12-13 at 13:12 +0100, Thomas Haller wrote: > On Sat, 2015-12-12 at 19:33 +, John Whitmore wrote: > > Hello all, > > > > I had a Raspberry Pi running Arch with two USB LTE Modems on two > > differet > > Network operators. This was all working perfectly but suddenly > > crashed mid

Re: Don't connect to specific *wired* networks?

On Thu, 2015-12-10 at 15:37 -0200, José Queiroz wrote: > 2015-12-10 14:55 GMT-02:00 Dan Williams <d...@redhat.com>: > > > On Thu, 2015-12-10 at 08:06 -0800, Nikolaus Rath wrote: > > > Hello, > > > > > > Is there a way to prevent Netwo

Re: Don't connect to specific *wired* networks?

On Thu, 2015-12-10 at 08:06 -0800, Nikolaus Rath wrote: > Hello, > > Is there a way to prevent NetworkManager from automatically > connecting > to specific *wired* networks? > > I think the network could be identified by the presence (or absence) > of > specific MACs, but I'd be open to other

Re: raw-ip support for qmi (mbim?) modems

On Thu, 2015-12-03 at 19:29 +0100, Thomas Schäfer wrote: > 25. November 2015, 11:12:45 Bjørn Mork: > > Judgement time coming up :) What do you think? Yes, this might > > not be > > the correct forum for kernel patches, but I believe it is where > > this has > > any meaning. The load is on

Re: [PATCH 1/1] initscript: remove all distribution initscripts

On Tue, 2015-12-01 at 19:22 +0100, Thomas Haller wrote: > These initscripts weren't modified for a long time. Are they > just unused or flawless? It seems they are no longer best-practice > (e.g. NetworkManager supports reloading configuration with SIGHUP, > which only x implement). > > Nowadays

Re: Question about captive portal problem

On Wed, 2015-12-02 at 21:23 +0100, Ties Jan Hefting wrote: > Hello all! > > First of all: thanks for all the hard work of the Network Manager. It > makes networking as easy as pie! :) > > I have a problem with the captive portal and I think I should direct > my > questions to this mailing list.

Re: MC 7304 ipv4v6

On Wed, 2015-11-25 at 08:51 +0100, Bjørn Mork wrote: > Dan Williams <d...@redhat.com> writes: > > > Well, if we're going to add rawip support, why bother emulating a > > netdev at all? > > (assuming you mean etherdev - we'll need the netdev in any case :) > >

Re: MC 7304 ipv4v6

On Tue, 2015-11-24 at 23:52 +0100, Bjørn Mork wrote: > Bjørn Mork <bj...@mork.no> writes: > > Dan Williams <d...@redhat.com> writes: > > > On Tue, 2015-11-24 at 22:51 +0100, Bjørn Mork wrote: > > > > > > My vote would be sysfs, with values &

Re: MC 7304 ipv4v6

On Tue, 2015-11-24 at 20:55 +0100, Thomas Schäfer wrote: > Am Dienstag, 24. November 2015, 16:06:22 schrieben Sie: > > On Mon, 23 Nov 2015 22:42:09 +0100 > > > > > > > Would you be more specific about the problems you have and attach > > more > > information? > > * What NM, MM versions do you

Re: MC 7304 ipv4v6

On Tue, 2015-11-24 at 22:51 +0100, Bjørn Mork wrote: > Reinhard Speyerer writes: > > > This looks rather similar to the "Dualstack errors with MC7354" > > problem > > described here > > https://forum.sierrawireless.com/viewtopic.php?f=117=8295 . > > > > Apparently the qmi_wwan

Re: MC 7304 ipv4v6

Adding libqmi-devel... On Tue, 2015-11-24 at 21:40 +0100, Reinhard Speyerer wrote: > [ please keep me CCed, I am not subscribed to the mailing list ] > > On Tue, Nov 24, 2015 at 08:55:42PM +0100, Thomas Schäfer wrote: > > Am Dienstag, 24. November 2015, 16:06:22 schrieben Sie: > > > On Mon, 23

Re: [RFC] Revise NM behavior for Unmanaged Devices and Assuming Connections (bgo 746440)

On Mon, 2015-11-09 at 17:43 +0100, Thomas Haller wrote: > Hi, > > > Regarding bug https://bugzilla.gnome.org/show_bug.cgi?id=746440, > about > unmanaged devices and assuming connections. > > The current behavior is broken and for nm-1-2 this shall be fixed as > follows: > > Basically, let NM

Re: Approaching NetworkManager 1.2

On Sat, 2015-11-21 at 10:02 +0100, Olaf Hering wrote: > On Fri, Nov 13, Dan Williams wrote: > > > Again, if you can get dispatcher debugging that would be great. > > Slaves > > should never have IP information *unless it's been added externally > > to > > NM*

Re: How to tell NM to ignore some interfaces

ven more interesting is that this tap0 interface ends up with > 2 IPs > obtained via dhcp NM should not be doing this. We'll look into it; is there any chance you could file a bug on bugzilla.gnome.org with the info so it doesn't get lost/forgotten/etc? Dan > Jeka > > >

Re: How to tell NM to ignore some interfaces

On Tue, 2015-11-17 at 13:30 +, Jetchko Jekov wrote: > Hi, > Here it is. NM will always detect all kernel interfaces and expose them through its APIs, but it will *not* necessarily actively manage them. That is what an "unmanaged" device means. But NM will still reflect the state of that

Re: [PATCH] nmcli: Made nmcli build optional

On Fri, 2015-11-13 at 19:35 +, Joel Holdsworth wrote: > Hi, here's a patch to make the nmcli build optional. In my use-case I > need to cross-build NetworkManager, and I don't want to have to > cross-build GNU readline for a binary I don't need. Thanks for the patch! Would you mind making

Re: Approaching NetworkManager 1.2

On Fri, 2015-11-13 at 21:38 +0100, Olaf Hering wrote: > On Mon, Nov 02, Lubomir Rintel wrote: > > > If anyone believes anything important is missing it's a good time > > to > > speak up now. > > The interface for scripts in /etc/NetworkManager/dispatcher.d/ is in > a > poor state. IMO there are

Re: [PATCH 1/1] all: add C99's "bool" define and encourage its use

On Wed, 2015-11-11 at 13:33 +0100, Thomas Haller wrote: > --- > Let's use bool. > > Comments? Since glib uses gboolean in quite a few places, would we have problems with casting it to gboolean if needed? Casting would be pretty ugly if we had to do it a bunch. Also, I don't think we'd save

Re: OpenVPN plugin and private key password

On Mon, 2015-11-09 at 17:51 -0200, Ethy H. Brito wrote: > On Mon, 9 Nov 2015 13:11:24 +0100 > Jirka Klimes wrote: > > > On Sat, 7 Nov 2015 13:55:39 -0200 > > "Ethy H. Brito" wrote: > > > > > > > > Hi All > > > > > > I am not certain if here is the

Re: nm in different linux distributions - ppp versus qmi-wwan

On Fri, 2015-11-06 at 23:40 +0100, Bjørn Mork wrote: > Thomas Schäfer writes: > > lsusb-20151106-suse.txt (good case) > > lsusb-20151106.txt (manjaro - bad case) > > > > > > both use kernel 4.1.x > > > > The diff is not big: > > Yes, the device appears identical, switched

Re: nm in different linux distributions - ppp versus qmi-wwan

On Fri, 2015-11-06 at 17:22 +0100, Thomas Schäfer wrote: > Hi, > > > That was the problem. option has occupied to much resources. > After removing option and qmi_wwan and adding them in reverse order > everything works as expected. > So now I have to find the right people of manjaro.. or they

Re: Approaching NetworkManager 1.2

On Wed, 2015-11-04 at 07:53 +0100, Tore Anderson wrote: > * Lubomir Rintel > > > If anyone believes anything important is missing it's a good time to > > speak up now. > > A couple of suggestions: > > 1) IPv6 method cleanup: >* Get rid of «Automatic (DHCP only)» >* Get

Re: nm in different linux distributions - ppp versus qmi-wwan

On Thu, 2015-11-05 at 19:15 +0100, Thomas Schäfer wrote: > Hi, > > the last days I tested the NetorkManager with the Huwei E398 with dualstack > on > livecd / fresh installed systems. (ISP Deutsche Telekom(t-mobile)) > > I observed the > > Opensuse 42.1 > nm1.0.6/mm1.4.10 --> uses qmi-wwan,

Re: [PATCH] bluetooth: fix missing 'connected' notifications (rh #1255284)

On Sun, 2015-10-25 at 19:55 +0100, Thomas Haller wrote: > On Fri, 2015-10-23 at 11:50 -0500, Dan Williams wrote: > > Because Bluez5 dropped DUN support, NM must do that manually which > > includes emulating the "connected" property for Bluetooth devices > >

[PATCH] bluetooth: fix missing 'connected' notifications (rh #1255284)

Because Bluez5 dropped DUN support, NM must do that manually which includes emulating the "connected" property for Bluetooth devices when DUN is used. It does this by setting priv->connected = TRUE in nm_bluez_device_connect_finish(). But for PAN, when NM does process the 'connected' property

Re: device not connecting with type=unknown

On Thu, 2015-10-15 at 17:02 -0500, Alex Ferm wrote: > I have an embedded arm device running network-manager 1.0.6 with a usb > ethernet gadget that I want to automatically connect using DHCP. > NetworkManager shows the device type as unknown rather than ethernet, > and I was unable to connect

Re: IPv6 with DHCP -- how is default route set?

On Wed, 2015-10-21 at 11:23 +0200, Tore Anderson wrote: > * Thomas Haller > > > "Automatic, DHCP only" will not use RA at all. > > Which means this variant really shouldn't exist at all, or at the very > least not in a GUI where users might deviced into believing it would >

Re: CentOS 7 and NetworkManager-gnome package

On Wed, 2015-10-14 at 18:55 +, Ron Wurzberger wrote: > There use to be a separate NetworkManager-gnome package in CentOS 6.x. Is > that package now included in the GNOME Desktop 3, or will it remain a > separate package for CentOS 7? If the later, when do you expect it to be > released for

Re: [PATCH] ifcfg-rh: deal with weird ifcfg properly

On Thu, 2015-10-08 at 10:45 +0200, Thomas Haller wrote: > On Wed, 2015-10-07 at 18:18 -0700, Josef Bacik wrote: > > Dracut when faced with an ipv6 only setup during kickstart will > > generate a ifcfg > > file that sets the ipv4 address things to null but sets > > BOOTPROTO=static. This > > makes

Re: How to configure a DHCP + (2nd) Static address (eg on eth0+eth0:0)?

On Wed, 2015-09-30 at 15:28 -0400, Derek Atkins wrote: > Dan, > > On Wed, September 30, 2015 12:44 pm, Dan Williams wrote: > > On Wed, 2015-09-30 at 12:25 -0400, Derek Atkins wrote: > >> Dan, > >> > >> Dan Williams <d...@redhat.com> writes: > >

Re: NM and IETF MIF working group

On Mon, 2015-09-28 at 22:29 +0200, Stjepan Groš wrote: > On 28.09.2015 11:48, David Woodhouse wrote: > > On Mon, 2015-09-07 at 12:05 +0200, Stjepan Groš wrote: > >> Two colleagues of mine and I started to work on MIF implementation on > >> Fedora. In case someone doesn't know, IETF MIF working

Re: NM and IETF MIF working group

On Tue, 2015-09-22 at 12:44 +0200, Stjepan Groš wrote: > Hi Lubomir, > > after some time I'm sending followup on this. I would like to flesh out > and discuss our ideas before we start implementing them to be certain > that they will be useful for NetworkManager users. > > On 07.09.2015 18:10,

Re: How to configure a DHCP + (2nd) Static address (eg on eth0+eth0:0)?

On Thu, 2015-10-01 at 13:34 -0400, Derek Atkins wrote: > Hi Dan, > > On Thu, October 1, 2015 12:49 pm, Dan Williams wrote: > > > Yes, you need a matching ifcfg file for the base interface. So you need > > both ifcfg-eth0 and ifcfg-eth0:0. See the examples, eg ifcf

Re: AP with Radius and VLAN?

On Tue, 2015-09-29 at 21:37 -0700, Frank Rizzo wrote: > Hey guys! > > I'm using Ubuntu 14.04 LTS, and using the applet I am able to do basic > configuration of an AP. I can then start it, connect to it, and use it. > But this base config is very simplistic. I need something more. I need

Re: How to configure a DHCP + (2nd) Static address (eg on eth0+eth0:0)?

On Wed, 2015-09-30 at 06:26 +0300, Andrei Borzenkov wrote: > 29.09.2015 20:54, Dan Williams пишет: > > > >> Basically I want to automate NM doing, effectively: > >> > >>ifconfig eth0:0 192.168.x.y > > > > Don't do this with interface aliases; t

Re: How to configure a DHCP + (2nd) Static address (eg on eth0+eth0:0)?

On Wed, 2015-09-30 at 10:15 -0400, Derek Atkins wrote: > Andrei, > > Andrei Borzenkov <arvidj...@gmail.com> writes: > > > 29.09.2015 20:54, Dan Williams пишет: > >> > >>> Basically I want to automate NM doing, effectively: > >>>

Re: failure with bridge devices

On Wed, 2015-09-30 at 09:59 +0200, Olaf Hering wrote: > Am 29.09.2015 um 13:21 schrieb Jirka Klimes: > > On Mon, 28 Sep 2015 09:05:02 +0200 > > Olaf Hering wrote: > >> So my questions: > >> Are there known bugs in the cooperation between NM and GNOME? > > I don't think there is a

Re: How to configure a DHCP + (2nd) Static address (eg on eth0+eth0:0)?

On Wed, 2015-09-30 at 12:25 -0400, Derek Atkins wrote: > Dan, > > Dan Williams <d...@redhat.com> writes: > > >> Could you explain more detail on how to add "label xxx" to the nmcli > >> command (which you inconveniently cut out of your reply, so I'

Re: How to configure a DHCP + (2nd) Static address (eg on eth0+eth0:0)?

On Tue, 2015-09-29 at 12:16 -0400, Derek Atkins wrote: > Hi, > > I've got an esoteric NM question. I've got two distinct networks that > share an ethernet fabric (poor man's vlans). I have a F22 server that I > want to put on both networks. It's currently configured to use DHCP for > the

Re: vpn password stored in plain text

On Mon, 2015-09-28 at 09:32 +0200, Olaf Hering wrote: > Why is the VPN password stored in plain text in > /etc/NetworkManager/system-connections? Is there a way to let the GUI > ask for it every time? Note that the file is read-only by root. If somebody has root on your machine, they can do a

Re: vpn password stored in plain text

On Mon, 2015-09-28 at 17:57 +0200, Olaf Hering wrote: > Am 28.09.2015 um 17:00 schrieb Dan Williams: > > On Mon, 2015-09-28 at 09:32 +0200, Olaf Hering wrote: > >> Why is the VPN password stored in plain text in > >> /etc/NetworkManager/system-connections? Is there a

Re: Network Manager Fails to control Wi-Fi

the code, or is run without the "-u" option Dan > cat /usr/share/dbus-1/system-services/fi.w1.wpa_supplicant1.service > [D-BUS Service] > Name=fi.w1.wpa_supplicant1 > Exec=/sbin/wpa_supplicant -B -P /run/sendsigs.omit.d/wpasupplicant.pid > -u -s -O /var/run/wpa_supplican

<    1   2   3   4   5   6   7   8   9   10   >