Spoofing MAC address on WAN interface
-
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:
On 2.4.2 (same configuration) the spoofing was possible:
On 2.4.4 it's now looking like this:
How to change then interface configuration to get the WAN spoofing back?
Any assistance is much appreciated! -
@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
-
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
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? -
Interfaces -> VLANs what does that show ?
-
@nogbadthebad
Interfaces -> VLANs shows
-
Assign igb0 to an interface, then you can edit it's MAC. Plain and simple.
-
@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.
