public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "R. W. Rodolico" <rodo@dailydata.net>
To: development@lists.ipfire.org
Subject: 104 and dnsmasq
Date: Tue, 13 Sep 2016 02:25:25 -0500	[thread overview]
Message-ID: <57D7A9E5.4050606@dailydata.net> (raw)

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

First, this may just be an issue with my firewall. I've used it for
testing for a long time; I need to just back it up and rebuild from scratch.

But, since upgrading to 104, I've had two instances when dnsmasq just
stopped. I was part of the testing when this happened a while ago, so I
recognize the situation and fix it pretty fast (log into firewall,
/etc/init.d/dnsmasq start).

As I said, this may not really be an issue with anything other than an
firewall that has been used for testing for a while. But I thought I'd
mention it and see if anyone else has a similar problem.

Next time it happens, I'll get a log dump. Forgot to do it before.

Rod
-- 
Rod Rodolico
Daily Data, Inc.
POB 140465
Dallas TX 75214-0465
214.827.2170
http://www.dailydata.net

             reply	other threads:[~2016-09-13  7:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-13  7:25 R. W. Rodolico [this message]
2016-09-13 14:30 ` Michael Tremer

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=57D7A9E5.4050606@dailydata.net \
    --to=rodo@dailydata.net \
    --cc=development@lists.ipfire.org \
    /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