FS#44754 - [netctl] auto-start with two NICs fails

Attached to Project: Arch Linux
Opened by abc (bigstick) - Tuesday, 28 April 2015, 05:36 GMT
Last edited by Jouke Witteveen (jouke) - Sunday, 08 October 2017, 07:56 GMT
Task Type Bug Report
Category Arch Projects
Status Closed
Assigned To Jouke Witteveen (jouke)
Architecture i686
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Additional info:
* package version(s) -> netctl 1.10-2
* config and/or log files etc.

config file '/etc/netctl/br'

Description='Bridge Interface'
Interface=br0
Connection=bridge
BindsToInterfaces=('enp0s8' 'enp0s18')
IP=static
Address=('192.168.10.11/24')
Gateway='192.168.10.254'
IP6=stateless

log:
localhost systemd[1]: Failed to start Networking for netctl profile wired.
localhost systemd[1]: Unit netctl@wired.service entered failed state.
localhost systemd[1]: netctl@wired.service failed.
localhost netctl[1]: Could not read state file '/var/lib/netctl/netctl.state'

Steps to reproduce: When two NICs are bridged and the above netctl profile is 'enabled' via `netctl enable br', it enter a infinite loop and I can hear that my NICs are under high load. There isn't any issue when the profile is 'disabled', which means that netctl won't start the profile automatically whenever the server is booted. I can start, restart and stop the 'br' profile by hand flawlessly. I experience almost identical issue like the previously reported one - https://bugs.archlinux.org/task/44731 , except it is related to bridged network interafaces.

I use dnscrypt and dnsmasq, if needed I can provide their configurations.
This task depends upon

Closed by  Jouke Witteveen (jouke)
Sunday, 08 October 2017, 07:56 GMT
Reason for closing:  No response
Comment by abc (bigstick) - Tuesday, 28 April 2015, 05:44 GMT
'wired' and 'br' refer to the same profile. On my primary computer, netctl is able to auto-start my 'wired' profile, the only difference is that Connection is set to ethernet and BindsToInterfaces, IP6 are removed. So I believe that the issue is related to bridged and bonded NICs only.
Comment by Jouke Witteveen (jouke) - Sunday, 14 June 2015, 13:00 GMT
This is weird behavior. Any news/more info? I don't have the time to solve the problem for you, but if you can solve it yourself and the problem was with netctl, I'd like to add the solution to netctl.

Loading...