Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Fred Stratton <fredstratton@imap.cc>
To: Dave Taht <dave.taht@gmail.com>, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] cerowrt 3.10.17-6 released
Date: Sat, 02 Nov 2013 09:01:52 +0000	[thread overview]
Message-ID: <5274BF80.4000001@imap.cc> (raw)
In-Reply-To: <CAA93jw7FHyheL+31DE_dHiEOPRcPZDDAVaanex4VVEc6Z_3XuA@mail.gmail.com>

Again, PPPoE does not function. Corroboration - or, better still, a 
workaround - would be useful.

I am not the only person with a PPPoE connection.


On 02/11/13 02:17, Dave Taht wrote:
> + resync with openwrt
> + dnsmasq 2.68test1
> + pie v3 (as submitted to the netdev list)
> - no sysupgrade fix
> - dnsmasq still restarted via /etc/rc.local
>
> That's at:
>
> http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.10.17-6/
>
> untested. I am getting in a vehicle for vancouver in 2 minutes....
>
> I also just built (and tested) the same code for the nanostation m5
> and picostation.
>
> http://snapon.lab.bufferbloat.net/~cero2/cerowrt/nano-m/3.10.17-6/
>
> Note: this is a rather specialized build for the yurtlab, with
> hardcoded ips and a hard dependency on babel being up and running, and
> it was a collossal PITA to make it do both a mesh and a AP mode (basically
> wlan0 MUST be the AP, wlan0-1 can be ad-hoc and then you have to edit
> the network and dhcp and babel files appropriately... which I should
> document if anyone cares to try this hardware. (I also note this has
> my public key allowed in by default, you should nuke it if you try it)
>
> Unless more bugs show up in pie or dnsmasq I'm not going to touch this
> stuff for a week. See you at ietf! The aqm and iccrg and webrtc and
> rmcat meetings should be pretty interesting.
>


  reply	other threads:[~2013-11-02  9:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-02  2:17 Dave Taht
2013-11-02  9:01 ` Fred Stratton [this message]
2013-11-07 10:48 ` Juergen Botz

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=5274BF80.4000001@imap.cc \
    --to=fredstratton@imap.cc \
    --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