IP Address moving between interfaces

Discussion in 'Proxmox VE: Networking and Firewall' started by sptnelson, Feb 16, 2016.

  1. sptnelson

    sptnelson New Member

    Joined:
    Sep 2, 2015
    Messages:
    8
    Likes Received:
    0
    I forgot to include this: ProxMox 4.1.2, pfSense 2.1.5

    I followed a guide on installing pfSense which said the best practice was to use two ports for the internal network, one for the ProxMox Console IP, the other for the internal interface of the firewall. I have 4 network cards, configured like this: http://take.ms/ZxGeh

    vmbr0 is the ProxMox console.
    vmbr1/2 are internet connections.
    vmbr3 is the internal interface of my firwall.

    I have the firewall configured like this: http://take.ms/cRooZ

    All of this works great.

    On the same network I have a physical FreeNAS box, and just about every day it sends me an e-mail with the following:

    pa-nas.starpoint.com kernel log messages:
    > arp: 192.168.7.8 moved from a0:36:9f:8b:d9:b4 to 0c:c4:7a:6c:63:21 on igb0
    > arp: 192.168.7.8 moved from 0c:c4:7a:6c:63:21 to a0:36:9f:8b:d9:b4 on igb0
    > arp: 192.168.7.8 moved from a0:36:9f:8b:d9:b4 to 0c:c4:7a:6c:63:21 on igb0
    > arp: 192.168.7.8 moved from a0:36:9f:8b:d9:b4 to 0c:c4:7a:6c:63:21 on igb0
    > arp: 192.168.7.8 moved from a0:36:9f:8b:d9:b4 to 0c:c4:7a:6c:63:21 on igb0
    > arp: 192.168.7.8 moved from 0c:c4:7a:6c:63:21 to a0:36:9f:8b:d9:b4 on igb0
    [ snipped for brevity ]

    192.168.7.8 is the IP address of the the ProxMox Console, and it's moving between eth0 (vmbr0) and eth3 (vmbr3) and I'm really not sure why.

    The ProxMox box has a NFS share mounted that is used to hold nightly backups.

    Below is /etc/network/interfaces, and the output from ifconfig -a . Other than the e-mail that I get, I'm not actually seeing any issues with server or any of the VMs. I'm just really curios why the IP address would be moving between network cards. I removed the tap interfaces from the ifconfig output because this post was too long with it all.

    Any help would be greatly appreciated.

    Thanks, Tony

    root@pa-vm01:~# cat /etc/network/interfaces
    # network interface settings; autogenerated
    # Please do NOT modify this file directly, unless you know what
    # you're doing.
    #
    # If you want to manage part of the network configuration manually,
    # please utilize the 'source' or 'source-directory' directives to do
    # so.
    # PVE will preserve these directives, but will NOT its network
    # configuration from sourced files, so do not attempt to move any of
    # the PVE managed interfaces into external files!

    auto lo
    iface lo inet loopback

    iface eth0 inet manual

    iface eth1 inet manual

    iface eth2 inet manual

    iface eth3 inet manual

    auto vmbr0
    iface vmbr0 inet static
    address 192.168.7.8
    netmask 255.255.255.0
    gateway 192.168.7.1
    bridge_ports eth0
    bridge_stp off
    bridge_fd 0

    auto vmbr1
    iface vmbr1 inet manual
    bridge_ports eth1
    bridge_stp off
    bridge_fd 0

    auto vmbr2
    iface vmbr2 inet manual
    bridge_ports eth2
    bridge_stp off
    bridge_fd 0

    auto vmbr3
    iface vmbr3 inet manual
    bridge_ports eth3
    bridge_stp off
    bridge_fd 0


    And the output from ifconfig -a

    root@pa-vm01:~# ifconfig -a
    eth0 Link encap:Ethernet HWaddr a0:36:9f:8b:d9:b4
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:562171397 errors:0 dropped:82000 overruns:18766 frame:0
    TX packets:704226017 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:45248392809 (42.1 GiB) TX bytes:1046957052531 (975.0 GiB)
    Memory:c7200000-c72fffff

    eth1 Link encap:Ethernet HWaddr a0:36:9f:8b:d9:b5
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:27896207 errors:0 dropped:0 overruns:0 frame:0
    TX packets:24888598 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:13552429249 (12.6 GiB) TX bytes:7114088796 (6.6 GiB)
    Memory:c7100000-c71fffff

    eth2 Link encap:Ethernet HWaddr 0c:c4:7a:6c:63:20
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:167141774 errors:0 dropped:0 overruns:0 frame:0
    TX packets:101192925 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:196766008928 (183.2 GiB) TX bytes:17611784728 (16.4 GiB)
    Memory:c7720000-c773ffff

    eth3 Link encap:Ethernet HWaddr 0c:c4:7a:6c:63:21
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:699281831 errors:0 dropped:82000 overruns:39316 frame:0
    TX packets:360289566 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:82553186295 (76.8 GiB) TX bytes:456433724719 (425.0 GiB)
    Memory:c7700000-c771ffff

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:65536 Metric:1
    RX packets:14337 errors:0 dropped:0 overruns:0 frame:0
    TX packets:14337 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:9903557 (9.4 MiB) TX bytes:9903557 (9.4 MiB)

    veth101i0 Link encap:Ethernet HWaddr fe:cd:21:85:63:bd
    inet6 addr: fe80::fccd:21ff:fe85:63bd/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:8400913 errors:0 dropped:0 overruns:0 frame:0
    TX packets:15033221 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:1588725299 (1.4 GiB) TX bytes:2142838690 (1.9 GiB)

    vmbr0 Link encap:Ethernet HWaddr a0:36:9f:8b:d9:b4
    inet addr:192.168.7.8 Bcast:192.168.7.255 Mask:255.255.255.0
    inet6 addr: fe80::a236:9fff:fe8b:d9b4/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:254728225 errors:0 dropped:4167 overruns:0 frame:0
    TX packets:32735688 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:15179902417 (14.1 GiB) TX bytes:1002629327981 (933.7 GiB)

    vmbr1 Link encap:Ethernet HWaddr a0:36:9f:8b:d9:b5
    inet6 addr: fe80::a236:9fff:fe8b:d9b5/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:1380128 errors:0 dropped:8334 overruns:0 frame:0
    TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:81969288 (78.1 MiB) TX bytes:828 (828.0 B)

    vmbr2 Link encap:Ethernet HWaddr 0c:c4:7a:6c:63:20
    inet6 addr: 2601:40:c104:6a00:ec4:7aff:fe6c:6320/64 Scope:Global
    inet6 addr: fe80::ec4:7aff:fe6c:6320/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:388443 errors:0 dropped:0 overruns:0 frame:0
    TX packets:34375 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:66505524 (63.4 MiB) TX bytes:3542793 (3.3 MiB)

    vmbr3 Link encap:Ethernet HWaddr 0c:c4:7a:6c:63:21
    inet6 addr: fe80::ec4:7aff:fe6c:6321/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:478340474 errors:0 dropped:4167 overruns:0 frame:0
    TX packets:2390 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:36589146743 (34.0 GiB) TX bytes:100692 (98.3 KiB)
     
  2. sptnelson

    sptnelson New Member

    Joined:
    Sep 2, 2015
    Messages:
    8
    Likes Received:
    0
    Has anyone else ever seen anything like this? I'm still seeing this issue every day.
     
  3. clicks

    clicks New Member

    Joined:
    Mar 4, 2015
    Messages:
    3
    Likes Received:
    0
    Yes, I see the exact same behavior on my Proxmox cluster. The FreeBSD storages connected to the three Proxmox hosts complain about IP addresses moving from one MAC-address to another. But on the corresponding hosts there is no event or log entry which explains this behavior.
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice