From 9818693f118659596c178e94701091d9b8ee0fc3 Mon Sep 17 00:00:00 2001 From: Darren 'Tadgy' Austin Date: Wed, 2 Dec 2020 08:44:22 +0000 Subject: Minor updates to README.networking - still a work in progress. --- README.networking | 28 ++++++++++++++++------------ 1 file changed, 16 insertions(+), 12 deletions(-) (limited to 'README.networking') diff --git a/README.networking b/README.networking index 0dfa103..bf90fec 100644 --- a/README.networking +++ b/README.networking @@ -10,8 +10,8 @@ each array index corresponding to a single network interface. This means that each set of parameters with an index of 0 configure the first interface (since indexing starts at 0), parameters with an index of 1 configure the second interface, and so on. Not all parameters need to be set for each type of -interface, or interface number. This is better illustrated with examples, which -you will find in the documentation below. +interface, or interface number. This is better illustrated with examples, +which you will find in the documentation below. Starting and Stopping Interfaces @@ -45,15 +45,15 @@ wlan0, etc). Guided Networking Configuration ------------------------------- The 'netconfig' script is capable of configuring basic networking parameters for -the first ethernet interface of the system, and writing a +the first ethernet interface of the system, and writing an annotated /etc/rc.d/rc.inet1.conf configuration file. 'netconfig' is usually invoked during installation to configure the first ethernet interface of your freshly installed system. 'netconfig' is capable of configuring a set of IPv4 and/or IPv6 addresses for an interface, or setting the interface to be configured using DHCP (both DHCPv4 and -DHCPv6) and IPv6 StateLess Address Auto Configuration (SLAAC). A default -gateway and nameservers can also be configured through the guided interface. +DHCPv6) and IPv6 StateLess Address Auto Configuration (SLAAC). The default +gateways and nameservers can also be configured through the guided interface. The option to use NetworkManager for interface configuration (instead of rc.inet1.conf) is also available. @@ -108,6 +108,11 @@ Notes: added to the interface after the IPADDR address is set. +Manual Networking Configuration +------------------------------- +FIXME + + IPv6 ---- Overview @@ -256,10 +261,6 @@ IPv6 the way dhcpcd operates, not an issue with rc.inet1. -Manual networking configuration -------------------------------- - - Bonding / Link Aggrigation -------------------------- Overview @@ -512,12 +513,15 @@ Advanced networking configuration It is also possible to use a bond as the underlying interface, which allows link aggregated VLAN interfaces to be created for network redundancy. For example: - IFNAME[0]="bond0.5" + IFNAME[0]="bond0" BONDNICS[0]="eth0 eth1" BONDMODE[0]="active-backup" IFOPTS[0]="miimon 100 | primary eth0" - IPADDRS[0]="192.168.5.10/24" - IP6ADDRS[0]="a:b:c:d::1/64" + IFNAME[1]="bond0.5" + IFNAME[2]="br0" + BRNICS[2]="bond0.5" + IPADDRS[2]="192.168.5.10/24" + IP6ADDRS[2]="a:b:c:d::1/64" Would create a bond interface using the eth0 and eth1 physical ethernet interfaces, in an "active-backup" redundancy configuration with the primary interface being "eth0", exposing VLAN ID 5 and setting an IPv4 address of -- cgit v1.2.3