From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from z.eggo.org (z.eggo.org [80.235.105.138]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id D9ABD3B2D8 for ; Tue, 21 Jun 2016 15:08:49 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by z.eggo.org (Postfix) with ESMTP id CEE1B580093; Tue, 21 Jun 2016 22:08:48 +0300 (EEST) Received: from z.eggo.org ([127.0.0.1]) by localhost (z.eggo.org [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id uM9qQhVzjfAa; Tue, 21 Jun 2016 22:08:48 +0300 (EEST) Received: from localhost (localhost [127.0.0.1]) by z.eggo.org (Postfix) with ESMTP id B13F358010B; Tue, 21 Jun 2016 22:08:48 +0300 (EEST) X-Virus-Scanned: amavisd-new at harvee.org Received: from z.eggo.org ([127.0.0.1]) by localhost (z.eggo.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id FyJt4nd0UaL9; Tue, 21 Jun 2016 22:08:48 +0300 (EEST) Received: from [192.168.9.71] (unknown [146.115.109.236]) by z.eggo.org (Postfix) with ESMTPSA id 2A70C580093; Tue, 21 Jun 2016 22:08:48 +0300 (EEST) To: Dave Taht References: Cc: "cerowrt-devel@lists.bufferbloat.net" From: Eric Johansson Message-ID: <583214db-2c3f-4545-9f56-168dff3879e2@eggo.org> Date: Tue, 21 Jun 2016 15:08:48 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Cerowrt-devel] anyone tried a wrtnode? X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jun 2016 19:08:50 -0000 On 6/21/2016 3:02 PM, Dave Taht wrote: > On Tue, Jun 21, 2016 at 11:59 AM, Eric Johansson wrote: >> I assume you've seen this list https://wikidevi.com/wiki/Ath9k >> >> I'm starting to play with mikrotek devices. routeros is a consultants >> full employment program so replacing it would be nice. > I *knew* I was in the wrong business and backing the wrong play here. > It is long past time that I start taking advantage of broken window > economics. It would keep a roof over my head and the lights on, and > affect the economy less, as building systems that worked well more of > the time, as we keep trying to do here, would put so many out of work. Assuming I can find enough consulting work, I want to spend some time building a better way of interfacing with these devices. The vendor supplied web interface is equivalent to someone giving you a big pile parts and saying, here's a low-cost car, You just need to put it together yourself. I want to focus on a task oriented interface where its notation is built on what we as network developers use, not what the capabilities of the device are. I did before with IP cop, I think I can do it again for more complex device. If I do it right, it should be able to be a good interface for any switch/firewall. for too long, people have made network infrastructure device user interfaces complicated. It's time to make them simple.