How to rename network interface in 15.10?

I decided to do a clean install of 15.10, and as a result, need to reinstall MATLAB. MATLAB licenses are tied to the the eth0 hardware address.

My Ethernet card is listed as enp1s0, and I need to rename it to eth0. only lo is listed in /etc/network/interfaces, and /etc/udev/rules.d/70-persistent-net.rules does not exist, so I'm unsure where to start.

edited Oct 25 '15 at 0:24

kyodake

9,65011932

asked Oct 24 '15 at 21:36

Steve Mohan

171124

1

You can define a udev rule to rename the interface as eth0..lets say the MAC address of the interface is xx:XX:xx:YY:yy:ZZ then you can create a file in /etc/udev/rules.d/ e.g. 99-rename-net.rules and put SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="xx:XX:xx:YY:yy:ZZ", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" in the file..if you don't know the MAC address then you can get it from /sys/class/net/enp1so/address file..
– heemayl
Oct 24 '15 at 22:35

@heemayl if you added that comment as an answer, then people could comment on it more easily and discuss why it seems to work for some people and not for others. Hugs!
– Jonathan Hartley
Mar 22 '16 at 20:20

@heemayl's answer in the comment above did not work for me, on a fresh Ubuntu 15.10 install.
– Jonathan Hartley
Mar 22 '16 at 20:30

In the above, @jdnz suggested using systemd's .link files, but some others suggested that this did not work for them. It most likely did not work because after editing the link files the initramfs must be updated. So, follow @jndz's answer first, and then follow the answer I linked above.
– Pinja-Liina Jalkanen
Dec 18 '18 at 17:49

add a comment |

I decided to do a clean install of 15.10, and as a result, need to reinstall MATLAB. MATLAB licenses are tied to the the eth0 hardware address.

edited Oct 25 '15 at 0:24

kyodake

9,65011932

asked Oct 24 '15 at 21:36

Steve Mohan

171124

1

You can define a udev rule to rename the interface as eth0..lets say the MAC address of the interface is xx:XX:xx:YY:yy:ZZ then you can create a file in /etc/udev/rules.d/ e.g. 99-rename-net.rules and put SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="xx:XX:xx:YY:yy:ZZ", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" in the file..if you don't know the MAC address then you can get it from /sys/class/net/enp1so/address file..
– heemayl
Oct 24 '15 at 22:35

@heemayl if you added that comment as an answer, then people could comment on it more easily and discuss why it seems to work for some people and not for others. Hugs!
– Jonathan Hartley
Mar 22 '16 at 20:20

@heemayl's answer in the comment above did not work for me, on a fresh Ubuntu 15.10 install.
– Jonathan Hartley
Mar 22 '16 at 20:30

In the above, @jdnz suggested using systemd's .link files, but some others suggested that this did not work for them. It most likely did not work because after editing the link files the initramfs must be updated. So, follow @jndz's answer first, and then follow the answer I linked above.
– Pinja-Liina Jalkanen
Dec 18 '18 at 17:49

add a comment |

I decided to do a clean install of 15.10, and as a result, need to reinstall MATLAB. MATLAB licenses are tied to the the eth0 hardware address.

edited Oct 25 '15 at 0:24

kyodake

9,65011932

asked Oct 24 '15 at 21:36

Steve Mohan

171124

I decided to do a clean install of 15.10, and as a result, need to reinstall MATLAB. MATLAB licenses are tied to the the eth0 hardware address.

networking

edited Oct 25 '15 at 0:24

kyodake

9,65011932

asked Oct 24 '15 at 21:36

Steve Mohan

171124

edited Oct 25 '15 at 0:24

kyodake

9,65011932

asked Oct 24 '15 at 21:36

Steve Mohan

171124

edited Oct 25 '15 at 0:24

kyodake

9,65011932

edited Oct 25 '15 at 0:24

kyodake

9,65011932

edited Oct 25 '15 at 0:24

kyodake

9,65011932

asked Oct 24 '15 at 21:36

Steve Mohan

171124

asked Oct 24 '15 at 21:36

Steve Mohan

171124

asked Oct 24 '15 at 21:36

Steve Mohan

171124

1

