It's supposed to be same after cloning. I don't know how people are configuring and creating a clash. ONT main MAC (fiber interface) address gets registered with OLT. The profiles such TR069, Internet and Voice have their own MAC address. Internet profile MAC address gets bound, the same profile can be turned to bridge mode and the address copied to another router for PPPoE.
Now on some ONT the bridge mode is enabled by simply deleting or not creating a profile at all. This shouldn't be the case for Netlink at least.
Now in my case, I was already using bridge when BSNL introduced address binding. I was using a USB ethernet adapter and the address for that got bound. Later when I changed to another USB ethernet adapter I simply copied the address from the first one and it worked perfectly. Now since they recently changed BNG the MAC address got blocked temporarily for reason unknown and I asked LCO to reset it and it started working even without a restart but then I removed the copied address and used the original of the adapter and then restarted the router and it got bound without any difficulty. Now, I don't understand why a third separate profile is needed just for bridge. The same profile can be used for route and bridge interchangeably without any issue unless the ONT device config is messed up.
Now on some ONT the bridge mode is enabled by simply deleting or not creating a profile at all. This shouldn't be the case for Netlink at least.
Now in my case, I was already using bridge when BSNL introduced address binding. I was using a USB ethernet adapter and the address for that got bound. Later when I changed to another USB ethernet adapter I simply copied the address from the first one and it worked perfectly. Now since they recently changed BNG the MAC address got blocked temporarily for reason unknown and I asked LCO to reset it and it started working even without a restart but then I removed the copied address and used the original of the adapter and then restarted the router and it got bound without any difficulty. Now, I don't understand why a third separate profile is needed just for bridge. The same profile can be used for route and bridge interchangeably without any issue unless the ONT device config is messed up.