I know it's too old, but today i have big problem without persistent net rules.
(sorry for my English)
I have VMWare 5.5.0 host and Ubuntu 12.04 guest with many virtual NICs (with MACs 00:0c:29*)
Today I updated kernel from 3.13.0-32 to 3.13.0-45
Rebooted VM
Lost connection to my VM over one of the NIC (which is connected to internet).
I connected to VMWare host (by VMware vSphere Client) and to Ubuntu guest (over LAN virtual NIC who worked)
And I saw, that NICs in Ubuntu guest have correct order and matches IP-ETHnumber like before kernel update and reboot, but IP-ETH does not match MAC-VLAN bindings in VMWare, except eth0 (LAN NIC).
I don't understend how it happened, as I remember, I updated kernel before many times (to 3.13.0-32) without problems.
So today I am commenting line after "ignore VMWare virtual interfaces" to make IP-ETH-MAC match persistent.
I know it's too old, but today i have big problem without persistent net rules.
(sorry for my English)
I have VMWare 5.5.0 host and Ubuntu 12.04 guest with many virtual NICs (with MACs 00:0c:29*)
Today I updated kernel from 3.13.0-32 to 3.13.0-45
Rebooted VM
Lost connection to my VM over one of the NIC (which is connected to internet).
I connected to VMWare host (by VMware vSphere Client) and to Ubuntu guest (over LAN virtual NIC who worked)
And I saw, that NICs in Ubuntu guest have correct order and matches IP-ETHnumber like before kernel update and reboot, but IP-ETH does not match MAC-VLAN bindings in VMWare, except eth0 (LAN NIC).
I don't understend how it happened, as I remember, I updated kernel before many times (to 3.13.0-32) without problems.
So today I am commenting line after "ignore VMWare virtual interfaces" to make IP-ETH-MAC match persistent.