Just a FYI, I got this from Mikrotik.. I wanted to make sure I sent it out to everyone..
The tranzeo timestamp issues comes from tranzeo implementing a timestamp check that is not included in the 802.11 standard for ap to client communications. The timestamp check is included in the standard for the adhoc (IBSS) wireless mode (which is not commonly used and Mikrotik does not support) -- and there is are reasons that it is included in adhoc mode and not in ap to client mode. The standard requires clients to accept the beacon timestamp unconditionally in ap to client mode. Tranzeo has added a specific check because they said they thought it is logical that the check be applied to ap to client mode. Good standards implementations do not add things to a standard. These standards are made by IEEE committees of engineers that are very specific on what they include and don't include. If a company wants to change a standard, then they need to join the committee and, through peer review, get a new standard approved. We have made a work-around for their violation of the standard. But rather than somebody saying thank you, the old saying of 'no good deed goes unpunished' is proven again. We make many work-arounds for incorrect standards implementations and extension by companies such as Microsoft, Realtek, and now Tranzeo. We do that to help our customers, but in reality, the vendors that do not follow the standards should fix the problem. In summary, it is very unfair that we are blamed for problems made by another company that does not implement the standard correctly. Many people in this business don't do it just for money, but because they like making things (be it WISP or equipment for WISP). Rants without basis kind of put a wet blanket on the whole party. For those that would like to research this, here a clear reference from the 802.11 standard that is pertinent: From 802.11-2007, 11.1.1.1 TSF for infrastructure networks: ... A receiving STA shall always accept the timing information in Beacon frames sent from the AP servicing its BSS. If a STAâEUR^(TM)s TSF timer is different from the timestamp in the received Beacon frame, the receiving STA shall set its local TSF timer to the received timestamp value. Tranzeo decided to assume that receiving a beacon with timestamp less than in previous beacon indicates that the AP has restarted (the standard has another method to handle restarted ap units). This check is not in the standard and this a tranzeo addition to the standard that has cause the disconnect problem that Ryan has suffered from. Regards, Mikrotik ------------------------------ * Dennis Burgess, CCNA, A+, Mikrotik Certified Trainer Link Technologies, Inc -- Mikrotik & WISP Support Services* 314-735-0270 http://www.linktechs.net <http://www.linktechs.net/> */ Link Technologies, Inc is offering LIVE Mikrotik On-Line Training <http://www.linktechs.net/onlinetraining.asp>/* D. Ryan Spott wrote: > Oh don't think I have not tried to shame them into this MULTIPLE times... :) > > Damian! Get on it! > > ryan > > -----Original Message----- > From: John Scrivner <[EMAIL PROTECTED]> > Sent: Tuesday, October 21, 2008 6:43 AM > To: WISPA General List <[EMAIL PROTECTED]> > Subject: Re: [WISPA] [Tranzeo] New Update - Tranzeo/Mtik disconnect issue > Oct 10th, 2008 > > Now if they would just drop a mere $1000 to join WISPA as a Vendor > Member they would earn mine. I use their products every day. I have > asked them to join, face to face, at shows as recently as the last > WiMax World a month ago. Tranzeo benefits regularly from WISPA but as > yet seems reluctant to support our industry efforts. > Scriv > > > On Mon, Oct 20, 2008 at 11:25 PM, Kurt Fankhauser <[EMAIL PROTECTED]> wrote: > >> I read every word. Tranzeo has earned my respect. >> >> Kurt Fankhauser >> WAVELINC >> P.O. Box 126 >> Bucyrus, OH 44820 >> 419-562-6405 >> www.wavelinc.com >> >> >> -----Original Message----- >> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On >> Behalf Of D. Ryan Spott >> Sent: Monday, October 20, 2008 6:04 PM >> To: [EMAIL PROTECTED]; WISPA General List; Mikrotik discussions; Mikrotik >> Users Mailing List >> Subject: Re: [WISPA] [Tranzeo] New Update - Tranzeo/Mtik disconnect issue >> Oct 10th, 2008 >> >> Ladies and Gentlemen, >> >> (Please pardon my extensive use of () and "" in this here email, I am >> not so good with the typin' stuff! >> >> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- >> >> A few weeks ago (years in some cases, hi Travis!) there was discovered a >> "random disconnect issue between Tranzeo CPE and Mtik APs." >> >> First it was prism vs atheos (no, that was not it) >> Then it was "tranzeo CPE are terrible. Yadda Yadda" (no that is not it >> either as even MTIK CPE were seing this, although "not as often") >> Then it was "you must have some power issue with the boards browning out >> on the routeros board you are using" (nope, not that either) >> Someone even threw in "Pluto is mad that it is not a planet any more." >> (Pluto is now considered the largest member of a distinct population >> called the Kuiper belt <http://en.wikipedia.org/wiki/Kuiper_belt>.) >> Even I said it was not an issue and "hey they just disconnect a few >> times a day.. who cares!" (whoops! talk to my P****** off customers!) >> Even Marlon the strange wizard from the far side of the mountains >> > > [The entire original message is not included] > > > -------------------------------------------------------------------------------- > WISPA Wants You! Join today! > http://signup.wispa.org/ > -------------------------------------------------------------------------------- > > WISPA Wireless List: [EMAIL PROTECTED] > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.butchevans.com/pipermail/mikrotik/attachments/20081022/d4781105/attachment.html
