[Freedombox-discuss] How to change default LAN network

Link Swanson link at mustbuild.com
Thu Jan 27 01:22:03 GMT 2022

Thank you Sunil. You provided the missing piece to my understanding. Your
explanation of how NetworkManager uses the LAN (shared interface type) to
set dnsmasq thus changing the subnet for DHCP and DNS as well was exactly
what I was looking for.

I went ahead and logged into Plinth using the WAN https entrypoint, set a
single IP address and netmask, saved the changes, deactivated the LAN
interface, activated again, and that was all I needed. All of the devices
on my LAN picked up a new lease from the new subnet and everything works

Thank you again!


On Wed, Jan 26, 2022 at 9:41 AM Sunil Mohan Adapa <sunil at medhas.org> wrote:

> On 1/26/22 05:04, Link Swanson wrote:
> > On a two-interface box with WAN + LAN interfaces, WAN having a public IP
> > from ISP, Freedombox sets up a default ipv4 IP for the LAN interface
> > with and the default DHCP server hands out leases between
> > and This is great, but I need to change it.
> >
> > How do I change the LAN subnet? Say I need it to be something like,
> > e.g., <>. What steps should I take
> > to ensure that Freedombox LAN interface IP, DHCP services, and internal
> > DNS all switch over to using the 192.168.x.x network and no longer use
> > the 10.42.x.x network?
> >
> > Can I accomplish this from within plinth? If not, which conf files do I
> > change and/or which commands do I need to run with nmcli? Is there
> > anything to consider before making such a change?
> >
> Network Manager (which FreedomBox uses for all things related to network
> configuration) selects the subnet based on IP address assigned to the
> interface. "shared" type network connections (like the LAN interface you
> have) don't usually need to be IP addresses as NM choose from the 256
> 10.42.x.x/24 subnets automatically. However, if you assign an IP address
> like, NM will select that range instead,
> which is what you want. And it will use that for IP address, DHCP and
> DNS by passing the appropriate parameters to dnsmasq. So, just set an
> IPv4 connection on that address. Of course, be sure to be connected via
> WAN while to do this change.
> If you need further tweaking (static assignments, bigger range, more
> leases) of dnsmasq behavior, then you can write a manual configuration
> file for it (to be used when NM spawns its own instance of dnsmasq). See
> the FreedomBox for Communities book[1] for an example.
> Links:
> -
> https://en.m.wikibooks.org/wiki/FreedomBox_for_Communities/Network_Configuration#Configuring_DHCP_Leases_and_Range
> --
> Sunil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/freedombox-discuss/attachments/20220126/66bc7a1b/attachment.htm>

More information about the Freedombox-discuss mailing list