The upstream source doesn't have the error:
https://salsa.debian.org/debian/ifupdown/-/blob/master/debian/if-up.d/resolved#L69
--
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/bug
My apologies, I neglected to specify these details:
OS: Ubuntu 22.04.2 LTS
Package: ifupdown
Version: 0.8.36+nmu1ubuntu3
It's the latest version of ifupdown.
** Package changed: systemd (Ubuntu) => ifupdown (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch
Whoops, found another bug:
```
# ifup enp2s0
/etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-enp2s0:
DNS=1.1.1.1: not found
/etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-enp2s0:
DOMAINS=example.org: not found
Failed to parse DNS server address: DNS
Failed to set DNS
After fixing those lines, there's yet another bug:
```
search example.org DOMAINS
```
Somehow it's deciding that the DNS search domains for static interfaces is
"DOMAINS". Sample /etc/network/interface file:
```
auto enp3s0
iface enp3s0 inet static
address 172.16.198.5
netmask 25
There's another similar typo in the /etc/network/if-up.d/resolved script, on
line 71:
```
if ! cmp --silent "$oldstate" "$newstate" 2>/dev/null; then
DNS DNS6 DOMAINS DOMAINS6 DEFAULT_ROUTE
# v4 first
```
Comment it out, as it's not valid code.
--
You received this bug notifi
** Description changed:
This error happens when you try to run ifup or ifdown:
```
# ifdown enp3s0
/etc/network/if-down.d/resolved: 12: mystatedir: not found
# ifup enp3s0
/etc/network/if-up.d/resolved: 12: mystatedir: not found
```
Here's the first 12 lines of those scrip
6 matches
Mail list logo