You can define a udev rule to rename the interface as eth0..lets say the MAC address of the interface is xx:XX:xx:YY:yy:ZZ then you can create a file in /etc/udev/rules.d/ e.g. 99-rename-net.rules and put SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="xx:XX:xx:YY:yy:ZZ", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" in the file..if you don't know the MAC address then you can get it from /sys/class/net/enp1so/address file..
– heemayl
Oct 24 '15 at 22:35

@heemayl if you added that comment as an answer, then people could comment on it more easily and discuss why it seems to work for some people and not for others. Hugs!
– Jonathan Hartley
Mar 22 '16 at 20:20

@heemayl's answer in the comment above did not work for me, on a fresh Ubuntu 15.10 install.
– Jonathan Hartley
Mar 22 '16 at 20:30

In the above, @jdnz suggested using systemd's .link files, but some others suggested that this did not work for them. It most likely did not work because after editing the link files the initramfs must be updated. So, follow @jndz's answer first, and then follow the answer I linked above.
– Pinja-Liina Jalkanen
Dec 18 '18 at 17:49

add a comment |

1

You can define a udev rule to rename the interface as eth0..lets say the MAC address of the interface is xx:XX:xx:YY:yy:ZZ then you can create a file in /etc/udev/rules.d/ e.g. 99-rename-net.rules and put SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="xx:XX:xx:YY:yy:ZZ", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" in the file..if you don't know the MAC address then you can get it from /sys/class/net/enp1so/address file..
– heemayl
Oct 24 '15 at 22:35

@heemayl if you added that comment as an answer, then people could comment on it more easily and discuss why it seems to work for some people and not for others. Hugs!
– Jonathan Hartley
Mar 22 '16 at 20:20

@heemayl's answer in the comment above did not work for me, on a fresh Ubuntu 15.10 install.
– Jonathan Hartley
Mar 22 '16 at 20:30

In the above, @jdnz suggested using systemd's .link files, but some others suggested that this did not work for them. It most likely did not work because after editing the link files the initramfs must be updated. So, follow @jndz's answer first, and then follow the answer I linked above.
– Pinja-Liina Jalkanen
Dec 18 '18 at 17:49

You can define a udev rule to rename the interface as eth0..lets say the MAC address of the interface is xx:XX:xx:YY:yy:ZZ then you can create a file in /etc/udev/rules.d/ e.g. 99-rename-net.rules and put

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="xx:XX:xx:YY:yy:ZZ", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

in the file..if you don't know the MAC address then you can get it from /sys/class/net/enp1so/address file..
– heemayl
Oct 24 '15 at 22:35

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="xx:XX:xx:YY:yy:ZZ", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

in the file..if you don't know the MAC address then you can get it from /sys/class/net/enp1so/address file..
– heemayl
Oct 24 '15 at 22:35

@heemayl if you added that comment as an answer, then people could comment on it more easily and discuss why it seems to work for some people and not for others. Hugs!
– Jonathan Hartley
Mar 22 '16 at 20:20

@heemayl's answer in the comment above did not work for me, on a fresh Ubuntu 15.10 install.
– Jonathan Hartley
Mar 22 '16 at 20:30

In the above, @jdnz suggested using systemd's .link files, but some others suggested that this did not work for them. It most likely did not work because after editing the link files the initramfs must be updated. So, follow @jndz's answer first, and then follow the answer I linked above.
– Pinja-Liina Jalkanen
Dec 18 '18 at 17:49

add a comment |

5 Answers
5

active

oldest

votes

My solution to this was to create a file /etc/udev/rules.d/10-rename-network.rules with the content:

SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="ff:ff:ff:ff:ff:ff", NAME="eth0"

answered Feb 18 '16 at 1:47

richvdh

84588

1

This DID work for me on Ubuntu 15.10 (unlike higher-voted answers and comments on the question)
– Jonathan Hartley
Mar 22 '16 at 20:35

1

@steve-mohan This is the right answer and should be marked as correct.
– Hubro
Apr 1 '16 at 18:38

5

This works indeed as of 16.04.
– EnzoR
Jun 16 '16 at 9:29

Since this is the top answer -- just want to note what actually worked for me .. had to change a grub config and regenerate the boot command so to disable renaming of the network interfaces as described here: itzgeek.com/how-tos/mini-howtos/…
– qodeninja
Jan 6 '18 at 23:03

1

Worked for me in 16.04. ff:ff:ff:ff:ff:ff needed to be replaced with the MAC address.
– Ken Shirriff
Mar 16 '18 at 2:08

add a comment |

