My eptp link was 2.4.3 with the issue for sure I had a ptmp AP (flexible) 2.5.1 that had an issue where no one could associate until I rebooted
I would think in 2.6.x it was resolved. I haven't seen any issues myself since 2.6.x. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Wed, Dec 5, 2018 at 5:09 PM Brandon Yuchasz <li...@gogebicrange.net> wrote: > Josh, > > Was the bug in 2.6.1.x? I will certainly upgrade but just wondering how > long this has been around. > > > > Thanks everyone. > > > > > > *From:* AF [mailto:af-boun...@af.afmug.com] *On Behalf Of *Josh Luthman > *Sent:* Wednesday, December 05, 2018 9:11 AM > *To:* AFMUG > *Subject:* Re: [AFMUG] odd Force 200 backhaul issues. > > > > There was a bug that caused it to hang way back in the day (when the Force > 200 and eptp came out). They patched my link and it quit dying entirely, > but I think it was some quick reset. > > There's a known bug in 3.5.1 that's semi-resolved in 3.5.2 relating to > this, but it is not 100% fixed from what I'm told. Upgrade to 3.5.2 and > when there's a new release you'll want to upgrade when you can. > > > > Josh Luthman > Office: 937-552-2340 > Direct: 937-552-2343 > 1100 Wayne St > Suite 1337 > Troy, OH 45373 > > > > > > On Tue, Dec 4, 2018 at 11:58 PM Mathew Howard <mhoward...@gmail.com> > wrote: > > I've seen that happen before, but I can't remember what we did to fix > it... I think we may have had to replace the radio. I can't remember if it > was a PTP or PTMP situation, either... it was a while ago. > > > > It might be worth switching it to TDD PTP mode instead, and see if that > helps. > > > > On Tue, Dec 4, 2018 at 10:14 PM Brandon Yuchasz <li...@gogebicrange.net> > wrote: > > Yes de-registering the link does make the link start passing traffic again > although it seems a lot shorter lived so far. Only lasted an hour. > > > > *From:* AF [mailto:af-boun...@af.afmug.com] *On Behalf Of *Brandon Yuchasz > *Sent:* Tuesday, December 04, 2018 7:56 PM > *To:* 'AnimalFarm Microwave Users Group' > *Subject:* Re: [AFMUG] odd Force 200 backhaul issues. > > > > I don’t know. I will report back after trying it. > > Thanks for the idea. > > > > > > *From:* AF [mailto:af-boun...@af.afmug.com] *On Behalf Of *Mathew Howard > *Sent:* Tuesday, December 04, 2018 4:02 PM > *To:* AFMUG > *Subject:* Re: [AFMUG] odd Force 200 backhaul issues. > > > > Does it start working again if you just de-register the link, instead of > rebooting the radio(s)? > > > > On Tue, Dec 4, 2018 at 9:33 AM Brandon Yuchasz <li...@gogebicrange.net> > wrote: > > Dave, > > I have not seems like such a strange issue I didn’t have much faith in > tech support. My experience is the list seems to have better info on these > odd issues. One side of this link requires snow shoes to get to so I am > trying to avoid replacement if at all possible. > > > > Thanks, > > Brandon > > > > > > *From:* AF [mailto:af-boun...@af.afmug.com] *On Behalf Of *Dave > *Sent:* Tuesday, December 04, 2018 8:01 AM > *To:* af@af.afmug.com > *Subject:* Re: [AFMUG] odd Force 200 backhaul issues. > > > > Have you placed a support request to cambium yet? > https://support.cambiumnetworks.com/ > > On 12/3/18 7:53 PM, Brandon Yuchasz wrote: > > Looking to see if anyone has experienced a similar issue to this: > > We have a force 200 backhaul on a small bridged network. > > Several times a day now it stops passing most traffic. It can be humming > along at 25mbps down and 5mbps upload and then drop down to 2mbps download > and less than 1mbps upload. > > Downlink RSSI -65 dBm > > Downlink SRN 30 dB > > Uplink MCS MCS 14 > > Downlink MCS MCS15 > > All remains constant during this time. > > > > The ping falls apart during this time between the AP and the SM although > pings through the network to the SM or through the network from the AM are > both fine it’s just between them that starts to drop packets. > > > > The units show heavy retransmission packets from the moment the link is > brought online around 40% at times. > > > > At this point I would assume noise is the issue. > > > > *But here is the odd part I would like some help with*. Rebooting the > link fixes the issue but leaving the link alone does not. It will stay > “broken” until one or both sides of the link are rebooted. Then it works > perfectly for a time and falls apart again. > > > > Current firmware is 3.5.1 but we have run it on 2.6.1.1 and 3.3 with > similar results. > > > > > > Any thoughts on how to troubleshot this one would be awesome. > > > > Best Regards. > > Brandon Yuchasz > > > > > > > > > > > > > > -- > *Error! Filename not specified.* > > -- > AF mailing list > AF@af.afmug.com > http://af.afmug.com/mailman/listinfo/af_af.afmug.com > > -- > AF mailing list > AF@af.afmug.com > http://af.afmug.com/mailman/listinfo/af_af.afmug.com > > -- > AF mailing list > AF@af.afmug.com > http://af.afmug.com/mailman/listinfo/af_af.afmug.com > > -- > AF mailing list > AF@af.afmug.com > http://af.afmug.com/mailman/listinfo/af_af.afmug.com >
-- AF mailing list AF@af.afmug.com http://af.afmug.com/mailman/listinfo/af_af.afmug.com
