Why is the network configuration I set in /etc/network/interfaces ignored on Ubuntu 17.10?
I've just installed ubuntu server 17.10. During installation, it suggested me to connect to the network through wifi, and so i did. After installation was finished and system was rebooted, computer connected to the wifi automatically (which means, it saved the connection creds somewhere). But in /etc/network/interfaces
i found nothing. I need my computer connect to wifi network with static ip, so I've put configuration into the /etc/network/interfaces
:
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
# Generated by debian-installer.
# The loopback interface
auto lo
iface lo inet loopback
iface wlp2s0b1 inet static
wpa-driver wext
address 192.168.0.12
netmask 255.255.255.0
gateway 192.168.0.1
wpa-ssid *****
wpa-psk **********
dns-nameservers 8.8.8.8 192.168.0.1
auto wlp2s0b1
When system starts, it doesn't connect using my configuration. It does only after
sudo ifdown wlp2s0b1 && sudo ifup -v wlp2s0b1
and after this command, system getting a SECOND IP! Server is still available by the ip it gets from DHCP, and in the same time, it is available by the static ip!
networking server wireless static-ip netplan
|
show 9 more comments
I've just installed ubuntu server 17.10. During installation, it suggested me to connect to the network through wifi, and so i did. After installation was finished and system was rebooted, computer connected to the wifi automatically (which means, it saved the connection creds somewhere). But in /etc/network/interfaces
i found nothing. I need my computer connect to wifi network with static ip, so I've put configuration into the /etc/network/interfaces
:
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
# Generated by debian-installer.
# The loopback interface
auto lo
iface lo inet loopback
iface wlp2s0b1 inet static
wpa-driver wext
address 192.168.0.12
netmask 255.255.255.0
gateway 192.168.0.1
wpa-ssid *****
wpa-psk **********
dns-nameservers 8.8.8.8 192.168.0.1
auto wlp2s0b1
When system starts, it doesn't connect using my configuration. It does only after
sudo ifdown wlp2s0b1 && sudo ifup -v wlp2s0b1
and after this command, system getting a SECOND IP! Server is still available by the ip it gets from DHCP, and in the same time, it is available by the static ip!
networking server wireless static-ip netplan
Please edit your question to add the result of:cat /etc/network/interfaces
. Welcome to Ask Ubuntu.
– chili555
Nov 14 '17 at 21:16
> Please edit your question to add the result of: cat /etc/network/interfaces.
Done!> Welcome to Ask Ubuntu.
Thank you!
– lucius
Nov 14 '17 at 21:43
Please edit out this:wpa-driver wext
Next, do:sudo ifdown wlp2s0b1 && sudo ifup -v wlp2s0b1
The -v for verbose should produce some clues as to what's going on or going wrong. Paste it here and give us the link: paste.ubuntu.com
– chili555
Nov 14 '17 at 21:51
Should i remove this line?wpa-driver wext
– lucius
Nov 14 '17 at 21:54
Yes, please and then:sudo ifdown wlp2s0b1 && sudo ifup -v wlp2s0b1
and then paste the output so we can see what's going wrong. Also, when it gets an IP address, presumably by DHCP, what is the address?
– chili555
Nov 14 '17 at 21:59
|
show 9 more comments
I've just installed ubuntu server 17.10. During installation, it suggested me to connect to the network through wifi, and so i did. After installation was finished and system was rebooted, computer connected to the wifi automatically (which means, it saved the connection creds somewhere). But in /etc/network/interfaces
i found nothing. I need my computer connect to wifi network with static ip, so I've put configuration into the /etc/network/interfaces
:
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
# Generated by debian-installer.
# The loopback interface
auto lo
iface lo inet loopback
iface wlp2s0b1 inet static
wpa-driver wext
address 192.168.0.12
netmask 255.255.255.0
gateway 192.168.0.1
wpa-ssid *****
wpa-psk **********
dns-nameservers 8.8.8.8 192.168.0.1
auto wlp2s0b1
When system starts, it doesn't connect using my configuration. It does only after
sudo ifdown wlp2s0b1 && sudo ifup -v wlp2s0b1
and after this command, system getting a SECOND IP! Server is still available by the ip it gets from DHCP, and in the same time, it is available by the static ip!
networking server wireless static-ip netplan
I've just installed ubuntu server 17.10. During installation, it suggested me to connect to the network through wifi, and so i did. After installation was finished and system was rebooted, computer connected to the wifi automatically (which means, it saved the connection creds somewhere). But in /etc/network/interfaces
i found nothing. I need my computer connect to wifi network with static ip, so I've put configuration into the /etc/network/interfaces
:
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
# Generated by debian-installer.
# The loopback interface
auto lo
iface lo inet loopback
iface wlp2s0b1 inet static
wpa-driver wext
address 192.168.0.12
netmask 255.255.255.0
gateway 192.168.0.1
wpa-ssid *****
wpa-psk **********
dns-nameservers 8.8.8.8 192.168.0.1
auto wlp2s0b1
When system starts, it doesn't connect using my configuration. It does only after
sudo ifdown wlp2s0b1 && sudo ifup -v wlp2s0b1
and after this command, system getting a SECOND IP! Server is still available by the ip it gets from DHCP, and in the same time, it is available by the static ip!
networking server wireless static-ip netplan
networking server wireless static-ip netplan
edited Mar 14 '18 at 9:48
Mathieu Trudel-Lapierre
2,0821131
2,0821131
asked Nov 14 '17 at 21:11
luciuslucius
9317
9317
Please edit your question to add the result of:cat /etc/network/interfaces
. Welcome to Ask Ubuntu.
– chili555
Nov 14 '17 at 21:16
> Please edit your question to add the result of: cat /etc/network/interfaces.
Done!> Welcome to Ask Ubuntu.
Thank you!
– lucius
Nov 14 '17 at 21:43
Please edit out this:wpa-driver wext
Next, do:sudo ifdown wlp2s0b1 && sudo ifup -v wlp2s0b1
The -v for verbose should produce some clues as to what's going on or going wrong. Paste it here and give us the link: paste.ubuntu.com
– chili555
Nov 14 '17 at 21:51
Should i remove this line?wpa-driver wext
– lucius
Nov 14 '17 at 21:54
Yes, please and then:sudo ifdown wlp2s0b1 && sudo ifup -v wlp2s0b1
and then paste the output so we can see what's going wrong. Also, when it gets an IP address, presumably by DHCP, what is the address?
– chili555
Nov 14 '17 at 21:59
|
show 9 more comments
Please edit your question to add the result of:cat /etc/network/interfaces
. Welcome to Ask Ubuntu.
– chili555
Nov 14 '17 at 21:16
> Please edit your question to add the result of: cat /etc/network/interfaces.
Done!> Welcome to Ask Ubuntu.
Thank you!
– lucius
Nov 14 '17 at 21:43
Please edit out this:wpa-driver wext
Next, do:sudo ifdown wlp2s0b1 && sudo ifup -v wlp2s0b1
The -v for verbose should produce some clues as to what's going on or going wrong. Paste it here and give us the link: paste.ubuntu.com
– chili555
Nov 14 '17 at 21:51
Should i remove this line?wpa-driver wext
– lucius
Nov 14 '17 at 21:54
Yes, please and then:sudo ifdown wlp2s0b1 && sudo ifup -v wlp2s0b1
and then paste the output so we can see what's going wrong. Also, when it gets an IP address, presumably by DHCP, what is the address?
– chili555
Nov 14 '17 at 21:59
Please edit your question to add the result of:
cat /etc/network/interfaces
. Welcome to Ask Ubuntu.– chili555
Nov 14 '17 at 21:16
Please edit your question to add the result of:
cat /etc/network/interfaces
. Welcome to Ask Ubuntu.– chili555
Nov 14 '17 at 21:16
> Please edit your question to add the result of: cat /etc/network/interfaces.
Done! > Welcome to Ask Ubuntu.
Thank you!– lucius
Nov 14 '17 at 21:43
> Please edit your question to add the result of: cat /etc/network/interfaces.
Done! > Welcome to Ask Ubuntu.
Thank you!– lucius
Nov 14 '17 at 21:43
Please edit out this:
wpa-driver wext
Next, do: sudo ifdown wlp2s0b1 && sudo ifup -v wlp2s0b1
The -v for verbose should produce some clues as to what's going on or going wrong. Paste it here and give us the link: paste.ubuntu.com– chili555
Nov 14 '17 at 21:51
Please edit out this:
wpa-driver wext
Next, do: sudo ifdown wlp2s0b1 && sudo ifup -v wlp2s0b1
The -v for verbose should produce some clues as to what's going on or going wrong. Paste it here and give us the link: paste.ubuntu.com– chili555
Nov 14 '17 at 21:51
Should i remove this line?
wpa-driver wext
– lucius
Nov 14 '17 at 21:54
Should i remove this line?
wpa-driver wext
– lucius
Nov 14 '17 at 21:54
Yes, please and then:
sudo ifdown wlp2s0b1 && sudo ifup -v wlp2s0b1
and then paste the output so we can see what's going wrong. Also, when it gets an IP address, presumably by DHCP, what is the address?– chili555
Nov 14 '17 at 21:59
Yes, please and then:
sudo ifdown wlp2s0b1 && sudo ifup -v wlp2s0b1
and then paste the output so we can see what's going wrong. Also, when it gets an IP address, presumably by DHCP, what is the address?– chili555
Nov 14 '17 at 21:59
|
show 9 more comments
2 Answers
2
active
oldest
votes
Networking is handled by netplan by default in Ubuntu Server 17.10 and later. I suggest that you edit the /etc/netplan/01-netcfg.yaml
file to read:
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
wifis:
wlp2s0b1:
dhcp4: no
dhcp6: no
addresses: [192.168.0.21/24]
gateway4: 192.168.0.1
nameservers:
addresses: [8.8.8.8,192.168.0.1]
access-points:
"******":
password: "**********"
Exit and save your changes by running the command:
sudo netplan generate
sudo netplan apply
Please note and follow the spacing and indentation. Also note that the SSID and password are in between quotes "
.
Comment out all the wlp2s0b1 stanzas in /etc/network/interfaces
and reboot.
Any improvement?
NOTE: The exact method to set a static IP address for a server with netplan and wifi is hard to find. We may need to tweak the settings a bit.
2
You spent 2 hours (!) of your life on my problem, and now it is solved! Thank you! I love ubuntu community!
– lucius
Nov 14 '17 at 23:40
2
No, thank you! I enjoy challenging problems. Glad it's working.
– chili555
Nov 15 '17 at 0:24
netplan
is just for server network admin?
– Thufir
Nov 29 '17 at 13:29
1
@Thufir netplan is also used in destop installations but, by default, turns over configuration to Network Manager.
– chili555
Nov 29 '17 at 13:40
1
This is awesome! However, I needed to installwpasupplicant
on my ubuntu server too.
– Nabheet
Mar 25 '18 at 7:16
|
show 4 more comments
I suggest you to completely remove netplan package and use networkd by creating config(s) in /etc/systemd/network/ directory.
Netplan exists only in Ubuntu and there are no one in any other distros.
The netplan.io package does not exist in the default 17.10 repositories.
– karel
Sep 8 '18 at 21:28
Sorry, it is in 18.04. If you want to move to networkd, you just neet to: 1) sudo systemctl enable systemd-networkd 2) sudo rm /etc/network/interfaces 3) sudo rm /etc/netplan/*
– Gannet
Sep 8 '18 at 21:47
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%2f976464%2fwhy-is-the-network-configuration-i-set-in-etc-network-interfaces-ignored-on-ubu%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Networking is handled by netplan by default in Ubuntu Server 17.10 and later. I suggest that you edit the /etc/netplan/01-netcfg.yaml
file to read:
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
wifis:
wlp2s0b1:
dhcp4: no
dhcp6: no
addresses: [192.168.0.21/24]
gateway4: 192.168.0.1
nameservers:
addresses: [8.8.8.8,192.168.0.1]
access-points:
"******":
password: "**********"
Exit and save your changes by running the command:
sudo netplan generate
sudo netplan apply
Please note and follow the spacing and indentation. Also note that the SSID and password are in between quotes "
.
Comment out all the wlp2s0b1 stanzas in /etc/network/interfaces
and reboot.
Any improvement?
NOTE: The exact method to set a static IP address for a server with netplan and wifi is hard to find. We may need to tweak the settings a bit.
2
You spent 2 hours (!) of your life on my problem, and now it is solved! Thank you! I love ubuntu community!
– lucius
Nov 14 '17 at 23:40
2
No, thank you! I enjoy challenging problems. Glad it's working.
– chili555
Nov 15 '17 at 0:24
netplan
is just for server network admin?
– Thufir
Nov 29 '17 at 13:29
1
@Thufir netplan is also used in destop installations but, by default, turns over configuration to Network Manager.
– chili555
Nov 29 '17 at 13:40
1
This is awesome! However, I needed to installwpasupplicant
on my ubuntu server too.
– Nabheet
Mar 25 '18 at 7:16
|
show 4 more comments
Networking is handled by netplan by default in Ubuntu Server 17.10 and later. I suggest that you edit the /etc/netplan/01-netcfg.yaml
file to read:
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
wifis:
wlp2s0b1:
dhcp4: no
dhcp6: no
addresses: [192.168.0.21/24]
gateway4: 192.168.0.1
nameservers:
addresses: [8.8.8.8,192.168.0.1]
access-points:
"******":
password: "**********"
Exit and save your changes by running the command:
sudo netplan generate
sudo netplan apply
Please note and follow the spacing and indentation. Also note that the SSID and password are in between quotes "
.
Comment out all the wlp2s0b1 stanzas in /etc/network/interfaces
and reboot.
Any improvement?
NOTE: The exact method to set a static IP address for a server with netplan and wifi is hard to find. We may need to tweak the settings a bit.
2
You spent 2 hours (!) of your life on my problem, and now it is solved! Thank you! I love ubuntu community!
– lucius
Nov 14 '17 at 23:40
2
No, thank you! I enjoy challenging problems. Glad it's working.
– chili555
Nov 15 '17 at 0:24
netplan
is just for server network admin?
– Thufir
Nov 29 '17 at 13:29
1
@Thufir netplan is also used in destop installations but, by default, turns over configuration to Network Manager.
– chili555
Nov 29 '17 at 13:40
1
This is awesome! However, I needed to installwpasupplicant
on my ubuntu server too.
– Nabheet
Mar 25 '18 at 7:16
|
show 4 more comments
Networking is handled by netplan by default in Ubuntu Server 17.10 and later. I suggest that you edit the /etc/netplan/01-netcfg.yaml
file to read:
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
wifis:
wlp2s0b1:
dhcp4: no
dhcp6: no
addresses: [192.168.0.21/24]
gateway4: 192.168.0.1
nameservers:
addresses: [8.8.8.8,192.168.0.1]
access-points:
"******":
password: "**********"
Exit and save your changes by running the command:
sudo netplan generate
sudo netplan apply
Please note and follow the spacing and indentation. Also note that the SSID and password are in between quotes "
.
Comment out all the wlp2s0b1 stanzas in /etc/network/interfaces
and reboot.
Any improvement?
NOTE: The exact method to set a static IP address for a server with netplan and wifi is hard to find. We may need to tweak the settings a bit.
Networking is handled by netplan by default in Ubuntu Server 17.10 and later. I suggest that you edit the /etc/netplan/01-netcfg.yaml
file to read:
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
wifis:
wlp2s0b1:
dhcp4: no
dhcp6: no
addresses: [192.168.0.21/24]
gateway4: 192.168.0.1
nameservers:
addresses: [8.8.8.8,192.168.0.1]
access-points:
"******":
password: "**********"
Exit and save your changes by running the command:
sudo netplan generate
sudo netplan apply
Please note and follow the spacing and indentation. Also note that the SSID and password are in between quotes "
.
Comment out all the wlp2s0b1 stanzas in /etc/network/interfaces
and reboot.
Any improvement?
NOTE: The exact method to set a static IP address for a server with netplan and wifi is hard to find. We may need to tweak the settings a bit.
edited Sep 8 '18 at 20:54
answered Nov 14 '17 at 23:24
chili555chili555
38.6k55177
38.6k55177
2
You spent 2 hours (!) of your life on my problem, and now it is solved! Thank you! I love ubuntu community!
– lucius
Nov 14 '17 at 23:40
2
No, thank you! I enjoy challenging problems. Glad it's working.
– chili555
Nov 15 '17 at 0:24
netplan
is just for server network admin?
– Thufir
Nov 29 '17 at 13:29
1
@Thufir netplan is also used in destop installations but, by default, turns over configuration to Network Manager.
– chili555
Nov 29 '17 at 13:40
1
This is awesome! However, I needed to installwpasupplicant
on my ubuntu server too.
– Nabheet
Mar 25 '18 at 7:16
|
show 4 more comments
2
You spent 2 hours (!) of your life on my problem, and now it is solved! Thank you! I love ubuntu community!
– lucius
Nov 14 '17 at 23:40
2
No, thank you! I enjoy challenging problems. Glad it's working.
– chili555
Nov 15 '17 at 0:24
netplan
is just for server network admin?
– Thufir
Nov 29 '17 at 13:29
1
@Thufir netplan is also used in destop installations but, by default, turns over configuration to Network Manager.
– chili555
Nov 29 '17 at 13:40
1
This is awesome! However, I needed to installwpasupplicant
on my ubuntu server too.
– Nabheet
Mar 25 '18 at 7:16
2
2
You spent 2 hours (!) of your life on my problem, and now it is solved! Thank you! I love ubuntu community!
– lucius
Nov 14 '17 at 23:40
You spent 2 hours (!) of your life on my problem, and now it is solved! Thank you! I love ubuntu community!
– lucius
Nov 14 '17 at 23:40
2
2
No, thank you! I enjoy challenging problems. Glad it's working.
– chili555
Nov 15 '17 at 0:24
No, thank you! I enjoy challenging problems. Glad it's working.
– chili555
Nov 15 '17 at 0:24
netplan
is just for server network admin?– Thufir
Nov 29 '17 at 13:29
netplan
is just for server network admin?– Thufir
Nov 29 '17 at 13:29
1
1
@Thufir netplan is also used in destop installations but, by default, turns over configuration to Network Manager.
– chili555
Nov 29 '17 at 13:40
@Thufir netplan is also used in destop installations but, by default, turns over configuration to Network Manager.
– chili555
Nov 29 '17 at 13:40
1
1
This is awesome! However, I needed to install
wpasupplicant
on my ubuntu server too.– Nabheet
Mar 25 '18 at 7:16
This is awesome! However, I needed to install
wpasupplicant
on my ubuntu server too.– Nabheet
Mar 25 '18 at 7:16
|
show 4 more comments
I suggest you to completely remove netplan package and use networkd by creating config(s) in /etc/systemd/network/ directory.
Netplan exists only in Ubuntu and there are no one in any other distros.
The netplan.io package does not exist in the default 17.10 repositories.
– karel
Sep 8 '18 at 21:28
Sorry, it is in 18.04. If you want to move to networkd, you just neet to: 1) sudo systemctl enable systemd-networkd 2) sudo rm /etc/network/interfaces 3) sudo rm /etc/netplan/*
– Gannet
Sep 8 '18 at 21:47
add a comment |
I suggest you to completely remove netplan package and use networkd by creating config(s) in /etc/systemd/network/ directory.
Netplan exists only in Ubuntu and there are no one in any other distros.
The netplan.io package does not exist in the default 17.10 repositories.
– karel
Sep 8 '18 at 21:28
Sorry, it is in 18.04. If you want to move to networkd, you just neet to: 1) sudo systemctl enable systemd-networkd 2) sudo rm /etc/network/interfaces 3) sudo rm /etc/netplan/*
– Gannet
Sep 8 '18 at 21:47
add a comment |
I suggest you to completely remove netplan package and use networkd by creating config(s) in /etc/systemd/network/ directory.
Netplan exists only in Ubuntu and there are no one in any other distros.
I suggest you to completely remove netplan package and use networkd by creating config(s) in /etc/systemd/network/ directory.
Netplan exists only in Ubuntu and there are no one in any other distros.
edited Sep 8 '18 at 21:48
answered Sep 8 '18 at 21:01
GannetGannet
1177
1177
The netplan.io package does not exist in the default 17.10 repositories.
– karel
Sep 8 '18 at 21:28
Sorry, it is in 18.04. If you want to move to networkd, you just neet to: 1) sudo systemctl enable systemd-networkd 2) sudo rm /etc/network/interfaces 3) sudo rm /etc/netplan/*
– Gannet
Sep 8 '18 at 21:47
add a comment |
The netplan.io package does not exist in the default 17.10 repositories.
– karel
Sep 8 '18 at 21:28
Sorry, it is in 18.04. If you want to move to networkd, you just neet to: 1) sudo systemctl enable systemd-networkd 2) sudo rm /etc/network/interfaces 3) sudo rm /etc/netplan/*
– Gannet
Sep 8 '18 at 21:47
The netplan.io package does not exist in the default 17.10 repositories.
– karel
Sep 8 '18 at 21:28
The netplan.io package does not exist in the default 17.10 repositories.
– karel
Sep 8 '18 at 21:28
Sorry, it is in 18.04. If you want to move to networkd, you just neet to: 1) sudo systemctl enable systemd-networkd 2) sudo rm /etc/network/interfaces 3) sudo rm /etc/netplan/*
– Gannet
Sep 8 '18 at 21:47
Sorry, it is in 18.04. If you want to move to networkd, you just neet to: 1) sudo systemctl enable systemd-networkd 2) sudo rm /etc/network/interfaces 3) sudo rm /etc/netplan/*
– Gannet
Sep 8 '18 at 21:47
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%2f976464%2fwhy-is-the-network-configuration-i-set-in-etc-network-interfaces-ignored-on-ubu%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
Please edit your question to add the result of:
cat /etc/network/interfaces
. Welcome to Ask Ubuntu.– chili555
Nov 14 '17 at 21:16
> Please edit your question to add the result of: cat /etc/network/interfaces.
Done!> Welcome to Ask Ubuntu.
Thank you!– lucius
Nov 14 '17 at 21:43
Please edit out this:
wpa-driver wext
Next, do:sudo ifdown wlp2s0b1 && sudo ifup -v wlp2s0b1
The -v for verbose should produce some clues as to what's going on or going wrong. Paste it here and give us the link: paste.ubuntu.com– chili555
Nov 14 '17 at 21:51
Should i remove this line?
wpa-driver wext
– lucius
Nov 14 '17 at 21:54
Yes, please and then:
sudo ifdown wlp2s0b1 && sudo ifup -v wlp2s0b1
and then paste the output so we can see what's going wrong. Also, when it gets an IP address, presumably by DHCP, what is the address?– chili555
Nov 14 '17 at 21:59