[Freedombox-discuss] Dev: Networking Interface Config?
- Subject: [Freedombox-discuss] Dev: Networking Interface Config?
- From: firstname.lastname@example.org (Nick Daly)
- Date: Wed, 01 Jan 2014 20:15:58 -0600
- Message-id: <[🔎] email@example.com>
- In-reply-to: <CAM-YhhDCk01L7dv7VH4_AcK8CtbEjycwnpysTNE7Vw_eVh_f5w@mail.gmail.com>
- References: <firstname.lastname@example.org> <20131217100422.GG6637@diskless.uio.no> <CAM-YhhDCk01L7dv7VH4_AcK8CtbEjycwnpysTNE7Vw_eVh_f5w@mail.gmail.com>
Nick Daly <nick.m.daly at gmail.com> writes:
> On Tue, Dec 17, 2013 at 4:04 AM, Petter Reinholdtsen <pere at hungry.com> wrote:
>> The network setup is done at first boot in
>> freedombox-setup/first-run.d/05_network, and there I was told by
>> jsullevan to use eth1, not eth0, on the dreamplug. What is correct?
I don't know that it matters which one we use, as long as we're
consistent and clear about how to use it correctly. FreedomBox-Setup
can now tell how many wired and wireless interfaces are available and
configure the networking setup appropriately (sbin/interface_detect.py
It's easy enough to get a reasonable first-boot networking configuration
in FBX-Setup, but I don't know how we should handle configuring the
network for the live system. Regardless, we should now have enough
information to be able to make those decisions .
Also, I experimented with making interface_detect as easy to understand
as possible, so I put it together in org mode and exported it a few
different ways . If you find the python script or the exported
source easier to read, please let me know.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 835 bytes
Desc: not available