From: Eric Johansson <esj@eggo.org>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] anyone tried a wrtnode?
Date: Tue, 21 Jun 2016 15:08:48 -0400 [thread overview]
Message-ID: <583214db-2c3f-4545-9f56-168dff3879e2@eggo.org> (raw)
In-Reply-To: <CAA93jw6saFS=W7-x_Y9UKaqBLC-SPQzWQcQvmSexSJ5Y1gUX2g@mail.gmail.com>
On 6/21/2016 3:02 PM, Dave Taht wrote:
> On Tue, Jun 21, 2016 at 11:59 AM, Eric Johansson <esj@eggo.org> 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.
next prev parent reply other threads:[~2016-06-21 19:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 6:36 Dave Taht
2016-06-21 18:59 ` Eric Johansson
2016-06-21 19:01 ` David Lang
2016-06-21 19:02 ` Dave Taht
2016-06-21 19:08 ` Eric Johansson [this message]
2016-06-21 20:04 ` Jonathan Morton
2016-06-21 22:55 ` Stephen Hemminger
2016-06-22 17:34 ` Eric Johansson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=583214db-2c3f-4545-9f56-168dff3879e2@eggo.org \
--to=esj@eggo.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox