Closed blackbicbiro closed 7 months ago
Files identified in the description:
If these files are incorrect, please update the component name
section of the description or use the !component
bot command.
cc @alcamie101 click here for bot help
Looking at the module file i assume its something do do with this on lines 1819. looks like it uses the default of bond. Regardless of defining it as bridge nmcli does allow you to define wifi interfaces as part of a bridge
elif self.type == 'wifi':
options.update({
'802-11-wireless.ssid': self.ssid,
'connection.slave-type': 'bond' if self.master else None,
Hi, found the same behavior in Raspberry PI OS Bookworm arm64, the wifi has connection.slave-type: bond instead of bridge, thanks
Summary
Attempting to create a wifi hotspot as part of a bridge. This is possible using the NMCLI. When attempting to do it using the NMCLI module the slave_type always defaults back to Bond.
Issue Type
Bug Report
Component Name
nmcli
Ansible Version
Community.general Version
Configuration
not setting the slave_type to bridge. It sets it to bond
OS / Environment
Host: Pop_OS! 22:04 Target: Ubuntu 22.04.4 server
Steps to Reproduce
Bridge setup with DHCP 1 x Ethernet at bridge slave 1 x wifi adaptor setup as bridge slave
Run playbook and check the settings for the connection profile
Output shows the slave-type as bond not bridge as defined with the play book
Running the playbook with verbose -vvv shows the following config so it should be setting the slave-type to bridge
Implemented the same config using CLI and NMCLI works every time.
Seems like the slave-type is being ignored and default to bond for wifi. It also seems to set a interface-name which is not required. nmcli will use the first available interface if not defined. it seems to set the interface name as the same as the connection name
Expected Results
Actual Results
Code of Conduct