From: Simon Kelley <simon@thekelleys.org.uk>
To: "Richard E. Brown" <richb.hanover@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Dnsmasq-discuss] Names not resolved on Wireless
Date: Sat, 12 Oct 2013 17:32:34 +0100 [thread overview]
Message-ID: <525979A2.6070108@thekelleys.org.uk> (raw)
In-Reply-To: <B3B0CBE6-5E53-49AF-B18E-4D676F5D3281@gmail.com>
On 11/10/13 18:52, Richard E. Brown wrote:
> Simon,
>
>> I'll try and learn how to flash the router Dave gave me so I can test this stuff myself.
>
> For anyone interested in trying to do this at home, Dave wrote a *very* good procedure for flashing the ...xxx-squashfs-factory.img firmware via tftp at:
>
> http://www.bufferbloat.net/projects/cerowrt/wiki/CeroWrt_flashing_instructions
>
> As noted on that page, the tftp process always works. You'll also need:
>
> - bent paper clip
> - Ethernet cable
> - tftp client on your computer
> - and of course, a WNDR3700v2 or WNDR3800 router
>
> It takes longer to read the steps than to flash the firmware. :-)
>
> Rich Brown
> Hanover, NH USA
>
Indeed. Being located in a nautical, rather than office, environment I
used a split-pin instead of a paperclip. I also had to find the firmware
for the ethernet port in the ship's computer, which is not supported
out-of-the-box by Ubuntu :-( That done, it went fine.
Poking around my newly flashed router, I find.
1) The dnsmasq config does indeed use --except-interface and no
--interface statements, so the SO_BINDTODEVICE bug a talked about before
may have caused the problem if exactly one interface is up when dnsmasq
starts. The code I committed yesterday which logs setting
SO_BINDTODEVICE is the final arbiter of this, but I think that bug
should be fixed anyway. It may have been the original source of the problem.
2) This is an out-of-the-box router, I've not changed the config at all.
I can see a single --dhcp-range,
172.30.42.2,172.30.42.27,255.255.255.224,24h which corresponds to the
wired interface. I can't see anything for the wireless interfaces. When
I go to the GUI for the wireless interface, I see it has address
172.30.42.65/26 and the DHCP service is enabled, but for start address 2
and 26 leases. Since 2 isn't in the 64-96 range, could that be the
problem, or am I missing something obvious?
Cheers,
Simon.
next prev parent reply other threads:[~2013-10-12 16:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 23:07 [Cerowrt-devel] " Fred Stratton
2013-10-07 23:40 ` David Personette
2013-10-10 12:30 ` David Personette
2013-10-10 14:43 ` Dave Taht
2013-10-10 17:32 ` Fred Stratton
[not found] ` <5256DBB1.50707@thekelleys.org.uk>
2013-10-10 18:30 ` [Cerowrt-devel] [Dnsmasq-discuss] " Dave Taht
2013-10-10 18:53 ` Simon Kelley
2013-10-10 20:23 ` Simon Kelley
2013-10-11 0:01 ` Dave Taht
2013-10-11 11:02 ` David Personette
2013-10-11 13:41 ` Fred Stratton
2013-10-11 14:30 ` Dave Taht
2013-10-11 15:37 ` Simon Kelley
2013-10-11 17:52 ` Richard E. Brown
2013-10-12 16:32 ` Simon Kelley [this message]
2013-10-11 19:46 ` Fred Stratton
2013-10-10 18:42 ` [Cerowrt-devel] " Richard E. Brown
2013-10-10 22:16 ` 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=525979A2.6070108@thekelleys.org.uk \
--to=simon@thekelleys.org.uk \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=richb.hanover@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