Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Michael Richardson <mcr@sandelman.ca>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] running cerowrt/*wrt in a VM
Date: Mon, 11 Nov 2013 12:13:53 -0800	[thread overview]
Message-ID: <CAA93jw5vX8ZV3h0-fzdrZB-xqDAYVW3fAu1jxnPFwG+4T27Bdw@mail.gmail.com> (raw)
In-Reply-To: <11578.1384198837@sandelman.ca>

I have had multiple requests for an x86 vm. I tried several times but
never got anything that even booted. And ENOBUDGET to make it work,
and ENOTIME to keep it working.

I do take patches, and all that is really needed for a cerowrt build
would be a new build script, .config file, and a working filesystem.

I'd argue for straight openwrt and/or see if you can leverage a trunk
build. Everything you describe has made it to openwrt "barrier
breaker" trunk already.

On Mon, Nov 11, 2013 at 11:40 AM, Michael Richardson <mcr@sandelman.ca> wrote:
>
> I need to do some testing of PPPoE, DHCPv6 (RFC6204/homenet) with an
> OpenWRT/CeroWRT.
>
> I want to do this virtually, so an x86 build would be best. I grabbed the kvm
> image of openwrt attitude adjustment, as per:
>   http://wiki.openwrt.org/doc/howto/qemu
> and
>   http://downloads.openwrt.org/attitude_adjustment/12.09/
>
> it appears that it hasn't got any IPv6 stuff in it.  I thought that all this
> stuff from openwrt went upstream?  Is 12.09 perhaps just too old?
>
> My choices are, I guess:
>    1) build cerowrt for x86
>    2) build latest openwrt from source
>
> Or did I miss an obvious image?
>
> --
> ]               Never tell me the odds!                 | ipv6 mesh networks [
> ]   Michael Richardson, Sandelman Software Works        | network architect  [
> ]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [
>
>
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel



-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

  parent reply	other threads:[~2013-11-11 20:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-11 19:40 Michael Richardson
2013-11-11 19:56 ` Paul Handly
2013-11-12 15:16   ` Michael Richardson
2013-11-11 20:13 ` Dave Taht [this message]
2013-11-12 15:26 ` Denis Ovsienko

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=CAA93jw5vX8ZV3h0-fzdrZB-xqDAYVW3fAu1jxnPFwG+4T27Bdw@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=mcr@sandelman.ca \
    /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