Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] cerowrt-3.10.44-6 released
Date: Tue, 24 Jun 2014 20:37:42 -0700	[thread overview]
Message-ID: <CAA93jw4gyMTjG2F+pN0MVnYJToh6W1RJKO9g-tshafM0MgS-LA@mail.gmail.com> (raw)

http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.10.44-6/

+ tested for all of 20 minutes - I intend to start a major test series overnight
and beat the c**p out of it and the other devices I'm working on. feel
free to wait to install.

+ fixed the basic problems with the -5 build
+ same update from openwrt head as in -5.

+ mdnsd nuked again (ultimately we're going to switch to it but not now)

   I had to completely strip mdnsd out of the build to make it go away
(./scripts/feeds uninstall mdnsd)

+ natpmp was conflicting with the same (new unified) functionality in
miniupnpd, si I nuked natpmp.
   not clear if better firewall rules are needed yet, the ipv6
functionality scares me.

- see some errors like:

Wed Jun 25 03:29:13 2014 daemon.warn miniupnpd[4119]: SSDP packet
sender 172.21.2.5:34062 not from a LAN, ignoring

+ netserver started again from xinetd

- it looks like the ntp monitoring thing toke did is not working
and/or we're running the wrong ntp now
    but dnsmasq does not run with timechecks enabled by default, so we do
dnssec correctly with invalid time until something sends a sighup

...

I'm really looking forward to the barrier breaker freeze.

I am doing no more builds until I replicate bug 442.


-- 
Dave Täht

             reply	other threads:[~2014-06-25  3:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-25  3:37 Dave Taht [this message]
2014-06-26 19:28 ` Jim Reisert AD1C
2014-06-26 19:53   ` Dave Taht
2014-07-06 19:45     ` R.

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=CAA93jw4gyMTjG2F+pN0MVnYJToh6W1RJKO9g-tshafM0MgS-LA@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /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