Ubuntu
netplan.io package

Old IP does not go away

Bug #1876020 reported by Leon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
netplan.io (Ubuntu)
New
Undecided
Unassigned

Bug Description

Version:

Description: Ubuntu 20.04 LTS
Release: 20.04
Codename: focal

I have changed machine's IP from 192.168.4.55 to 192.168.4.5 in the netplan config file:

leonbrag@minivm:/etc/network$ cat /etc/netplan/00-installer-config.yaml
# This is the network config written by 'subiquity'
 network:
    version: 2
    renderer: networkd
    ethernets:
       eth0:
          dhcp4: no
          addresses: [192.168.4.5/24]
          gateway4: 192.168.4.1
          nameservers:
             addresses: [192.168.4.1]

However old IP did not go away and machine can be pinged using old IP as well.

leonbrag@minivm:/etc/network$ ip addr
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: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:15:5d:91:c9:00 brd ff:ff:ff:ff:ff:ff
    inet 192.168.4.5/24 brd 192.168.4.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet 192.168.4.55/24 brd 192.168.4.255 scope global secondary noprefixroute eth0
       valid_lft forever preferred_lft forever
    inet6 2601:600:9480:1e4:6b2b:1db2:658b:e692/64 scope global dynamic mngtmpaddr noprefixroute
       valid_lft 2591616sec preferred_lft 604416sec
    inet6 2601:600:9480:1e4:215:5dff:fe91:c900/64 scope global dynamic mngtmpaddr noprefixroute
       valid_lft 2591616sec preferred_lft 604416sec
    inet6 fe80::215:5dff:fe91:c900/64 scope link
       valid_lft forever preferred_lft forever
leonbrag@minivm:/etc/network$

machine was rebooted more then once.

Tags: bot-comment
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1876020/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Brian Murray (brian-murray)
affects: ubuntu → netplan.io (Ubuntu)
Revision history for this message
Leon (leonbrag) wrote :

The second IP address was caused by DHCPCD running and assigning address via DHCP. This seems to the bug, because via netplan I have assigned static IP

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.