03-23-2015 11:34 AM - edited 03-23-2015 11:35 AM
Is there a way to do the link aggregation between the switches? I mean to link them with 1g+1g = 2g. In the controller he say: Error Invalide aggregate range.
Thanks for your help.
04-29-2015 08:00 AM
03-31-2015 05:43 AM
the Problem with Port aggregation (Trunking) is not solved with the controller 4.6.3. It is not working you can't setup the aggregation. I want to do aply but the contoller give no reaction.
03-31-2015 12:59 PM - edited 03-31-2015 12:59 PM
Ok... This is embrassing, we fixed it but then later broke again while improving aggregation logic, and we did not capture the second time and it slips into v4.6.3. Anyway, appologize about that, this will be fixed in the next version, and we are also working on implementing automated tests for this part.
04-29-2015 08:00 AM
04-29-2015 10:53 AM
Has there been thought to pushing releases every 2 weeks on a schedule (scrum) ? That way a quick bug fix can be pushed out quickly without having to wait for other less priority fixes or features to be rolled out with it.
We ended up doing a hybrid approach by splitting off some team members. Basically we do fixes and small feature changes every 2 weeks and larger features every other release.
05-01-2015 06:54 AM
@UBNT-MikeD, your making me do more work now with this cdn thing....
Oh, because it's not in the repo yet? Due to the way releases are currently, we only provide a .deb package for soaking releases. If a soaking release is considered good, no major regressions, typically it is pushed to the repo and main download site. The folder structure also changes to the usual naming scheme when it moves from soaking to stable.
Eventually when v2 and/or v3 are retired we will adjust the naming scheme. We may even see the naming scheme match up again.. unifi being stable, rapid being the "soaking" and maybe even betas. This paragraph is purely a personal statement though and doesn't necessarily reflect our direction.