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: Re: [Cerowrt-devel] cerowrt-3.10.44-2 released
Date: Tue, 17 Jun 2014 16:09:52 -0700	[thread overview]
Message-ID: <CAA93jw7NO-jpcgp0V70P3h5HOPqfu9E1J6kR=AOLu38Sgfk+VA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6UbYgkLLOYvUEZcU0ugXwcZN5O=O1DkuhWgYwE2mHOpQ@mail.gmail.com>

cautionary note: After installing hnetd, etc, "Bad things happen".

What I'm seeing is the interfaces get cycled every minute or so, thus
losing connectivity for 10-20 seconds.

 2249 root      1416 S    {hotplug-call} /bin/sh /sbin/hotplug-call iface
 2357 root      1400 S    -ash
 2393 root      1500 S    {hotplug-call} /bin/sh /sbin/hotplug-call iface

The reason for the caution is that it is not certain that I did this
to myself...
and removing hnetd doesn't fix it.

more news in an hour.


On Tue, Jun 17, 2014 at 2:08 PM, Dave Taht <dave.taht@gmail.com> wrote:
> and of course, it's available at:
> http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.10.44-2/
>
> On Tue, Jun 17, 2014 at 2:06 PM, Dave Taht <dave.taht@gmail.com> wrote:
>> + huge resync with openwrt head
>>    among many other things this includes a lot of rework of the wifi drivers
>>    which may have some influence on bug 442
>>    update to iproute2
>>    many updates all across the board
>> + sqm fixed to work with modern luci (thx Magnus Olsson!)
>> + Rich Brown's cerowrt-scripts installed for the first time by default -
>>    bug: they need to have -4 or -6 specified for certain targets, and
>> two of the targets in circulation
>>    are not responding to netperf (try netperf-west.bufferbloat.net)
>>
>>    It could use a gui for running the test and displaying the results...
>>
>> - tested for all of 5 minutes
>> - it is possible to switch dns servers from odhcp to dnsmasq and vice
>> versa via changing maindhcp in /etc/config/dhcp (not tested)
>> - conflict between avahi-daemon and mdns.
>>
>> Disable one on your first boot. (/etc/init.d/avahi-daemon disable
>> or /etc/init.d/mdnsd disable). I'd like it if people explored mdsnd
>> with awareness that it doesn't proxy yet...
>>
>> - the hnetd and mdnsproxy work is still in progress, and these daemons
>> are built but not installed by default.
>>
>> I would generally discourage everyone from installing this as your
>> main router, but I know how effective that is. Certainly if you are
>> experiencing wifi hangs this is worth trying.
>>
>> --
>> Dave Täht
>
>
>
> --
> Dave Täht
>
> NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article



-- 
Dave Täht

NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article

  reply	other threads:[~2014-06-17 23:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-17 21:06 Dave Taht
2014-06-17 21:08 ` Dave Taht
2014-06-17 23:09   ` Dave Taht [this message]
2014-06-17 23:49     ` Dave Taht
2014-06-18 14:47 ` [Cerowrt-devel] mdnsd in cerowrt-3.10.44-3 Rich Brown

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='CAA93jw7NO-jpcgp0V70P3h5HOPqfu9E1J6kR=AOLu38Sgfk+VA@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