#405 Issue closed: Network interfaces not recognized in recent version¶
Labels: enhancement, support / question, fixed / solved / done
ypid opened issue at 2014-05-02 16:42:¶
Hi
I noticed that current rear master checkout does not show any network interfaces (except of lo) in recover mode with a current Debian testing amd64 system.
I was able to track the commit down which introduced this behavior (using git bisect). It was first introduced in 4ff29ff439a3d9d5b46911f52e52bbe24346bd52.
My systemd version is:
systemd 204
+PAM +LIBWRAP +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL
+XZ
gdha commented at 2014-05-04 18:55:¶
Is systemd-udev not working on Debian?
ypid commented at 2014-05-04 19:19:¶
I think not:
pgrep -a systemd
4524 /lib/systemd/systemd-logind
Maybe the test introduced in 4ff29ff439a3d9d5b46911f52e52bbe24346bd52 should also make sure that systemd is running?
gdha commented at 2014-05-23 08:49:¶
@ypid not a bad point - do you know what systems/systemd-logind is
used for? I guess only login.
ypid commented at 2014-05-23 16:46:¶
Thats probably it, which is also confirmed by this source.
gdha commented at 2014-06-20 13:59:¶
@ypid could you verify if the fix is working for you?
ypid commented at 2014-06-20 14:10:¶
Seems good to me. systemd-udevd is not running on my up to date Debian testing system.
gdha commented at 2014-06-25 14:40:¶
keep ticket open for end-user response or feedback...
ypid commented at 2014-07-03 21:38:¶
I can confirm that the network is now configured properly on recover with d33cc9c676b02552c12b602768c4cbf13fc03623.
gdha commented at 2015-02-11 10:14:¶
added to the release notes so we can close this issue
[Export of Github issue for rear/rear.]