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: Bug Report - setup
Date: Sat, 25 Oct 2014 22:46:32 -0500	[thread overview]
Message-ID: <544C6E98.2080800@dailydata.net> (raw)

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

I was having some problems with a remote router not resolving addresses,
so I started 'setup' from the CLI to change them. When I did this, I had
the same problem (and suspected a network issue). Clearing dnsmasq
(dnsmasqctl restart) showed it was still using the old DNS servers.

The router is using DHCP for the red interface, but I am trying to
override the DNS given by them (it is their little monitoring tool).

Investigating, I found the following happened:

1. DNS settings appear in two places
   /var/ipfire/ethernet/settings
   /var/ipfire/dns/settings

2. 'setup' modifies /var/ipfire/ethernet/settings, but does not modify
/var/ipfire/dns/settings. It appears dnsmasql uses /var/ipfire/dns/settings.

3. In the webui, 'Network | Assign DNS Server' reads
/var/ipfire/dns/settings, so changes made there correctly work.

Resolution:

Either fix the code or simply remove the text that says you can change
the DNS for DHCP there:

Enter the DNS and gateway information.  These settings are used only
with Static IP (and DHCP if DNS set) on the RED interface.

Frankly, the latter would be easiest, and most people will use the
WebGUI, and weirdos like me will simply edit the settings file if I
happen to need to change it from the CLI.

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

             reply	other threads:[~2014-10-26  3:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-26  3:46 R. W. Rodolico [this message]
2014-10-28  0:51 ` Michael Tremer
2014-10-28  1:27   ` R. W. Rodolico
2014-10-28  1:41     ` Michael Tremer
2014-10-28  2:24       ` R. W. Rodolico

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=544C6E98.2080800@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