Duo-v2 upgrade HELP

vandermerwe wrote:
The purpose of testing the dhcp assignment is to make sure the NAS can get an IP address other than 192.168.168.168. You have made it very clear that you don't want to use dhcp in your earlier posts. I also use static ip addresses only. Good luck, try the beta, you seem to have given up so you don't have anything to lose.

Vandermerwe,
I had a previous note to you that somehow got killed when I somehow got logged off the forum. I got a phone call from an old friend before I clicked 'Submit." I apologize.
In any case, I do understand your feelings, even though I still stubbornly choose not to test DHCP. I am happy to know that you also do static assignment of ip addy's.
I accept that I am very stubborn on trying various network related stuff. I think I've learned enough to do this task; still learning about sub-net masks, however.
I do believe that the DUO-v2 and/or its' f/w has a serious bug that still needs to be killed. Fine. Ultimately I may choose another Readynas hdw platform to build my Brother's NAS upon.
I had trouble with this DUO-v2 back in FEB12 when I bought it. That's why it lived in its' box since now. I figured just maybe I'd get lucky. Nope.
Yes, I will try the new beta f/w v5.3.9-T5. This can't hurt anything. Yes, I'm also looking a hdw platform replacements and have raised threads on our forum. I am trying to avoid choosing a Synology choice at this time. At this point, I'd like to just end this thread; but, I will share my RAIDiator v5.3.9-T5 results here post trial/error.

Believe me, I truly appreciate your help and patience. I will solve this issue one way or another.