Re: spamming router with router solicitations

On Mon, 2019-06-24 at 08:52 +0200, Beniamino Galvani via networkmanager-list wrote: > > Hi, Hi Beniamino, > I checked again the log you sent and I see the problem now. When NM > receives a RA, it checks whether the parameters Which parameters exactly? Because I might be able to shed some

Re: spamming router with router solicitations

On Fri, Jun 21, 2019 at 01:03:11PM -0400, Brian J. Murrell wrote: > On Fri, 2019-06-21 at 17:58 +0200, Beniamino Galvani via > networkmanager-list wrote: > > > > Sounds ok. > > Thanks. > > > Which kernel version do you have on the EL 7.6 machine? > > 3.10.0-957.21.2.el7.x86_64 Hi, I checked

Re: spamming router with router solicitations

On Fri, 2019-06-21 at 17:58 +0200, Beniamino Galvani via networkmanager-list wrote: > > Sounds ok. Thanks. > Which kernel version do you have on the EL 7.6 machine? 3.10.0-957.21.2.el7.x86_64 Cheers, b. signature.asc Description: This is a digitally signed message part

Re: spamming router with router solicitations

On Tue, Jun 18, 2019 at 02:24:09PM -0400, Brian J. Murrell wrote: > On Mon, 2019-06-03 at 14:17 -0400, Brian J. Murrell wrote: > > > > I think I had it set to DEBUG. Let me see if I can reproduce with it > > set to TRACE. > > I have to correct myself. It was set to TRACE. > > > It goes up

Re: spamming router with router solicitations

On Fri, 2019-05-24 at 13:16 +0200, Till Maas via networkmanager-list wrote: > Hi Brian, Hi. > You can try if it is fixed in a never version. You can find builds > from latest GIT branches for EL 7 here: > > https://copr.fedorainfracloud.org/coprs/networkmanager/ No, the

Re: Reconnecting GSM profile after a long period of no signal

On Tue, 2019-06-18 at 22:58 +, Matthew Starr wrote: > I am running NetworkManager 1.12.0 on an embedded Linux device that > has Ethernet, Wi-Fi, and cellular. I am seeing a connection issue on > GSM profiles that are setup for autoconnect=true. If I am able to > establish a connection on

Re: Connection policies control

Hi, On Sat, 2019-06-15 at 14:36 +0200, Daniel Vázquez via networkmanager- list wrote: > I'll want to setup a connect security policy like whitelist rules or > similar, some like: > - Users can connect only to any AP with security WPA2 As said, you cannot run you own script that hooks into the

Reconnecting GSM profile after a long period of no signal

I am running NetworkManager 1.12.0 on an embedded Linux device that has Ethernet, Wi-Fi, and cellular. I am seeing a connection issue on GSM profiles that are setup for autoconnect=true. If I am able to establish a connection on cellular, then lose signal (move out of range) for 20-60

Re: spamming router with router solicitations

On Mon, 2019-06-03 at 14:17 -0400, Brian J. Murrell wrote: > > I think I had it set to DEBUG. Let me see if I can reproduce with it > set to TRACE. I have to correct myself. It was set to TRACE. > It goes up quite a bit. More indication that it is NM. CPU is pegged between NM, journald and

Re: Connection policies control

Hi Thomas, thanks for your response. I have previously used org.freedesktop.NetworkManager.settings.modify.system to allow or deny authorization of wifi connections. This works in scenario where the policy is focused to allow/deny know connections or fully allow/deny actions or use NM by some

Re: Connection policies control

On Sat, 2019-06-15 at 14:36 +0200, Daniel Vázquez via networkmanager- list wrote: > Hi guys!! > > I'll want to setup a connect security policy like whitelist rules or > similar, some like: > - Users can connect only to any AP with security WPA2 > - User can connect only to any AP in this list

Connection policies control

Hi guys!! I'll want to setup a connect security policy like whitelist rules or similar, some like: - Users can connect only to any AP with security WPA2 - User can connect only to any AP in this list [{ssid:wnet01, mac:E8:AD:A6:BC:EF:F2}, {ssid:wnet02, mac:B0:BE:76:73:20:8E}, ...] First, I

Re: [PATCH] core/pppd-plugin: wait to recover port settings before notifying death

On Thu, 2019-06-13 at 18:23 +0200, Alfonso Sánchez-Beato via networkmanager-list wrote: > pppd restores the previous settings for the serial port it uses right > before exiting. It is especially important to do so because otherwise > ModemManager is not able to recover the port as it can receive a

Re: DHCP and static IP configuration hangs when no DHCP

