MAC address spoofing on PPPoE interface

BlackByte

I tried to add PPPoE interface with different MAC address, but it does not change the address of the real WAN interface (fxp0 in my case). I tried everything from web interface (creating WAN interface and so on) but nothing works.

I solved the problem with manually add to /conf/config.xml to interface section:

and everything works PERFECT. However I think it is just a workaround to a problem.

In 1.2.x this works fine.

Efonnes

That might cause it to get the interface mismatch screen on the console when you reboot it.

BlackByte

I didn't see any mismatch screen on the console after reboot. As I said it works perfect.

I'm new to pfSense so I'm not sure about the details.

jimp

I wouldn't do it that way, you will have problems, it's just a matter of when.

Just assign that interface (fxp0), set the type to none, and just set the MAC there.

Or install the shellcmd package and setup an earlyshellcmd to set it.

BlackByte

I think I've tried it, but there is no place to change the MAC address if it is not PPPoE. From the web interface only place is to spoof the MAC is when you say it is PPPoE, but it doesn't change the MAC on the real interface.

jimp

You misunderstood what I wrote.

When you make a PPPoE interface, it is really assigned as, say, pppoe0 - NOT fxp0.

You can go to Interfaces > (assign) and assign fxp0 directly, and change the MAC on that interface.

BlackByte

No I didn't misunderstood you :) This is what you can't done from web interface. I'll try it now on a vmware machine, but I'm sure that before editing the config file I tried this.

I'll post later with more information.

jimp

Every interface has the box to change the MAC address now (WAN, LAN, OPTs, etc), and regardless of type (None, Static, DHCP, etc).

BlackByte

Hmmm… really strange. I've tested it on new VMware machine and it works as you suggested. Anyway I'm sure that I tried this. Of course as I can't replicate the problem (and I don't want to brake my working router), I'll accept that I made something wrong. Is it possible that there could be any problem on 7th Nov build?

Anyway could you explain me what is the difference between adding this in the config file and adding it from the web interface? In my new install in the config file it is the same information except the "descr" tag.

jimp

<fxp0>is not a valid interface tag/name.

It should be wan, lan, or opt <x>where x is a number starting at 1.

It just happens to work for you by accident.</x></fxp0>

BlackByte

ah…ok... first it was "sux" because I was testing :) after it worked I decided to change it to something different :) ok I'll change it to opt1

Thank you very much for the information.