Navigation

    Netgate Discussion Forum
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search

    Virtual IP Duplicated on Interface Change

    2.1 Snapshot Feedback and Problems - RETIRED
    2
    3
    1016
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      stompro last edited by

      Hello, I just noticed this on a test machine and I'm wondering if this would be considered a bug.

      Running 2.1-Beta1(i386) Thur May 2 build on a netgate Hamakua-1U.

      I have 12 Virtual IP's setup on my wan interface.  I changed the physical interface that the wan interface is associated with.  When I looked at the ifconfig, I see that the virtual IP's are now setup for both the old and new interfaces.  It looks like the code that deals with interface reassignment may need to remove the virual ip's when there is a change.

      Should I file this as a bug?  Or is this something else I'm running into.  I'll make sure I can reproduce the problem next week.

      em2: 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:bc
      	inet6 fe80::290:bff:fe14:f7bb%em2 prefixlen 64 scopeid 0x3
      	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 (1000baseT <full-duplex>)
      	status: active
      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
      	inet 216.234.20.98 netmask 0xfffffff0 broadcast 216.234.20.111
      	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</performnud></rxcsum,vlan_mtu,wol_magic></up,broadcast,running,simplex,multicast></full-duplex></performnud></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_magic,vlan_hwtso></up,broadcast,running,simplex,multicast>
      
      1 Reply Last reply Reply Quote 0
      • C
        cmb last edited by

        If that's reproducible, yeah please file a bug report with steps to replicate.

        1 Reply Last reply Reply Quote 0
        • S
          stompro last edited by

          The situation does clear up after a reboot, but comes back when I change the wan interface again.  I will file a bug report.
          Josh

          1 Reply Last reply Reply Quote 0
          • First post
            Last post

          Products

          • Platform Overview
          • TNSR
          • pfSense
          • Appliances

          Services

          • Training
          • Professional Services

          Support

          • Subscription Plans
          • Contact Support
          • Product Lifecycle
          • Documentation

          News

          • Media Coverage
          • Press
          • Events

          Resources

          • Blog
          • FAQ
          • Find a Partner
          • Resource Library
          • Security Information

          Company

          • About Us
          • Careers
          • Partners
          • Contact Us
          • Legal
          Our Mission

          We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

          Subscribe to our Newsletter

          Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

          © 2021 Rubicon Communications, LLC | Privacy Policy