Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Fred Stratton <fredstratton@imap.cc>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] 3.8.13-6 No name resolution over wireless
Date: Fri, 7 Jun 2013 10:04:12 -0700	[thread overview]
Message-ID: <CAA93jw57LnxLCsOeDoLGb1rtKxFQo-J-zqdpktwNFfhNiMr82w@mail.gmail.com> (raw)
In-Reply-To: <2FB25374-452D-414E-9056-016C0C2C4FF8@imap.cc>

[-- Attachment #1: Type: text/plain, Size: 2324 bytes --]

On Thu, Jun 6, 2013 at 3:23 AM, Fred Stratton <fredstratton@imap.cc> wrote:

> Taeht wants all User posting on this list.
>

No, just posts about dev versions. I note that what you are fiddling with
is not even a released dev version. Toke's doing builds too but he's trying
to finish a thesis...

I REALLY appreciate the testing but I'm not planning on installing anything
myself until after the adsl fixes for htb stablize, and not until after
june 17th regardless. (I do try to keep up with openwrt head so as to
minimize problems with CI (continuous integration)).

The only things different in -6 are a newer dnsmasq, some aqm script
improvements, and a patch for 6in4 stuff... hmm, I should mention that.


>
> I am not a developer, though you need a certain skill set to manipulate
> Cerowrt as a user.
>

yep! It's not for grandma yet!


>
> The weather here is good, whilst the rest of Europe drowns, and poorer
> wireless reception has come with the sunshine, which hampers
> troubleshooting.
>

I am glad to be back at the yurtlab where all the code in use is cero.


>
> This build works better on ADSL, so I am reluctant to regress to an
> earlier one.
>

the aqm code continues to evolve. What is in the next build has been
more thoroughly tested (on an atom box) but Jesper's ADSL fix remains
pending.


>
> Ethernet connected clients work as expected.
>
> Wireless clients connect, but neither Ubuntu 12.04.2 nor ML machines can
> resolve URIs.
>

Hmm. I note there is a bug in dnsmasq here under tcp, fixed in the latest
test release of dnsmasq, but I don't understand what's going on for you.

Do your wireless clients get a dns server? what does nslookup report?



>
> I suspect this is a configuration problem. /etc/config/wireless is
> difficult to understand with so many routed interfaces.
>
> 3.8.13-5 did not have the problem.
>

there was an update to dnsmasq in this non-release, but so far as I knew it
was a fix, not a regression.


>
>
> _______________________________________________
> 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

[-- Attachment #2: Type: text/html, Size: 3657 bytes --]

  reply	other threads:[~2013-06-07 17:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-06 10:23 Fred Stratton
2013-06-07 17:04 ` Dave Taht [this message]
2013-06-07 17:07 ` Felix Fietkau
2013-06-07 20:19   ` Fred Stratton

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=CAA93jw57LnxLCsOeDoLGb1rtKxFQo-J-zqdpktwNFfhNiMr82w@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=fredstratton@imap.cc \
    /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