Ubuntu Server 18.04.1 Cannot Keep Static IP Address After AssignedHow do I disable network manager permanently?netplan vs NetworkManager on Ubuntu 18.04 and aboveNetPlan Static IP address not acceptiingRaspberry Pi 3B with Ubuntu Server(CLI) with No Ethernet Recognition and No Wlan0 ListWireless problems Lenovo Thinkpad E580How to enable wireless on Ubuntu Server 18.04 via CLI?Updating server OS, installation and internet connectivity issues in using Ubuntu Server
No transit zone at Linate airport. Couldn't get on connecting flight. Whose responsibility is it?
bc - command: not giving appropriate results
one list minus another
Bi Directional Dictionary
What license do I use when I don't want stock image companies charging people money for photos?
Placing a contour line at y when f(x)>=y
"Sack" data structure in C#
Is a datagram from an upper network layer converted 1:1 to one of the lower layer?
I've never seen this before. Is this primarily a "rote computational trick" for multiplication by 9 ...?
Reference book or websites on how Mac OS works
How to join many tables side by side?
The algorithm of the new quantum factoring record 1,099,551,473,989
Risk of AIDS Infection - Overestimation?
Is it safe to wear earplugs in flight?
Who started calling the matrix multiplication "multiplication"?
Which seat 'predicts' the outcomes of UK General Elections the best?
How does a religion based around destroying the world attract followers
Missing links in crossword
Do photons have kinetic energy?
Is harmlessly appearing to be a school bus driver a crime?
What are the disadvantages of using a Zener diode over a linear voltage regulator?
shadow prices associated with nonnegativity constraints
How to pair a xrightarrow with text on the top) to a sort of xleftarrow (with text on the bottom)?
Book about aliens sending instructions to build a supercomputer
Ubuntu Server 18.04.1 Cannot Keep Static IP Address After Assigned
How do I disable network manager permanently?netplan vs NetworkManager on Ubuntu 18.04 and aboveNetPlan Static IP address not acceptiingRaspberry Pi 3B with Ubuntu Server(CLI) with No Ethernet Recognition and No Wlan0 ListWireless problems Lenovo Thinkpad E580How to enable wireless on Ubuntu Server 18.04 via CLI?Updating server OS, installation and internet connectivity issues in using Ubuntu Server
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;
2
I am trying to assign a series of static IP addresses to my homelab server so that I can run a media service.
I edited /etc/netplan/ with the following:
01-netcfg.yaml:
network:
version: 2
renderer: networkd
ethernets:
enp0s20f0:
dhcp4: no
addresses: [192.168.0.100/24]
gateway4: 192.168.0.1
nameservers:
addresses: [192.168.0.1,8.8.4.8,8.8.8.8]
Then I repeated for the other three ports I was assigning. e.g., 02-netcfg.yaml, etc.
When I run
sudo netplan apply
I get the correct IP addresses.
After a period of mins, I lose the assigned numbers and get new IPs from my router's DHCP.
I've also tried to set the static IPs via the router, but I get the same problem.
Any ideas?
(I'm happy to provide more logs as needed.)
UPDATE: Output from syslog
/var/log$ tail -100 syslog
Aug 19 12:13:06 mythtv-server systemd[1]: Starting Network Name Resolution...
Aug 19 12:13:06 mythtv-server systemd-resolved[14306]: Positive Trust Anchors:
Aug 19 12:13:06 mythtv-server systemd-resolved[14306]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Aug 19 12:13:06 mythtv-server systemd-resolved[14306]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Aug 19 12:13:06 mythtv-server systemd-resolved[14306]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test
Aug 19 12:13:06 mythtv-server systemd-resolved[14306]: Using system hostname 'mythtv-server'.
Aug 19 12:13:06 mythtv-server systemd[1]: Started Network Name Resolution.
Aug 19 12:13:10 mythtv-server dhclient[11809]: DHCPDISCOVER on enp0s20f3 to 255.255.255.255 port 67 interval 11 (xid=0x80e80479)
Aug 19 12:13:10 mythtv-server dhclient[11809]: send_packet: No such device or address
Aug 19 12:13:10 mythtv-server dhclient[11809]: dhclient.c:2438: Failed to send 300 byte long packet over enp0s20f3 interface.
Aug 19 12:13:10 mythtv-server dhclient[28319]: DHCPDISCOVER on enp0s20f3 to 255.255.255.255 port 67 interval 20 (xid=0x6ab1ec09)
Aug 19 12:13:10 mythtv-server dhclient[28319]: send_packet: No such device or address
Aug 19 12:13:10 mythtv-server dhclient[28319]: dhclient.c:2438: Failed to send 300 byte long packet over enp0s20f3 interface.
Aug 19 12:13:11 mythtv-server dhclient[27706]: DHCPDISCOVER on enp0s20f3 to 255.255.255.255 port 67 interval 12 (xid=0x9f278b66)
Aug 19 12:13:11 mythtv-server dhclient[27706]: send_packet: No such device or address
Aug 19 12:13:11 mythtv-server dhclient[27706]: dhclient.c:2438: Failed to send 300 byte long packet over enp0s20f3 interface.
Aug 19 12:13:15 mythtv-server dhclient[28739]: DHCPDISCOVER on enp0s20f1 to 255.255.255.255 port 67 interval 3 (xid=0xf969ca13)
Aug 19 12:13:15 mythtv-server dhclient[28739]: send_packet: No such device or address
Aug 19 12:13:15 mythtv-server dhclient[28739]: dhclient.c:2438: Failed to send 300 byte long packet over enp0s20f1 interface.
Aug 19 12:13:18 mythtv-server dhclient[11809]: DHCPDISCOVER on enp0s20f1 to 255.255.255.255 port 67 interval 7 (xid=0x8354462)
Aug 19 12:13:18 mythtv-server dhclient[11809]: send_packet: No such device or address
Aug 19 12:13:18 mythtv-server dhclient[11809]: dhclient.c:2438: Failed to send 300 byte long packet over enp0s20f1 interface.
Aug 19 12:13:18 mythtv-server dhclient[3290]: DHCPDISCOVER on enp0s20f3 to 255.255.255.255 port 67 interval 9 (xid=0xc9123118)
Aug 19 12:13:18 mythtv-server dhclient[3290]: send_packet: No such device or address
Aug 19 12:13:18 mythtv-server dhclient[3290]: dhclient.c:2438: Failed to send 300 byte long packet over enp0s20f3 interface.
Aug 19 12:13:18 mythtv-server dhclient[28739]: DHCPDISCOVER on enp0s20f1 to 255.255.255.255 port 67 interval 6 (xid=0xf969ca13)
Aug 19 12:13:18 mythtv-server dhclient[28739]: send_packet: No such device or address
Aug 19 12:13:18 mythtv-server dhclient[28739]: dhclient.c:2438: Failed to send 300 byte long packet over enp0s20f1 interface.
Aug 19 12:13:21 mythtv-server dhclient[11809]: DHCPDISCOVER on enp0s20f3 to 255.255.255.255 port 67 interval 15 (xid=0x80e80479)
UPDATE2: I've added the output from ip a
ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s20f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether ac:1f:6b:46:da:74 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.100/24 brd 192.168.0.255 scope global enp0s20f0
valid_lft forever preferred_lft forever
inet 192.168.0.6/24 brd 192.168.0.255 scope global secondary dynamic enp0s20f0
valid_lft 2391sec preferred_lft 2391sec
inet6 2605:a000:45c9:3100::3/128 scope global dynamic noprefixroute
valid_lft 3277sec preferred_lft 1477sec
inet6 2605:a000:45c9:3100:ae1f:6bff:fe46:da74/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 604796sec preferred_lft 604796sec
inet6 fe80::ae1f:6bff:fe46:da74/64 scope link
valid_lft forever preferred_lft forever
3: enp0s20f1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether ac:1f:6b:46:da:75 brd ff:ff:ff:ff:ff:ff
4: enp0s20f2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether ac:1f:6b:46:da:76 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.102/24 brd 192.168.0.255 scope global enp0s20f2
valid_lft forever preferred_lft forever
inet 192.168.0.68/24 brd 192.168.0.255 scope global secondary dynamic enp0s20f2
valid_lft 2389sec preferred_lft 2389sec
inet6 2605:a000:45c9:3100::2/128 scope global dynamic noprefixroute
valid_lft 3379sec preferred_lft 1579sec
inet6 2605:a000:45c9:3100:ae1f:6bff:fe46:da76/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 604796sec preferred_lft 604796sec
inet6 fe80::ae1f:6bff:fe46:da76/64 scope link
valid_lft forever preferred_lft forever
5: enp0s20f3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether ac:1f:6b:46:da:77 brd ff:ff:ff:ff:ff:ff
networking server 18.04 ip netplan
edited Oct 1 at 12:52
Saxtheowl
36810 bronze badges
asked Aug 18 '18 at 21:32
crumcrum
194 bronze badges
|
show 4 more comments
2
I am trying to assign a series of static IP addresses to my homelab server so that I can run a media service.
I edited /etc/netplan/ with the following:
01-netcfg.yaml:
network:
version: 2
renderer: networkd
ethernets:
enp0s20f0:
dhcp4: no
addresses: [192.168.0.100/24]
gateway4: 192.168.0.1
nameservers:
addresses: [192.168.0.1,8.8.4.8,8.8.8.8]
Then I repeated for the other three ports I was assigning. e.g., 02-netcfg.yaml, etc.
When I run
sudo netplan apply
I get the correct IP addresses.
After a period of mins, I lose the assigned numbers and get new IPs from my router's DHCP.
I've also tried to set the static IPs via the router, but I get the same problem.
Any ideas?
(I'm happy to provide more logs as needed.)
UPDATE: Output from syslog
/var/log$ tail -100 syslog
Aug 19 12:13:06 mythtv-server systemd[1]: Starting Network Name Resolution...
Aug 19 12:13:06 mythtv-server systemd-resolved[14306]: Positive Trust Anchors:
Aug 19 12:13:06 mythtv-server systemd-resolved[14306]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Aug 19 12:13:06 mythtv-server systemd-resolved[14306]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Aug 19 12:13:06 mythtv-server systemd-resolved[14306]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test
Aug 19 12:13:06 mythtv-server systemd-resolved[14306]: Using system hostname 'mythtv-server'.
Aug 19 12:13:06 mythtv-server systemd[1]: Started Network Name Resolution.
Aug 19 12:13:10 mythtv-server dhclient[11809]: DHCPDISCOVER on enp0s20f3 to 255.255.255.255 port 67 interval 11 (xid=0x80e80479)
Aug 19 12:13:10 mythtv-server dhclient[11809]: send_packet: No such device or address
Aug 19 12:13:10 mythtv-server dhclient[11809]: dhclient.c:2438: Failed to send 300 byte long packet over enp0s20f3 interface.
Aug 19 12:13:10 mythtv-server dhclient[28319]: DHCPDISCOVER on enp0s20f3 to 255.255.255.255 port 67 interval 20 (xid=0x6ab1ec09)
Aug 19 12:13:10 mythtv-server dhclient[28319]: send_packet: No such device or address
Aug 19 12:13:10 mythtv-server dhclient[28319]: dhclient.c:2438: Failed to send 300 byte long packet over enp0s20f3 interface.
Aug 19 12:13:11 mythtv-server dhclient[27706]: DHCPDISCOVER on enp0s20f3 to 255.255.255.255 port 67 interval 12 (xid=0x9f278b66)
Aug 19 12:13:11 mythtv-server dhclient[27706]: send_packet: No such device or address
Aug 19 12:13:11 mythtv-server dhclient[27706]: dhclient.c:2438: Failed to send 300 byte long packet over enp0s20f3 interface.
Aug 19 12:13:15 mythtv-server dhclient[28739]: DHCPDISCOVER on enp0s20f1 to 255.255.255.255 port 67 interval 3 (xid=0xf969ca13)
Aug 19 12:13:15 mythtv-server dhclient[28739]: send_packet: No such device or address
Aug 19 12:13:15 mythtv-server dhclient[28739]: dhclient.c:2438: Failed to send 300 byte long packet over enp0s20f1 interface.
Aug 19 12:13:18 mythtv-server dhclient[11809]: DHCPDISCOVER on enp0s20f1 to 255.255.255.255 port 67 interval 7 (xid=0x8354462)
Aug 19 12:13:18 mythtv-server dhclient[11809]: send_packet: No such device or address
Aug 19 12:13:18 mythtv-server dhclient[11809]: dhclient.c:2438: Failed to send 300 byte long packet over enp0s20f1 interface.
Aug 19 12:13:18 mythtv-server dhclient[3290]: DHCPDISCOVER on enp0s20f3 to 255.255.255.255 port 67 interval 9 (xid=0xc9123118)
Aug 19 12:13:18 mythtv-server dhclient[3290]: send_packet: No such device or address
Aug 19 12:13:18 mythtv-server dhclient[3290]: dhclient.c:2438: Failed to send 300 byte long packet over enp0s20f3 interface.
Aug 19 12:13:18 mythtv-server dhclient[28739]: DHCPDISCOVER on enp0s20f1 to 255.255.255.255 port 67 interval 6 (xid=0xf969ca13)
Aug 19 12:13:18 mythtv-server dhclient[28739]: send_packet: No such device or address
Aug 19 12:13:18 mythtv-server dhclient[28739]: dhclient.c:2438: Failed to send 300 byte long packet over enp0s20f1 interface.
Aug 19 12:13:21 mythtv-server dhclient[11809]: DHCPDISCOVER on enp0s20f3 to 255.255.255.255 port 67 interval 15 (xid=0x80e80479)
UPDATE2: I've added the output from ip a
ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s20f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether ac:1f:6b:46:da:74 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.100/24 brd 192.168.0.255 scope global enp0s20f0
valid_lft forever preferred_lft forever
inet 192.168.0.6/24 brd 192.168.0.255 scope global secondary dynamic enp0s20f0
valid_lft 2391sec preferred_lft 2391sec
inet6 2605:a000:45c9:3100::3/128 scope global dynamic noprefixroute
valid_lft 3277sec preferred_lft 1477sec
inet6 2605:a000:45c9:3100:ae1f:6bff:fe46:da74/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 604796sec preferred_lft 604796sec
inet6 fe80::ae1f:6bff:fe46:da74/64 scope link
valid_lft forever preferred_lft forever
3: enp0s20f1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether ac:1f:6b:46:da:75 brd ff:ff:ff:ff:ff:ff
4: enp0s20f2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether ac:1f:6b:46:da:76 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.102/24 brd 192.168.0.255 scope global enp0s20f2
valid_lft forever preferred_lft forever
inet 192.168.0.68/24 brd 192.168.0.255 scope global secondary dynamic enp0s20f2
valid_lft 2389sec preferred_lft 2389sec
inet6 2605:a000:45c9:3100::2/128 scope global dynamic noprefixroute
valid_lft 3379sec preferred_lft 1579sec
inet6 2605:a000:45c9:3100:ae1f:6bff:fe46:da76/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 604796sec preferred_lft 604796sec
inet6 fe80::ae1f:6bff:fe46:da76/64 scope link
valid_lft forever preferred_lft forever
5: enp0s20f3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether ac:1f:6b:46:da:77 brd ff:ff:ff:ff:ff:ff
networking server 18.04 ip netplan
edited Oct 1 at 12:52
Saxtheowl
36810 bronze badges
asked Aug 18 '18 at 21:32
crumcrum
194 bronze badges
Is the 24 bit mask intentional on your static IP? i.e. If you want that interface to have an address of 192.168.0.100, then the mask should be /32, otherwise, you’re liable to acquire any 192.168.0.x address. Or am I missing how netplan handles that config parameter?
– Piotrek
Aug 19 '18 at 3:46
Piotrek - I'm relatively new to this... does this thread cover cover what you are referring to? arstechnica.com/civis/viewtopic.php?t=751834
– crum
Aug 19 '18 at 12:07
Both of these references use the /24 mask. techrepublic.com/article/… and linuxconfig.org/…
– crum
Aug 19 '18 at 12:24
As an experiment - I tried the/32idea. Didn't work. Still getting new IP addresses assigned.
– crum
Aug 19 '18 at 16:39
What is running dhclient on your system? Your configuration clearly shows dhcp4: no; and networkd never calls dhclient, it uses its own internal implementation. Something else on your system is trying to configure these interfaces via dhcp which is overriding the static addresses configured in netplan. Is this an upgrade from pre-18.04? Do you have configuration in /etc/network/interfaces still?
– slangasek
Aug 21 '18 at 22:15
|
show 4 more comments
2
2
2
1
I am trying to assign a series of static IP addresses to my homelab server so that I can run a media service.
I edited /etc/netplan/ with the following:
01-netcfg.yaml:
network:
version: 2
renderer: networkd
ethernets:
enp0s20f0:
dhcp4: no
addresses: [192.168.0.100/24]
gateway4: 192.168.0.1
nameservers:
addresses: [192.168.0.1,8.8.4.8,8.8.8.8]
Then I repeated for the other three ports I was assigning. e.g., 02-netcfg.yaml, etc.
When I run
sudo netplan apply
I get the correct IP addresses.
After a period of mins, I lose the assigned numbers and get new IPs from my router's DHCP.
I've also tried to set the static IPs via the router, but I get the same problem.
Any ideas?
(I'm happy to provide more logs as needed.)
UPDATE: Output from syslog
/var/log$ tail -100 syslog
Aug 19 12:13:06 mythtv-server systemd[1]: Starting Network Name Resolution...
Aug 19 12:13:06 mythtv-server systemd-resolved[14306]: Positive Trust Anchors:
Aug 19 12:13:06 mythtv-server systemd-resolved[14306]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Aug 19 12:13:06 mythtv-server systemd-resolved[14306]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Aug 19 12:13:06 mythtv-server systemd-resolved[14306]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test
Aug 19 12:13:06 mythtv-server systemd-resolved[14306]: Using system hostname 'mythtv-server'.
Aug 19 12:13:06 mythtv-server systemd[1]: Started Network Name Resolution.
Aug 19 12:13:10 mythtv-server dhclient[11809]: DHCPDISCOVER on enp0s20f3 to 255.255.255.255 port 67 interval 11 (xid=0x80e80479)
Aug 19 12:13:10 mythtv-server dhclient[11809]: send_packet: No such device or address
Aug 19 12:13:10 mythtv-server dhclient[11809]: dhclient.c:2438: Failed to send 300 byte long packet over enp0s20f3 interface.
Aug 19 12:13:10 mythtv-server dhclient[28319]: DHCPDISCOVER on enp0s20f3 to 255.255.255.255 port 67 interval 20 (xid=0x6ab1ec09)
Aug 19 12:13:10 mythtv-server dhclient[28319]: send_packet: No such device or address
Aug 19 12:13:10 mythtv-server dhclient[28319]: dhclient.c:2438: Failed to send 300 byte long packet over enp0s20f3 interface.
Aug 19 12:13:11 mythtv-server dhclient[27706]: DHCPDISCOVER on enp0s20f3 to 255.255.255.255 port 67 interval 12 (xid=0x9f278b66)
Aug 19 12:13:11 mythtv-server dhclient[27706]: send_packet: No such device or address
Aug 19 12:13:11 mythtv-server dhclient[27706]: dhclient.c:2438: Failed to send 300 byte long packet over enp0s20f3 interface.
Aug 19 12:13:15 mythtv-server dhclient[28739]: DHCPDISCOVER on enp0s20f1 to 255.255.255.255 port 67 interval 3 (xid=0xf969ca13)
Aug 19 12:13:15 mythtv-server dhclient[28739]: send_packet: No such device or address
Aug 19 12:13:15 mythtv-server dhclient[28739]: dhclient.c:2438: Failed to send 300 byte long packet over enp0s20f1 interface.
Aug 19 12:13:18 mythtv-server dhclient[11809]: DHCPDISCOVER on enp0s20f1 to 255.255.255.255 port 67 interval 7 (xid=0x8354462)
Aug 19 12:13:18 mythtv-server dhclient[11809]: send_packet: No such device or address
Aug 19 12:13:18 mythtv-server dhclient[11809]: dhclient.c:2438: Failed to send 300 byte long packet over enp0s20f1 interface.
Aug 19 12:13:18 mythtv-server dhclient[3290]: DHCPDISCOVER on enp0s20f3 to 255.255.255.255 port 67 interval 9 (xid=0xc9123118)
Aug 19 12:13:18 mythtv-server dhclient[3290]: send_packet: No such device or address
Aug 19 12:13:18 mythtv-server dhclient[3290]: dhclient.c:2438: Failed to send 300 byte long packet over enp0s20f3 interface.
Aug 19 12:13:18 mythtv-server dhclient[28739]: DHCPDISCOVER on enp0s20f1 to 255.255.255.255 port 67 interval 6 (xid=0xf969ca13)
Aug 19 12:13:18 mythtv-server dhclient[28739]: send_packet: No such device or address
Aug 19 12:13:18 mythtv-server dhclient[28739]: dhclient.c:2438: Failed to send 300 byte long packet over enp0s20f1 interface.
Aug 19 12:13:21 mythtv-server dhclient[11809]: DHCPDISCOVER on enp0s20f3 to 255.255.255.255 port 67 interval 15 (xid=0x80e80479)
UPDATE2: I've added the output from ip a
ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s20f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether ac:1f:6b:46:da:74 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.100/24 brd 192.168.0.255 scope global enp0s20f0
valid_lft forever preferred_lft forever
inet 192.168.0.6/24 brd 192.168.0.255 scope global secondary dynamic enp0s20f0
valid_lft 2391sec preferred_lft 2391sec
inet6 2605:a000:45c9:3100::3/128 scope global dynamic noprefixroute
valid_lft 3277sec preferred_lft 1477sec
inet6 2605:a000:45c9:3100:ae1f:6bff:fe46:da74/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 604796sec preferred_lft 604796sec
inet6 fe80::ae1f:6bff:fe46:da74/64 scope link
valid_lft forever preferred_lft forever
3: enp0s20f1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether ac:1f:6b:46:da:75 brd ff:ff:ff:ff:ff:ff
4: enp0s20f2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether ac:1f:6b:46:da:76 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.102/24 brd 192.168.0.255 scope global enp0s20f2
valid_lft forever preferred_lft forever
inet 192.168.0.68/24 brd 192.168.0.255 scope global secondary dynamic enp0s20f2
valid_lft 2389sec preferred_lft 2389sec
inet6 2605:a000:45c9:3100::2/128 scope global dynamic noprefixroute
valid_lft 3379sec preferred_lft 1579sec
inet6 2605:a000:45c9:3100:ae1f:6bff:fe46:da76/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 604796sec preferred_lft 604796sec
inet6 fe80::ae1f:6bff:fe46:da76/64 scope link
valid_lft forever preferred_lft forever
5: enp0s20f3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether ac:1f:6b:46:da:77 brd ff:ff:ff:ff:ff:ff
networking server 18.04 ip netplan
edited Oct 1 at 12:52
Saxtheowl
36810 bronze badges
asked Aug 18 '18 at 21:32
crumcrum
194 bronze badges
I am trying to assign a series of static IP addresses to my homelab server so that I can run a media service.
I edited /etc/netplan/ with the following:
01-netcfg.yaml:
network:
version: 2
renderer: networkd
ethernets:
enp0s20f0:
dhcp4: no
addresses: [192.168.0.100/24]
gateway4: 192.168.0.1
nameservers:
addresses: [192.168.0.1,8.8.4.8,8.8.8.8]
Then I repeated for the other three ports I was assigning. e.g., 02-netcfg.yaml, etc.
When I run
sudo netplan apply
I get the correct IP addresses.
After a period of mins, I lose the assigned numbers and get new IPs from my router's DHCP.
I've also tried to set the static IPs via the router, but I get the same problem.
Any ideas?
(I'm happy to provide more logs as needed.)
UPDATE: Output from syslog
/var/log$ tail -100 syslog
Aug 19 12:13:06 mythtv-server systemd[1]: Starting Network Name Resolution...
Aug 19 12:13:06 mythtv-server systemd-resolved[14306]: Positive Trust Anchors:
Aug 19 12:13:06 mythtv-server systemd-resolved[14306]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Aug 19 12:13:06 mythtv-server systemd-resolved[14306]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Aug 19 12:13:06 mythtv-server systemd-resolved[14306]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test
Aug 19 12:13:06 mythtv-server systemd-resolved[14306]: Using system hostname 'mythtv-server'.
Aug 19 12:13:06 mythtv-server systemd[1]: Started Network Name Resolution.
Aug 19 12:13:10 mythtv-server dhclient[11809]: DHCPDISCOVER on enp0s20f3 to 255.255.255.255 port 67 interval 11 (xid=0x80e80479)
Aug 19 12:13:10 mythtv-server dhclient[11809]: send_packet: No such device or address
Aug 19 12:13:10 mythtv-server dhclient[11809]: dhclient.c:2438: Failed to send 300 byte long packet over enp0s20f3 interface.
Aug 19 12:13:10 mythtv-server dhclient[28319]: DHCPDISCOVER on enp0s20f3 to 255.255.255.255 port 67 interval 20 (xid=0x6ab1ec09)
Aug 19 12:13:10 mythtv-server dhclient[28319]: send_packet: No such device or address
Aug 19 12:13:10 mythtv-server dhclient[28319]: dhclient.c:2438: Failed to send 300 byte long packet over enp0s20f3 interface.
Aug 19 12:13:11 mythtv-server dhclient[27706]: DHCPDISCOVER on enp0s20f3 to 255.255.255.255 port 67 interval 12 (xid=0x9f278b66)
Aug 19 12:13:11 mythtv-server dhclient[27706]: send_packet: No such device or address
Aug 19 12:13:11 mythtv-server dhclient[27706]: dhclient.c:2438: Failed to send 300 byte long packet over enp0s20f3 interface.
Aug 19 12:13:15 mythtv-server dhclient[28739]: DHCPDISCOVER on enp0s20f1 to 255.255.255.255 port 67 interval 3 (xid=0xf969ca13)
Aug 19 12:13:15 mythtv-server dhclient[28739]: send_packet: No such device or address
Aug 19 12:13:15 mythtv-server dhclient[28739]: dhclient.c:2438: Failed to send 300 byte long packet over enp0s20f1 interface.
Aug 19 12:13:18 mythtv-server dhclient[11809]: DHCPDISCOVER on enp0s20f1 to 255.255.255.255 port 67 interval 7 (xid=0x8354462)
Aug 19 12:13:18 mythtv-server dhclient[11809]: send_packet: No such device or address
Aug 19 12:13:18 mythtv-server dhclient[11809]: dhclient.c:2438: Failed to send 300 byte long packet over enp0s20f1 interface.
Aug 19 12:13:18 mythtv-server dhclient[3290]: DHCPDISCOVER on enp0s20f3 to 255.255.255.255 port 67 interval 9 (xid=0xc9123118)
Aug 19 12:13:18 mythtv-server dhclient[3290]: send_packet: No such device or address
Aug 19 12:13:18 mythtv-server dhclient[3290]: dhclient.c:2438: Failed to send 300 byte long packet over enp0s20f3 interface.
Aug 19 12:13:18 mythtv-server dhclient[28739]: DHCPDISCOVER on enp0s20f1 to 255.255.255.255 port 67 interval 6 (xid=0xf969ca13)
Aug 19 12:13:18 mythtv-server dhclient[28739]: send_packet: No such device or address
Aug 19 12:13:18 mythtv-server dhclient[28739]: dhclient.c:2438: Failed to send 300 byte long packet over enp0s20f1 interface.
Aug 19 12:13:21 mythtv-server dhclient[11809]: DHCPDISCOVER on enp0s20f3 to 255.255.255.255 port 67 interval 15 (xid=0x80e80479)
UPDATE2: I've added the output from ip a
ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s20f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether ac:1f:6b:46:da:74 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.100/24 brd 192.168.0.255 scope global enp0s20f0
valid_lft forever preferred_lft forever
inet 192.168.0.6/24 brd 192.168.0.255 scope global secondary dynamic enp0s20f0
valid_lft 2391sec preferred_lft 2391sec
inet6 2605:a000:45c9:3100::3/128 scope global dynamic noprefixroute
valid_lft 3277sec preferred_lft 1477sec
inet6 2605:a000:45c9:3100:ae1f:6bff:fe46:da74/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 604796sec preferred_lft 604796sec
inet6 fe80::ae1f:6bff:fe46:da74/64 scope link
valid_lft forever preferred_lft forever
3: enp0s20f1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether ac:1f:6b:46:da:75 brd ff:ff:ff:ff:ff:ff
4: enp0s20f2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether ac:1f:6b:46:da:76 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.102/24 brd 192.168.0.255 scope global enp0s20f2
valid_lft forever preferred_lft forever
inet 192.168.0.68/24 brd 192.168.0.255 scope global secondary dynamic enp0s20f2
valid_lft 2389sec preferred_lft 2389sec
inet6 2605:a000:45c9:3100::2/128 scope global dynamic noprefixroute
valid_lft 3379sec preferred_lft 1579sec
inet6 2605:a000:45c9:3100:ae1f:6bff:fe46:da76/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 604796sec preferred_lft 604796sec
inet6 fe80::ae1f:6bff:fe46:da76/64 scope link
valid_lft forever preferred_lft forever
5: enp0s20f3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether ac:1f:6b:46:da:77 brd ff:ff:ff:ff:ff:ff
networking server 18.04 ip netplan
networking server 18.04 ip netplan
edited Oct 1 at 12:52
Saxtheowl
36810 bronze badges
asked Aug 18 '18 at 21:32
crumcrum
194 bronze badges
edited Oct 1 at 12:52
Saxtheowl
36810 bronze badges
asked Aug 18 '18 at 21:32
crumcrum
194 bronze badges
edited Oct 1 at 12:52
Saxtheowl
36810 bronze badges
edited Oct 1 at 12:52
Saxtheowl
36810 bronze badges
edited Oct 1 at 12:52
Saxtheowl
36810 bronze badges
36810 bronze badges
asked Aug 18 '18 at 21:32
crumcrum
194 bronze badges
asked Aug 18 '18 at 21:32
crumcrum
194 bronze badges
asked Aug 18 '18 at 21:32
crumcrum
194 bronze badges
194 bronze badges
Is the 24 bit mask intentional on your static IP? i.e. If you want that interface to have an address of 192.168.0.100, then the mask should be /32, otherwise, you’re liable to acquire any 192.168.0.x address. Or am I missing how netplan handles that config parameter?
– Piotrek
Aug 19 '18 at 3:46
Piotrek - I'm relatively new to this... does this thread cover cover what you are referring to? arstechnica.com/civis/viewtopic.php?t=751834
– crum
Aug 19 '18 at 12:07
Both of these references use the /24 mask. techrepublic.com/article/… and linuxconfig.org/…
– crum
Aug 19 '18 at 12:24
As an experiment - I tried the/32idea. Didn't work. Still getting new IP addresses assigned.
– crum
Aug 19 '18 at 16:39
What is running dhclient on your system? Your configuration clearly shows dhcp4: no; and networkd never calls dhclient, it uses its own internal implementation. Something else on your system is trying to configure these interfaces via dhcp which is overriding the static addresses configured in netplan. Is this an upgrade from pre-18.04? Do you have configuration in /etc/network/interfaces still?
– slangasek
Aug 21 '18 at 22:15
|
show 4 more comments
Is the 24 bit mask intentional on your static IP? i.e. If you want that interface to have an address of 192.168.0.100, then the mask should be /32, otherwise, you’re liable to acquire any 192.168.0.x address. Or am I missing how netplan handles that config parameter?
– Piotrek
Aug 19 '18 at 3:46
Piotrek - I'm relatively new to this... does this thread cover cover what you are referring to? arstechnica.com/civis/viewtopic.php?t=751834
– crum
Aug 19 '18 at 12:07
Both of these references use the /24 mask. techrepublic.com/article/… and linuxconfig.org/…
– crum
Aug 19 '18 at 12:24
As an experiment - I tried the/32idea. Didn't work. Still getting new IP addresses assigned.
– crum
Aug 19 '18 at 16:39
What is running dhclient on your system? Your configuration clearly shows dhcp4: no; and networkd never calls dhclient, it uses its own internal implementation. Something else on your system is trying to configure these interfaces via dhcp which is overriding the static addresses configured in netplan. Is this an upgrade from pre-18.04? Do you have configuration in /etc/network/interfaces still?
– slangasek
Aug 21 '18 at 22:15
Is the 24 bit mask intentional on your static IP? i.e. If you want that interface to have an address of 192.168.0.100, then the mask should be /32, otherwise, you’re liable to acquire any 192.168.0.x address. Or am I missing how netplan handles that config parameter?
– Piotrek
Aug 19 '18 at 3:46
Is the 24 bit mask intentional on your static IP? i.e. If you want that interface to have an address of 192.168.0.100, then the mask should be /32, otherwise, you’re liable to acquire any 192.168.0.x address. Or am I missing how netplan handles that config parameter?
– Piotrek
Aug 19 '18 at 3:46
Piotrek - I'm relatively new to this... does this thread cover cover what you are referring to? arstechnica.com/civis/viewtopic.php?t=751834
– crum
Aug 19 '18 at 12:07
Piotrek - I'm relatively new to this... does this thread cover cover what you are referring to? arstechnica.com/civis/viewtopic.php?t=751834
– crum
Aug 19 '18 at 12:07
Both of these references use the /24 mask. techrepublic.com/article/… and linuxconfig.org/…
– crum
Aug 19 '18 at 12:24
Both of these references use the /24 mask. techrepublic.com/article/… and linuxconfig.org/…
– crum
Aug 19 '18 at 12:24
As an experiment - I tried the
/32 idea. Didn't work. Still getting new IP addresses assigned.– crum
Aug 19 '18 at 16:39
As an experiment - I tried the
/32 idea. Didn't work. Still getting new IP addresses assigned.– crum
Aug 19 '18 at 16:39
What is running dhclient on your system? Your configuration clearly shows dhcp4: no; and networkd never calls dhclient, it uses its own internal implementation. Something else on your system is trying to configure these interfaces via dhcp which is overriding the static addresses configured in netplan. Is this an upgrade from pre-18.04? Do you have configuration in /etc/network/interfaces still?
– slangasek
Aug 21 '18 at 22:15
What is running dhclient on your system? Your configuration clearly shows dhcp4: no; and networkd never calls dhclient, it uses its own internal implementation. Something else on your system is trying to configure these interfaces via dhcp which is overriding the static addresses configured in netplan. Is this an upgrade from pre-18.04? Do you have configuration in /etc/network/interfaces still?
– slangasek
Aug 21 '18 at 22:15
|
show 4 more comments
2 Answers
2
active
oldest
votes
1
It could be NetworkManager service that does that.
Just purge it, and hopefully it will work.
For more details on how to purge it, goto : How do I disable network manager permanently?
NB :
(Source : netplan vs NetworkManager on Ubuntu 18.04 and above)
NetworkManageris normally used in desktop applications, and was used in all prior versions of Ubuntu.If you are using
netplan, it's totally safe to removeNetworkManagerFixed the same issue for me on Ubuntu 18.04.3 LTS.
answered Oct 1 at 8:10
pymym213pymym213
4511 silver badge11 bronze badges
add a comment
|
-1
Check out this related bug on netplan...
https://bugs.launchpad.net/netplan/+bug/1781652
You can easily migrate back to ifupdown if you still have issues with netplan. I sure did.
answered Aug 19 '18 at 1:42
Software_ProgramineerSoftware_Programineer
4242 silver badges10 bronze badges
not related; his config shows dhcp4: no so dhclient should not be running at all.
– slangasek
Aug 21 '18 at 22:13
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/4.0/"u003ecc by-sa 4.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%2f1066681%2fubuntu-server-18-04-1-cannot-keep-static-ip-address-after-assigned%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
1
It could be NetworkManager service that does that.
Just purge it, and hopefully it will work.
For more details on how to purge it, goto : How do I disable network manager permanently?
NB :
(Source : netplan vs NetworkManager on Ubuntu 18.04 and above)
NetworkManageris normally used in desktop applications, and was used in all prior versions of Ubuntu.If you are using
netplan, it's totally safe to removeNetworkManagerFixed the same issue for me on Ubuntu 18.04.3 LTS.
answered Oct 1 at 8:10
pymym213pymym213
4511 silver badge11 bronze badges
add a comment
|
1
It could be NetworkManager service that does that.
Just purge it, and hopefully it will work.
For more details on how to purge it, goto : How do I disable network manager permanently?
NB :
(Source : netplan vs NetworkManager on Ubuntu 18.04 and above)
NetworkManageris normally used in desktop applications, and was used in all prior versions of Ubuntu.If you are using
netplan, it's totally safe to removeNetworkManagerFixed the same issue for me on Ubuntu 18.04.3 LTS.
answered Oct 1 at 8:10
pymym213pymym213
4511 silver badge11 bronze badges
add a comment
|
1
1
1
It could be NetworkManager service that does that.
Just purge it, and hopefully it will work.
For more details on how to purge it, goto : How do I disable network manager permanently?
NB :
(Source : netplan vs NetworkManager on Ubuntu 18.04 and above)
NetworkManageris normally used in desktop applications, and was used in all prior versions of Ubuntu.If you are using
netplan, it's totally safe to removeNetworkManagerFixed the same issue for me on Ubuntu 18.04.3 LTS.
answered Oct 1 at 8:10
pymym213pymym213
4511 silver badge11 bronze badges
It could be NetworkManager service that does that.
Just purge it, and hopefully it will work.
For more details on how to purge it, goto : How do I disable network manager permanently?
NB :
(Source : netplan vs NetworkManager on Ubuntu 18.04 and above)
NetworkManageris normally used in desktop applications, and was used in all prior versions of Ubuntu.If you are using
netplan, it's totally safe to removeNetworkManagerFixed the same issue for me on Ubuntu 18.04.3 LTS.
answered Oct 1 at 8:10
pymym213pymym213
4511 silver badge11 bronze badges
edited Oct 1 at 8:16
answered Oct 1 at 8:10
pymym213pymym213
4511 silver badge11 bronze badges
answered Oct 1 at 8:10
pymym213pymym213
4511 silver badge11 bronze badges
answered Oct 1 at 8:10
pymym213pymym213
4511 silver badge11 bronze badges
4511 silver badge11 bronze badges
add a comment
|
add a comment
|
-1
Check out this related bug on netplan...
https://bugs.launchpad.net/netplan/+bug/1781652
You can easily migrate back to ifupdown if you still have issues with netplan. I sure did.
answered Aug 19 '18 at 1:42
Software_ProgramineerSoftware_Programineer
4242 silver badges10 bronze badges
not related; his config shows dhcp4: no so dhclient should not be running at all.
– slangasek
Aug 21 '18 at 22:13
add a comment
|
-1
Check out this related bug on netplan...
https://bugs.launchpad.net/netplan/+bug/1781652
You can easily migrate back to ifupdown if you still have issues with netplan. I sure did.
answered Aug 19 '18 at 1:42
Software_ProgramineerSoftware_Programineer
4242 silver badges10 bronze badges
not related; his config shows dhcp4: no so dhclient should not be running at all.
– slangasek
Aug 21 '18 at 22:13
add a comment
|
-1
-1
-1
Check out this related bug on netplan...
https://bugs.launchpad.net/netplan/+bug/1781652
You can easily migrate back to ifupdown if you still have issues with netplan. I sure did.
answered Aug 19 '18 at 1:42
Software_ProgramineerSoftware_Programineer
4242 silver badges10 bronze badges
Check out this related bug on netplan...
https://bugs.launchpad.net/netplan/+bug/1781652
You can easily migrate back to ifupdown if you still have issues with netplan. I sure did.
answered Aug 19 '18 at 1:42
Software_ProgramineerSoftware_Programineer
4242 silver badges10 bronze badges
answered Aug 19 '18 at 1:42
Software_ProgramineerSoftware_Programineer
4242 silver badges10 bronze badges
answered Aug 19 '18 at 1:42
Software_ProgramineerSoftware_Programineer
4242 silver badges10 bronze badges
answered Aug 19 '18 at 1:42
Software_ProgramineerSoftware_Programineer
4242 silver badges10 bronze badges
4242 silver badges10 bronze badges
not related; his config shows dhcp4: no so dhclient should not be running at all.
– slangasek
Aug 21 '18 at 22:13
add a comment
|
not related; his config shows dhcp4: no so dhclient should not be running at all.
– slangasek
Aug 21 '18 at 22:13
not related; his config shows dhcp4: no so dhclient should not be running at all.
– slangasek
Aug 21 '18 at 22:13
not related; his config shows dhcp4: no so dhclient should not be running at all.
– slangasek
Aug 21 '18 at 22:13
add a comment
|
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.
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%2f1066681%2fubuntu-server-18-04-1-cannot-keep-static-ip-address-after-assigned%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
Is the 24 bit mask intentional on your static IP? i.e. If you want that interface to have an address of 192.168.0.100, then the mask should be /32, otherwise, you’re liable to acquire any 192.168.0.x address. Or am I missing how netplan handles that config parameter?
– Piotrek
Aug 19 '18 at 3:46
Piotrek - I'm relatively new to this... does this thread cover cover what you are referring to? arstechnica.com/civis/viewtopic.php?t=751834
– crum
Aug 19 '18 at 12:07
Both of these references use the /24 mask. techrepublic.com/article/… and linuxconfig.org/…
– crum
Aug 19 '18 at 12:24
As an experiment - I tried the
/32idea. Didn't work. Still getting new IP addresses assigned.– crum
Aug 19 '18 at 16:39
What is running dhclient on your system? Your configuration clearly shows dhcp4: no; and networkd never calls dhclient, it uses its own internal implementation. Something else on your system is trying to configure these interfaces via dhcp which is overriding the static addresses configured in netplan. Is this an upgrade from pre-18.04? Do you have configuration in /etc/network/interfaces still?
– slangasek
Aug 21 '18 at 22:15