From: Dave Taht <dave.taht@gmail.com>
To: Philippe Huybrechts <philippe@twixel.be>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Cerowrt on WDR4900
Date: Mon, 19 May 2014 15:50:08 -0700 [thread overview]
Message-ID: <CAA93jw60jx8nkvSrQpqLEmj-_JzHWhGj_8PepnwdLxfXEwv0iQ@mail.gmail.com> (raw)
In-Reply-To: <537A67A0.4040702@twixel.be>
On Mon, May 19, 2014 at 1:20 PM, Philippe Huybrechts <philippe@twixel.be> wrote:
> Is there a canonical way of building Cerowrt for a different device? I am
> trying to get it to run on a TP-Link WDR4900.
>
> I am starting from a clean build of the openwrt trunk, and trying to mix in
> the different cerowrt repo, but I think there must be a better way.
No. Getting a different arch up is a pita the first time.
Simplest thing to do is just add ceropackages to your feeds.conf, and build
sqm-scripts and luci-app-sqm for cerowrt's qos system, and/or
add override packages for things like dnsmasq with dnssec.
Is there something else besides that you wanted?
I just built cerowrt semi-successfully for the archer c7v2, steps needed
were complex... and took me most of a weekend. I will try to write them
up, but basically you need cerowrt-3.10, cerofiles-3.10, and ceropackages,
you need to merge in the correct switch and interface data for your
device into files/etc/config/network, then hammer in the right package
files from the cerofiles packages.list and override.list, wash , rinse
and repeat, and then hope you got the switch OR wifi info right so
you can flash a box and get into it to see what else broke.
>
>
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
--
Dave Täht
NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article
prev parent reply other threads:[~2014-05-19 22:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 20:20 Philippe Huybrechts
2014-05-19 22:50 ` Dave Taht [this message]
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=CAA93jw60jx8nkvSrQpqLEmj-_JzHWhGj_8PepnwdLxfXEwv0iQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=philippe@twixel.be \
/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