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

Pfsync between different network cards

Scheduled Pinned Locked Moved 2.2 Snapshot Feedback and Problems - RETIRED
5 Posts 2 Posters 1.2k Views
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.
  • V
    vindenesen
    last edited by Dec 11, 2014, 7:24 PM

    Hello everyone,

    Using "2.2-RC (amd64) built on Thu Dec 11 03:41:41 CST 2014".

    I'm running a HA setup, and just recently moved my primary from a vm to a physical server. The secondary is a vm, using e1000 nic, and the physical server is using igb (A1SRI C2758). Pfsync doesn't seem to be syncing states. A while back, when the primary was a vm, I tested using vmxnet3 on the secondary, and the same thing happened.

    Is this normal? Does pfsync require you to use the same NIC driver on both the primary and secondary?

    Support the project by buying a Gold Subscription at https://portal.pfsense.org
    Running pfSense on SuperMicro A1SRI-2758F with ESXi 5.5

    1 Reply Last reply Reply Quote 0
    • C
      cmb
      last edited by Dec 11, 2014, 11:36 PM

      The states contain the interface name. They'll still sync across, but never match on the secondary, if its interfaces are different.

      1 Reply Last reply Reply Quote 0
      • V
        vindenesen
        last edited by Dec 12, 2014, 5:47 AM

        Thanks for your answer cmb :)

        Was afraid of that. There's no way around this? Like maybe create a lagg-interface on top of the em0? I'm using lagg on the physical server.

        Support the project by buying a Gold Subscription at https://portal.pfsense.org
        Running pfSense on SuperMicro A1SRI-2758F with ESXi 5.5

        1 Reply Last reply Reply Quote 0
        • C
          cmb
          last edited by Dec 12, 2014, 6:00 AM

          It's been annoying me of late as well, as I have a physical box as a primary and ESX VM as a secondary. The physical box has lagg with LACP, the VM doesn't. You should be fine if you setup all your interfaces as matching laggX interfaces between them, even if the lagg has only 1 member NIC. That's exactly what I was considering doing, haven't had a chance to do it yet.

          1 Reply Last reply Reply Quote 0
          • V
            vindenesen
            last edited by Dec 12, 2014, 7:18 PM

            Looks like it works :) Did a search and replace in a backup of the config, replaced em0 with lagg0. And then added a lagg-interface to the config. Restored the new config, rebooted, and done. States are now visible on the secondary.

            I did receive a message about an interface mismatch right after I pressed the restore button. Pressed apply changes, it rebooted, and it looks fine now.

            Support the project by buying a Gold Subscription at https://portal.pfsense.org
            Running pfSense on SuperMicro A1SRI-2758F with ESXi 5.5

            1 Reply Last reply Reply Quote 0
            1 out of 5
            • First post
              1/5
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
              This community forum collects and processes your personal information.
              consent.not_received