Dear Debian community, I've exercised several directions to solve the issue, however I've failed. Would be great if somebody can share his idea. After upgrading from Debian buster to bullseye I still have the same issue:
# systemctl status networking.service — networking.service - Raise network interfaces Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2022-04-04 00:37:29 CEST; 31min ago Docs: man:interfaces(5) Process: 1287 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE) Main PID: 1287 (code=exited, status=1/FAILURE) CPU: 83ms Apr 04 00:37:28 debian systemd[1]: Starting Raise network interfaces... Apr 04 00:37:28 debian ifup[1287]: ifup: unknown interface eth0 Apr 04 00:37:28 debian ifup[1287]: ifup: unknown interface eth1 Apr 04 00:37:29 debian systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE Apr 04 00:37:29 debian systemd[1]: networking.service: Failed with result 'exit-code'. Apr 04 00:37:29 debian systemd[1]: Failed to start Raise network interfaces. Up-to-date log: Apr 4 00:37:28 debian ifup[1287]: ifup: unknown interface eth0 Apr 4 00:37:28 debian ifup[1287]: ifup: unknown interface eth1 Apr 4 00:37:28 debian kernel: [ 1.049742] r8169 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control Apr 4 00:37:28 debian kernel: [ 1.066552] r8169 0000:02:00.0 eth0: RTL8168g/8111g, 00:17:e8:92:b7:77, XID 4c0, IRQ 30 Apr 4 00:37:28 debian kernel: [ 1.066553] r8169 0000:02:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko] Apr 4 00:37:28 debian kernel: [ 1.066581] r8169 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control Apr 4 00:37:28 debian kernel: [ 10.804450] r8169 0000:02:00.0 eth0: renamed from enp2s0 Apr 4 00:37:28 debian kernel: [ 10.825386] r8169 0000:03:00.0 eth1: renamed from enp3s0 Apr 4 00:37:28 debian kernel: [ 1.082558] r8169 0000:03:00.0 eth1: RTL8168g/8111g, 00:17:20:53:44:58, XID 4c0, IRQ 32 Apr 4 00:37:28 debian kernel: [ 1.082560] r8169 0000:03:00.0 eth1: jumbo features [frames: 9194 bytes, tx checksumming: ko] Apr 4 00:37:28 debian kernel: [ 1.083615] r8169 0000:02:00.0 enp2s0: renamed from eth0 Apr 4 00:37:28 debian kernel: [ 1.108937] r8169 0000:03:00.0 enp3s0: renamed from eth1 Apr 4 00:37:28 debian kernel: [ 21.674276] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this. Apr 4 00:37:28 debian kernel: [ 21.681297] br0: port 1(eth0) entered blocking state Apr 4 00:37:28 debian kernel: [ 21.681300] br0: port 1(eth0) entered disabled state Apr 4 00:37:28 debian kernel: [ 21.681355] device eth0 entered promiscuous mode Apr 4 00:37:28 debian kernel: [ 21.684702] r8169 0000:02:00.0: firmware: direct-loading firmware rtl_nic/rtl8168g-2.fw Apr 4 00:37:28 debian kernel: [ 21.716835] Generic FE-GE Realtek PHY r8169-0-200:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-0-200:00, irq=IGNORE) Apr 4 00:37:28 debian kernel: [ 21.921156] r8169 0000:02:00.0 eth0: Link is Down Apr 4 00:37:28 debian kernel: [ 21.921770] br0: port 2(eth1) entered blocking state Apr 4 00:37:28 debian kernel: [ 21.921772] br0: port 2(eth1) entered disabled state Apr 4 00:37:28 debian kernel: [ 21.921822] device eth1 entered promiscuous mode Apr 4 00:37:28 debian kernel: [ 21.948807] Generic FE-GE Realtek PHY r8169-0-300:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-0-300:00, irq=IGNORE) Apr 4 00:37:28 debian kernel: [ 22.157113] r8169 0000:03:00.0 eth1: Link is Down Apr 4 00:37:28 debian kernel: [ 22.158495] br0: port 2(eth1) entered blocking state Apr 4 00:37:28 debian kernel: [ 22.158498] br0: port 2(eth1) entered forwarding state Apr 4 00:37:28 debian kernel: [ 22.158511] br0: port 1(eth0) entered blocking state Apr 4 00:37:28 debian kernel: [ 22.158513] br0: port 1(eth0) entered forwarding state Apr 4 00:37:28 debian sh[329]: ifquery: unknown interface eth0 Apr 4 00:37:28 debian sh[329]: ifquery: unknown interface eth1 Apr 4 00:37:28 debian systemd[1]: Finished Helper to synchronize boot up for ifupdown. Apr 4 00:37:28 debian systemd[1]: Started Hostname Service. Apr 4 00:37:28 debian systemd[1]: Starting Hostname Service... Apr 4 00:37:28 debian systemd[1]: Starting Raise network interfaces... Apr 4 00:37:28 debian systemd-udevd[335]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. Apr 4 00:37:28 debian systemd-udevd[342]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. Apr 4 00:37:29 debian hostapd[1627]: Using interface wlan0 with hwaddr 00:07:71:de:5f:b5 and ssid "Guest" Apr 4 00:37:29 debian hostapd[1627]: wlan0: AP-ENABLED Apr 4 00:37:29 debian hostapd[1627]: wlan0: interface state UNINITIALIZED->ENABLED Apr 4 00:37:29 debian kernel: [ 22.487228] br0: port 3(wlan0) entered blocking state Apr 4 00:37:29 debian kernel: [ 22.487233] br0: port 3(wlan0) entered disabled state Apr 4 00:37:29 debian kernel: [ 22.487279] device wlan0 entered promiscuous mode Apr 4 00:37:29 debian kernel: [ 22.487298] br0: port 3(wlan0) entered blocking state Apr 4 00:37:29 debian kernel: [ 22.487299] br0: port 3(wlan0) entered forwarding state Apr 4 00:37:29 debian kernel: [ 22.676802] br0: port 1(eth0) entered disabled state Apr 4 00:37:29 debian kernel: [ 22.676917] br0: port 2(eth1) entered disabled state Apr 4 00:37:29 debian systemd[1]: Failed to start Raise network interfaces. Apr 4 00:37:29 debian systemd[1]: networking.service: Failed with result 'exit-code'. Apr 4 00:37:29 debian systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE Apr 4 00:37:31 debian kernel: [ 24.515701] r8169 0000:02:00.0 eth0: Link is Up - 1Gbps/Full - flow control rx/tx Apr 4 00:37:31 debian kernel: [ 24.515722] br0: port 1(eth0) entered blocking state Apr 4 00:37:31 debian kernel: [ 24.515727] br0: port 1(eth0) entered forwarding state What confuses me is that hostapd is configured to run after network.target, but in fact is running together with it. Maybe there is a side effect when hostapd adds wlan0 to br0? On 2021-02-17 15:38, Gary Dale wrote: > On 2021-02-17 08:28, Andrei POPESCU wrote: >> On Mi, 17 feb 21, 00:01:01, Gary Dale wrote: >>> On 2021-02-16 19:44, Dmitry Katsubo wrote: >>>> Dear Debian community, >>>> >>>> I am puzzled with the following problem. When my Debian 10.8 starts, the >>>> unit "networking.service" is >>>> marked as failed with the following reason: >>>> >>>> root@debian:~ # systemctl status networking.service >>>> *— networking.service - Raise network interfaces >>>> Loaded: loaded (/lib/systemd/system/networking.service; enabled; >>>> vendor preset: enabled) >>>> Active: failed (Result: exit-code) since Tue 2021-02-16 08:56:16 CET; >>>> 5h 27min ago >>>> Docs: man:interfaces(5) >>>> Process: 691 ExecStart=/sbin/ifup -a --read-environment (code=exited, >>>> status=1/FAILURE) >>>> Main PID: 691 (code=exited, status=1/FAILURE) >>> Debian/Busteris still using Network Manager not systemd to control the >>> network so I think the network.service shouldn't be used. >> Well, systemd as init is starting everything so that necessarily >> includes starting "the network", which in practice means starting >> whatever network management framework is in use[1]. >> >> The 'networking.service' service is part of ifupdown, Debian's default >> network management framework (Priority: important). >> >> Network Manager is Priority: optional and typically installed as a >> Depends/Recommends of Desktop Environments. >> >> [1] this is applicable even for systemd's own network management >> framework systemd-networkd, which is included in the 'systemd' Debian >> package, but not activated by default. >> >> Kind regards, >> Andrei > Sorry, it was midnight when I replied. However the failure is likely still > due to the interfaces misconfiguration - probably reporting a failure to > raise a non-existent interface. > On 2021-02-17 07:55, Reco wrote: > Try running this: > > ifdown -a --force > ifup -a -v > > Last command should show you the source of the trouble. > > Reco Reco, here is the log: # ifdown -a --force; ifup -a -v /bin/run-parts --exit-on-error --verbose /etc/network/if-pre-up.d run-parts: executing /etc/network/if-pre-up.d/bridge run-parts: executing /etc/network/if-pre-up.d/ethtool run-parts: executing /etc/network/if-pre-up.d/hostapd run-parts: executing /etc/network/if-pre-up.d/wireless-tools run-parts: executing /etc/network/if-pre-up.d/wpasupplicant ifup: configuring interface lo=lo (inet) /bin/run-parts --exit-on-error --verbose /etc/network/if-pre-up.d run-parts: executing /etc/network/if-pre-up.d/bridge run-parts: executing /etc/network/if-pre-up.d/ethtool run-parts: executing /etc/network/if-pre-up.d/hostapd run-parts: executing /etc/network/if-pre-up.d/wireless-tools run-parts: executing /etc/network/if-pre-up.d/wpasupplicant /sbin/ip link set dev lo up /bin/run-parts --exit-on-error --verbose /etc/network/if-up.d run-parts: executing /etc/network/if-up.d/avahi-autoipd run-parts: executing /etc/network/if-up.d/ethtool run-parts: executing /etc/network/if-up.d/wpasupplicant ifup: unknown interface eth0 ifup: unknown interface eth1 ifup: configuring interface br0=br0 (inet) /bin/run-parts --exit-on-error --verbose /etc/network/if-pre-up.d run-parts: executing /etc/network/if-pre-up.d/bridge run-parts: executing /etc/network/if-pre-up.d/ethtool run-parts: executing /etc/network/if-pre-up.d/hostapd run-parts: executing /etc/network/if-pre-up.d/wireless-tools run-parts: executing /etc/network/if-pre-up.d/wpasupplicant /sbin/ip addr add 192.168.10.1/255.255.255.0 broadcast 192.168.10.255 dev br0 label br0 /sbin/ip link set dev br0 up /sbin/ip route add default via 192.168.10.254 dev br0 onlink /bin/run-parts --exit-on-error --verbose /etc/network/if-up.d run-parts: executing /etc/network/if-up.d/avahi-autoipd run-parts: executing /etc/network/if-up.d/ethtool run-parts: executing /etc/network/if-up.d/wpasupplicant Has anything drawn your attention? On 2021-02-17 14:21, Henning Follmann wrote: > Are you using eth0, eth1? > Or are you using predictable network names? > https://wiki.debian.org/NetworkInterfaceNames Well, I use eth0/eth1 as I have renamed them from predictable network names via /etc/udev/rules.d/70-persistent-net.rules: ACTION=="add", SUBSYSTEM=="net", ATTR{address}=="00:17:e8:92:b7:77", KERNEL=="eth*", NAME="eth0" ACTION=="add", SUBSYSTEM=="net", ATTR{address}=="00:17:20:53:44:58", KERNEL=="eth*", NAME="eth1" Thanks in advance! -- With best regards, Dmitry
