*** This bug is a duplicate of bug 1324558 ***
https://bugs.launchpad.net/bugs/1324558
Faye, I have p4p2 in my interfaces file and it still gets renamed to
rename3.
this are two dmesg outputs when I only restarted my server, no files
changed or anything.
zidar@vedi:~$ dmesg | grep eth
[ 26
*** This bug is a duplicate of bug 1324558 ***
https://bugs.launchpad.net/bugs/1324558
** This bug is no longer a duplicate of bug 1284043
udev renaming the same hardware network i/f to different name, breaks
networking and firewall
** This bug has been marked a duplicate of bug 1324558
*** This bug is a duplicate of bug 1284043 ***
https://bugs.launchpad.net/bugs/1284043
** This bug has been marked a duplicate of bug 1284043
udev renaming the same hardware network i/f to different name, breaks
networking and firewall
--
You received this bug notification because you ar
The interface was set to renameX during installation, I suspect because dhcp
was triggered before udev had settled.
This named my interface renameX in /etc/network/interfaces, which meant that
network-interface.conf was triggering when it saw the renameX interface.
Changing the interface name in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: biosdevname (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295873
Title:
** Changed in: biosdevname (Ubuntu)
Milestone: None => ubuntu-14.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295873
Title:
biosdevname messes up interface names from emX to renameX
To man
