70-persistent-net.rules not being honoured
0
This is a PXE-install, which has previously been 14.04. I'm moving it to 18.04, and most things are OK, but for some reason, only one of the rules in /etc/udev/rules.d/70-persistent-net.rules (automatically generated by the preseed script) is being honoured.
/etc/udev/rules.d/70-persistent-net.rules:
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="40:8d:5c:5c:df:ce", ATTR{dev_id}=="0x0", ATTR{type}=="1", NAME="ctrl1"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="68:05:ca:22:c6:0b", ATTR{dev_id}=="0x0", ATTR{type}=="1", NAME="data1"
/etc/network/interfaces:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto ctrl1
iface ctrl1 inet dhcp
auto data1
iface data1 inet static
address 10.255.01.13
netmask 255.255.255.240
network 10.255.01.0
broadcast 10.255.01.255
ifconfig output:
foo@bar:~# ifconfig
data1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet xx.xx.xx.xx netmask 255.255.255.240 broadcast 10.255.1.255
inet6 fe80::6a05:caff:fe22:c60b prefixlen 64 scopeid 0x20<link>
ether 68:05:ca:22:c6:0b txqueuelen 1000 (Ethernet)
RX packets 123 bytes 10749 (10.7 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 44 bytes 3772 (3.7 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 17 memory 0xdc040000-dc060000
enp0s31f6: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet xx.xx.xx.xx netmask 255.255.255.128 broadcast 192.168.166.255
inet6 fe80::428d:5cff:fe5c:dfce prefixlen 64 scopeid 0x20<link>
ether 40:8d:5c:5c:df:ce txqueuelen 1000 (Ethernet)
RX packets 966 bytes 89471 (89.4 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 701 bytes 391743 (391.7 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16 memory 0xdc100000-dc120000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 697 bytes 57332 (57.3 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 697 bytes 57332 (57.3 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
data1 is OK, but ctrl1 is not being set.
Any ideas?
networking 18.04 udev
asked Dec 3 '18 at 16:29
SiHa
1033
add a comment |
0
This is a PXE-install, which has previously been 14.04. I'm moving it to 18.04, and most things are OK, but for some reason, only one of the rules in /etc/udev/rules.d/70-persistent-net.rules (automatically generated by the preseed script) is being honoured.
/etc/udev/rules.d/70-persistent-net.rules:
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="40:8d:5c:5c:df:ce", ATTR{dev_id}=="0x0", ATTR{type}=="1", NAME="ctrl1"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="68:05:ca:22:c6:0b", ATTR{dev_id}=="0x0", ATTR{type}=="1", NAME="data1"
/etc/network/interfaces:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto ctrl1
iface ctrl1 inet dhcp
auto data1
iface data1 inet static
address 10.255.01.13
netmask 255.255.255.240
network 10.255.01.0
broadcast 10.255.01.255
ifconfig output:
foo@bar:~# ifconfig
data1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet xx.xx.xx.xx netmask 255.255.255.240 broadcast 10.255.1.255
inet6 fe80::6a05:caff:fe22:c60b prefixlen 64 scopeid 0x20<link>
ether 68:05:ca:22:c6:0b txqueuelen 1000 (Ethernet)
RX packets 123 bytes 10749 (10.7 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 44 bytes 3772 (3.7 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 17 memory 0xdc040000-dc060000
enp0s31f6: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet xx.xx.xx.xx netmask 255.255.255.128 broadcast 192.168.166.255
inet6 fe80::428d:5cff:fe5c:dfce prefixlen 64 scopeid 0x20<link>
ether 40:8d:5c:5c:df:ce txqueuelen 1000 (Ethernet)
RX packets 966 bytes 89471 (89.4 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 701 bytes 391743 (391.7 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16 memory 0xdc100000-dc120000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 697 bytes 57332 (57.3 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 697 bytes 57332 (57.3 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
data1 is OK, but ctrl1 is not being set.
Any ideas?
networking 18.04 udev
asked Dec 3 '18 at 16:29
SiHa
1033
I'm not sure SystemD actually honors the udev rules... I'd have to check, but I'm pretty sure you wouldn't be able to easily make it obey the Udev definitions you've stated since SystemD operates slightly differently...
– Thomas Ward♦
Dec 3 '18 at 16:31
Oh. That's interesting - there's all sorts of information out there on the interwebs about manually configuring the udev rules on 18.04. I'vs had a quick look at the SystemD stuff, and it looks promising. I'll have a further dig tomorrow, thanks.
– SiHa
Dec 3 '18 at 16:53
add a comment |
0
0
0
This is a PXE-install, which has previously been 14.04. I'm moving it to 18.04, and most things are OK, but for some reason, only one of the rules in /etc/udev/rules.d/70-persistent-net.rules (automatically generated by the preseed script) is being honoured.
/etc/udev/rules.d/70-persistent-net.rules:
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="40:8d:5c:5c:df:ce", ATTR{dev_id}=="0x0", ATTR{type}=="1", NAME="ctrl1"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="68:05:ca:22:c6:0b", ATTR{dev_id}=="0x0", ATTR{type}=="1", NAME="data1"
/etc/network/interfaces:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto ctrl1
iface ctrl1 inet dhcp
auto data1
iface data1 inet static
address 10.255.01.13
netmask 255.255.255.240
network 10.255.01.0
broadcast 10.255.01.255
ifconfig output:
foo@bar:~# ifconfig
data1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet xx.xx.xx.xx netmask 255.255.255.240 broadcast 10.255.1.255
inet6 fe80::6a05:caff:fe22:c60b prefixlen 64 scopeid 0x20<link>
ether 68:05:ca:22:c6:0b txqueuelen 1000 (Ethernet)
RX packets 123 bytes 10749 (10.7 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 44 bytes 3772 (3.7 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 17 memory 0xdc040000-dc060000
enp0s31f6: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet xx.xx.xx.xx netmask 255.255.255.128 broadcast 192.168.166.255
inet6 fe80::428d:5cff:fe5c:dfce prefixlen 64 scopeid 0x20<link>
ether 40:8d:5c:5c:df:ce txqueuelen 1000 (Ethernet)
RX packets 966 bytes 89471 (89.4 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 701 bytes 391743 (391.7 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16 memory 0xdc100000-dc120000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 697 bytes 57332 (57.3 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 697 bytes 57332 (57.3 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
data1 is OK, but ctrl1 is not being set.
Any ideas?
networking 18.04 udev
asked Dec 3 '18 at 16:29
SiHa
1033
This is a PXE-install, which has previously been 14.04. I'm moving it to 18.04, and most things are OK, but for some reason, only one of the rules in /etc/udev/rules.d/70-persistent-net.rules (automatically generated by the preseed script) is being honoured.
/etc/udev/rules.d/70-persistent-net.rules:
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="40:8d:5c:5c:df:ce", ATTR{dev_id}=="0x0", ATTR{type}=="1", NAME="ctrl1"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="68:05:ca:22:c6:0b", ATTR{dev_id}=="0x0", ATTR{type}=="1", NAME="data1"
/etc/network/interfaces:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto ctrl1
iface ctrl1 inet dhcp
auto data1
iface data1 inet static
address 10.255.01.13
netmask 255.255.255.240
network 10.255.01.0
broadcast 10.255.01.255
ifconfig output:
foo@bar:~# ifconfig
data1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet xx.xx.xx.xx netmask 255.255.255.240 broadcast 10.255.1.255
inet6 fe80::6a05:caff:fe22:c60b prefixlen 64 scopeid 0x20<link>
ether 68:05:ca:22:c6:0b txqueuelen 1000 (Ethernet)
RX packets 123 bytes 10749 (10.7 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 44 bytes 3772 (3.7 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 17 memory 0xdc040000-dc060000
enp0s31f6: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet xx.xx.xx.xx netmask 255.255.255.128 broadcast 192.168.166.255
inet6 fe80::428d:5cff:fe5c:dfce prefixlen 64 scopeid 0x20<link>
ether 40:8d:5c:5c:df:ce txqueuelen 1000 (Ethernet)
RX packets 966 bytes 89471 (89.4 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 701 bytes 391743 (391.7 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16 memory 0xdc100000-dc120000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 697 bytes 57332 (57.3 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 697 bytes 57332 (57.3 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
data1 is OK, but ctrl1 is not being set.
Any ideas?
networking 18.04 udev
networking 18.04 udev
asked Dec 3 '18 at 16:29
SiHa
1033
asked Dec 3 '18 at 16:29
SiHa
1033
asked Dec 3 '18 at 16:29
SiHa
1033
asked Dec 3 '18 at 16:29
SiHa
1033
asked Dec 3 '18 at 16:29
SiHa
1033
1033
I'm not sure SystemD actually honors the udev rules... I'd have to check, but I'm pretty sure you wouldn't be able to easily make it obey the Udev definitions you've stated since SystemD operates slightly differently...
– Thomas Ward♦
Dec 3 '18 at 16:31
Oh. That's interesting - there's all sorts of information out there on the interwebs about manually configuring the udev rules on 18.04. I'vs had a quick look at the SystemD stuff, and it looks promising. I'll have a further dig tomorrow, thanks.
– SiHa
Dec 3 '18 at 16:53
add a comment |
I'm not sure SystemD actually honors the udev rules... I'd have to check, but I'm pretty sure you wouldn't be able to easily make it obey the Udev definitions you've stated since SystemD operates slightly differently...
– Thomas Ward♦
Dec 3 '18 at 16:31
Oh. That's interesting - there's all sorts of information out there on the interwebs about manually configuring the udev rules on 18.04. I'vs had a quick look at the SystemD stuff, and it looks promising. I'll have a further dig tomorrow, thanks.
– SiHa
Dec 3 '18 at 16:53
I'm not sure SystemD actually honors the udev rules... I'd have to check, but I'm pretty sure you wouldn't be able to easily make it obey the Udev definitions you've stated since SystemD operates slightly differently...
– Thomas Ward♦
Dec 3 '18 at 16:31
I'm not sure SystemD actually honors the udev rules... I'd have to check, but I'm pretty sure you wouldn't be able to easily make it obey the Udev definitions you've stated since SystemD operates slightly differently...
– Thomas Ward♦
Dec 3 '18 at 16:31
Oh. That's interesting - there's all sorts of information out there on the interwebs about manually configuring the udev rules on 18.04. I'vs had a quick look at the SystemD stuff, and it looks promising. I'll have a further dig tomorrow, thanks.
– SiHa
Dec 3 '18 at 16:53
Oh. That's interesting - there's all sorts of information out there on the interwebs about manually configuring the udev rules on 18.04. I'vs had a quick look at the SystemD stuff, and it looks promising. I'll have a further dig tomorrow, thanks.
– SiHa
Dec 3 '18 at 16:53
add a comment |
0
active
oldest
votes
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');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1098191%2f70-persistent-net-rules-not-being-honoured%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1098191%2f70-persistent-net-rules-not-being-honoured%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I'm not sure SystemD actually honors the udev rules... I'd have to check, but I'm pretty sure you wouldn't be able to easily make it obey the Udev definitions you've stated since SystemD operates slightly differently...
– Thomas Ward♦
Dec 3 '18 at 16:31
Oh. That's interesting - there's all sorts of information out there on the interwebs about manually configuring the udev rules on 18.04. I'vs had a quick look at the SystemD stuff, and it looks promising. I'll have a further dig tomorrow, thanks.
– SiHa
Dec 3 '18 at 16:53