We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I configured the role like this based on hints from https://wiki.debian.org/NetworkConfiguration#Network_Interface_Names:
network_interfaces_interfaces: - device: "{{ ansible_interfaces | select('match', '^en') | list | first }}" auto: true family: inet method: dhcp - device: "{{ ansible_interfaces | select('match', '^en') | list | first }}" auto: true family: inet method: static address: '192.168.178.4'
I'd expect an output like this:
# Ansible managed auto enx001e06360900 iface enx001e06360900 inet dhcp iface enx001e06360900 inet static address 192.168.178.4
Instead I got this (which destroys connectivity):
# Ansible managed auto enx001e06360900 iface enx001e06360900 inet static address 192.168.178.4
The text was updated successfully, but these errors were encountered:
Is this even possible? An interface being inet dhcp and inet static. Can you point me to an example?
inet dhcp
inet static
Sorry, something went wrong.
Yes it is. The first IP would be managed by DHCP and a second IP is attached statically.
No branches or pull requests
I configured the role like this based on hints from https://wiki.debian.org/NetworkConfiguration#Network_Interface_Names:
I'd expect an output like this:
Instead I got this (which destroys connectivity):
The text was updated successfully, but these errors were encountered: