Correction. XW.v5.6-beta5.24359.141008.1600

Based on the pattern, this beta is from October 2014.

Latest one on their web site is XW.v5.6.1-beta2.26499.150225.1705.bin <http://www.ubnt.com/downloads/XN-fw-internal/v5.6.1/XW.v5.6.1-beta2.26499.150225.1705.bin> (February 2015)

<http://www.ubnt.com/downloads/XN-fw-internal/v5.6/XW.v5.6-beta3.21929.140418.1218.bin>

bp
<part15sbs{at}gmail{dot}com>

On 4/7/2015 3:07 PM, Bill Prince wrote:
v5.6-beta5.24359 (XW)

bp
<part15sbs{at}gmail{dot}com>

On 4/7/2015 3:04 PM, That One Guy /sarcasm wrote:
what release of 5.6?

On Tue, Apr 7, 2015 at 5:01 PM, Bill Prince <part15...@gmail.com <mailto:part15...@gmail.com>> wrote:

    The existing SNMP stack on 5.5.10 works as long as you _*DON'T
    TOUCH*_ the OIDs that don't work. Touch any of the non-functional
    OIDs and the SNMP query will come back null. The OIDs that do
    work (and I haven't explored extensively) are:

        traffic
        uptime
        signal level
        data rate
        load average
        noise floor (but it's a lie)

    We also have 5.6 running on exactly one subscriber radio. It
    provides many more OIDs that all seem to work. It's been running
    fine for about 2 months with no apparent problems. Note that all
    the OIDs are different between 5.5.10 and 5.6.

    bp
    <part15sbs{at}gmail{dot}com>

    On 4/7/2015 2:47 PM, That One Guy /sarcasm wrote:
    most of our ubnt crap sits on 5.5.10, of course the powercode
    real time monitors dont work, halk the existing graphs arent
    working
    trying to figure out from the ubnt forums where snmp stands is
    like screwing a piranha.

    pretty much everything thats not airfiber  we have is M series.
    Is there a list of functional OIDs for 5.5.10?

    isnt 5.6 beta supposed to have some mibs? is there a stable
    enough beta?

    what year is this?

-- If you only see yourself as part of the team but you don't see
    your team as part of yourself you have already failed as part of
    the team.




--
If you only see yourself as part of the team but you don't see your team as part of yourself you have already failed as part of the team.


Reply via email to