Subsequently I performed a reboot/restart of the NAS and everything appeared normal (no warning messages) BUT the GUI shows that The Bonded Interface has the (correctly) assigned IP no, while the LAN1 interface has the default "unassiged" ip address. (attachment)
Never seen this before and The nas running 6.0.124 is 'normal' showing The bond and lan1 with same address as usual.
Attachments
F5-221 5.1.123, 8GB System Partition on 3 x 4TB Traid; 3TB EXT4
F2-221 TOS6 (Beta), 8GB System Partition on 2 x 6TB in Traid. (Latest Update 11/04/24)
To try and better understand this I deleted the bond I had set up. This reverted me to the 2 assigned (via DHCP) as expected. I then updated to 5.1.103 to be on the latest version. This was successful
I then re-created the Bond as before and things were back where we started. With the added fact that I now noticed the WAN IP was blank.
My solution for now is to reassign another IP to LAN1 via DHCP. Then I created the Bond with a Fixed IP assigned fron the nas. This appears to work as I can see 3 separate IP addresses for LAN1, LAN2 and BOND but the BOND still shared MAC address with one of the LAN interfaces. Plus the WAN IP has reappeared.
Not particularly the way I would want it and not sure how this works in reallity with the shared MAC address.
Any other ideas suggestions would be welcome
F5-221 5.1.123, 8GB System Partition on 3 x 4TB Traid; 3TB EXT4
F2-221 TOS6 (Beta), 8GB System Partition on 2 x 6TB in Traid. (Latest Update 11/04/24)
We will verify the issue you have reported shortly.
To contact our team, please send email to following addresses, remember to replace (at) with @:
Support team: support(at)terra-master.com (for technical support only)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
). 
