No, the purpose of a mesh system is to use a common SSID (so clients can roam.) The nodes do have distinct BSSIDs. In fact, an access point may have multiple BSSIDs if it has more than one radio and/or serves multiple SSIDs to separate clients into different groups / WLANs.
Juniper has a good explanation.
Well, if your problem is about the MAC address, actually you can quite spoof your MAC address in many ways. For example by using Scapy.
Here is a snippet I shamelessly taken from this thread:
>>> send(Ether(src="ab:cd:ef:ab:cd:ef", dst="ff:ff:ff:ff:ff:ff")/IP(src="188.8.131.52", dst="184.108.40.206")/UDP(dport=9)/b"...
The WLC uses the number as the Destination Port for CAPWAP Ctl/Data
In this context "Ctl" (Control) is the management traffic between the A.P. itself and the controller (pushing configuration, gathering information, firmware updates, etc...), and "Data" is the data streams from the wireless clients connected to this A.P.
So when ...
It's right there in the footnote:
Arbitrary port number is assigned to every AP from range 1024 - 65535
when the AP joins the WLC. The WLC uses the number as the Destination
Port for CAPWAP Ctl/Data as long as the AP is connected.
Option one is a "wireless bridge". Certainly common enough, but wifi is often too slow and unstable. Option two is similar to #1. (slow, and surprisingly easy to break.)
Option three is code violation. You cannot put low voltage cabling in the same conduit as high voltage cabling. This is for safety reasons; there's very little concern of powerline ...