Package: ifupdown2
Version: 3.0.0-1
Severity: normal
X-Debbugs-Cc: bluestonech...@gmail.com

Dear Maintainer,

I configure tincvpn interface as follow:

auto tincvpn
iface tincvpn inet static
        address 10.100.6.5/24
        tinc-net do
        tinc-debug 1
        tinc-user nobody
        tinc-pidfile /tmp/tinc.pid
        tinc-logfile /tmp/tinc.log

When I use ifup from ifupdown2 to bringup this interface, the interface is 
bringed up, but the address is not assigned. 

If I switchback to ifupdown, the tincvpn interface can be bringed up and the ip 
address is assigned too.

-- System Information:
Debian Release: 11.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-9-amd64 (SMP w/56 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ifupdown2 depends on:
ii  iproute2  5.10.0-4
ii  python3   3.9.2-3

ifupdown2 recommends no packages.

Versions of packages ifupdown2 suggests:
pn  bridge-utils     <none>
pn  ethtool          <none>
ii  isc-dhcp-client  4.4.1-2.3
pn  python3-gvgen    <none>
pn  python3-mako     <none>

Reply via email to