Hi Francesco, I had Network Manager 1.6.2 from Debian Stretch installed and there it does not work, no IP assigned while connecting. I updated to 1.14 and there it indeed works like you were expecting. And this does what I need it to, so thank you very much for the help! Regards, David On Wed,

[PATCH] core/pppd-plugin: wait to recover port settings before notifying death

pppd restores the previous settings for the serial port it uses right before exiting. It is especially important to do so because otherwise ModemManager is not able to recover the port as it can receive a hangup event from the port due to CLOCAL not being restored. However, there is currently a

Re: Looking for advice how to start contributing in NetworkManager and implement Hotstpot 2.0 feature for WiFi

On Thu, 2019-06-13 at 14:17 +0600, work vlpl via networkmanager-list wrote: > Hello, > > I want to contribute to NetworkManger but don't know where to start, > so I am looking for advise how I can start it. Hi, thanks for reaching out. We would very welcome your help! > wpa_supplicant supports

Looking for advice how to start contributing in NetworkManager and implement Hotstpot 2.0 feature for WiFi

Hello, I want to contribute to NetworkManger but don't know where to start, so I am looking for advise how I can start it. wpa_supplicant supports great feature Hotspot 2.0 and contains in its distribution program - osu_client, that allow to do automatic wifi configuration provision using

Re: DHCP and static IP configuration hangs when no DHCP

Hi David, On 6/12/19 8:17 PM, David Bourgeois wrote: The only hack I found is to create a static IP only, then in add a up-post script that manually launches dhclient on the interface. That does what I need but it's somehow cumbersome. On Wed, Jun 12, 2019 at 8:15 PM David Bourgeois

Re: DHCP and static IP configuration hangs when no DHCP

The only hack I found is to create a static IP only, then in add a up-post script that manually launches dhclient on the interface. That does what I need but it's somehow cumbersome. On Wed, Jun 12, 2019 at 8:15 PM David Bourgeois wrote: > Hi Francesco, > > Thank you for your answer. I can

Re: DHCP and static IP configuration hangs when no DHCP

Hi Francesco, Thank you for your answer. I can indeed do that to keep DHCP trying forever or nearly, that's a good idea. But my problem is that the static IP is not created at all until there's an answer from a DHCP server. I was expecting that the static IP would be created then the dynamic IP

Re: Fwd: Added configuration for TELEKOM.RO (Romanian provider)

On Mon, 2019-06-10 at 16:11 +0300, fo'rika endre wrote: > -- Forwarded message - > From: fo'rika endre > Date: Mon, Jun 10, 2019 at 4:10 PM > Subject: Added configuration for TELEKOM.RO (Romanian provider) > To: < >

Re: DHCP and static IP configuration hangs when no DHCP

Hi David, On 6/11/19 12:24 AM, David Bourgeois wrote: Hi, I can't find the proper configuration to have an always enabled static IP address and an optional DHCP address when connected to a network that has a DHCP server. My use case is a portable device that connects to local embedded

NetworkManager licensing and all new contributions must be under LGPL-2.0+

Hi all, TL;DR: if you contribute to NetworkManager ([1]), then these contributions must be made under terms of LGPL-2.0+ license. The source code of NetworkManager [1] both contains the daemon and the client library (libnm). Traditionally, the daemon is GPL-2.0+ licensed, while the library

Fwd: Added configuration for TELEKOM.RO (Romanian provider)

-- Forwarded message - From: fo'rika endre Date: Mon, Jun 10, 2019 at 4:10 PM Subject: Added configuration for TELEKOM.RO (Romanian provider) To: This patch adds TELEKOM.RO (old Cosmote RO) a romanian network provider to the list available in the mobile network configuration

DHCP and static IP configuration hangs when no DHCP

Hi, I can't find the proper configuration to have an always enabled static IP address and an optional DHCP address when connected to a network that has a DHCP server. My use case is a portable device that connects to local embedded devices using a private local LAN so the static IP should always

Re: NetworkManager dnsmasq plugin and docker

On Sat, May 25, 2019, at 3:35 AM, Till Maas via networkmanager-list wrote: > Hi, > > I am using NetworkManager with dnsmasq with this confguration: > > cat > '/etc/NetworkManager/conf.d/dns.conf' < [main] > dns=dnsmasq > EOF Using podman will help if you're using host networking:

Re: spamming router with router solicitations

On Sun, 2019-06-02 at 10:29 +0200, Thomas Haller via networkmanager- list wrote: > > Thanks, that's of course a string indication that NetworkManager is > the > culprit. Seems so to me. As well as (see answer to your other question below)... > Just to check, did you enable level=TRACE I think

Re: spamming router with router solicitations

On Sat, 2019-06-01 at 07:00 -0400, Brian J. Murrell wrote: > On Thu, 2019-05-30 at 12:23 +0200, Thomas Haller via networkmanager- > list wrote: > > On Wed, 2019-05-29 at 12:23 -0400, Brian J. Murrell wrote: > > > On Wed, 2019-05-29 at 09:28 +0200, Thomas Haller via > > > networkmanager- > > > list

Re: spamming router with router solicitations

On Thu, 2019-05-30 at 12:23 +0200, Thomas Haller via networkmanager- list wrote: > On Wed, 2019-05-29 at 12:23 -0400, Brian J. Murrell wrote: > > On Wed, 2019-05-29 at 09:28 +0200, Thomas Haller via > > networkmanager- > > list wrote: > > > If this is happening, when you kill NetworkManager with

Re: spamming router with router solicitations

On Wed, 2019-05-29 at 12:23 -0400, Brian J. Murrell wrote: > On Wed, 2019-05-29 at 09:28 +0200, Thomas Haller via networkmanager- > list wrote: > > If this is happening, when you kill NetworkManager with SIGKILL, it > > would not give NetworkManager to cleanup... > > > > sudo killall -SIGKILL

Re: spamming router with router solicitations

On Wed, 2019-05-29 at 09:28 +0200, Thomas Haller via networkmanager- list wrote: > > If this is happening, when you kill NetworkManager with SIGKILL, it > would not give NetworkManager to cleanup... > > sudo killall -SIGKILL NetworkManager > > (and veryify that NetworkManager is indeed not

Re: Adding basic OpenVPN PKCS#11 support

I did a first patch which used a naive approach and just added support for specifying the pkcs11-providers and pkcs11-id in the GUI. This works but is not elegant or user friendly and requires that openvpn plays nicely with the desired pkcs#11 provider. In practice this is often a big problem.

Re: spamming router with router solicitations

On Mon, 2019-05-27 at 06:59 -0400, Brian J. Murrell wrote: > On Mon, 2019-05-27 at 10:16 +0200, Beniamino Galvani via > networkmanager-list wrote: > > Are you sure you don't have other daemons like systemd-networkd > > # repoquery -q systemd-networkd > systemd-networkd-0:219-62.el7_6.6.x86_64 >

Re: spamming router with router solicitations

On Mon, 2019-05-27 at 10:16 +0200, Beniamino Galvani via networkmanager-list wrote: > > Are you sure you don't have other daemons like systemd-networkd # repoquery -q systemd-networkd systemd-networkd-0:219-62.el7_6.6.x86_64 # rpm -q systemd-networkd package systemd-networkd is not installed

Re: spamming router with router solicitations

On Sat, May 25, 2019 at 03:47:37PM -0400, Brian J. Murrell wrote: > On Sat, 2019-05-25 at 08:52 +0200, Beniamino Galvani via > networkmanager-list wrote: > > > > Hi, it is not NM sending those RS. > > But they stop as soon as I stop NM. > > > If it were, you would see in the > > journal

NetworkManager dnsmasq plugin and docker

Hi, I am using NetworkManager with dnsmasq with this confguration: cat > '/etc/NetworkManager/conf.d/dns.conf'

Re: spamming router with router solicitations

On Sun, May 12, 2019 at 10:41:28AM -0400, Brian J. Murrell wrote: > On Sat, 2019-05-11 at 17:46 -0500, Ian Pilcher via networkmanager-list > wrote: > > > > Presumably you've told NetworkManager to auto-configure the interface > > for IPv6. If you don't want it to do that, set it to link-local >

Re: spamming router with router solicitations

Hi Brian, Am Do., 23. Mai 2019 um 14:46 Uhr schrieb Brian J. Murrell : > > On Thu, 2019-05-09 at 18:25 -0400, Brian J. Murrell wrote: > > NetworkManager 1.12 on EL7.6 is spamming my router with IPv6 router > > solicitations: > > Nobody has any idea about this or what more can be done to debug it?

[nmstate] [RFC] Reorgnize code from dict based to object based

Hi Guys, PR https://github.com/nmstate/nmstate/pull/354 has express a initial layout. I want to expand that to discuss of how we reorganize our code: * `InterfaecBasic` contains IPv4, IPv6 and other stuff shared between interfaces. * Specific interface type will have their own class like:

[nmstate] Re-licensing to LGPL

Hello, Due to requests from the OpenStack community, we have been asked to soften nmstate licensing. Re-licensing to LGPL seems to satisfy OpenStack dependency rules. Two tickets have been opened to track this: https://nmstate.atlassian.net/browse/NMSTATE-193

Re: [PATCH] Add support of disabling IPv6.

On Sat, May 18, 2019 at 05:24:31PM +0200, Thomas Haller wrote: > On Sat, 2019-05-18 at 20:32 +0800, Gris Ge via networkmanager-list > wrote: > > **My first patch to NM, need some help for test cases** > > > > Use NM_SETTING_IP6_CONFIG_METHOD_DISABLED/"disabled" for disabling > > IPv6 per profile.

AW: Run dispatcher.d script when lte device is unplugged

Hi, thank you for your suggestion. Unfortunately, starting OpenVPN is not the only thing we need to do when LTE comes up, so until now dispatcher.d seems to us what ist the most versatile solution to fit our needs. Anyways, I will give your solution a shot when the routers running NM will be

Re: [PATCH] nm-hostname-manager.c: Use fqdn for persistent hostname on Slackware

On Sun, 19 May 2019 10:55:52 +0200 Thomas Haller wrote: > On Sat, 2019-05-18 at 21:08 -0500, Robby Workman wrote: > > The attached patch can be applied to master and 1.12 branches. > > It's specific to the hostname handling on Slackware, so it > > shouldn't affect anyone else. > > > > > >

Re: [PATCH] nm-hostname-manager.c: Use fqdn for persistent hostname on Slackware

On Sat, 2019-05-18 at 21:08 -0500, Robby Workman wrote: > The attached patch can be applied to master and 1.12 branches. > It's specific to the hostname handling on Slackware, so it > shouldn't affect anyone else. > Hi, Merged to upstream. Since the patch only affects Slackware, I assume you

[PATCH] nm-hostname-manager.c: Use fqdn for persistent hostname on Slackware

The attached patch can be applied to master and 1.12 branches. It's specific to the hostname handling on Slackware, so it shouldn't affect anyone else. -RW >From 53676bdf67e1132df02b61416fe03027213afdcc Mon Sep 17 00:00:00 2001 From: "Patrick J. Volkerding" Date: Mon, 13 Nov 2017 00:17:38 -0600

Re: [PATCH] Add support of disabling IPv6.

On Sat, 2019-05-18 at 20:32 +0800, Gris Ge via networkmanager-list wrote: > **My first patch to NM, need some help for test cases** > > Use NM_SETTING_IP6_CONFIG_METHOD_DISABLED/"disabled" for disabling > IPv6 per profile. > > Signed-off-by: Gris Ge Hi Gris, great that you gave it a shot!!

[PATCH] Add support of disabling IPv6.

**My first patch to NM, need some help for test cases** Use NM_SETTING_IP6_CONFIG_METHOD_DISABLED/"disabled" for disabling IPv6 per profile. Signed-off-by: Gris Ge --- clients/common/nm-meta-setting-desc.c | 3 +- clients/common/nm-vpn-helpers.c | 2 +-

Re: spamming router with router solicitations

On Sat, 2019-05-11 at 17:46 -0500, Ian Pilcher via networkmanager-list wrote: > > Presumably you've told NetworkManager to auto-configure the interface > for IPv6. If you don't want it to do that, set it to link-local > only. But surely NM doesn't need to send dozens of RS's per second to do

Re: spamming router with router solicitations

On 5/9/19 5:25 PM, Brian J. Murrell wrote: Any idea what's causing it? Presumably you've told NetworkManager to auto-configure the interface for IPv6. If you don't want it to do that, set it to link-local only. -- Ian

Re: Run dispatcher.d script when lte device is unplugged

Hi, Am Fr., 10. Mai 2019 um 11:16 Uhr schrieb Chauchet, Martin : > We are currently working on an automated OpenVPN connection over LTE > connections, i.e. whenever an LTE stick ist plugged in and the connection ist > established, OpenVPN is required to be started automatically. Same thing >

Run dispatcher.d script when lte device is unplugged

Hello everyone, I hope this question has not been answered yet, bus since I did not find anything similar on the webz, I decided to use this mailing list. We are currently working on an automated OpenVPN connection over LTE connections, i.e. whenever an LTE stick ist plugged in and the

Re: Can't create OVS bridge - device is strictly unmanaged

On 5/7/19 2:53 PM, Beniamino Galvani via networkmanager-list wrote: Do you have any special configuration that makes the device unmanaged? Great timing! I just figured out that the presence of the old ifcfg-ovs0 file (which of course included NM_CONTROLLED=no) was causing the problem.

Re: Can't create OVS bridge - device is strictly unmanaged

On Tue, May 07, 2019 at 02:00:00PM -0500, Ian Pilcher via networkmanager-list wrote: > I am trying to switch from using old-style ifcfg files to NetworkManager > to set up an OVS bridge on my (Fedora 30) laptop. Because this is a > laptop, no physical interface is connected to the bridge; all VM

Can't create OVS bridge - device is strictly unmanaged

I am trying to switch from using old-style ifcfg files to NetworkManager to set up an OVS bridge on my (Fedora 30) laptop. Because this is a laptop, no physical interface is connected to the bridge; all VM traffic to the outside world is "NAT'ed" by iptables. Also, for reasons that I can't even

Re: Frequent network drops (NM, FC29)?

Derek, I'll preface this by stating I'm no progammer, or expert on NM. I didn't see any response, this looks like wpa_supplicant and the chip didn't communicate - Right after CTRL-EVENT-CONNECTED, I usually see something like this, never bgscan messages. May  5 11:31:43 Tuxedo1

Frequent network drops (NM, FC29)?

HI, I'm having an issue on my Fedora-29 laptop where my Wifi shows periodic network drops. I'm running mtr and it's working fine, but then it effectively stops transmitting packets for a few seconds, and then it starts up again. This pause coincides with the following entries in my

ANN: NetworkManager 1.18.0 released

Hi, I am happy to announce the newest major release of NetworkManager. While NetworkManager 1.16.0 took 6 months after the previous release, 1.18.0 comes with just one month of development time. The reason for this shorter time is that we want to get some of the new features into RHEL 7.7, and

Listing currently registered secret agents?

Is there any way to see which secret agents are currently registered with NM? basically to see where user connection secrets may be stored? Thank you! ___ networkmanager-list mailing list networkmanager-list@gnome.org

Re: How to deal with a new Wifi Adapter?

Thanks. -derek Thomas Haller writes: > On Thu, 2019-04-11 at 10:16 -0400, Derek Atkins wrote: >> Thanks, Thomas, >> >> Thomas Haller via networkmanager-list >> writes: >> >> [snip] >> >> Any chance you could give a quick explanation of what these (two?) >> sets >> of commands are doing? >

Re: How to deal with a new Wifi Adapter?

On Thu, 2019-04-11 at 10:16 -0400, Derek Atkins wrote: > Thanks, Thomas, > > Thomas Haller via networkmanager-list > writes: > > [snip] > > Any chance you could give a quick explanation of what these (two?) > sets > of commands are doing? Hi, UUIDS is a variable containing all the

Re: How to deal with a new Wifi Adapter?

Thanks, Thomas, Thomas Haller via networkmanager-list writes: [snip] Any chance you could give a quick explanation of what these (two?) sets of commands are doing? Thanks, -derek > Hi, > > I'd do: > > UUIDS="$(nmcli -g TYPE,UUID connection show | \ > sed -n

Re: How to deal with a new Wifi Adapter?

On Wed, 2019-04-10 at 12:24 -0400, Derek Atkins wrote: > Hi, > I'm currently running Fedora 29 and my embedded wifi adapter is > failing. So I bought a USB Wifi adapter, which seems to be working > well.. Except for one problem: Network Manager does not know to > apply > all my existing wifi

How to deal with a new Wifi Adapter?

Hi, I'm currently running Fedora 29 and my embedded wifi adapter is failing. So I bought a USB Wifi adapter, which seems to be working well.. Except for one problem: Network Manager does not know to apply all my existing wifi connection information to the new adapter. Short of going through

[NetworkManager - 0.9.4] - dhclient v6

Hi, I m trying to use the older version of Networkmanager i.e 0.9.4, because of dependency on version of libc(2.15) running in my board. Intention is to assign ipv6 address to one interface(eth3) using dhcpv6, but I always see that dhclient -4 is getting invoked. cat

Re: Adding basic OpenVPN PKCS#11 support

On Tue, 2019-03-26 at 08:41 +0100, Martin Forssen via networkmanager- list wrote: > Hello, > > I have the need to run OpenVPN with PKCS#11 hardware certificates on > Linux. This does currently not seem to be possible with > NetworkManager. > > I have looked around a bit and realize this is a can

Re: openvpn: "Authenticate/Decrypt packet error: bad packet ID", link-mtu=1472 consequences

On Wed, 2019-03-27 at 18:56 +, avemilia via networkmanager-list wrote: > Sorry, I have assumed that the VPN tunnel is up with this link-mtu > setting, but > in reality it is not. Hi, Try: sudo nmcli general logging level TRACE domains ALL,VPN_PLUGIN:TRACE and reactivate the VPN

Re: openvpn: "Authenticate/Decrypt packet error: bad packet ID", link-mtu=1472 consequences

Sorry, I have assumed that the VPN tunnel is up with this link-mtu setting, but in reality it is not. Now I have spotted in the journal: > [...] vpn-connection[...]: VPN connection: failed to connect: > 'property “link-mtu” invalid or not supported' So, instead I am looking for a working

openvpn: "Authenticate/Decrypt packet error: bad packet ID", link-mtu=1472 consequences

Hello list, openSUSE Tumbleweed (KDE Plasma) NetworkManager-1.16.0-1.1.x86_64 NetworkManager-openvpn-1.8.10-1.1.x86_64 with this openvpn configuration: > [vpn] > auth= > ca= > cipher= > comp-lzo=adaptive > connection-type=password > float=no > mssfix=no > password-flags=1 > port= > proto-tcp=no

Re: Reciving multiple RAs causes NetworkManager to storm the network with RSes

On Fri, 2019-02-15 at 09:05 +0100, Thomas Haller via networkmanager- list wrote: > > Hi, Hi Thomas, > Best way is: > > - first disable ratelimiting in journald. For that, set > RateLimitIntervalSec=0 in /etc/systemd/journald.conf and > `systemctl restart systemd-journald.service` > > -

Re: [nmstate] [RFC] ip route partial editing vs whole-state editing

On Thu, Mar 21, 2019 at 11:02 AM Till Maas wrote: > Hi, > > Am Do., 21. März 2019 um 09:16 Uhr schrieb Edward Haas >: > > > > > > > > On Wed, Mar 20, 2019 at 8:35 PM Till Maas wrote: > >> > >> Hi, > >> > >> Am Mi., 20. März 2019 um 18:13 Uhr schrieb Edward Haas via > >> networkmanager-list : >

Re: [nmstate] [RFC] ip route partial editing vs whole-state editing

Hi, Am Do., 21. März 2019 um 09:16 Uhr schrieb Edward Haas : > > > > On Wed, Mar 20, 2019 at 8:35 PM Till Maas wrote: >> >> Hi, >> >> Am Mi., 20. März 2019 um 18:13 Uhr schrieb Edward Haas via >> networkmanager-list : >> > >> > >> > >> > On Wed, Mar 13, 2019 at 3:48 PM Gris Ge via

Re: [nmstate] [RFC] ip route partial editing vs whole-state editing

On Wed, Mar 20, 2019 at 8:35 PM Till Maas wrote: > Hi, > > Am Mi., 20. März 2019 um 18:13 Uhr schrieb Edward Haas via > networkmanager-list : > > > > > > > > On Wed, Mar 13, 2019 at 3:48 PM Gris Ge via networkmanager-list < > networkmanager-list@gnome.org> wrote: > >> > >> Hi Guys, > >> > >> For

Re: [nmstate] [RFC] ip route partial editing vs whole-state editing

Hi, Am Mi., 20. März 2019 um 18:13 Uhr schrieb Edward Haas via networkmanager-list : > > > > On Wed, Mar 13, 2019 at 3:48 PM Gris Ge via networkmanager-list > wrote: >> >> Hi Guys, >> >> For the IP route editing in nmstate, the parietal editing is >> problematic: >> >> User case A: >>

Re: [nmstate] [RFC] ip route partial editing vs whole-state editing

Hi, Am Mi., 13. März 2019 um 14:48 Uhr schrieb Gris Ge via networkmanager-list : > > * nmstate.netapplier.add() # Add new stuff > * nmstate.netapplier.edit() # Override existing stuff > * nmstate.netapplier.remove() # Remove stuff > > Any comments

Re: automatic APN selection

Hi, On Mon, Mar 18, 2019 at 5:23 PM Lubomir Rintel wrote: > > Ahoj, > > On Tue, 2019-02-12 at 11:49 +0100, Belisko Marek via networkmanager- > list wrote: > > Hello, > > > > I posted yesterday question to ModemManger mailing list about implementing > > automatic APN selection (based on mobile

Re: automatic APN selection

Ahoj, On Tue, 2019-02-12 at 11:49 +0100, Belisko Marek via networkmanager- list wrote: > Hello, > > I posted yesterday question to ModemManger mailing list about implementing > automatic APN selection (based on mobile broadband database) and it was > pointed [0] out that this feature should be

Re: NetworkManager, ModemManager, and pppd

On Thu, 2019-03-14 at 16:52 +1300, Harry Mander via networkmanager-list wrote: > Hi, > > I have a PPP connection brought up by pppd running on a ttyUSB > connection > to an LTE modem, which is managed by ModemManager. When pppd is > started > after simple-connecting the modem using ModemManager

ANN: NetworkManager 1.16.0 released

Hi, today we released NetworkManager 1.16.0. See the NEWS file https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?id=1.16.0 and the overview written by Lubomir https://blogs.gnome.org/lkundrak/2019/03/15/networkmanager-1-16/ Find the tarball at our usual location:

NetworkManager, ModemManager, and pppd

Hi, I have a PPP connection brought up by pppd running on a ttyUSB connection to an LTE modem, which is managed by ModemManager. When pppd is started after simple-connecting the modem using ModemManager it is able to get an IP address fine (which can be seen from ifconfig and ip route etc.) and I

[nmstate] [RFC] ip route partial editing vs whole-state editing

Hi Guys, For the IP route editing in nmstate, the parietal editing is problematic: User case A: Current routes: 1.1.1.0/24 via 2.2.2.2 dev eth1 Desired routes: changed next hope to 3.3.3.3 User case B: Current routes: 1.1.1.0/24 via 2.2.2.2 dev eth1

ANN: NetworkManager 1.15.91 (1.16-rc2) released

Hi, there is now a second release candidate for upcoming 1.16.0. While it was planned to release 1.16.0 shortly after 1.16-rc1 [1], there were some issue which warrant a delay and this second release- candidate. There are API and ABI changes compared to 1.16-rc1. Notable changes are: -

Re: [PATCH] tests: Fix variant_from_dbus() for arrays of UInt32

On Wed, 2019-03-06 at 11:59 +0100, Frédéric Danis via networkmanager- list wrote: > Using test-networkmanager-servic.py, I get the following error when > trying to add manual config with a dns address: > Hi, looks good. Merged as

[PATCH] tests: Fix variant_from_dbus() for arrays of UInt32

Using test-networkmanager-servic.py, I get the following error when trying to add manual config with a dns address: Error: g-io-error-quark: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/dbus/service.py", line 707, in _message_cb retval = candidate_method(self,

Re: [RFC] [nmstate] Linux routing in nmstate

Hi Guys, I believe we can cast vote on these options based on feedback: Option A: https://gist.github.com/cathay4t/70b69bda1de0f60ec533bf98fdc04f95 Notes: * The basic layout: info['routes'][0] = * Each route entry will have 'family' property. * The route protocol

Re: [RFC] [nmstate] Linux routing in nmstate

On Tue, Mar 5, 2019 at 9:35 AM Edward Haas wrote: > > > On Tue, Mar 5, 2019 at 9:25 AM Gris Ge wrote: > >> On Mon, Mar 04, 2019 at 05:58:01PM +0100, Thomas Haller wrote: >> > On Mon, 2019-03-04 at 22:11 +0800, Gris Ge wrote: >> > > * Top tree is 'routes', and subtree is 'ipv4' and 'ipv6'. >> >

Re: [RFC] [nmstate] Linux routing in nmstate

On Tue, Mar 5, 2019 at 9:25 AM Gris Ge wrote: > On Mon, Mar 04, 2019 at 05:58:01PM +0100, Thomas Haller wrote: > > On Mon, 2019-03-04 at 22:11 +0800, Gris Ge wrote: > > > * Top tree is 'routes', and subtree is 'ipv4' and 'ipv6'. > > >Even the IPv4 and IPv6 route entry are mostly identical,

Re: [RFC] [nmstate] Linux routing in nmstate

On Mon, Mar 04, 2019 at 05:58:01PM +0100, Thomas Haller wrote: > On Mon, 2019-03-04 at 22:11 +0800, Gris Ge wrote: > > * Top tree is 'routes', and subtree is 'ipv4' and 'ipv6'. > >Even the IPv4 and IPv6 route entry are mostly identical, but we > > need > >schema to differentiate the

Re: [RFC] [nmstate] Linux routing in nmstate

On Mon, Mar 4, 2019 at 6:58 PM Thomas Haller wrote: > On Mon, 2019-03-04 at 22:11 +0800, Gris Ge wrote: > > Based on feedbacks, this is V2 scheme for review: > > > > ``` > > { > > "routes": { > > "ipv4": [ # Sorted with 'table-id' then > > 'destination' > >

Re: [RFC] [nmstate] Linux routing in nmstate

On Mon, 2019-03-04 at 22:11 +0800, Gris Ge wrote: > Based on feedbacks, this is V2 scheme for review: > > ``` > { > "routes": { > "ipv4": [ # Sorted with 'table-id' then > 'destination' > { > "status": "up", >

Re: [RFC] [nmstate] Linux routing in nmstate

Based on feedbacks, this is V2 scheme for review: ``` { "routes": { "ipv4": [ # Sorted with 'table-id' then 'destination' { "status": "up", # up or absent(to be removed) # If not

Re: [RFC] [nmstate] Linux routing in nmstate

On Fri, Mar 1, 2019 at 9:41 AM Thomas Haller wrote: > On Thu, 2019-02-28 at 22:40 +0200, Edward Haas via networkmanager-list > wrote: > > Thank you Gris. > > Comments in-line. > > > > On Tue, Feb 26, 2019 at 8:56 AM Gris Ge wrote: > > > Hi Guys, > > > > > > Could you review below schema for

Re: [RFC] [nmstate] Linux routing in nmstate

On Fri, Mar 1, 2019 at 9:43 AM Thomas Haller wrote: > Hi, > > On Tue, 2019-02-26 at 14:56 +0800, Gris Ge via networkmanager-list > > > "protocol": "dhcp", # "static" or "dhcp" > > "protocol" sounds a bit like iproute2's "protocol" option (struct > rtmsg's rtm_protocol). But I

Re: [RFC] [nmstate] Linux routing in nmstate

Hi, On Tue, 2019-02-26 at 14:56 +0800, Gris Ge via networkmanager-list > "protocol": "dhcp", # "static" or "dhcp" "protocol" sounds a bit like iproute2's "protocol" option (struct rtmsg's rtm_protocol). But I think it's not. I would call this "source". best, Thomas

Re: [RFC] [nmstate] Linux routing in nmstate

On Thu, 2019-02-28 at 22:40 +0200, Edward Haas via networkmanager-list wrote: > Thank you Gris. > Comments in-line. > > On Tue, Feb 26, 2019 at 8:56 AM Gris Ge wrote: > > Hi Guys, > > > > Could you review below schema for routing in nmstate before we > > start > > add routing support in

Re: [RFC] [nmstate] Linux routing in nmstate

On Fri, Mar 1, 2019 at 4:34 AM Gris Ge wrote: > On Thu, Feb 28, 2019 at 10:40:48PM +0200, Edward Haas wrote: > > > > What is the root level key? `routing`? > The root level is 'ipv4-routes' and 'ipv6-routes'. > > Try to save a layer for user to type comparing to ['routing']['routes'] > > The ip

Re: [RFC] [nmstate] Linux routing in nmstate

On Thu, Feb 28, 2019 at 10:40:48PM +0200, Edward Haas wrote: > > What is the root level key? `routing`? The root level is 'ipv4-routes' and 'ipv6-routes'. Try to save a layer for user to type comparing to ['routing']['routes'] > ipv4 and ipv6 look identical to me here. > It makes sense then to

Re: [RFC] [nmstate] Linux routing in nmstate

Thank you Gris. Comments in-line. On Tue, Feb 26, 2019 at 8:56 AM Gris Ge wrote: > Hi Guys, > > Could you review below schema for routing in nmstate before we start > add routing support in nmstate? > > ``` > What is the root level key? `routing`? { > "ipv4-routes": [# Sorted

Re: NM 1.14.6 build error

On Tue, 2019-02-26 at 09:03 +0200, Cristian Crinteanu wrote: > .. > src/settings/plugins/ifcfg-rh/nms-ifcfg-rh-reader.c: In function > ‘discover_mac_address’: > src/settings/plugins/ifcfg-rh/nms-ifcfg-rh-reader.c:572:15: error: > storage size of ‘ifr’ isn’t known > struct ifreq ifr; >

NM 1.14.6 build error

.. src/settings/plugins/ifcfg-rh/nms-ifcfg-rh-reader.c: In function ‘discover_mac_address’: src/settings/plugins/ifcfg-rh/nms-ifcfg-rh-reader.c:572:15: error: storage size of ‘ifr’ isn’t known struct ifreq ifr; ^~~ src/settings/plugins/ifcfg-rh/nms-ifcfg-rh-reader.c:590:32:

[RFC] [nmstate] Linux routing in nmstate

Hi Guys, Could you review below schema for routing in nmstate before we start add routing support in nmstate? ``` { "ipv4-routes": [# Sorted with 'table-id' then 'destination' { "table-name": "main", # Empty if no name attached

<    5   6   7   8   9   10   11   12   13   14   >