Project

General

Profile

Bug #1522

Changing interface IP doesn't (always?) remove old interface IP

Added by Jim Pingle about 8 years ago. Updated about 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Interfaces
Target version:
Start date:
05/12/2011
Due date:
% Done:

100%

Estimated time:
Affected Version:
2.0
Affected Architecture:
All

Description

When you change the IP of an interface (ex: LAN) using the Interfaces > [name] page, the old IP remains on the interface.

For example, changing the LAN IP from 192.168.1.1 to 192.168.10.1, upon applying the settings, ifconfig shows both IPs on the interface:

em1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
        ether 00:0c:29:41:01:67
        inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255
        inet6 fe80::20c:29ff:fe41:167%em1 prefixlen 64 scopeid 0x2 
        inet 192.168.10.1 netmask 0xffffff00 broadcast 192.168.10.255
        nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active

Side effect of this bug is being unable to change DHCP settings on LAN after applying, but that's really a separate issue I'll start another ticket for.

The expected behavior would be for the old IP to be removed, and only the new IP to be present.

Associated revisions

Revision bb4fcffd (diff)
Added by Ermal Luçi about 8 years ago

Fixes #1522. Call interface reconfigure so we bring down the interface and than re-configure it.

History

#1 Updated by Ermal Luçi about 8 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

#2 Updated by Jim Pingle about 8 years ago

  • Status changed from Feedback to Resolved

Confirmed this is fixed now.

Also available in: Atom PDF