#3053: Network Configuration - ifup, ifdown, bridge, ipv4-static
-------------------------+--------------------------------------------------
Reporter: qrux | Owner: bdubbs@…
Type: enhancement | Status: assigned
Priority: normal | Milestone: 7.2
Component: Bootscripts | Version: SVN
Severity: normal | Keywords: network, bridge, ifup, ifdown, ipv4,
dhcp
-------------------------+--------------------------------------------------
Comment(by qrux):
The gist is to separate out the different interface names. In the prior
version, the variable IFACE held the physical interface name, which caused
an issue with interfaces like bridge. Specifically, in a vanilla
ipv4-static setup, the user never notices the difference between the
physical link with the "logical link" because they are both named, for
example, eth0.
In bridging, though, the logical link is the bridge (e.g., br0) and not
the physical link (e.g., eth0). To resolve this, several new variables are
proposed, along with changing the name of the IFACE variable to PHYS (to
unambiguously name the physical interface). This separation has several
benefits, including the ability to properly separate logic between ifup
and the downstream services. For example, ifup can now properly set MTU on
the physical link. It's also responsible for bringing the physical link
into the UP state (and ifdown for the DOWN state). Then, each downstream
service will see its own interface variable. IPV4_IF was chosen for the
ipv4-static service, and BRIDGE_IF was chosen for the bridge service.
For maximum "ease of transition", ipv4-static has been modified to look
first for its own variable IPV4_IF; failing to find that, it will use the
first word of PHYS as the service interface; i.e., the interface to be
configured with IPv4 parameters. For non-bridge (and other tunnel-like
link) users, the impact is fairly minimal--it's simply changing IFACE in
the existing configuration files to PHYS.
For bridge (and other tunnel-like link) users, the impact is two
additional variables: BRIDGE_IF (e.g., "br0") and IPV4_IF (e.g., "br0").
This allows the bridge service to create a bridge named by BRIDGE_IF, and
allows ipv4-static to assign the IPv4 parameters to the interface named by
IPV4_IF (e.g., "br0"). This also prevents user-error when configuring
bridges by a previously confusing naming convention (disambiguating IFACE
from INTERFACES).
--
Ticket URL: <http://wiki.linuxfromscratch.org/lfs/ticket/3053#comment:2>
LFS Trac <http://wiki.linuxfromscratch.org/lfs/>
Linux From Scratch: Your Distro, Your Rules.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
