ifconfig-changes not saved after rebootwired connection not working under Ubuntu 10.04Why does wlan1 not get a static IP?Wait for interface to brought up before UDHCPhow does /etc/init.d/networking restart cause wpa_supplicant to be run using the previous configurations?Ubuntu 15.10 Network Interfaces Namewhy does ifup wlan0 also configure wlan1?Ubuntu 16.04 not getting dhcp leaseNetwork manager show eth0 connection but no interenet accessChange Mac Address permanently inside /etc/network/interfacesDebian8 server : Can't resolve IP adresses or DNS
How old can references or sources in a thesis be?
What Brexit solution does the DUP want?
How long does it take to type this?
Motorized valve interfering with button?
How can bays and straits be determined in a procedurally generated map?
Why did the Germans forbid the possession of pet pigeons in Rostov-on-Don in 1941?
Why Is Death Allowed In the Matrix?
What would the Romans have called "sorcery"?
Is it possible to do 50 km distance without any previous training?
TGV timetables / schedules?
Can Medicine checks be used, with decent rolls, to completely mitigate the risk of death from ongoing damage?
Is there a minimum number of transactions in a block?
Can I interfere when another PC is about to be attacked?
Circuitry of TV splitters
Is it tax fraud for an individual to declare non-taxable revenue as taxable income? (US tax laws)
DOS, create pipe for stdin/stdout of command.com(or 4dos.com) in C or Batch?
Do airline pilots ever risk not hearing communication directed to them specifically, from traffic controllers?
How do you conduct xenoanthropology after first contact?
black dwarf stars and dark matter
What do you call a Matrix-like slowdown and camera movement effect?
Prevent a directory in /tmp from being deleted
I’m planning on buying a laser printer but concerned about the life cycle of toner in the machine
Why is the design of haulage companies so “special”?
declaring a variable twice in IIFE
ifconfig-changes not saved after reboot
wired connection not working under Ubuntu 10.04Why does wlan1 not get a static IP?Wait for interface to brought up before UDHCPhow does /etc/init.d/networking restart cause wpa_supplicant to be run using the previous configurations?Ubuntu 15.10 Network Interfaces Namewhy does ifup wlan0 also configure wlan1?Ubuntu 16.04 not getting dhcp leaseNetwork manager show eth0 connection but no interenet accessChange Mac Address permanently inside /etc/network/interfacesDebian8 server : Can't resolve IP adresses or DNS
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I changed my network device names, but it doesn't kept saved after rebooting. I also deactivated interface wlan0, but it is still on again after rebooting.
Using UBUNTU.
Here /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d
# The loopback network interface
auto lo
iface lo inet loopback
# The wan0 network interface
auto wan0
iface wan0 inet dhcp
# The eth0 network interface
auto eth0
iface eth0 inet dhcp
linux ubuntu ifconfig
migrated from serverfault.com Oct 5 '16 at 14:45
This question came from our site for system and network administrators.
add a comment |
I changed my network device names, but it doesn't kept saved after rebooting. I also deactivated interface wlan0, but it is still on again after rebooting.
Using UBUNTU.
Here /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d
# The loopback network interface
auto lo
iface lo inet loopback
# The wan0 network interface
auto wan0
iface wan0 inet dhcp
# The eth0 network interface
auto eth0
iface eth0 inet dhcp
linux ubuntu ifconfig
migrated from serverfault.com Oct 5 '16 at 14:45
This question came from our site for system and network administrators.
I am sorry, is it wan0 or wlan0? You seem to be mentioning both and I sense this may be just a matter of a typo somewhere.
– Boris Epstein
Oct 2 '16 at 13:22
@BorisEpsteinwan0
andwlan0
.wlan0
is the interface that should stay disabled andwan0
andeth0
are the interfaces that get back to their original name after boot.
– 1072
Oct 3 '16 at 9:52
add a comment |
I changed my network device names, but it doesn't kept saved after rebooting. I also deactivated interface wlan0, but it is still on again after rebooting.
Using UBUNTU.
Here /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d
# The loopback network interface
auto lo
iface lo inet loopback
# The wan0 network interface
auto wan0
iface wan0 inet dhcp
# The eth0 network interface
auto eth0
iface eth0 inet dhcp
linux ubuntu ifconfig
I changed my network device names, but it doesn't kept saved after rebooting. I also deactivated interface wlan0, but it is still on again after rebooting.
Using UBUNTU.
Here /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d
# The loopback network interface
auto lo
iface lo inet loopback
# The wan0 network interface
auto wan0
iface wan0 inet dhcp
# The eth0 network interface
auto eth0
iface eth0 inet dhcp
linux ubuntu ifconfig
linux ubuntu ifconfig
asked Oct 2 '16 at 11:01
1072
migrated from serverfault.com Oct 5 '16 at 14:45
This question came from our site for system and network administrators.
migrated from serverfault.com Oct 5 '16 at 14:45
This question came from our site for system and network administrators.
I am sorry, is it wan0 or wlan0? You seem to be mentioning both and I sense this may be just a matter of a typo somewhere.
– Boris Epstein
Oct 2 '16 at 13:22
@BorisEpsteinwan0
andwlan0
.wlan0
is the interface that should stay disabled andwan0
andeth0
are the interfaces that get back to their original name after boot.
– 1072
Oct 3 '16 at 9:52
add a comment |
I am sorry, is it wan0 or wlan0? You seem to be mentioning both and I sense this may be just a matter of a typo somewhere.
– Boris Epstein
Oct 2 '16 at 13:22
@BorisEpsteinwan0
andwlan0
.wlan0
is the interface that should stay disabled andwan0
andeth0
are the interfaces that get back to their original name after boot.
– 1072
Oct 3 '16 at 9:52
I am sorry, is it wan0 or wlan0? You seem to be mentioning both and I sense this may be just a matter of a typo somewhere.
– Boris Epstein
Oct 2 '16 at 13:22
I am sorry, is it wan0 or wlan0? You seem to be mentioning both and I sense this may be just a matter of a typo somewhere.
– Boris Epstein
Oct 2 '16 at 13:22
@BorisEpstein
wan0
and wlan0
. wlan0
is the interface that should stay disabled and wan0
and eth0
are the interfaces that get back to their original name after boot.– 1072
Oct 3 '16 at 9:52
@BorisEpstein
wan0
and wlan0
. wlan0
is the interface that should stay disabled and wan0
and eth0
are the interfaces that get back to their original name after boot.– 1072
Oct 3 '16 at 9:52
add a comment |
4 Answers
4
active
oldest
votes
If you use ifconfig
to configure your network interfaces, the changes will be lost after reboot.
To make your changes persistent, you need to modify configuration files like /etc/network/interfaces
. For example, to disable an interface you can simply remove its config part from the file.
You can check man interfaces
for available options and format of network config file for Ubuntu.
1
Problem is thatwlan0
doesn't has an entry in the file, but is again available after reboot.
– 1072
Oct 3 '16 at 9:50
add a comment |
For the interface name part, you should check this file (if it's there on Ubuntu, I have it on Debian):
/etc/udev/rules.d/70-persistent-net.rules
Edit it if needed as per the comment inside
If there's no such file (in recent udev), there's still a specific package you can use to have the renaming done at boot: ifrename
, or you can add some boot script yourself.
for deactivating wlan0, there are different things beside the /etc/network/interfaces. There's always NetworkManager lurking around. It's handy but it often interferes with the settings. See if you can do something with NetworkManager graphically or using nmcli
, like:
nmcli radio wifi off
There's also the rfkill
command (rfkill package). It uses the same backend as nmcli radio
. For example you can prevent all wireless related activity with rfkill block all
/etc/udev/rules.d/70-persistent-net.rules
doesn't exist ... so is there are way to rename the connections usingnmcli
?
– 1072
Oct 3 '16 at 9:54
add a comment |
In case anyone else is here looking for help in later versions of ubuntu server (17.x). They have switched from network
(/etc/network/interfaces
) to netplan
(/etc/netplan/*.yml
).
Hopefully this helps someone else/saves them some time.
Simple sample for a static IP configuration.
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
ethernets:
eth0:
dhcp4: no
dhcp6: no
addresses: [192.168.1.100/24]
gateway4: 192.168.1.1
nameservers:
addresses: [192.168.1.1,8.8.8.8]
add a comment |
On ubuntu v17 when the static ip parameters in the file "interfaces" were set after rebooting the machine it gets the IP address from DHCP. (After this /etc/init.d/networking restart
or ifdown/ifup work well but they are only temporary solutions). It is enough to replace the "dhcp4: yes" row to "dhcp4: no" in the /etc/netplan/*.yaml
file and after reboot the settings in the file "interfaces" are asserted without giving any further settings in the netplan file. (A note: in man pages the syntax talks about only "dhcp4: true" with static IP settings(!))
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f314494%2fifconfig-changes-not-saved-after-reboot%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
If you use ifconfig
to configure your network interfaces, the changes will be lost after reboot.
To make your changes persistent, you need to modify configuration files like /etc/network/interfaces
. For example, to disable an interface you can simply remove its config part from the file.
You can check man interfaces
for available options and format of network config file for Ubuntu.
1
Problem is thatwlan0
doesn't has an entry in the file, but is again available after reboot.
– 1072
Oct 3 '16 at 9:50
add a comment |
If you use ifconfig
to configure your network interfaces, the changes will be lost after reboot.
To make your changes persistent, you need to modify configuration files like /etc/network/interfaces
. For example, to disable an interface you can simply remove its config part from the file.
You can check man interfaces
for available options and format of network config file for Ubuntu.
1
Problem is thatwlan0
doesn't has an entry in the file, but is again available after reboot.
– 1072
Oct 3 '16 at 9:50
add a comment |
If you use ifconfig
to configure your network interfaces, the changes will be lost after reboot.
To make your changes persistent, you need to modify configuration files like /etc/network/interfaces
. For example, to disable an interface you can simply remove its config part from the file.
You can check man interfaces
for available options and format of network config file for Ubuntu.
If you use ifconfig
to configure your network interfaces, the changes will be lost after reboot.
To make your changes persistent, you need to modify configuration files like /etc/network/interfaces
. For example, to disable an interface you can simply remove its config part from the file.
You can check man interfaces
for available options and format of network config file for Ubuntu.
answered Oct 2 '16 at 11:22
KhaledKhaled
28625
28625
1
Problem is thatwlan0
doesn't has an entry in the file, but is again available after reboot.
– 1072
Oct 3 '16 at 9:50
add a comment |
1
Problem is thatwlan0
doesn't has an entry in the file, but is again available after reboot.
– 1072
Oct 3 '16 at 9:50
1
1
Problem is that
wlan0
doesn't has an entry in the file, but is again available after reboot.– 1072
Oct 3 '16 at 9:50
Problem is that
wlan0
doesn't has an entry in the file, but is again available after reboot.– 1072
Oct 3 '16 at 9:50
add a comment |
For the interface name part, you should check this file (if it's there on Ubuntu, I have it on Debian):
/etc/udev/rules.d/70-persistent-net.rules
Edit it if needed as per the comment inside
If there's no such file (in recent udev), there's still a specific package you can use to have the renaming done at boot: ifrename
, or you can add some boot script yourself.
for deactivating wlan0, there are different things beside the /etc/network/interfaces. There's always NetworkManager lurking around. It's handy but it often interferes with the settings. See if you can do something with NetworkManager graphically or using nmcli
, like:
nmcli radio wifi off
There's also the rfkill
command (rfkill package). It uses the same backend as nmcli radio
. For example you can prevent all wireless related activity with rfkill block all
/etc/udev/rules.d/70-persistent-net.rules
doesn't exist ... so is there are way to rename the connections usingnmcli
?
– 1072
Oct 3 '16 at 9:54
add a comment |
For the interface name part, you should check this file (if it's there on Ubuntu, I have it on Debian):
/etc/udev/rules.d/70-persistent-net.rules
Edit it if needed as per the comment inside
If there's no such file (in recent udev), there's still a specific package you can use to have the renaming done at boot: ifrename
, or you can add some boot script yourself.
for deactivating wlan0, there are different things beside the /etc/network/interfaces. There's always NetworkManager lurking around. It's handy but it often interferes with the settings. See if you can do something with NetworkManager graphically or using nmcli
, like:
nmcli radio wifi off
There's also the rfkill
command (rfkill package). It uses the same backend as nmcli radio
. For example you can prevent all wireless related activity with rfkill block all
/etc/udev/rules.d/70-persistent-net.rules
doesn't exist ... so is there are way to rename the connections usingnmcli
?
– 1072
Oct 3 '16 at 9:54
add a comment |
For the interface name part, you should check this file (if it's there on Ubuntu, I have it on Debian):
/etc/udev/rules.d/70-persistent-net.rules
Edit it if needed as per the comment inside
If there's no such file (in recent udev), there's still a specific package you can use to have the renaming done at boot: ifrename
, or you can add some boot script yourself.
for deactivating wlan0, there are different things beside the /etc/network/interfaces. There's always NetworkManager lurking around. It's handy but it often interferes with the settings. See if you can do something with NetworkManager graphically or using nmcli
, like:
nmcli radio wifi off
There's also the rfkill
command (rfkill package). It uses the same backend as nmcli radio
. For example you can prevent all wireless related activity with rfkill block all
For the interface name part, you should check this file (if it's there on Ubuntu, I have it on Debian):
/etc/udev/rules.d/70-persistent-net.rules
Edit it if needed as per the comment inside
If there's no such file (in recent udev), there's still a specific package you can use to have the renaming done at boot: ifrename
, or you can add some boot script yourself.
for deactivating wlan0, there are different things beside the /etc/network/interfaces. There's always NetworkManager lurking around. It's handy but it often interferes with the settings. See if you can do something with NetworkManager graphically or using nmcli
, like:
nmcli radio wifi off
There's also the rfkill
command (rfkill package). It uses the same backend as nmcli radio
. For example you can prevent all wireless related activity with rfkill block all
answered Oct 2 '16 at 12:08
A.BA.B
5,94711030
5,94711030
/etc/udev/rules.d/70-persistent-net.rules
doesn't exist ... so is there are way to rename the connections usingnmcli
?
– 1072
Oct 3 '16 at 9:54
add a comment |
/etc/udev/rules.d/70-persistent-net.rules
doesn't exist ... so is there are way to rename the connections usingnmcli
?
– 1072
Oct 3 '16 at 9:54
/etc/udev/rules.d/70-persistent-net.rules
doesn't exist ... so is there are way to rename the connections using nmcli
?– 1072
Oct 3 '16 at 9:54
/etc/udev/rules.d/70-persistent-net.rules
doesn't exist ... so is there are way to rename the connections using nmcli
?– 1072
Oct 3 '16 at 9:54
add a comment |
In case anyone else is here looking for help in later versions of ubuntu server (17.x). They have switched from network
(/etc/network/interfaces
) to netplan
(/etc/netplan/*.yml
).
Hopefully this helps someone else/saves them some time.
Simple sample for a static IP configuration.
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
ethernets:
eth0:
dhcp4: no
dhcp6: no
addresses: [192.168.1.100/24]
gateway4: 192.168.1.1
nameservers:
addresses: [192.168.1.1,8.8.8.8]
add a comment |
In case anyone else is here looking for help in later versions of ubuntu server (17.x). They have switched from network
(/etc/network/interfaces
) to netplan
(/etc/netplan/*.yml
).
Hopefully this helps someone else/saves them some time.
Simple sample for a static IP configuration.
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
ethernets:
eth0:
dhcp4: no
dhcp6: no
addresses: [192.168.1.100/24]
gateway4: 192.168.1.1
nameservers:
addresses: [192.168.1.1,8.8.8.8]
add a comment |
In case anyone else is here looking for help in later versions of ubuntu server (17.x). They have switched from network
(/etc/network/interfaces
) to netplan
(/etc/netplan/*.yml
).
Hopefully this helps someone else/saves them some time.
Simple sample for a static IP configuration.
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
ethernets:
eth0:
dhcp4: no
dhcp6: no
addresses: [192.168.1.100/24]
gateway4: 192.168.1.1
nameservers:
addresses: [192.168.1.1,8.8.8.8]
In case anyone else is here looking for help in later versions of ubuntu server (17.x). They have switched from network
(/etc/network/interfaces
) to netplan
(/etc/netplan/*.yml
).
Hopefully this helps someone else/saves them some time.
Simple sample for a static IP configuration.
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
ethernets:
eth0:
dhcp4: no
dhcp6: no
addresses: [192.168.1.100/24]
gateway4: 192.168.1.1
nameservers:
addresses: [192.168.1.1,8.8.8.8]
answered Jan 11 '18 at 10:44
CheruvianCheruvian
1113
1113
add a comment |
add a comment |
On ubuntu v17 when the static ip parameters in the file "interfaces" were set after rebooting the machine it gets the IP address from DHCP. (After this /etc/init.d/networking restart
or ifdown/ifup work well but they are only temporary solutions). It is enough to replace the "dhcp4: yes" row to "dhcp4: no" in the /etc/netplan/*.yaml
file and after reboot the settings in the file "interfaces" are asserted without giving any further settings in the netplan file. (A note: in man pages the syntax talks about only "dhcp4: true" with static IP settings(!))
add a comment |
On ubuntu v17 when the static ip parameters in the file "interfaces" were set after rebooting the machine it gets the IP address from DHCP. (After this /etc/init.d/networking restart
or ifdown/ifup work well but they are only temporary solutions). It is enough to replace the "dhcp4: yes" row to "dhcp4: no" in the /etc/netplan/*.yaml
file and after reboot the settings in the file "interfaces" are asserted without giving any further settings in the netplan file. (A note: in man pages the syntax talks about only "dhcp4: true" with static IP settings(!))
add a comment |
On ubuntu v17 when the static ip parameters in the file "interfaces" were set after rebooting the machine it gets the IP address from DHCP. (After this /etc/init.d/networking restart
or ifdown/ifup work well but they are only temporary solutions). It is enough to replace the "dhcp4: yes" row to "dhcp4: no" in the /etc/netplan/*.yaml
file and after reboot the settings in the file "interfaces" are asserted without giving any further settings in the netplan file. (A note: in man pages the syntax talks about only "dhcp4: true" with static IP settings(!))
On ubuntu v17 when the static ip parameters in the file "interfaces" were set after rebooting the machine it gets the IP address from DHCP. (After this /etc/init.d/networking restart
or ifdown/ifup work well but they are only temporary solutions). It is enough to replace the "dhcp4: yes" row to "dhcp4: no" in the /etc/netplan/*.yaml
file and after reboot the settings in the file "interfaces" are asserted without giving any further settings in the netplan file. (A note: in man pages the syntax talks about only "dhcp4: true" with static IP settings(!))
edited Mar 27 at 14:49
GAD3R
28k1958114
28k1958114
answered Mar 27 at 14:47
Zoltán KallóZoltán Kalló
111
111
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f314494%2fifconfig-changes-not-saved-after-reboot%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
-ifconfig, linux, ubuntu
I am sorry, is it wan0 or wlan0? You seem to be mentioning both and I sense this may be just a matter of a typo somewhere.
– Boris Epstein
Oct 2 '16 at 13:22
@BorisEpstein
wan0
andwlan0
.wlan0
is the interface that should stay disabled andwan0
andeth0
are the interfaces that get back to their original name after boot.– 1072
Oct 3 '16 at 9:52