From: Michael Richardson <mcr@sandelman.ca>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] 3.10.36-4 field report: dnsmasq made to work
Date: Sun, 15 Jun 2014 17:06:34 -0400 [thread overview]
Message-ID: <13509.1402866394@sandelman.ca> (raw)
I forklift upgraded from 3.10.24-8 (I think), to 3.10.36-4 today.
Forklift, because I factory flashed my spare unit with .36, uploaded the
backed up configuration, and then swapped.
1) I figured out my problems with SSH to the device. Nothing malicious,
it turns out that ssh to 42.1 is accepted only if you are on the 42.x
network, which I *thought* my desktop was via a VLAN, but it turns out
that it wasn't. So the ssh was going in via a different port, and
connecting, and then dropbear was (correctly!) disconnecting. More
logging needed there.
2) dnsmasq did not start properly.
First the problem seemed to be that odhcpd was running, so port 547 was
busy (DHCPv6 server port). Should it be running? where would I have
enabled that?
I killed it off, and ran /etc/rc.d/S35odhcpd disable, and then
I got a complaint that the /var/lib/misc/dnsmasq.leases could not be
created. We need to have:
mkdir -p /var/lib/misc
touch /var/lib/misc/dnsmasq.leases
in the start up scripts, and somehow we also need to have some way to
see how daemons are being started up. The /etc/rc.common stuff creates
a huge verbosity if you set -x things.
Given how import dnsmasq is, it really really needs to never refuse to run.
I'm gonna power cycle the unit and see if it comes back okay.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
next reply other threads:[~2014-06-15 21:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-15 21:06 Michael Richardson [this message]
2014-06-16 0:06 ` Michael Richardson
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=13509.1402866394@sandelman.ca \
--to=mcr@sandelman.ca \
--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