I had the same problem and adding files to /etc/udev/rules.d/ did not help. The issue seems to be in the use of Predictable Network Interface Names as described here. To create your own manual naming scheme, i.e., to name your device "eth0" for MATLAB, you can create your own .link files in /etc/systemd/network/ as described here.

Specifically, I created a file /etc/systemd/network/10-eth.link with the contents

[Match]

MACAddress=ff:ff:ff:ff:ff:ff

[Link]

Name=eth0

replacing ff:ff:ff:ff:ff:ff with the MAC address of the device I wanted to change. After reboot the name was as desired.

answered Nov 16 '15 at 14:42

jdnz

874

This didn't work for me, and I would love to know why.
– richvdh
Feb 18 '16 at 1:38

This didn't work for me on Ubuntu 15.10
– Jonathan Hartley
Mar 22 '16 at 20:22

This won't work as of 16.04.
– EnzoR
Jun 16 '16 at 9:26

add a comment |

If for any reason answer suggested by @zab doesnt work for you, you can also disable this naming scheme like it made here. But the method proposed by @zab is potentially safer

I just did not include biosdevname=0 to command line argument, it seems to be turned off by default.

Following steps schould be made:

$ sudo nano /etc/default/grub

At the line GRUB_CMDLINE_LINUX add net.ifnames=0

GRUB_CMDLINE_LINUX="[previous parameters] net.ifnames=0"

Then generate new grub file:

$ sudo grub-mkconfig -o /boot/grub/grub.cfg

At the end reboot system.

edited Sep 15 '16 at 12:40

answered Sep 14 '16 at 8:18

Dmitriy Kozlov

6112

1

Could you please elaborate so that this answer will still be useful if that link is not available in the future?
– Zanna
Sep 14 '16 at 12:01

@Zanna That's done
– Dmitriy Kozlov
Sep 15 '16 at 12:42

2

After countless attempts at everything on the entire internet, this is what fixed ethernet for me. My situation (for Google Searches in the future) was no ethernet after installing Linux Mint (or Ubuntu) via Serva / PXE because the stupid network adapter uses predictable network interface name instead of eth0. The instructions were found here: itzgeek.com/how-tos/mini-howtos/…
– ThePCpenguin
May 19 '17 at 1:33

As of today (with all updates installed) this works. Thank you.
– Erutan409
Aug 9 '17 at 15:04

add a comment |

This worked for me on 16.04 server as eno1 was showing when I did ifconfig -a. I had to bring up the interface as ifconfig eno1 up then I did the following:

vi /etc/udev/rules.d/10-network.rules



SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="ff:ff:ff:ff:ff:ff", NAME="eth0"

edited Aug 2 '16 at 4:10

edwinksl

16.5k125385

answered Aug 2 '16 at 3:15

Jose

211

Does this change the name immediately, or only after a reboot?
– Xen2050
Apr 15 '17 at 20:41

add a comment |

I had this issue running 16.04 Server (minimal) on a raspberry pi 3 and none of the posted answers helped. What solved the problem was disabling Predictable Network Interface Names as descripbed here: https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

by running this command:

ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules

answered Sep 1 '16 at 9:52

Lost in OWL

1235

add a comment |

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f689501%2fhow-to-rename-network-interface-in-15-10%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

5 Answers
5

active

oldest

votes

5 Answers
5

active

oldest

votes

My solution to this was to create a file /etc/udev/rules.d/10-rename-network.rules with the content:

SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="ff:ff:ff:ff:ff:ff", NAME="eth0"

answered Feb 18 '16 at 1:47

richvdh

84588

1

This DID work for me on Ubuntu 15.10 (unlike higher-voted answers and comments on the question)
– Jonathan Hartley
Mar 22 '16 at 20:35

1

@steve-mohan This is the right answer and should be marked as correct.
– Hubro
Apr 1 '16 at 18:38

5

This works indeed as of 16.04.
– EnzoR
Jun 16 '16 at 9:29

Since this is the top answer -- just want to note what actually worked for me .. had to change a grub config and regenerate the boot command so to disable renaming of the network interfaces as described here: itzgeek.com/how-tos/mini-howtos/…
– qodeninja
Jan 6 '18 at 23:03

1

Worked for me in 16.04. ff:ff:ff:ff:ff:ff needed to be replaced with the MAC address.
– Ken Shirriff
Mar 16 '18 at 2:08

