The throughput I think was the same OID. Signal definitely changed from 5.5 to 5.6
Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Feb 22, 2016 12:53 PM, "Vlad Sedov" <[email protected]> wrote: > Hmm, what version of firmware are you running on the UBNTs? I can't even > get a value from those MIBs through SNMPwalk. > We also run Dude 4.0beta3.. > > > Vlad > > On 2/22/2016 11:24 AM, Jason McKemie wrote: > > I'll try a different type of probe and see if anything changes. Thanks. > > On Mon, Feb 22, 2016 at 3:23 AM, Adam Moffett <[email protected]> wrote: > >> 4.0b3 >> >> I also am not using a "function" probe type anywhere. I do use the SNMP >> probe type extensively. >> >> >> On 2/22/2016 1:52 AM, Jason McKemie wrote: >> >> Upon searching in the Mikrotik Forums, it looks like this could be an >> issue with custom OIDs on the newer versions of the dude. What version are >> you using? >> >> On Sat, Feb 20, 2016 at 8:29 PM, Adam Moffett <[email protected]> >> wrote: >> >>> Try >>> oid_raw("1.3.6.1.4.1.32050.2.1.27.5.0") >>> >>> I'm not totally sure what the difference is, other than sometimes that >>> one works. >>> >>> >>> >>> On 2/20/2016 8:14 PM, Jason McKemie wrote: >>> >>>> I've just started working with using the Dude for monitoring on the >>>> bench, but I'm getting a parse failed on the probe for a test device. I've >>>> attached an image showing the function and probe I created. Any ideas what >>>> I'm doing wrong? Please note that this is just a test setup using a >>>> Ubiquiti AP with no client. I'm aware that the noise floor reading is >>>> essentially useless and have no intention of graphing it in a production >>>> environment. >>>> >>>> -Jason >>>> >>> >>> >> >> > >
