IP Address Conflict

[Gremlin]

Something strange happened yesterday. Received Tnas notification via automatic email from NAS:

Address conflict detected for IP 192.168.155.224,192.168.155.224!

------------------------------

Device name: NAS-1
Model: F5-221
TOS version: TOS_X642.0_5.1.95

TNAS System Notification
https://www.terra-master.com/support/

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.

[Gremlin]

(Cant edit post)
AND
the LAN2 address is the address assigned to LAN1 (via DHCP)

Nothing has changed to the cabling (in a remote building) but I will be chacking later and probably doing a shutdown/restart.

[Gremlin]

OK, after shut/down and wait then start up It appears working ok. However I am now a bit confused (mind you, that could be permanent ).

As per the attachment, it now appears that the Bond (Balanced-alb) is taking the IP assigned to LAN2, but using the MAC-address for LAN1.

Not like that on my other machine. Any ideas?

[Gremlin]

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

[TMroy]

We will verify the issue you have reported shortly.