How can I set an address for ethernet (enp2s0) which persists through reboot?
up vote
0
down vote
favorite
Dell inspiron 5565 mint 19
ed@ed-Inspiron-5565 ~ $ ifconfig enp2s0
enp2s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether d0:94:66:ea:71:2c txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
I can enter inet address, route, dns, etc. and it works unil I reboot.
How can I make the changes permanent?
networking dell ethernet
edited 13 hours ago
heynnema
17k22052
asked 15 hours ago
Ed Iglehart
11
|
show 1 more comment
up vote
0
down vote
favorite
Dell inspiron 5565 mint 19
ed@ed-Inspiron-5565 ~ $ ifconfig enp2s0
enp2s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether d0:94:66:ea:71:2c txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
I can enter inet address, route, dns, etc. and it works unil I reboot.
How can I make the changes permanent?
networking dell ethernet
edited 13 hours ago
heynnema
17k22052
asked 15 hours ago
Ed Iglehart
11
Normally you can use network manager and changes persist. as you click ok. Something revert to initial state. The bios, or Ubuntu configs under /etc/network may do reversion of settings. Rather then use old way ifconfig, you try a human readable netplan. Check netplan.io for example of config. Then sudo netplan apply.
– Yurij
14 hours ago
@Yurij for non-server applications, NetworkManager and its GUI settings panels are the way to go. Netplan is really for servers, and the "human readable" .yaml files are somewhat difficult, for all but the simplest configs.
– heynnema
13 hours ago
@heynnema NetworkManager is optional and many users prefer networkd as netplan renderer. NetworkManager is for cli-averse users. For most configurations the yaml is simple and the system is far simpler overall than that of network-manager. As with all GUIs NM's errors and failures tend to remain hidden so that despite its seemingly simple UI its effective use is actually arcane.
– Stephen Boston
13 hours ago
@StephenBoston netplan isn't very good for allowing the user to connect to various wireless networks at will.
– heynnema
13 hours ago
@heynnema netplan itself is not responsible for maintaining network configuration. It is more about devices. For maintaining networks, we can use wpa_supplicant configuration, most easily through the wpa_cli. This is not a nice GUI application but it is simple to use, effective, and clear. Even network manager will require some configuration at the first visit to Starbucks.
– Stephen Boston
12 hours ago
|
show 1 more comment
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Dell inspiron 5565 mint 19
ed@ed-Inspiron-5565 ~ $ ifconfig enp2s0
enp2s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether d0:94:66:ea:71:2c txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
I can enter inet address, route, dns, etc. and it works unil I reboot.
How can I make the changes permanent?
networking dell ethernet
edited 13 hours ago
heynnema
17k22052
asked 15 hours ago
Ed Iglehart
11
Dell inspiron 5565 mint 19
ed@ed-Inspiron-5565 ~ $ ifconfig enp2s0
enp2s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether d0:94:66:ea:71:2c txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
I can enter inet address, route, dns, etc. and it works unil I reboot.
How can I make the changes permanent?
networking dell ethernet
networking dell ethernet
edited 13 hours ago
heynnema
17k22052
asked 15 hours ago
Ed Iglehart
11
edited 13 hours ago
heynnema
17k22052
asked 15 hours ago
Ed Iglehart
11
edited 13 hours ago
heynnema
17k22052
edited 13 hours ago
heynnema
17k22052
edited 13 hours ago
heynnema
17k22052
17k22052
asked 15 hours ago
Ed Iglehart
11
asked 15 hours ago
Ed Iglehart
11
asked 15 hours ago
Ed Iglehart
11
11
Normally you can use network manager and changes persist. as you click ok. Something revert to initial state. The bios, or Ubuntu configs under /etc/network may do reversion of settings. Rather then use old way ifconfig, you try a human readable netplan. Check netplan.io for example of config. Then sudo netplan apply.
– Yurij
14 hours ago
@Yurij for non-server applications, NetworkManager and its GUI settings panels are the way to go. Netplan is really for servers, and the "human readable" .yaml files are somewhat difficult, for all but the simplest configs.
– heynnema
13 hours ago
@heynnema NetworkManager is optional and many users prefer networkd as netplan renderer. NetworkManager is for cli-averse users. For most configurations the yaml is simple and the system is far simpler overall than that of network-manager. As with all GUIs NM's errors and failures tend to remain hidden so that despite its seemingly simple UI its effective use is actually arcane.
– Stephen Boston
13 hours ago
@StephenBoston netplan isn't very good for allowing the user to connect to various wireless networks at will.
– heynnema
13 hours ago
@heynnema netplan itself is not responsible for maintaining network configuration. It is more about devices. For maintaining networks, we can use wpa_supplicant configuration, most easily through the wpa_cli. This is not a nice GUI application but it is simple to use, effective, and clear. Even network manager will require some configuration at the first visit to Starbucks.
– Stephen Boston
12 hours ago
|
show 1 more comment
Normally you can use network manager and changes persist. as you click ok. Something revert to initial state. The bios, or Ubuntu configs under /etc/network may do reversion of settings. Rather then use old way ifconfig, you try a human readable netplan. Check netplan.io for example of config. Then sudo netplan apply.
– Yurij
14 hours ago
@Yurij for non-server applications, NetworkManager and its GUI settings panels are the way to go. Netplan is really for servers, and the "human readable" .yaml files are somewhat difficult, for all but the simplest configs.
– heynnema
13 hours ago
@heynnema NetworkManager is optional and many users prefer networkd as netplan renderer. NetworkManager is for cli-averse users. For most configurations the yaml is simple and the system is far simpler overall than that of network-manager. As with all GUIs NM's errors and failures tend to remain hidden so that despite its seemingly simple UI its effective use is actually arcane.
– Stephen Boston
13 hours ago
@StephenBoston netplan isn't very good for allowing the user to connect to various wireless networks at will.
– heynnema
13 hours ago
@heynnema netplan itself is not responsible for maintaining network configuration. It is more about devices. For maintaining networks, we can use wpa_supplicant configuration, most easily through the wpa_cli. This is not a nice GUI application but it is simple to use, effective, and clear. Even network manager will require some configuration at the first visit to Starbucks.
– Stephen Boston
12 hours ago
Normally you can use network manager and changes persist. as you click ok. Something revert to initial state. The bios, or Ubuntu configs under /etc/network may do reversion of settings. Rather then use old way ifconfig, you try a human readable netplan. Check netplan.io for example of config. Then sudo netplan apply.
– Yurij
14 hours ago
Normally you can use network manager and changes persist. as you click ok. Something revert to initial state. The bios, or Ubuntu configs under /etc/network may do reversion of settings. Rather then use old way ifconfig, you try a human readable netplan. Check netplan.io for example of config. Then sudo netplan apply.
– Yurij
14 hours ago
@Yurij for non-server applications, NetworkManager and its GUI settings panels are the way to go. Netplan is really for servers, and the "human readable" .yaml files are somewhat difficult, for all but the simplest configs.
– heynnema
13 hours ago
@Yurij for non-server applications, NetworkManager and its GUI settings panels are the way to go. Netplan is really for servers, and the "human readable" .yaml files are somewhat difficult, for all but the simplest configs.
– heynnema
13 hours ago
@heynnema NetworkManager is optional and many users prefer networkd as netplan renderer. NetworkManager is for cli-averse users. For most configurations the yaml is simple and the system is far simpler overall than that of network-manager. As with all GUIs NM's errors and failures tend to remain hidden so that despite its seemingly simple UI its effective use is actually arcane.
– Stephen Boston
13 hours ago
@heynnema NetworkManager is optional and many users prefer networkd as netplan renderer. NetworkManager is for cli-averse users. For most configurations the yaml is simple and the system is far simpler overall than that of network-manager. As with all GUIs NM's errors and failures tend to remain hidden so that despite its seemingly simple UI its effective use is actually arcane.
– Stephen Boston
13 hours ago
@StephenBoston netplan isn't very good for allowing the user to connect to various wireless networks at will.
– heynnema
13 hours ago
@StephenBoston netplan isn't very good for allowing the user to connect to various wireless networks at will.
– heynnema
13 hours ago
@heynnema netplan itself is not responsible for maintaining network configuration. It is more about devices. For maintaining networks, we can use wpa_supplicant configuration, most easily through the wpa_cli. This is not a nice GUI application but it is simple to use, effective, and clear. Even network manager will require some configuration at the first visit to Starbucks.
– Stephen Boston
12 hours ago
@heynnema netplan itself is not responsible for maintaining network configuration. It is more about devices. For maintaining networks, we can use wpa_supplicant configuration, most easily through the wpa_cli. This is not a nice GUI application but it is simple to use, effective, and clear. Even network manager will require some configuration at the first visit to Starbucks.
– Stephen Boston
12 hours ago
|
show 1 more comment
1 Answer
1
active
oldest
votes
up vote
0
down vote
When using NetworkManager, just go to the Wired Settings and select the wired profile that you'd like to set permanent settings. The IPv4 tab should look like this...
Set your IPv4 method to Manual, enter your desired Addresses and DNS servers, turn off Automatic for DNS, and you're done!
answered 13 hours ago
heynnema
17k22052
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
When using NetworkManager, just go to the Wired Settings and select the wired profile that you'd like to set permanent settings. The IPv4 tab should look like this...
Set your IPv4 method to Manual, enter your desired Addresses and DNS servers, turn off Automatic for DNS, and you're done!
answered 13 hours ago
heynnema
17k22052
add a comment |
up vote
0
down vote
When using NetworkManager, just go to the Wired Settings and select the wired profile that you'd like to set permanent settings. The IPv4 tab should look like this...
Set your IPv4 method to Manual, enter your desired Addresses and DNS servers, turn off Automatic for DNS, and you're done!
answered 13 hours ago
heynnema
17k22052
add a comment |
up vote
0
down vote
up vote
0
down vote
When using NetworkManager, just go to the Wired Settings and select the wired profile that you'd like to set permanent settings. The IPv4 tab should look like this...
Set your IPv4 method to Manual, enter your desired Addresses and DNS servers, turn off Automatic for DNS, and you're done!
answered 13 hours ago
heynnema
17k22052
When using NetworkManager, just go to the Wired Settings and select the wired profile that you'd like to set permanent settings. The IPv4 tab should look like this...
Set your IPv4 method to Manual, enter your desired Addresses and DNS servers, turn off Automatic for DNS, and you're done!
answered 13 hours ago
heynnema
17k22052
answered 13 hours ago
heynnema
17k22052
answered 13 hours ago
heynnema
17k22052
answered 13 hours ago
heynnema
17k22052
17k22052
add a comment |
add a comment |
draft saved
draft discarded
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
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1092269%2fhow-can-i-set-an-address-for-ethernet-enp2s0-which-persists-through-reboot%23new-answer', 'question_page');
}
);
Post as a guest
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
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
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
Normally you can use network manager and changes persist. as you click ok. Something revert to initial state. The bios, or Ubuntu configs under /etc/network may do reversion of settings. Rather then use old way ifconfig, you try a human readable netplan. Check netplan.io for example of config. Then sudo netplan apply.
– Yurij
14 hours ago
@Yurij for non-server applications, NetworkManager and its GUI settings panels are the way to go. Netplan is really for servers, and the "human readable" .yaml files are somewhat difficult, for all but the simplest configs.
– heynnema
13 hours ago
@heynnema NetworkManager is optional and many users prefer networkd as netplan renderer. NetworkManager is for cli-averse users. For most configurations the yaml is simple and the system is far simpler overall than that of network-manager. As with all GUIs NM's errors and failures tend to remain hidden so that despite its seemingly simple UI its effective use is actually arcane.
– Stephen Boston
13 hours ago
@StephenBoston netplan isn't very good for allowing the user to connect to various wireless networks at will.
– heynnema
13 hours ago
@heynnema netplan itself is not responsible for maintaining network configuration. It is more about devices. For maintaining networks, we can use wpa_supplicant configuration, most easily through the wpa_cli. This is not a nice GUI application but it is simple to use, effective, and clear. Even network manager will require some configuration at the first visit to Starbucks.
– Stephen Boston
12 hours ago