New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement Debian workaround for bonded network interfaces non-DHCP "cannot send bond option because the bond has slaves" #204

Closed
jefft4 opened this Issue Nov 8, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@jefft4

jefft4 commented Nov 8, 2018

I have a bonded interface on my OMV server. I need to set it up with a static address, in order to force the default gateway (an issue with Plex behaving stupidly, don't ask...)

If I set the interface as static, I get a complaint from the Debian OS at boot, 'cannot send bond option because the bond has slaves', and the interface does not function. If I leave it DHCP, I can't set the default gateway (ok, I can edit /etc/network/interfaces directly but that's dangerous with OMV thinking it controls the file).

The problem is a known Debian screw-up, bug report here: bugs.debian.org/cgi-bin/bugreport.cgi?bug=870633 - but no sign of anyone fixing it. There is, on that thread, a workaround involving moving the bond options to a different config file.

Any chance that OMV could implement the workaround, please?

@votdev votdev added 4.x wontfix labels Nov 9, 2018

@votdev

This comment has been minimized.

Collaborator

votdev commented Nov 9, 2018

I don't think this workaround will be implemented in OMV because this is definitely a upstream bug and making changes in a really important subsystem at this stage of the release is not good. In OMV5 the network handling is now done by systemd, so this issue is resolved in OMV5.

@votdev votdev closed this Nov 9, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment