Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Simon Kelley <simon@thekelleys.org.uk>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Fwd: [Dnsmasq-discuss] Testers wanted: DNSSEC.
Date: Mon, 10 Feb 2014 11:39:16 +0000	[thread overview]
Message-ID: <52F8BA64.2050401@thekelleys.org.uk> (raw)
In-Reply-To: <87bnyg55tp.fsf@toke.dk>

On 09/02/14 21:33, Toke Høiland-Jørgensen wrote:
> Simon Kelley<simon@thekelleys.org.uk>  writes:
>
>> It's possible, indeed that's happened during testing. Dave, could you
>> talk me through getting the latest dnsmasq package on the 3800 you
>> gave me?
>
> The packages I've built are here:
> http://archive.tohojo.dk/cerowrt/wndr/3.10.28-4-tohojo/packages/
>
> They're packaged as libhogweed, libnettle, libgmp and dnsmasq-dhcpv6 --
> dunno if they're installable without further ado on your box. But if so
> you should be able to just download those four package files onto your
> router (stick them in /tmp to avoid running out of flash) and calling
> opkg to install them...


Great, thanks. I've done that and confirmed what you are seeing. At this 
point I need to trace through the whole validation process in parallel 
on working and broken platforms, to see where the two diverge.
(I've had to do this before. It was not fun, but it did produce 
results.) I've installed gdb and can run dnsmasq under gdb, but the 
binary is very thoroughly stripped, so I can't get any useful 
information out. Best way to get a non-stripped dnsmasq binary on there?



Cheers,

Simon.




  parent reply	other threads:[~2014-02-10 11:39 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-04 16:20 Dave Taht
2014-02-05  7:13 ` Toke Høiland-Jørgensen
2014-02-05 17:10   ` Toke Høiland-Jørgensen
2014-02-05 19:51     ` Simon Kelley
2014-02-05 20:09       ` Toke Høiland-Jørgensen
2014-02-05 22:26         ` Simon Kelley
2014-02-06  7:28           ` Toke Høiland-Jørgensen
2014-02-06 10:53             ` Simon Kelley
2014-02-06 10:57               ` Toke Høiland-Jørgensen
2014-02-06 11:27                 ` Simon Kelley
2014-02-06 12:35                   ` Toke Høiland-Jørgensen
2014-02-06 15:01                     ` Simon Kelley
2014-02-09 12:09                       ` Toke Høiland-Jørgensen
2014-02-09 12:23                         ` Simon Kelley
2014-02-09 12:48                           ` Toke Høiland-Jørgensen
2014-02-09 18:04                             ` Dave Taht
2014-02-09 18:47                               ` Toke Høiland-Jørgensen
2014-02-09 21:02                               ` Simon Kelley
2014-02-09 20:59                             ` Simon Kelley
2014-02-09 21:07                               ` Dave Taht
2014-02-09 21:16                                 ` Toke Høiland-Jørgensen
2014-02-09 21:33                               ` Toke Høiland-Jørgensen
2014-02-10 10:50                                 ` Simon Kelley
2014-02-10 11:39                                 ` Simon Kelley [this message]
2014-02-10 12:59                                   ` Toke Høiland-Jørgensen
2014-02-10 16:45                                     ` Simon Kelley
2014-02-10 16:59                                       ` Toke Høiland-Jørgensen
2014-02-10 17:12                                         ` Simon Kelley
2014-02-10 17:14                                         ` Dave Taht
2014-02-10 21:47                                           ` Simon Kelley
2014-02-11 11:34                                         ` Simon Kelley
2014-02-11 14:01                                           ` Toke Høiland-Jørgensen
2014-02-11 15:51                                             ` Simon Kelley
2014-02-11 16:25                                               ` Toke Høiland-Jørgensen
2014-02-06 13:42                   ` Toke Høiland-Jørgensen
2014-02-06 14:40                     ` Simon Kelley

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=52F8BA64.2050401@thekelleys.org.uk \
    --to=simon@thekelleys.org.uk \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    /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