It’s sad to see that kind of feedback… It is understandable to have issues and bugs, but there is always a right and bad way to do it.
I understand that it makes you angry to still have those bugs/issues when you are paying for a solution (hardware and software). Since it is networking, you can see the impact daily, but I don’t think that blaming Alta’s Team on the forum is the right way…
Personally, if someone yelled/raged at me it didn’t motivate me to help him back since there is no mutual respect.
Keep in mind that the device was released 2 months ago for an early adapter since some features will be released as time goes by. It is a first-generation router with a lot of nice features (SPF+ and 2.5Gbps ports) at an interesting price (~199$). It didn’t excuse the bugs or the issues you’re having, but nothing is perfect.
Be more open and comprehensive and you will see that will come back to you.
This is not a roasting post, it is only to show you the impressions of your posts by a community guy.
Have a nice one and Alta, continue your great work!
Speaking personally here, I don’t care that there are bugs/issues with the product. I know the team hears and sees my complaints (those that aren’t removed), and I have had nothing short of exceptional customer service when I had to call in. I’m here to be involved in the communities efforts of having a superior product. My mindset is the hardware and aesthetics is there, let’s get the software side to match.
Text doesn’t convey dialect well. What you see as anger and rage, others may interpret as seeking answers, although frustrated. Don’t take this as me defending any specific user, as I agree some have gone about their grievances terribly. To believe they are unfounded would be incorrect though.
I have personally had my posts removed for breaking community guidelines when the post did nothing but state what had happened as a matter of fact.
I know it has been looked at, and I believe Chris is aware of it, but I’ll bring it up again to note.
If you have a device that gets a DHCP lease from route 10, then disconnects from the network and does not come back, it remains in the devices list until the DHCP lease expires. Is that intended behavior? If so, perhaps can we have a selectable view for online or offline devices?
We cannot reproduce it, and neither can some of the people that were originally able to reproduce it. If we can get access to a site where the problem occurs, that will greatly increase our chances of fixing it, if it’s still happening.
You, and any other readers, may note that the thread Jeff linked is now resolved thanks to the cooperation of some of our thoughtful community members. I hope we can now allow this current thread to be about the 1.3u release for Route10 again.
