This bug was fixed in the package ifupdown - 0.8.36+nmu1ubuntu3.1
---
ifupdown (0.8.36+nmu1ubuntu3.1) jammy; urgency=medium
[ Uwe Kleine-König ]
* Fix if-up.d/resolved hook to properly work with nameservers and search
domains (LP: #1981103)
[ Heinrich Schuchardt ]
*
This bug was fixed in the package ifupdown - 0.8.36+nmu1ubuntu4.1
---
ifupdown (0.8.36+nmu1ubuntu4.1) lunar; urgency=medium
[ Uwe Kleine-König ]
* Fix if-up.d/resolved hook to properly work with nameservers and search
domains (LP: #1981103)
-- Heitor Alves de Siqueira
Validated for Jammy according to test case from description. No error
messages were thrown, and networking has been correctly set up.
root@halves-lp1981103-j:~# ifdown enp5s0; ifup enp5s0
Killed old client process
Internet Systems Consortium DHCP Client 4.4.1
Copyright 2004-2018 Internet Systems
Validated for Lunar according to test case from description. No error
messages were thrown, and networking has been correctly set up.
root@halves-lp1981103-l:~# ifdown enp5s0; ifup enp5s0
Killed old client process
Internet Systems Consortium DHCP Client 4.4.3-P1
Copyright 2004-2022 Internet
Hello Uwe, or anyone else affected,
Accepted ifupdown into lunar-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/ifupdown/0.8.36+nmu1ubuntu4.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Focal isn't affected by this, so marking it as Fix Released.
** Changed in: ifupdown (Ubuntu Focal)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
** Description changed:
+ [ Impact ]
+ ifupdown configurations will stop having a working DNS server on upgrade
+
+ [ Test Plan ]
+ Upgrading from an Ubuntu 18.04 or earlier release, bounce a network interface
with configured DNS server:
+
+ root@pangaea-pm:~# ifdown ens13; ifup ens13
+
This bug was fixed in the package ifupdown - 0.8.36+nmu1ubuntu5
---
ifupdown (0.8.36+nmu1ubuntu5) mantic; urgency=medium
[ Uwe Kleine-König ]
* Fix if-up.d/resolved hook to properly work with nameservers and search
domains (LP: #1981103)
-- Heitor Alves de Siqueira Wed,
Thanks. The 0.8.41 Debian package contains this fix already (so no
forwarding needed). So uploaded to mantic (included some trailing space
removals).
** Changed in: ifupdown (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of
** Patch added: "lp1981103.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1981103/+attachment/5698057/+files/lp1981103.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
I've attached a debdiff with the patches for fixing this one. I've
subscribed ubuntu-sponsors to kindly request sponsorship for mantic.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
Thank you for describing the solution in this bug report.
Could somebody come up with a patch/debdiff, so that any MOTU could test
& sponsor the ifupdown fix into universe?
** Tags removed: foundations-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
*This* bug has the full information in the first post including all
needed to fix the problem. Actually there are more problems in the
script regarding syntax, so more issues exist, leading to unwanted
behavior.
Uwe
Am 22. Oktober 2022 22:05:59 MESZ schrieb David Kowis
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1910273
This one seems to have the full patch repair in the bug description.
None of the other bugs I've found relating to this have the full
solution.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Tags added: foundations-triage-discuss
** Changed in: ifupdown (Ubuntu)
Status: Confirmed => Triaged
** Changed in: ifupdown (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Deleted my incorrect comment about the use of "local", that doesn't
work. https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1907878
has the correct fix.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in
The same error also happened in the ifdown script for resolved. Weird.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1981103
Title:
System with DNS server in
Affecting me too on 22.04. By comparing with isc-dhcp-client's
/etc/dhcp/dhclient-exit-hooks.d/resolved I reckon the missing keyword
for those variable declartions is "local" i.e.
local DNS DNS6 DOMAINS DOMAINS6 DEFAULT_ROUTE
and so on.
--
You received this bug notification because you are a
If you changed away from /etc/network/interfaces file to netplan.io
configuration (/etc/netplan/...) then you won't need ifupdown. There is
a configuartion tool, with simple configs it works: See this info how to
convert your network config. But be sure to have physical access to the
machine's
+1, can I simply remove ifupdown (e.g. apt remove ifupdown), do I still
need it with 22.04.1?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1981103
Title:
System with
This is affecting me too. It's only happening on systems that started
life as Ubuntu 18.04 and earlier - any server that was installed as
20.04 is upgrading to 22.04 without problem. Once I make the same change
as Uwe, systemd-resolved is getting configured correctly.
--
You received this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ifupdown (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
One addition, line 71 in script also looks strange:
if ! cmp --silent "$oldstate" "$newstate" 2>/dev/null; then
DNS DNS6 DOMAINS DOMAINS6 DEFAULT_ROUTE
This causes:
/etc/network/if-up.d/resolved: 71: DNS: not found
If you are on it, please fix this, too.
--
You received this bug
I think this should unset the variables, then error goes away and it
makes sense!
if ! cmp --silent "$oldstate" "$newstate" 2>/dev/null; then
unset DNS DNS6 DOMAINS DOMAINS6 DEFAULT_ROUTE
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
24 matches
Mail list logo
