From: Matt Taggart <matt@lackof.org>
To: Matt Taggart <matt@lackof.org>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] using an alternate tftp server
Date: Sat, 04 Oct 2014 16:43:59 -0700 [thread overview]
Message-ID: <20141004234359.B7F101B1@taggart.lackof.org> (raw)
In-Reply-To: <20140926221942.5F52C1B6@taggart.lackof.org>
Matt Taggart writes:
> Hi cerowrt-devel,
>
> I needed to tell dnsmasq to use an alternate tftp server and the ability to
> do so isn't exposed through the web UI, so I figured out how to do it. Here
> is a description, if it looks OK maybe it can go in the FAQ?
>
> =======================================================================
> Q: How do I use an alternate tftp boot server?
>
> A: The web configuration interface lets you enable a local TFTP server
> and set its root and boot file name, but if you just want the DHCP
> response to supply a different path/file/server do the following:
> * edit /etc/config/dhcp and in the "config dnsmasq" section add
> something like
> "option dhcp_boot 'tag:se00,pxelinux.0,,172.30.42.5'"
> where 'se00' is the interface, 'pxelinux.0' the path/file, an empty
> server hostname, and IP address of the next-server.
> * run '/etc/init.d/dnsmasq restart'
> * if you are debugging and want to check that the line you added
> resulted in the changes you want, look at /var/etc/dnsmasq.conf
>
> =======================================================================
I discovered that making changes via the web ui ends up overwriting any by
hand changes to this option :( I haven't investigated why yet (or how I
might prevent that or expose this functionality via the ui).
--
Matt Taggart
matt@lackof.org
prev parent reply other threads:[~2014-10-04 23:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 22:19 Matt Taggart
2014-10-04 23:43 ` Matt Taggart [this message]
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=20141004234359.B7F101B1@taggart.lackof.org \
--to=matt@lackof.org \
--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