Bug 1600285

+++ This bug was initially created as a clone of Bug #1481171 +++

Description of problem:

Want to create bond interface using eth and wifi on laptop:  using NetworkManager gui, under Cinnamon, wifi devices are NOT allowed to be created as part of the bond.

This fedora link:
https://fedoraproject.org/wiki/Features/NetworkManagerBonding

claims this is to in progress.

Version-Release number of selected component (if applicable):
F26, latest network manager

How reproducible:

Always

Steps to Reproduce:
Use NetworkManager to create bond.  Try to add wifi interface; not available in drop down list

Actual results:
no wifi interface to be selected

Expected results:
allow bond i/f to use both ethernet and wifi devices

Additional info:

This works perfectly on Raspbian

--- Additional comment from aoeuser on 2017-11-16 13:56:57 EST ---

Workaround for this use case by cloning the wifi mac to the ethernet interface and making arp behave?

nmcli connection modify ${ETHERNET_CONNECTION} 802-3-ethernet.cloned-mac-address ${WIFI_MAC_ADDRESS}

# /etc/sysctl.d/70-arp_settings.conf
# Reference: https://support.cumulusnetworks.com/hc/en-us/articles/203859616-Default-ARP-Settings-in-Cumulus-Linux
#
# source requests from interface addr
net.ipv4.conf.default.arp_announce = 2
#
# answer based on routing preference
net.ipv4.conf.default.arp_filter = 1
#
# answer only if target is on receiving interface and source is on subnet
net.ipv4.conf.default.arp_ignore = 2


NetworkManager will let a lower metric for the ethernet route when available, so that connection will be preferred as long as it's up.

--- Additional comment from Fedora End Of Life on 2018-05-03 04:05:58 EDT ---

This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

--- Additional comment from Fedora End Of Life on 2018-05-29 08:25:27 EDT ---

Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--- Additional comment from  on 2018-07-11 19:22:28 EDT ---

This bug persists through to Fedora 27.