ConnMan network manager
 help / color / mirror / Atom feed
From: Grant Erickson <gerickson@nuovations.com>
To: connman@lists.linux.dev
Subject: When 'EnableOnlineCheck' Is Asserted Two Recurring IPv4 and One IPv6 Reachability Checks Get Scheduled
Date: Mon, 13 Nov 2023 10:38:28 -0800	[thread overview]
Message-ID: <5B0B6864-28B9-4891-B30A-6024F9D8CED8@nuovations.com> (raw)

ConnMan Community:

The latest issue I am jumping into in top-of-tree now that the two heap-use-after-free issues have been
addressed is "When 'EnableOnlineCheck' Is Asserted Two (2) Recurring IPv4 and One (1) IPv6
Reachability Checks Get Scheduled” rather than one of each. Feel free to track progress here:

    https://github.com/Nuovations/connman/issues/74

Best,

Grant

-- 
Principal
Nuovations

gerickson@nuovations.com
http://www.nuovations.com/


             reply	other threads:[~2023-11-13 18:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-13 18:38 Grant Erickson [this message]
2023-11-13 23:16 ` When 'EnableOnlineCheck' Is Asserted Two Recurring IPv4 and One IPv6 Reachability Checks Get Scheduled Grant Erickson
2023-11-14 15:45   ` Grant Erickson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5B0B6864-28B9-4891-B30A-6024F9D8CED8@nuovations.com \
    --to=gerickson@nuovations.com \
    --cc=connman@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).