Package: ifupdown Version: 0.7.53.1 Severity: normal Dear Maintainer,
I need to set some properties on a network interface BEFORE it is brought up. So I use a script in if-pre-up.d that sets said properties. This works fine if the interface is "auto". I had to change this to "allow-hotplug" because there can be one or two of those interfaces. However, in the case of "allow-hotplug", someone else sets the interface to "up" before ifup runs. This breaks my usecase and the interface is not setup correctly after boot. I don't know who brings the interface up too early, I searched in udev/systemd and ifupdown, but couldn't find out who is responsible. Any help appreciated. For the interested: I set network coalesce options with ethtools to disable interrupt throttling. But for some reason, this is not reliable when I do this while the interface is coming up (that is after ifconfig up). I suspect some kind of race inside the driver (e1000e and igb). Thanks! Christoph -- System Information: Debian Release: 8.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.4.15-realtime-1-rt23 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ifupdown depends on: ii adduser 3.113+nmu3 ii initscripts 2.88dsf-59 ii iproute 1:3.16.0-2 ii iproute2 3.16.0-2 ii libc6 2.19-18+deb8u4 ii lsb-base 4.1+Debian13+nmu1 Versions of packages ifupdown recommends: ii isc-dhcp-client [dhcp-client] 4.3.1-6+deb8u2 Versions of packages ifupdown suggests: ii net-tools 1.60-26+b1 pn ppp <none> pn rdnssd <none> -- no debconf information
