[Help] Bond: Dynamic IP canged after update

[FNIK]

I installed the latest update to TOS 6.0.770. I noticed that after the update, the TNAS received a different IP address from the router. The IP address is linked to the MAC address by the router. I have combined both network interfaces as a bond. After the update, the bond suddenly has the other MAC address externally, and so the router also assigns a different IP. I have noticed with several updates that the MAC addresses were changed after the update. Apparently, the bond once had the MAC from the first network interface and, after an update, from the other. Please take a look at this.

[sianderson]

this has been noted previously, i guess it still happens the solution i found was to just fix the IP on the TNAS rather than using DHCP, that way it only ever gets the same IP for the bond

[Gremlin]

Just a thought = check Control Panel > Network > Service Sequence (right-hand icon). This affects some things as to the order in which network interfaces are used. I discovered this when setting up a remote folder. When I established a new remote folder, it used Lan2 to establish the link; which I found was the primary lan set in service sequence. Changed that to Lan1 (the faster interface on my -221), re-established the remote folder and then transfers went over the Lan1 interface. You never know .......

[TMvalen]

Hello, and thank you for your attention and feedback. The situation you mentioned is a normal phenomenon. Please see the detailed explanation below:

During a system upgrade, changes in the MAC address are primarily related to the upgrade and adjustments of the network management tool:

1. In version 694, the MAC address of the bond interface was automatically selected by the network management tool from one of the two bound network cards.

2. After upgrading to version 750, a brand-new network management tool was introduced, and the MAC address generation algorithm was updated accordingly, resulting in a change of the bond address.

3. In version 770, the algorithm was further optimised and final calibration was completed. The MAC address was recalculated and changed once more. However, after this adjustment, subsequent versions will maintain a stable MAC address without further changes.

In addition, the change in the IP address you mentioned after the upgrade occurs because the device is configured by default to obtain an IP address via DHCP. The DHCP server in the network environment may dynamically reassign IP addresses. If you need a fixed IP address, you can manually configure the network settings to use a static IP. Once configured, the IP address will remain stable.

[Gremlin]

Since WOL function also depends on MAC address, how has this been affected? I'm not sure I understand how a MAC address can be "recalculated".