add a comment |

My solution to this was to create a file /etc/udev/rules.d/10-rename-network.rules with the content:

SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="ff:ff:ff:ff:ff:ff", NAME="eth0"

answered Feb 18 '16 at 1:47

richvdh

84588

1

This DID work for me on Ubuntu 15.10 (unlike higher-voted answers and comments on the question)
– Jonathan Hartley
Mar 22 '16 at 20:35

1

@steve-mohan This is the right answer and should be marked as correct.
– Hubro
Apr 1 '16 at 18:38

5

This works indeed as of 16.04.
– EnzoR
Jun 16 '16 at 9:29

Since this is the top answer -- just want to note what actually worked for me .. had to change a grub config and regenerate the boot command so to disable renaming of the network interfaces as described here: itzgeek.com/how-tos/mini-howtos/…
– qodeninja
Jan 6 '18 at 23:03

1

Worked for me in 16.04. ff:ff:ff:ff:ff:ff needed to be replaced with the MAC address.
– Ken Shirriff
Mar 16 '18 at 2:08

add a comment |

My solution to this was to create a file /etc/udev/rules.d/10-rename-network.rules with the content:

SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="ff:ff:ff:ff:ff:ff", NAME="eth0"

answered Feb 18 '16 at 1:47

richvdh

84588

My solution to this was to create a file /etc/udev/rules.d/10-rename-network.rules with the content:

SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="ff:ff:ff:ff:ff:ff", NAME="eth0"

answered Feb 18 '16 at 1:47

richvdh

84588

answered Feb 18 '16 at 1:47

richvdh

84588

answered Feb 18 '16 at 1:47

richvdh

84588

answered Feb 18 '16 at 1:47

richvdh

84588

1

This DID work for me on Ubuntu 15.10 (unlike higher-voted answers and comments on the question)
– Jonathan Hartley
Mar 22 '16 at 20:35

1

@steve-mohan This is the right answer and should be marked as correct.
– Hubro
Apr 1 '16 at 18:38

5

This works indeed as of 16.04.
– EnzoR
Jun 16 '16 at 9:29

Since this is the top answer -- just want to note what actually worked for me .. had to change a grub config and regenerate the boot command so to disable renaming of the network interfaces as described here: itzgeek.com/how-tos/mini-howtos/…
– qodeninja
Jan 6 '18 at 23:03

1

Worked for me in 16.04. ff:ff:ff:ff:ff:ff needed to be replaced with the MAC address.
– Ken Shirriff
Mar 16 '18 at 2:08

add a comment |

1

This DID work for me on Ubuntu 15.10 (unlike higher-voted answers and comments on the question)
– Jonathan Hartley
Mar 22 '16 at 20:35

1

@steve-mohan This is the right answer and should be marked as correct.
– Hubro
Apr 1 '16 at 18:38

5

This works indeed as of 16.04.
– EnzoR
Jun 16 '16 at 9:29

Since this is the top answer -- just want to note what actually worked for me .. had to change a grub config and regenerate the boot command so to disable renaming of the network interfaces as described here: itzgeek.com/how-tos/mini-howtos/…
– qodeninja
Jan 6 '18 at 23:03

1

Worked for me in 16.04. ff:ff:ff:ff:ff:ff needed to be replaced with the MAC address.
– Ken Shirriff
Mar 16 '18 at 2:08

This DID work for me on Ubuntu 15.10 (unlike higher-voted answers and comments on the question)
– Jonathan Hartley
Mar 22 '16 at 20:35

@steve-mohan This is the right answer and should be marked as correct.
– Hubro
Apr 1 '16 at 18:38

This works indeed as of 16.04.
– EnzoR
Jun 16 '16 at 9:29

Since this is the top answer -- just want to note what actually worked for me .. had to change a grub config and regenerate the boot command so to disable renaming of the network interfaces as described here: itzgeek.com/how-tos/mini-howtos/…
– qodeninja
Jan 6 '18 at 23:03

Worked for me in 16.04. ff:ff:ff:ff:ff:ff needed to be replaced with the MAC address.
– Ken Shirriff
Mar 16 '18 at 2:08

add a comment |

Specifically, I created a file /etc/systemd/network/10-eth.link with the contents

[Match]

MACAddress=ff:ff:ff:ff:ff:ff

[Link]

Name=eth0

