No way to change MAC of Bonded interface ?
I do not see a way to change the MAC address of a bonded interface ?
Re: No way to change MAC of Bonded interface ?
What if you change MACs of member ports before bonding them? Usually bond takes up MAC of one of participating ports ...
Re: No way to change MAC of Bonded interface ?
From the manual:
It may be possible to make a script that takes down the interface, removes the bond, change mac address on the first interface, bound it with another and turn port on again. (Just an idea)forced-mac-address (MAC address; Default: none)
By default, bonding interface will use MAC address of the first selected slave interface. This property allows to configure static MAC address for the bond interface (all zeros, broadcast or multicast addresses will not apply). RouterOS will automatically change the MAC address for slave interfaces and it will be visible in /interface ethernet configuration export
Re: No way to change MAC of Bonded interface ?
Changing the MAC of the members did not work.
After a lot of playing I found something that did. This script gives me a new MAC each time I run it. I have NO idea why. This is sloppy and I need to clean it up some as it leaves a interface list member dangling.
I need to change the MAC of the bonded 802.3ad link in order to force the cable modem ( Arris SB8200 ) to get a new dynamically assigned IP.
Previously I randomized the single ethernet MAC and rebooted the modem. This would give me a new IP..
Now with the newly added LAG of 2 ports on the modem I can get past 1Gbps but I need to be able to run a script and get a new IP on a regular basis. I get new IPs from the ISP to prevent ad targeting and tracking..
When i remove and add back the bonding interface this scrambles the DHCP client and interface WAN list. My script puts those back in place..
BUT this leaves a interface list member entry i cant remove.. Well I can from command line with remove 1,, but not from the script..
Now why this generates a new MAC for the 802.3ad bonded interface, I dont know. But it does for sure..
After a lot of playing I found something that did. This script gives me a new MAC each time I run it. I have NO idea why. This is sloppy and I need to clean it up some as it leaves a interface list member dangling.
I need to change the MAC of the bonded 802.3ad link in order to force the cable modem ( Arris SB8200 ) to get a new dynamically assigned IP.
Previously I randomized the single ethernet MAC and rebooted the modem. This would give me a new IP..
Now with the newly added LAG of 2 ports on the modem I can get past 1Gbps but I need to be able to run a script and get a new IP on a regular basis. I get new IPs from the ISP to prevent ad targeting and tracking..
When i remove and add back the bonding interface this scrambles the DHCP client and interface WAN list. My script puts those back in place..
Code: Select all
/interface bonding remove Modem1;
/interface bonding add name=Modem1 mode=802.3ad slaves=ether7,ether8 transmit-hash-policy=layer-3-and-4;
/ip dhcp-client set 0 interface=Modem1;
/interface list member add interface=Modem1 list=WAN
Now why this generates a new MAC for the 802.3ad bonded interface, I dont know. But it does for sure..