Thanks, the upstream bug reference is

** Bug watch added: #1147

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

** Changed in: network-manager (Ubuntu)
       Status: Confirmed => Triaged

** Also affects: network-manager via
   Importance: Unknown
       Status: Unknown

You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.

  network-manager fails to trigger dispatcher scripts with action
  dhcp4-change when dhcp lease is renewed

Status in NetworkManager:
Status in network-manager package in Ubuntu:

Bug description:
  We rely on network-manager dispatcher scripts on our desktop and
  laptop computers. The dispatcher scripts are used to update DNS
  records with nsupdate when the dhcp lease is renewed.

  With jammy this is not working anymore. It seems that dispatcher
  scripts are run only when the interface comes up (with action 'up')
  and with the initial dhcp lease (with action 'dhcp4-change'), but when
  the lease is renewed, the dispatcher scripts are not run with any
  action. The only action the dispatcher scripts are run regularly with
  is 'connectivity-change', which seems to occur twice in a row every
  few hours.

  I have made a simple script to log how the dispatcher scripts are run:

  echo $(date) 0: $0 IFACE: $1 ACTION: $2 >> /tmp/nm.log

  This script proves that action 'dhcp4-change' only occurs when I
  manually restart NetworkManager.service or unplug and replug the
  ethernet cable.

  network-manager version: 1.36.6-0ubuntu2

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to