replacing ff:ff:ff:ff:ff:ff with the MAC address of the device I wanted to change. After reboot the name was as desired.

answered Nov 16 '15 at 14:42

jdnz

874

This didn't work for me, and I would love to know why.
– richvdh
Feb 18 '16 at 1:38

This didn't work for me on Ubuntu 15.10
– Jonathan Hartley
Mar 22 '16 at 20:22

This won't work as of 16.04.
– EnzoR
Jun 16 '16 at 9:26

add a comment |

Specifically, I created a file /etc/systemd/network/10-eth.link with the contents

[Match]

MACAddress=ff:ff:ff:ff:ff:ff

[Link]

Name=eth0

replacing ff:ff:ff:ff:ff:ff with the MAC address of the device I wanted to change. After reboot the name was as desired.

answered Nov 16 '15 at 14:42

jdnz

874

This didn't work for me, and I would love to know why.
– richvdh
Feb 18 '16 at 1:38

This didn't work for me on Ubuntu 15.10
– Jonathan Hartley
Mar 22 '16 at 20:22

This won't work as of 16.04.
– EnzoR
Jun 16 '16 at 9:26

add a comment |

Specifically, I created a file /etc/systemd/network/10-eth.link with the contents

[Match]

MACAddress=ff:ff:ff:ff:ff:ff

[Link]

Name=eth0

replacing ff:ff:ff:ff:ff:ff with the MAC address of the device I wanted to change. After reboot the name was as desired.

answered Nov 16 '15 at 14:42

jdnz

874

Specifically, I created a file /etc/systemd/network/10-eth.link with the contents

[Match]

MACAddress=ff:ff:ff:ff:ff:ff

[Link]

Name=eth0

replacing ff:ff:ff:ff:ff:ff with the MAC address of the device I wanted to change. After reboot the name was as desired.

answered Nov 16 '15 at 14:42

jdnz

874

answered Nov 16 '15 at 14:42

jdnz

874

answered Nov 16 '15 at 14:42

jdnz

874

answered Nov 16 '15 at 14:42

jdnz

874

This didn't work for me, and I would love to know why.
– richvdh
Feb 18 '16 at 1:38

This didn't work for me on Ubuntu 15.10
– Jonathan Hartley
Mar 22 '16 at 20:22

This won't work as of 16.04.
– EnzoR
Jun 16 '16 at 9:26

add a comment |

This didn't work for me, and I would love to know why.
– richvdh
Feb 18 '16 at 1:38

This didn't work for me on Ubuntu 15.10
– Jonathan Hartley
Mar 22 '16 at 20:22

This won't work as of 16.04.
– EnzoR
Jun 16 '16 at 9:26

This didn't work for me, and I would love to know why.
– richvdh
Feb 18 '16 at 1:38

This didn't work for me on Ubuntu 15.10
– Jonathan Hartley
Mar 22 '16 at 20:22

This won't work as of 16.04.
– EnzoR
Jun 16 '16 at 9:26

add a comment |

If for any reason answer suggested by @zab doesnt work for you, you can also disable this naming scheme like it made here. But the method proposed by @zab is potentially safer

I just did not include biosdevname=0 to command line argument, it seems to be turned off by default.

Following steps schould be made:

$ sudo nano /etc/default/grub

At the line GRUB_CMDLINE_LINUX add net.ifnames=0

GRUB_CMDLINE_LINUX="[previous parameters] net.ifnames=0"

Then generate new grub file:

$ sudo grub-mkconfig -o /boot/grub/grub.cfg

At the end reboot system.

edited Sep 15 '16 at 12:40

answered Sep 14 '16 at 8:18

Dmitriy Kozlov

6112

1

Could you please elaborate so that this answer will still be useful if that link is not available in the future?
– Zanna
Sep 14 '16 at 12:01

@Zanna That's done
– Dmitriy Kozlov
Sep 15 '16 at 12:42

2

After countless attempts at everything on the entire internet, this is what fixed ethernet for me. My situation (for Google Searches in the future) was no ethernet after installing Linux Mint (or Ubuntu) via Serva / PXE because the stupid network adapter uses predictable network interface name instead of eth0. The instructions were found here: itzgeek.com/how-tos/mini-howtos/…
– ThePCpenguin
May 19 '17 at 1:33

As of today (with all updates installed) this works. Thank you.
– Erutan409
Aug 9 '17 at 15:04

add a comment |

If for any reason answer suggested by @zab doesnt work for you, you can also disable this naming scheme like it made here. But the method proposed by @zab is potentially safer

I just did not include biosdevname=0 to command line argument, it seems to be turned off by default.

Following steps schould be made:

$ sudo nano /etc/default/grub

At the line GRUB_CMDLINE_LINUX add net.ifnames=0

GRUB_CMDLINE_LINUX="[previous parameters] net.ifnames=0"

Then generate new grub file:

$ sudo grub-mkconfig -o /boot/grub/grub.cfg

At the end reboot system.

edited Sep 15 '16 at 12:40

answered Sep 14 '16 at 8:18

Dmitriy Kozlov

6112

1

Could you please elaborate so that this answer will still be useful if that link is not available in the future?
– Zanna
Sep 14 '16 at 12:01

@Zanna That's done
– Dmitriy Kozlov
Sep 15 '16 at 12:42

2

After countless attempts at everything on the entire internet, this is what fixed ethernet for me. My situation (for Google Searches in the future) was no ethernet after installing Linux Mint (or Ubuntu) via Serva / PXE because the stupid network adapter uses predictable network interface name instead of eth0. The instructions were found here: itzgeek.com/how-tos/mini-howtos/…
– ThePCpenguin
May 19 '17 at 1:33

As of today (with all updates installed) this works. Thank you.
– Erutan409
Aug 9 '17 at 15:04

add a comment |

If for any reason answer suggested by @zab doesnt work for you, you can also disable this naming scheme like it made here. But the method proposed by @zab is potentially safer

I just did not include biosdevname=0 to command line argument, it seems to be turned off by default.

Following steps schould be made:

$ sudo nano /etc/default/grub

At the line GRUB_CMDLINE_LINUX add net.ifnames=0

GRUB_CMDLINE_LINUX="[previous parameters] net.ifnames=0"

Then generate new grub file:

$ sudo grub-mkconfig -o /boot/grub/grub.cfg

At the end reboot system.

edited Sep 15 '16 at 12:40

answered Sep 14 '16 at 8:18

Dmitriy Kozlov

6112

If for any reason answer suggested by @zab doesnt work for you, you can also disable this naming scheme like it made here. But the method proposed by @zab is potentially safer

I just did not include biosdevname=0 to command line argument, it seems to be turned off by default.

Following steps schould be made:

$ sudo nano /etc/default/grub

At the line GRUB_CMDLINE_LINUX add net.ifnames=0

GRUB_CMDLINE_LINUX="[previous parameters] net.ifnames=0"

Then generate new grub file:

$ sudo grub-mkconfig -o /boot/grub/grub.cfg

At the end reboot system.

edited Sep 15 '16 at 12:40

answered Sep 14 '16 at 8:18

Dmitriy Kozlov

6112

edited Sep 15 '16 at 12:40

answered Sep 14 '16 at 8:18

Dmitriy Kozlov

6112

answered Sep 14 '16 at 8:18

Dmitriy Kozlov

6112

answered Sep 14 '16 at 8:18

Dmitriy Kozlov

6112

1

Could you please elaborate so that this answer will still be useful if that link is not available in the future?
– Zanna
Sep 14 '16 at 12:01

@Zanna That's done
– Dmitriy Kozlov
Sep 15 '16 at 12:42

2

After countless attempts at everything on the entire internet, this is what fixed ethernet for me. My situation (for Google Searches in the future) was no ethernet after installing Linux Mint (or Ubuntu) via Serva / PXE because the stupid network adapter uses predictable network interface name instead of eth0. The instructions were found here: itzgeek.com/how-tos/mini-howtos/…
– ThePCpenguin
May 19 '17 at 1:33

As of today (with all updates installed) this works. Thank you.
– Erutan409
Aug 9 '17 at 15:04

add a comment |

1

Could you please elaborate so that this answer will still be useful if that link is not available in the future?
– Zanna
Sep 14 '16 at 12:01

@Zanna That's done
– Dmitriy Kozlov
Sep 15 '16 at 12:42

2

After countless attempts at everything on the entire internet, this is what fixed ethernet for me. My situation (for Google Searches in the future) was no ethernet after installing Linux Mint (or Ubuntu) via Serva / PXE because the stupid network adapter uses predictable network interface name instead of eth0. The instructions were found here: itzgeek.com/how-tos/mini-howtos/…
– ThePCpenguin
May 19 '17 at 1:33

