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

    Spoofing MAC address on WAN interface

    Problems Installing or Upgrading pfSense Software
    3
    7
    11.6k
    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.
    • L
      locutus44
      last edited by

      After the Update to 2.4.4 a month ago my pfSense router failed to connect to the internet.
      As I ran out of time, I gave up and used a spare pfSense but still running on 2.4.2.

      Yesterday I gave it another try and found out: Simply disabling and re-enabling the WAN interface did the trick.
      But my spoofed MAC address for the WAN interface was gone.
      (Starting with pfSense two years ago my ISP only accepted "known" MAC addresses, happily he decided to do otherwise... for now.)

      As there the internet traffic is coming on VLAN 10 and TV traffic on VLAN 20, the interface configuration is this:

      0_1544681888786_cb84824c-4a8a-450f-a77f-6afbbd0294a0-image.png

      On 2.4.2 (same configuration) the spoofing was possible:
      0_1544681906590_32d202d2-70b7-45ac-89e1-af9980cccffb-image.png

      On 2.4.4 it's now looking like this:
      0_1544681935923_9fab85cb-cfc0-4b6b-a155-b22b0cee1103-image.png

      How to change then interface configuration to get the WAN spoofing back?
      Any assistance is much appreciated!

      L 1 Reply Last reply Reply Quote 0
      • NogBadTheBadN
        NogBadTheBad
        last edited by NogBadTheBad

        @locutus44 said in Spoofing MAC address on WAN interface:

        ting with pfSense two years ago my ISP only accepted "known" MAC addresses, happily he decided to do otherwise... for now.)
        As there the internet traffic is coming on VLAN 10 and TV traffic on VLAN 20, the interface configuration is this:

        You need to change the MAC address on the parent interface igb0 not the VLAN interface, that will change the mac address on all the VLANS where igb0 is the parent interface.

        Hence the "The MAC address of a VLAN interface must be set on its parent interface" text

        Andy

        1 x Netgate SG-4860 - 3 x Linksys LGS308P - 1 x Aruba InstantOn AP22

        1 Reply Last reply Reply Quote 0
        • L
          locutus44 @locutus44
          last edited by

          Thank you for your reply, your are right.
          But how to do that? As you can see in my first post, since 2.4.4 the click on WAN

          0_1544715285400_7d22c4c5-f867-4b2f-8a7e-88a459726d2a-image.png
          brings me to "WAN(igb0.10)" configuration ("igb0.10" obviously stands for VLAN 10) , where I can't set the MAC address.
          In previous versions the same menu item was opening the "WAN" configuration, where i could set the MAC address.
          So how to get access to that or do I have to create somehow an additional parent interface?

          1 Reply Last reply Reply Quote 0
          • NogBadTheBadN
            NogBadTheBad
            last edited by

            Interfaces -> VLANs what does that show ?

            Andy

            1 x Netgate SG-4860 - 3 x Linksys LGS308P - 1 x Aruba InstantOn AP22

            L 1 Reply Last reply Reply Quote 0
            • L
              locutus44 @NogBadTheBad
              last edited by

              @nogbadthebad
              Interfaces -> VLANs shows
              0_1544720651294_dfac2b46-bf78-4afc-9803-a60f77085674-image.png

              1 Reply Last reply Reply Quote 0
              • GrimsonG
                Grimson Banned
                last edited by

                Assign igb0 to an interface, then you can edit it's MAC. Plain and simple.

                L 1 Reply Last reply Reply Quote 0
                • L
                  locutus44 @Grimson
                  last edited by

                  @grimson
                  Thank you! Case closed ☺ . So it seems like it was a bug in pre 2.4.4 versions, that my previous configuration was working well, not a feature.

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