I think everyone is missing Travis's point. Everyone is trying to find the work around, or partial solution, using the tools a product already has. Sure all these tools help. But they do NOT replace a tool that is better that someone has had in their hands for years proving the value of that tool.
There are reasons why products Like Trango have been so popular with the larger scale WISP commmunitiy, and their secret is they give the professional tools that make just that little bit more difference that matters, for a WISP to detect, resolve, and certify network connections inthe quickest manner. If Mikrotik wants to be in the same league as the big boys, they need to make new better big boy tools, not only hold on to the existing tools they have that offer 70% of the solution. This is not meant to be a comparision of vendors or an attack on Mikrotik. I think Mikrotik has made huge strides in this industry, and really is starting to have a very feature rich product, that can't be ignored. I really respect what they have accomplished, and amazing value. But they are still missing the boat in some areas/tools. What Travis wants is a quicktool to certify a link, that his staff can rely on without individual interpretation. the Trango Linktest tool, gives exactly that. Its within Mikrotik's power to add those tools. Or atleast get closer to them. The question is whether they truly understand why the tools are needed, or whether they just don't have the time to make them, or if there is some technical barrier that prevents them from being made. The first step is making them understand why it is needed. Second step is making it clear exactly what it is that is needed. And third is getting them to make time to make it. And if we can accomplish that, then Mikrotik will just be a better product because of it. Tom DeReggi RapidDSL & Wireless, Inc IntAirNet- Fixed Wireless Broadband ----- Original Message ----- From: "George Rogato" <[EMAIL PROTECTED]> To: "WISPA General List" <wireless@wispa.org> Sent: Thursday, February 14, 2008 12:39 AM Subject: Re: [WISPA] MT tools > Don't you see real time active rissi etc when you look into the ap's > interface listing all the clients? > > > Travis Johnson wrote: >> What I really want is a way to right-click on an entry in the >> Registration table and have an option that says "Linktest". It would >> test sending 100 packets each direction, 10 times. It would then report: >> >> distance of the link (based on time calculations) >> error rate going from AP to CPE (%) >> error rate going from CPE to AP (%) >> Calculated throughput based on those results >> >> This simple tool has proven invaluable with our Trango system. Our 1st >> level techs can login to the AP and do a "linktest" on a customer's >> radio and know in 10 seconds if there is an RF problem or something >> else. Having to look at CCQ numbers, packet frames vs. hardware frames, >> etc. is way too complicated for a 1st level tech. >> >> Yes, we monitor and graph signal levels, bytes, packets, errors, etc. on >> every customer we have now... but that simple 10 second test makes life >> much, much easier. >> >> Travis >> Microserv >> >> Butch Evans wrote: >>> On Tue, 12 Feb 2008, Travis Johnson wrote: >>> >>> >>>> With a product like Trango, they have a utility called "linktest" >>>> that shows packet loss after sending ten sets of 100 packets and >>>> measuring on both sides the loss: >>>> >>> >>> With Mikrotik, you have stats for the wireless link as well. You >>> can double-click an entry under WIRELESS->Registration-Table and you >>> have a stats tab that will show you tx and rx packets, bytes, >>> frames, frame bytes, hardware frame bytes and frames. The >>> difference between packets and frames is loss on the link. I agree >>> that it would be nice to have a calculated value displayed, but the >>> information is available. The packet data is available via snmp as >>> well, though the hardware frame data is not. You can get (from >>> snmp) the OID that includes errors (in and out) on the wireless link >>> as well as other interfaces. The OID is found with: "/interface >>> print oid". Is this what you are wanting? >>> >>> >> >> ------------------------------------------------------------------------ >> >> >> >> -------------------------------------------------------------------------------- >> WISPA Wants You! Join today! >> http://signup.wispa.org/ >> -------------------------------------------------------------------------------- >> >> WISPA Wireless List: wireless@wispa.org >> >> Subscribe/Unsubscribe: >> http://lists.wispa.org/mailman/listinfo/wireless >> >> Archives: http://lists.wispa.org/pipermail/wireless/ > > -- > George Rogato > > Welcome to WISPA > > www.wispa.org > > http://signup.wispa.org/ > > > -------------------------------------------------------------------------------- > WISPA Wants You! Join today! > http://signup.wispa.org/ > -------------------------------------------------------------------------------- > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ -------------------------------------------------------------------------------- WISPA Wants You! Join today! http://signup.wispa.org/ -------------------------------------------------------------------------------- WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
