Yes, that is a huge issue with them. It started the Great WISP Buffer Debate of $YEAR of which nothing ever came. One of the longest threads in UBNT Forum History.
On Aug 15, 2017 6:51 AM, "Mike Hammett" <[email protected]> wrote: > Some were related to inadequate buffer sizes causing mixing 100 meg and 1 > gig interfaces to have issues. > > > > ----- > Mike Hammett > Intelligent Computing Solutions <http://www.ics-il.com/> > <https://www.facebook.com/ICSIL> > <https://plus.google.com/+IntelligentComputingSolutionsDeKalb> > <https://www.linkedin.com/company/intelligent-computing-solutions> > <https://twitter.com/ICSIL> > Midwest Internet Exchange <http://www.midwest-ix.com/> > <https://www.facebook.com/mdwestix> > <https://www.linkedin.com/company/midwest-internet-exchange> > <https://twitter.com/mdwestix> > The Brothers WISP <http://www.thebrotherswisp.com/> > <https://www.facebook.com/thebrotherswisp> > > > <https://www.youtube.com/channel/UCXSdfxQv7SpoRQYNyLwntZg> > ------------------------------ > *From: *"Forrest Christian (List Account)" <[email protected]> > *To: *"af" <[email protected]> > *Sent: *Monday, August 14, 2017 4:13:54 PM > *Subject: *Re: [AFMUG] Toughswitch/low cost ethernet forwarding > failure reminder? > > > The old archived emails I've found on the toughswitch problem was random > packetloss. But I remember someone had figured out more details, just > don't remember what they were and haven't found an email which contains the > discussion. I vaguely think it might have been load or pps related, but > before what you'd think was full load. > > On Mon, Aug 14, 2017 at 1:41 PM, Josh Reynolds <[email protected]> > wrote: > >> Fill up the bridge table and see how it responds, for one. >> >> Not forwarding though, sounds like a chipset bug you'd need to catch. >> >> On Aug 14, 2017 3:39 PM, "Forrest Christian (List Account)" < >> [email protected]> wrote: >> >> Let me phrase this differently: I am evaluating a new switch platform >> that I am skeptical of. I want to construct a test that the toughswitch >> would fail (but a properly operating switch should pass) to ensure that >> this platform hasn't made a similar error. >> >> If there are other known bad platforms I would like to include those in >> this test suite as well. >> >> >> >> On Mon, Aug 14, 2017 at 12:12 PM, Josh Luthman < >> [email protected]> wrote: >> >>> Symptom of Toughswitch is you installed one in the network. Get rid of >>> it. >>> >>> Use a PowerBox or Netonix. >>> >>> Josh Luthman >>> Office: 937-552-2340 <(937)%20552-2340> >>> Direct: 937-552-2343 <(937)%20552-2343> >>> 1100 Wayne St >>> Suite 1337 >>> Troy, OH 45373 >>> >>> On Aug 14, 2017 1:18 PM, "Forrest Christian (List Account)" < >>> [email protected]> wrote: >>> >>>> Could someone who is familiar with the problem with a the packet >>>> forwarding problems that were seen with a toughswitch remind me about the >>>> details of the symptoms/cause? >>>> >>>> I also remember similar problems with certain other switches. >>>> >>>> I am evaluating a couple of switches and want to make sure I can >>>> validate that this problem doesn't occur. >>>> >>>> -- >>>> *Forrest Christian* *CEO**, PacketFlux Technologies, Inc.* >>>> Tel: 406-449-3345 | Address: 3577 Countryside Road, Helena, MT 59602 >>>> [email protected] | http://www.packetflux.com >>>> <http://www.linkedin.com/in/fwchristian> >>>> <http://facebook.com/packetflux> <http://twitter.com/@packetflux> >>>> >>>> >> >> >> -- >> *Forrest Christian* *CEO**, PacketFlux Technologies, Inc.* >> Tel: 406-449-3345 | Address: 3577 Countryside Road, Helena, MT 59602 >> [email protected] | http://www.packetflux.com >> <http://www.linkedin.com/in/fwchristian> >> <http://facebook.com/packetflux> <http://twitter.com/@packetflux> >> >> >> > > > -- > *Forrest Christian* *CEO**, PacketFlux Technologies, Inc.* > Tel: 406-449-3345 | Address: 3577 Countryside Road, Helena, MT 59602 > [email protected] | http://www.packetflux.com > <http://www.linkedin.com/in/fwchristian> <http://facebook.com/packetflux> > <http://twitter.com/@packetflux> > > >
