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

    Problem with Static ARP entry for VLAN/Virtual Interface

    Scheduled Pinned Locked Moved General pfSense Questions
    4 Posts 3 Posters 609 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.
    • J
      joelones
      last edited by

      Not sure if someone could chime here in, I'm experiencing an odd issue after upgrading to Mac OSX 10.13.6 - it's propabably more of a networking question, sorry not sure where else to post.

      Let me explain, on my Mac OS X box I've created a Virtual Interface and gave it an IP 192.168.10.90 in the VLAN10 subnet ( the switch port of my Mac OSX is trunked to VLAN10 as well so I have both untagged and VLAN10 going through one cable, reason being I don't have another free port on my switch ).

      Furthermore, my Parellels Linux VM 192.168.10.20 (on my Mac OS X box) is bridged on that virtual interface and is given an address on VLAN10 via pfSense's DHCP.

      On the pfSense side of things for VLAN10, in the DHCP settings I have "Enable Static ARP entries" checked, and I statically assign IPs here based on MAC addresses, including this VM and its MAC address. Prior to the Mac OS X upgrade all worked fine where I had entered the MAC address of the VM in the DHCP settings.

      After the change, I now noticed that from the VM, I cannot access pfSense ( hence the internet ) but if I uncheck "Enable Static ARP entries" it works. I'd like to keep that option on, so I putzed and noticed if I enter the MAC address of the NIC of the Mac OS X box it works but no longer works with the MAC address of the VM ( which is a bit baffling as it was working before ).

      More so, when looking at the pfSense's ARP table, 192.168.10.20 has the Mac OS X NIC's MAC address not the VM's.

      I'm not sure what happened or whether it was the Apple update or my mind playing games on me or whether this is the intended behaviour when it comes to bridged adapters - which I doubt. Any thought would be greatly appreciated.

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        That looks like a change in OSX or in parallels.
        If pfSense is seeing a different MAC address it can't really be anything else.

        Steve

        1 Reply Last reply Reply Quote 0
        • M
          marvosa
          last edited by

          @joelones said in Problem with Static ARP entry for VLAN/Virtual Interface:

          the switch port of my Mac OSX is trunked to VLAN10

          Please clarify... cause none of this sounds right

          J 1 Reply Last reply Reply Quote 0
          • J
            joelones @marvosa
            last edited by

            @marvosa said in Problem with Static ARP entry for VLAN/Virtual Interface:

            @joelones said in Problem with Static ARP entry for VLAN/Virtual Interface:

            the switch port of my Mac OSX is trunked to VLAN10

            Please clarify... cause none of this sounds right

            What I meant to say, was the the port of the netgear switch on which my Mac OS X box is connected allows untagged as well as VLAN 10 traffic to pass.

            But I suspect the Mac OS X update did something to affect this behaviour as it was working fine before the update and pfSense saw the VM's MAC address now it does not.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.