Problems with static IP config via interfaces file
I'd like to setup a static IP on Kubuntu 17.10 for my desktop PC.
ifconfig
enp10s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.100.32 netmask 255.255.255.0 broadcast 192.168.100.255
inet6 fe80::71e0:527e:96cd:4128 prefixlen 64 scopeid 0x20<link>
ether 70:85:c2:41:08:d0 txqueuelen 1000 (Ethernet)
RX packets 12849 bytes 4063036 (4.0 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 10032 bytes 1116381 (1.1 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
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 (Lokale Schleife)
RX packets 854 bytes 69858 (69.8 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 854 bytes 69858 (69.8 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Working interfaces:
auto lo
iface lo inet loopback
Not working interfaces:
auto lo
iface lo inet loopback
auto enp10s0
iface enp10s0 inet static
address 192.168.100.99
netmask 255.255.255.0
gateway 192.168.100.1
After a sudo service network-manager restart my connection isn't connected. If I delete the enp10s0 entry (revert back to the working interfaces) and restart the network-manager, the network/internet is working again.
It's a fairly standard setup and not my first time changing something in the interfaces but I can't see my mistake here. Anybody?
networking network-manager static-ip
asked Nov 27 '17 at 5:38
ChrisChris
11112
add a comment |
I'd like to setup a static IP on Kubuntu 17.10 for my desktop PC.
ifconfig
enp10s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.100.32 netmask 255.255.255.0 broadcast 192.168.100.255
inet6 fe80::71e0:527e:96cd:4128 prefixlen 64 scopeid 0x20<link>
ether 70:85:c2:41:08:d0 txqueuelen 1000 (Ethernet)
RX packets 12849 bytes 4063036 (4.0 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 10032 bytes 1116381 (1.1 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
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 (Lokale Schleife)
RX packets 854 bytes 69858 (69.8 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 854 bytes 69858 (69.8 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Working interfaces:
auto lo
iface lo inet loopback
Not working interfaces:
auto lo
iface lo inet loopback
auto enp10s0
iface enp10s0 inet static
address 192.168.100.99
netmask 255.255.255.0
gateway 192.168.100.1
After a sudo service network-manager restart my connection isn't connected. If I delete the enp10s0 entry (revert back to the working interfaces) and restart the network-manager, the network/internet is working again.
It's a fairly standard setup and not my first time changing something in the interfaces but I can't see my mistake here. Anybody?
networking network-manager static-ip
asked Nov 27 '17 at 5:38
ChrisChris
11112
Maybe only a dns problem, try addingdns-nameservers 192.168.100.1to/etc/network/interface
– pim
Nov 27 '17 at 8:05
I tried it with and without the dns-nameservers entry but no change there.
– Chris
Nov 27 '17 at 8:13
add a comment |
I'd like to setup a static IP on Kubuntu 17.10 for my desktop PC.
ifconfig
enp10s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.100.32 netmask 255.255.255.0 broadcast 192.168.100.255
inet6 fe80::71e0:527e:96cd:4128 prefixlen 64 scopeid 0x20<link>
ether 70:85:c2:41:08:d0 txqueuelen 1000 (Ethernet)
RX packets 12849 bytes 4063036 (4.0 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 10032 bytes 1116381 (1.1 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
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 (Lokale Schleife)
RX packets 854 bytes 69858 (69.8 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 854 bytes 69858 (69.8 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Working interfaces:
auto lo
iface lo inet loopback
Not working interfaces:
auto lo
iface lo inet loopback
auto enp10s0
iface enp10s0 inet static
address 192.168.100.99
netmask 255.255.255.0
gateway 192.168.100.1
After a sudo service network-manager restart my connection isn't connected. If I delete the enp10s0 entry (revert back to the working interfaces) and restart the network-manager, the network/internet is working again.
It's a fairly standard setup and not my first time changing something in the interfaces but I can't see my mistake here. Anybody?
networking network-manager static-ip
asked Nov 27 '17 at 5:38
ChrisChris
11112
I'd like to setup a static IP on Kubuntu 17.10 for my desktop PC.
ifconfig
enp10s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.100.32 netmask 255.255.255.0 broadcast 192.168.100.255
inet6 fe80::71e0:527e:96cd:4128 prefixlen 64 scopeid 0x20<link>
ether 70:85:c2:41:08:d0 txqueuelen 1000 (Ethernet)
RX packets 12849 bytes 4063036 (4.0 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 10032 bytes 1116381 (1.1 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
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 (Lokale Schleife)
RX packets 854 bytes 69858 (69.8 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 854 bytes 69858 (69.8 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Working interfaces:
auto lo
iface lo inet loopback
Not working interfaces:
auto lo
iface lo inet loopback
auto enp10s0
iface enp10s0 inet static
address 192.168.100.99
netmask 255.255.255.0
gateway 192.168.100.1
After a sudo service network-manager restart my connection isn't connected. If I delete the enp10s0 entry (revert back to the working interfaces) and restart the network-manager, the network/internet is working again.
It's a fairly standard setup and not my first time changing something in the interfaces but I can't see my mistake here. Anybody?
networking network-manager static-ip
networking network-manager static-ip
asked Nov 27 '17 at 5:38
ChrisChris
11112
asked Nov 27 '17 at 5:38
ChrisChris
11112
asked Nov 27 '17 at 5:38
ChrisChris
11112
asked Nov 27 '17 at 5:38
ChrisChris
11112
asked Nov 27 '17 at 5:38
ChrisChris
11112
11112
Maybe only a dns problem, try addingdns-nameservers 192.168.100.1to/etc/network/interface
– pim
Nov 27 '17 at 8:05
I tried it with and without the dns-nameservers entry but no change there.
– Chris
Nov 27 '17 at 8:13
add a comment |
Maybe only a dns problem, try addingdns-nameservers 192.168.100.1to/etc/network/interface
– pim
Nov 27 '17 at 8:05
I tried it with and without the dns-nameservers entry but no change there.
– Chris
Nov 27 '17 at 8:13
Maybe only a dns problem, try adding
dns-nameservers 192.168.100.1 to /etc/network/interface– pim
Nov 27 '17 at 8:05
Maybe only a dns problem, try adding
dns-nameservers 192.168.100.1 to /etc/network/interface– pim
Nov 27 '17 at 8:05
I tried it with and without the dns-nameservers entry but no change there.
– Chris
Nov 27 '17 at 8:13
I tried it with and without the dns-nameservers entry but no change there.
– Chris
Nov 27 '17 at 8:13
add a comment |
1 Answer
1
active
oldest
votes
Ubuntu is using the Netplan configuration abstraction from version 17.10.
So instead of /etc/network/interfaces we now use /etc/netplan/*.yaml
The config for my single interface with static IP:
# Let NetworkManager manage all devices on this system
network:
version: 2
#renderer: NetworkManager
renderer: networkd
ethernets:
enp10s0:
dhcp4: no
dhcp6: no
addresses: [192.168.100.99/24]
gateway4: 192.168.100.1
nameservers:
addresses: [8.8.8.8,8.8.4.4]
sudo netplan generate generates the configuration for the network render.
Note: I tried sudo netplan --debug generate and kept on running into a message:
DEBUG: NetworkManager: definition enp10s0 is not for us (backend 1)
But still, a restart assigned the correct IP and everything seems to be working smoothly.
answered Nov 27 '17 at 12:58
ChrisChris
11112
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
});
}
});
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%2f980600%2fproblems-with-static-ip-config-via-interfaces-file%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Ubuntu is using the Netplan configuration abstraction from version 17.10.
So instead of /etc/network/interfaces we now use /etc/netplan/*.yaml
The config for my single interface with static IP:
# Let NetworkManager manage all devices on this system
network:
version: 2
#renderer: NetworkManager
renderer: networkd
ethernets:
enp10s0:
dhcp4: no
dhcp6: no
addresses: [192.168.100.99/24]
gateway4: 192.168.100.1
nameservers:
addresses: [8.8.8.8,8.8.4.4]
sudo netplan generate generates the configuration for the network render.
Note: I tried sudo netplan --debug generate and kept on running into a message:
DEBUG: NetworkManager: definition enp10s0 is not for us (backend 1)
But still, a restart assigned the correct IP and everything seems to be working smoothly.
answered Nov 27 '17 at 12:58
ChrisChris
11112
add a comment |
Ubuntu is using the Netplan configuration abstraction from version 17.10.
So instead of /etc/network/interfaces we now use /etc/netplan/*.yaml
The config for my single interface with static IP:
# Let NetworkManager manage all devices on this system
network:
version: 2
#renderer: NetworkManager
renderer: networkd
ethernets:
enp10s0:
dhcp4: no
dhcp6: no
addresses: [192.168.100.99/24]
gateway4: 192.168.100.1
nameservers:
addresses: [8.8.8.8,8.8.4.4]
sudo netplan generate generates the configuration for the network render.
Note: I tried sudo netplan --debug generate and kept on running into a message:
DEBUG: NetworkManager: definition enp10s0 is not for us (backend 1)
But still, a restart assigned the correct IP and everything seems to be working smoothly.
answered Nov 27 '17 at 12:58
ChrisChris
11112
add a comment |
Ubuntu is using the Netplan configuration abstraction from version 17.10.
So instead of /etc/network/interfaces we now use /etc/netplan/*.yaml
The config for my single interface with static IP:
# Let NetworkManager manage all devices on this system
network:
version: 2
#renderer: NetworkManager
renderer: networkd
ethernets:
enp10s0:
dhcp4: no
dhcp6: no
addresses: [192.168.100.99/24]
gateway4: 192.168.100.1
nameservers:
addresses: [8.8.8.8,8.8.4.4]
sudo netplan generate generates the configuration for the network render.
Note: I tried sudo netplan --debug generate and kept on running into a message:
DEBUG: NetworkManager: definition enp10s0 is not for us (backend 1)
But still, a restart assigned the correct IP and everything seems to be working smoothly.
answered Nov 27 '17 at 12:58
ChrisChris
11112
Ubuntu is using the Netplan configuration abstraction from version 17.10.
So instead of /etc/network/interfaces we now use /etc/netplan/*.yaml
The config for my single interface with static IP:
# Let NetworkManager manage all devices on this system
network:
version: 2
#renderer: NetworkManager
renderer: networkd
ethernets:
enp10s0:
dhcp4: no
dhcp6: no
addresses: [192.168.100.99/24]
gateway4: 192.168.100.1
nameservers:
addresses: [8.8.8.8,8.8.4.4]
sudo netplan generate generates the configuration for the network render.
Note: I tried sudo netplan --debug generate and kept on running into a message:
DEBUG: NetworkManager: definition enp10s0 is not for us (backend 1)
But still, a restart assigned the correct IP and everything seems to be working smoothly.
answered Nov 27 '17 at 12:58
ChrisChris
11112
answered Nov 27 '17 at 12:58
ChrisChris
11112
answered Nov 27 '17 at 12:58
ChrisChris
11112
answered Nov 27 '17 at 12:58
ChrisChris
11112
11112
add a comment |
add a comment |
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.
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%2f980600%2fproblems-with-static-ip-config-via-interfaces-file%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
Maybe only a dns problem, try adding
dns-nameservers 192.168.100.1to/etc/network/interface– pim
Nov 27 '17 at 8:05
I tried it with and without the dns-nameservers entry but no change there.
– Chris
Nov 27 '17 at 8:13