On 04/11/2014 04:57 PM, Sean Darcy wrote:
Changed the name of the connection to "internal" , same as the device.Again, NM treated it as dynamic. But someplace it has the correct info. nmcli -a -p connection show configured internal connection.id: internal connection.uuid: ef5b0746-2604-b21f-c03e-00556aef68fc connection.interface-name: internal connection.type: 802-3-ethernet connection.autoconnect: yes connection.timestamp: 0 ..... ipv4.method: manual ipv4.dns: ipv4.dns-search: ipv4.addresses: { ip = 10.10.11.251/24, gw = 0.0.0.0 } ipv4.routes: { dst = 192.168.0.0/24, nh = 10.10.11.251, mt = 0 } ipv4.ignore-auto-routes: no ipv4.ignore-auto-dns: no ipv4.dhcp-client-id: -- ipv4.dhcp-send-hostname: yes ipv4.dhcp-hostname: -- ipv4.never-default: yes ipv4.may-fail: yes ......... Even stranger. nmcli connection up internal worked!
OK, the culprit was ifcfg-external, the other connection. ifcfg-external had no DEVICE or HWADDR. It seems NM just applied it to any device it found, even if that device already had a connection.
Adding DEVICE=external made it all work. Odd that it worked in F19. sean -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