As of today (with all updates installed) this works. Thank you.
– Erutan409
Aug 9 '17 at 15:04

Could you please elaborate so that this answer will still be useful if that link is not available in the future?
– Zanna
Sep 14 '16 at 12:01

@Zanna That's done
– Dmitriy Kozlov
Sep 15 '16 at 12:42

After countless attempts at everything on the entire internet, this is what fixed ethernet for me. My situation (for Google Searches in the future) was no ethernet after installing Linux Mint (or Ubuntu) via Serva / PXE because the stupid network adapter uses predictable network interface name instead of eth0. The instructions were found here: itzgeek.com/how-tos/mini-howtos/…
– ThePCpenguin
May 19 '17 at 1:33

As of today (with all updates installed) this works. Thank you.
– Erutan409
Aug 9 '17 at 15:04

add a comment |

This worked for me on 16.04 server as eno1 was showing when I did ifconfig -a. I had to bring up the interface as ifconfig eno1 up then I did the following:

vi /etc/udev/rules.d/10-network.rules



SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="ff:ff:ff:ff:ff:ff", NAME="eth0"

edited Aug 2 '16 at 4:10

edwinksl

16.5k125385

answered Aug 2 '16 at 3:15

Jose

211

Does this change the name immediately, or only after a reboot?
– Xen2050
Apr 15 '17 at 20:41

add a comment |

This worked for me on 16.04 server as eno1 was showing when I did ifconfig -a. I had to bring up the interface as ifconfig eno1 up then I did the following:

vi /etc/udev/rules.d/10-network.rules



SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="ff:ff:ff:ff:ff:ff", NAME="eth0"

edited Aug 2 '16 at 4:10

edwinksl

16.5k125385

answered Aug 2 '16 at 3:15

Jose

211

Does this change the name immediately, or only after a reboot?
– Xen2050
Apr 15 '17 at 20:41

add a comment |

This worked for me on 16.04 server as eno1 was showing when I did ifconfig -a. I had to bring up the interface as ifconfig eno1 up then I did the following:

vi /etc/udev/rules.d/10-network.rules



SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="ff:ff:ff:ff:ff:ff", NAME="eth0"

edited Aug 2 '16 at 4:10

edwinksl

16.5k125385

answered Aug 2 '16 at 3:15

Jose

211

This worked for me on 16.04 server as eno1 was showing when I did ifconfig -a. I had to bring up the interface as ifconfig eno1 up then I did the following:

vi /etc/udev/rules.d/10-network.rules



SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="ff:ff:ff:ff:ff:ff", NAME="eth0"

edited Aug 2 '16 at 4:10

edwinksl

16.5k125385

answered Aug 2 '16 at 3:15

Jose

211

edited Aug 2 '16 at 4:10

edwinksl

16.5k125385

edited Aug 2 '16 at 4:10

edwinksl

16.5k125385

edited Aug 2 '16 at 4:10

edwinksl

16.5k125385

answered Aug 2 '16 at 3:15

Jose

211

answered Aug 2 '16 at 3:15

Jose

211

answered Aug 2 '16 at 3:15

Jose

211

Does this change the name immediately, or only after a reboot?
– Xen2050
Apr 15 '17 at 20:41

add a comment |

Does this change the name immediately, or only after a reboot?
– Xen2050
Apr 15 '17 at 20:41

Does this change the name immediately, or only after a reboot?
– Xen2050
Apr 15 '17 at 20:41

add a comment |

by running this command:

ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules

answered Sep 1 '16 at 9:52

Lost in OWL

1235

add a comment |

by running this command:

ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules

answered Sep 1 '16 at 9:52

Lost in OWL

1235

add a comment |

by running this command:

ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules

answered Sep 1 '16 at 9:52

Lost in OWL

1235

by running this command:

ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules

answered Sep 1 '16 at 9:52

Lost in OWL

1235

answered Sep 1 '16 at 9:52

Lost in OWL

1235

answered Sep 1 '16 at 9:52

Lost in OWL

1235

answered Sep 1 '16 at 9:52

Lost in OWL

1235

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Ask Ubuntu!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

Some of your past answers have not been well-received, and you're in danger of being blocked from answering.

Please pay close attention to the following guidance:

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Bdtyktl