Project

General

Profile

Actions
Copy link

Bug #2981

closed

Virtual IP's not cleaned up on interface change

Added by Josh Stompro over 11 years ago. Updated about 10 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Virtual IP Addresses
Target version:
-
Start date:
05/06/2013
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.1
Affected Architecture:

Description

Running 2.1-Beta1 (i386) Thur May 2 00:11:40 EDT 2013 Nanobsd 2G

The problem I'm seeing is that when I change the WAN interface from one physical interface to another, and I have virtual IP's setup on the WAN interface, the Virtual IP's are not removed from the old interface, they are just added to the new interface.

I don't know if this actually causes any problems, or if it is just cosmetic.

Steps to reproduce
  1. Add virtual IP's to WAN
  2. Change WAN interface from one physical interface to another.
  3. Examine the interfaces (ifconfig).

This is what ifconfig reports on my machine after I make the interface change. Trimmed to just the relevant interfaces.

[2.1-BETA1][root@mh-firewall.larl.org]/root(1): ifconfig
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=4209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,VLAN_HWTSO>
        ether 00:90:0b:14:f7:bd
        inet 216.234.20.98 netmask 0xfffffff0 broadcast 216.234.20.111
        inet6 fe80::290:bff:fe14:f7bd%em0 prefixlen 64 scopeid 0x1
        inet 216.234.20.99 netmask 0xffffffff broadcast 216.234.20.99
        inet 216.234.20.100 netmask 0xffffffff broadcast 216.234.20.100
        inet 216.234.20.101 netmask 0xffffffff broadcast 216.234.20.101
        inet 216.234.20.102 netmask 0xffffffff broadcast 216.234.20.102
        inet 216.234.20.103 netmask 0xffffffff broadcast 216.234.20.103
        inet 216.234.20.104 netmask 0xffffffff broadcast 216.234.20.104
        inet 216.234.20.105 netmask 0xffffffff broadcast 216.234.20.105
        inet 216.234.20.106 netmask 0xffffffff broadcast 216.234.20.106
        inet 216.234.20.107 netmask 0xffffffff broadcast 216.234.20.107
        inet 216.234.20.108 netmask 0xffffffff broadcast 216.234.20.108
        inet 216.234.20.109 netmask 0xffffffff broadcast 216.234.20.109
        inet 216.234.20.110 netmask 0xffffffff broadcast 216.234.20.110
        nd6 options=1<PERFORMNUD>
        media: Ethernet autoselect
        status: no carrier
fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=2009<RXCSUM,VLAN_MTU,WOL_MAGIC>
        ether 00:90:0b:14:f7:be
        inet6 fe80::290:bff:fe14:f7be%fxp0 prefixlen 64 scopeid 0x5
        inet 216.234.20.99 netmask 0xffffffff broadcast 216.234.20.99
        inet 216.234.20.100 netmask 0xffffffff broadcast 216.234.20.100
        inet 216.234.20.101 netmask 0xffffffff broadcast 216.234.20.101
        inet 216.234.20.102 netmask 0xffffffff broadcast 216.234.20.102
        inet 216.234.20.103 netmask 0xffffffff broadcast 216.234.20.103
        inet 216.234.20.104 netmask 0xffffffff broadcast 216.234.20.104
        inet 216.234.20.105 netmask 0xffffffff broadcast 216.234.20.105
        inet 216.234.20.106 netmask 0xffffffff broadcast 216.234.20.106
        inet 216.234.20.107 netmask 0xffffffff broadcast 216.234.20.107
        inet 216.234.20.108 netmask 0xffffffff broadcast 216.234.20.108
        inet 216.234.20.109 netmask 0xffffffff broadcast 216.234.20.109
        inet 216.234.20.110 netmask 0xffffffff broadcast 216.234.20.110
        nd6 options=1<PERFORMNUD>
        media: Ethernet autoselect (none)
        status: no carrier

After a reboot the situation clears up. I think the virtual IP code needs to remove all the virtual IP entries from the current interface when it is making the change, it must just add them at this point.

Thanks
Josh

Actions
Copy link

Also available in: Atom PDF