1
=== modified file 'serverguide/C/network-config.xml'
2
--- serverguide/C/network-config.xml	2018-04-24 14:55:32 +0000
3
+++ serverguide/C/network-config.xml	2018-05-21 14:38:40 +0000
4
@@ -1,5 +1,5 @@
5
1
<?xml version="1.0" encoding="UTF-8"?>
1
<?xml version="1.0" encoding="UTF-8"?>
7
2
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" 
2
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
8
3
	"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
3
	"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
9
4
<!ENTITY % globalent SYSTEM "../../libs/global.ent">
4
<!ENTITY % globalent SYSTEM "../../libs/global.ent">
10
5
%globalent;
5
%globalent;
11
@@ -10,49 +10,60 @@
12
10
<chapter id="networking" status="review">
10
<chapter id="networking" status="review">
13
11
	<title>Networking</title>
11
	<title>Networking</title>
14
12
	<para>
12
	<para>
19
13
	Networks consist of two or more devices, such as computer systems, printers, 
13
	Networks consist of two or more devices, such as computer systems, printers,
20
14
	and related equipment which are connected by either physical cabling or 
14
	and related equipment which are connected by either physical cabling or
21
15
	wireless links for the purpose of sharing and distributing information among 
15
	wireless links for the purpose of sharing and distributing information among
22
16
	the connected devices. 
16
	the connected devices.
23
17
  	</para>
17
  	</para>
24
18
  	<para>
18
  	<para>
25
19
	This section provides general and specific information pertaining
19
	This section provides general and specific information pertaining
27
20
        to networking, including an overview of network concepts and detailed 
20
        to networking, including an overview of network concepts and detailed
28
21
	discussion of popular network protocols.
21
	discussion of popular network protocols.
29
22
	</para>
22
	</para>
30
23
23
31
24
	<sect1 id="network-configuration" status="review">
24
	<sect1 id="network-configuration" status="review">
32
25
	<title>Network Configuration</title>
25
	<title>Network Configuration</title>
33
26
	<para>
26
	<para>
36
27
	Ubuntu ships with a number of graphical utilities to configure your 
27
	Ubuntu ships with a number of graphical utilities to configure your
37
28
	network devices.  This document is geared toward server administrators 
28
	network devices.  This document is geared toward server administrators
38
29
	and will focus on managing your	network on the command line.
29
	and will focus on managing your	network on the command line.
39
30
    </para>
30
    </para>
40
31
31
41
32
		<sect2 id="ethernet-interfaces" status="review">
32
		<sect2 id="ethernet-interfaces" status="review">
42
33
		<title>Ethernet Interfaces</title>
33
		<title>Ethernet Interfaces</title>
43
34
		<para>
34
		<para>
50
35
		Ethernet interfaces are identified by the system using the naming convention of 
35
		Ethernet interfaces are identified by the system using predictable network
51
36
		<emphasis role="italix">ethX</emphasis>, where <emphasis role="italic">X</emphasis> 
36
		interface names. These names can appear as <emphasis role="italix">eno1</emphasis>
52
37
		represents a numeric value.  The first Ethernet interface is typically identified 
37
		or <emphasis role="italix">enp0s25</emphasis>. However, in some cases an
53
38
		as <emphasis role="italic">eth0</emphasis>, the second as 
38
		interface may still use the kernel <emphasis role="italix">eth#</emphasis>
54
39
		<emphasis role="italic">eth1</emphasis>, and all others should move up in 
39
		style of naming.
49
40
		numerical order.
55
41
		</para>
40
		</para>
56
42
41
57
43
			<sect3 id="identify-ethernet-interfaces" status="review">
42
			<sect3 id="identify-ethernet-interfaces" status="review">
58
44
			<title>Identify Ethernet Interfaces</title>
43
			<title>Identify Ethernet Interfaces</title>
59
45
			<para>
44
			<para>
62
46
			To quickly identify all available Ethernet interfaces, you can use the 
45
			To quickly identify all available Ethernet interfaces, you can use the
63
47
			<application>ifconfig</application> command as shown below.
46
			<application>ip</application> command as shown below.
64
48
			</para>
47
			</para>
65
49
<screen>
48
<screen>
68
50
<command>ifconfig -a | grep eth</command>
49
<command>ip a</command><computeroutput>
69
51
<computeroutput>eth0      Link encap:Ethernet  HWaddr 00:15:c5:4a:16:5a</computeroutput>
50
1: lo: &lt;LOOPBACK,UP,LOWER_UP&gt; mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
70
51
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
71
52
    inet 127.0.0.1/8 scope host lo
72
53
       valid_lft forever preferred_lft forever
73
54
    inet6 ::1/128 scope host
74
55
       valid_lft forever preferred_lft forever
75
56
2: enp0s25: &lt;BROADCAST,MULTICAST,UP,LOWER_UP&gt; mtu 1500 qdisc noqueue state UP group default qlen 1000
76
57
    link/ether 00:16:3e:e2:52:42 brd ff:ff:ff:ff:ff:ff link-netnsid 0
77
58
    inet 10.102.66.200/24 brd 10.102.66.255 scope global dynamic eth0
78
59
       valid_lft 3257sec preferred_lft 3257sec
79
60
    inet6 fe80::216:3eff:fee2:5242/64 scope link
80
61
       valid_lft forever preferred_lft forever</computeroutput>
81
52
</screen>
62
</screen>
82
53
			<para>
63
			<para>
85
54
			Another application that can help identify all network interfaces available to your system 
64
			Another application that can help identify all network interfaces available to your system
86
55
			is the <application>lshw</application> command.  In the example below, <application>lshw</application> 
65
			is the <application>lshw</application> command.  This command provides greater details around the
87
66
			hardware capabilities of specific adapters. In the example below, <application>lshw</application>
88
56
			shows a single Ethernet interface with the logical name of <emphasis role="italic">eth0</emphasis>
67
			shows a single Ethernet interface with the logical name of <emphasis role="italic">eth0</emphasis>
89
57
			along with bus information, driver details and all supported capabilities.
68
			along with bus information, driver details and all supported capabilities.
90
58
			</para>
69
			</para>
91
@@ -60,96 +71,78 @@
92
60
<command>sudo lshw -class network</command>
71
<command>sudo lshw -class network</command>
93
61
<computeroutput>  *-network
72
<computeroutput>  *-network
94
62
       description: Ethernet interface
73
       description: Ethernet interface
97
63
       product: BCM4401-B0 100Base-TX
74
       product: MT26448 [ConnectX EN 10GigE, PCIe 2.0 5GT/s]
98
64
       vendor: Broadcom Corporation
75
       vendor: Mellanox Technologies
99
65
       physical id: 0
76
       physical id: 0
107
66
       bus info: pci@0000:03:00.0
77
       bus info: pci@0004:01:00.0
108
67
       logical name: eth0
78
       logical name: eth4
109
68
       version: 02
79
       version: b0
110
69
       serial: 00:15:c5:4a:16:5a
80
       serial: e4:1d:2d:67:83:56
111
70
       size: 10MB/s
81
       slot: U78CB.001.WZS09KB-P1-C6-T1
112
71
       capacity: 100MB/s
82
       size: 10Gbit/s
113
72
       width: 32 bits
83
       capacity: 10Gbit/s
114
84
       width: 64 bits
115
73
       clock: 33MHz
85
       clock: 33MHz
119
74
       capabilities: (snipped for brevity)
86
       capabilities: pm vpd msix pciexpress bus_master cap_list ethernet physical fibre 10000bt-fd
120
75
       configuration: (snipped for brevity)
87
       configuration: autonegotiation=off broadcast=yes driver=mlx4_en driverversion=4.0-0 duplex=full firmware=2.9.1326 ip=192.168.1.1 latency=0 link=yes multicast=yes port=fibre speed=10Gbit/s
121
76
       resources: irq:17 memory:ef9fe000-ef9fffff</computeroutput>
88
       resources: iomemory:24000-23fff irq:481 memory:3fe200000000-3fe2000fffff memory:240000000000-240007ffffff</computeroutput>
122
77
</screen>
89
</screen>
123
78
			</sect3>
90
			</sect3>
124
79
91
125
80
			<sect3 id="ethernet-interface-names" status="review">
92
			<sect3 id="ethernet-interface-names" status="review">
126
81
			<title>Ethernet Interface Logical Names</title>
93
			<title>Ethernet Interface Logical Names</title>
127
82
			<para>
94
			<para>
134
83
			Interface logical names are configured in the file 
95
			Interface logical names can also be configured via a netplan configuration.  If you would
135
84
			<filename>/etc/udev/rules.d/70-persistent-net.rules.</filename>  If you would 
96
			like control which interface receives a particular logical name use the
136
85
			like control which interface receives a particular logical name, find the line 
97
			<emphasis role="italic">match</emphasis> and <emphasis role="italic">set-name</emphasis> keys.
137
86
			matching the interfaces physical MAC address and modify the value of 
98
			The match key is used to find an adapter based on some criteria like MAC address, driver, etc.
138
87
			<emphasis role="italic">NAME=ethX</emphasis> to the desired logical name. 
99
			Then the set-name key can be used to change the device to the desired logial name.
133
88
			Reboot the system to commit your changes.
139
89
			</para>
100
			</para>
140
90
			</sect3>
141
91
101
142
102
<screen>
143
103
<computeroutput>network:
144
104
  version: 2
145
105
  renderer: networkd
146
106
  ethernets:
147
107
    eth_lan0:
148
108
      dhcp4: true
149
109
	  match:
150
110
	    macaddress: 00:11:22:33:44:55
151
111
	  set-name: eth_lan0</computeroutput>
152
112
</screen>
153
113
</sect3>
154
92
			<sect3 id="ethernet-interface-settings" status="review">
114
			<sect3 id="ethernet-interface-settings" status="review">
155
93
			<title>Ethernet Interface Settings</title>
115
			<title>Ethernet Interface Settings</title>
156
94
			<para>
116
			<para>
166
95
			<application>ethtool</application> is a program that displays and changes Ethernet 
117
			<application>ethtool</application> is a program that displays and changes Ethernet
167
96
			card settings such as auto-negotiation, port speed, duplex mode, and Wake-on-LAN. It
118
			card settings such as auto-negotiation, port speed, duplex mode, and Wake-on-LAN.
168
97
			is not installed by default, but is available for installation in the repositories.
119
			The following is an example of how to view supported features and configured
160
98
			</para>
161
99
<screen>
162
100
<command>sudo apt install ethtool</command>
163
101
</screen>
164
102
			<para>
165
103
			The following is an example of how to view supported features and configured 
169
104
			settings of an Ethernet interface.
120
			settings of an Ethernet interface.
170
105
			</para>
121
			</para>
171
106
<screen>
122
<screen>
193
107
<command>sudo ethtool eth0</command>
123
<command>sudo ethtool eth4</command>
194
108
<computeroutput>Settings for eth0:
124
<computeroutput>Settings for eth4:
195
109
        Supported ports: [ TP ]
125
	Supported ports: [ FIBRE ]
196
110
        Supported link modes:   10baseT/Half 10baseT/Full 
126
	Supported link modes:   10000baseT/Full
197
111
                                100baseT/Half 100baseT/Full 
127
	Supported pause frame use: No
198
112
                                1000baseT/Half 1000baseT/Full 
128
	Supports auto-negotiation: No
199
113
        Supports auto-negotiation: Yes
129
	Supported FEC modes: Not reported
200
114
        Advertised link modes:  10baseT/Half 10baseT/Full 
130
	Advertised link modes:  10000baseT/Full
201
115
                                100baseT/Half 100baseT/Full 
131
	Advertised pause frame use: No
202
116
                                1000baseT/Half 1000baseT/Full 
132
	Advertised auto-negotiation: No
203
117
        Advertised auto-negotiation: Yes
133
	Advertised FEC modes: Not reported
204
118
        Speed: 1000Mb/s
134
	Speed: 10000Mb/s
205
119
        Duplex: Full
135
	Duplex: Full
206
120
        Port: Twisted Pair
136
	Port: FIBRE
207
121
        PHYAD: 1
137
	PHYAD: 0
208
122
        Transceiver: internal
138
	Transceiver: internal
209
123
        Auto-negotiation: on
139
	Auto-negotiation: off
210
124
        Supports Wake-on: g
140
	Supports Wake-on: d
211
125
        Wake-on: d
141
	Wake-on: d
212
126
        Current message level: 0x000000ff (255)
142
	Current message level: 0x00000014 (20)
213
127
        Link detected: yes</computeroutput>
143
			       link ifdown
214
144
	Link detected: yes</computeroutput>
215
128
</screen>
145
</screen>
216
129
			<para>
217
130
			Changes made with the <application>ethtool</application> command are temporary 
218
131
			and will be lost after a reboot. If you would like to retain settings, simply add 
219
132
			the desired <application>ethtool</application> command to a <emphasis role="italic">pre-up</emphasis> 
220
133
			statement in the interface configuration file <filename>/etc/network/interfaces</filename>. 
221
134
			</para>
222
135
			<para>
223
136
			The following is an example of how the interface identified as <emphasis role="italic">eth0</emphasis>
224
137
			could be permanently configured with a port speed of 1000Mb/s running in full duplex mode.
225
138
			</para>
226
139
<programlisting>
227
140
auto eth0
228
141
iface eth0 inet static
229
142
pre-up /sbin/ethtool -s eth0 speed 1000 duplex full
230
143
</programlisting>
231
144
			<note>
232
145
			<para>
233
146
			Although the example above shows the interface configured to use the 
234
147
			<emphasis role="italic">static</emphasis> method, it actually works with other 
235
148
			methods as well, such as DHCP.  The example is meant to demonstrate only proper 
236
149
			placement of the <emphasis role="italic">pre-up</emphasis> statement in relation 
237
150
			to the rest of the interface configuration.
238
151
			</para>
239
152
			</note>
240
153
			</sect3>
146
			</sect3>
241
154
		</sect2>
147
		</sect2>
242
155
148
243
@@ -164,63 +157,65 @@
244
164
			<sect3 id="temp-ip-assignment" status="review">
157
			<sect3 id="temp-ip-assignment" status="review">
245
165
			<title>Temporary IP Address Assignment</title>
158
			<title>Temporary IP Address Assignment</title>
246
166
			<para>
159
			<para>
253
167
			For temporary network configurations, you can use standard commands 
160
			For temporary network configurations, you can use the
254
168
			such as <application>ip</application>, <application>ifconfig</application> 
161
			<application>ip</application> command which is also found on most other
255
169
			and <application>route</application>, which are also found on most other 
162
			GNU/Linux operating systems.  The <application>ip</application> command
256
170
			GNU/Linux operating systems.  These commands allow you to configure settings
163
			allows you to configure settings which take effect immediately, however
257
171
			which take effect immediately, however they are not persistent and will
164
			they are not persistent and will be lost after a reboot.
252
172
			be lost after a reboot.
258
173
			</para>
165
			</para>
259
174
			<para>
166
			<para>
262
175
			To temporarily configure an IP address, you can use the <application>ifconfig</application> 
167
			To temporarily configure an IP address, you can use the <application>ip</application>
263
176
			command in the following manner. Just modify the IP address and subnet mask to match your 
168
			command in the following manner. Modify the IP address and subnet mask to match your
264
177
			network requirements.
169
			network requirements.
265
178
			</para>
170
			</para>
266
179
<screen>
171
<screen>
288
180
<command>sudo ifconfig eth0 10.0.0.100 netmask 255.255.255.0</command>
172
<command>sudo ip addr add 10.102.66.200/24 dev enp0s25</command>
289
181
</screen>
173
</screen>
290
182
			<para>
174
			<para>
291
183
			To verify the IP address configuration of <application>eth0</application>, 
175
			The <application>ip</application> can then be used to set the link up or down.
292
184
			you can use the <application>ifconfig</application> command in the following manner.
176
			</para>
293
185
			</para>
177
<screen>
294
186
<screen>
178
<command>ip link set dev enp0s25 up</command>
295
187
<command>ifconfig eth0</command>
179
<command>ip link set dev enp0s25 down</command>
296
188
<computeroutput>eth0      Link encap:Ethernet  HWaddr 00:15:c5:4a:16:5a  
180
</screen>
297
189
          inet addr:10.0.0.100  Bcast:10.0.0.255  Mask:255.255.255.0
181
			<para>
298
190
          inet6 addr: fe80::215:c5ff:fe4a:165a/64 Scope:Link
182
			To verify the IP address configuration of <application>enp0s25</application>,
299
191
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
183
			you can use the <application>ip</application> command in the following manner.
300
192
          RX packets:466475604 errors:0 dropped:0 overruns:0 frame:0
184
			</para>
301
193
          TX packets:403172654 errors:0 dropped:0 overruns:0 carrier:0
185
<screen>
302
194
          collisions:0 txqueuelen:1000 
186
<command>ip address show dev enp0s25</command>
303
195
          RX bytes:2574778386 (2.5 GB)  TX bytes:1618367329 (1.6 GB)
187
<computeroutput>10: enp0s25: &lt;BROADCAST,MULTICAST,UP,LOWER_UP&gt; mtu 1500 qdisc noqueue state UP group default qlen 1000
304
196
          Interrupt:16</computeroutput> 
188
    link/ether 00:16:3e:e2:52:42 brd ff:ff:ff:ff:ff:ff link-netnsid 0
305
197
</screen>
189
    inet 10.102.66.200/24 brd 10.102.66.255 scope global dynamic eth0
306
198
			<para>
190
       valid_lft 2857sec preferred_lft 2857sec
307
199
			To configure a default gateway, you can use the <application>route</application> 
191
    inet6 fe80::216:3eff:fee2:5242/64 scope link
308
200
			command in the following manner.  Modify the default gateway address to match 
192
       valid_lft forever preferred_lft forever6</computeroutput>
309
193
</screen>
310
194
			<para>
311
195
			To configure a default gateway, you can use the <application>ip</application>
312
196
			command in the following manner.  Modify the default gateway address to match
313
201
			your network requirements.
197
			your network requirements.
314
202
			</para>
198
			</para>
315
203
<screen>
199
<screen>
317
204
<command>sudo route add default gw 10.0.0.1 eth0</command>
200
<command>sudo ip route add default via 10.102.66.1</command>
318
205
</screen>
201
</screen>
319
206
			<para>
202
			<para>
321
207
			To verify your default gateway configuration, you can use the <application>route</application> 
203
			To verify your default gateway configuration, you can use the <application>ip</application>
322
208
			command in the following manner.
204
			command in the following manner.
323
209
			</para>
205
			</para>
324
210
<screen>
206
<screen>
330
211
<command>route -n</command>
207
<command>ip route show</command>
331
212
<computeroutput>Kernel IP routing table
208
<computeroutput>default via 10.102.66.1 dev eth0 proto dhcp src 10.102.66.200 metric 100
332
213
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
209
10.102.66.0/24 dev eth0 proto kernel scope link src 10.102.66.200
333
214
10.0.0.0        0.0.0.0         255.255.255.0   U     1      0        0 eth0
210
10.102.66.1 dev eth0 proto dhcp scope link src 10.102.66.200 metric 100 </computeroutput>
329
215
0.0.0.0         10.0.0.1        0.0.0.0         UG    0      0        0 eth0</computeroutput>
334
216
</screen>
211
</screen>
335
217
			<para>
212
			<para>
336
218
			If you require DNS for your temporary network configuration, you can add DNS server
213
			If you require DNS for your temporary network configuration, you can add DNS server
337
219
			IP addresses in the file <filename>/etc/resolv.conf</filename>. In general, editing
214
			IP addresses in the file <filename>/etc/resolv.conf</filename>. In general, editing
338
220
                        <filename>/etc/resolv.conf</filename> directly is not recommanded, but this is a
215
                        <filename>/etc/resolv.conf</filename> directly is not recommanded, but this is a
342
221
                        temporary and non-persistent configuration. The example below 
216
                        temporary and non-persistent configuration. The example below
343
222
			shows how to enter two DNS servers to <filename>/etc/resolv.conf</filename>, which 
217
			shows how to enter two DNS servers to <filename>/etc/resolv.conf</filename>, which
344
223
			should be changed to servers appropriate for your network. A more lengthy description 
218
			should be changed to servers appropriate for your network. A more lengthy description
345
224
			of the proper persistent way to do DNS client configuration is in a following section.
219
			of the proper persistent way to do DNS client configuration is in a following section.
346
225
			</para>
220
			</para>
347
226
<programlisting>
221
<programlisting>
348
@@ -230,17 +225,17 @@
349
230
			<para>
225
			<para>
350
231
			If you no longer need this configuration and wish to purge all IP configuration from
226
			If you no longer need this configuration and wish to purge all IP configuration from
351
232
			an interface, you can use the <application>ip</application> command with the flush option
227
			an interface, you can use the <application>ip</application> command with the flush option
353
233
			as shown below.  
228
			as shown below.
354
234
			</para>
229
			</para>
355
235
<screen>
230
<screen>
356
236
<command>ip addr flush eth0</command>
231
<command>ip addr flush eth0</command>
357
237
</screen>
232
</screen>
358
238
			<note>
233
			<note>
359
239
			<para>
234
			<para>
361
240
			Flushing the IP configuration using the <application>ip</application> command does not clear the 
235
			Flushing the IP configuration using the <application>ip</application> command does not clear the
362
241
			contents of <filename>/etc/resolv.conf</filename>. You must remove or modify those entries manually,
236
			contents of <filename>/etc/resolv.conf</filename>. You must remove or modify those entries manually,
365
242
                        or re-boot which should also cause <filename>/etc/resolv.conf</filename>, which is actually now a
237
                        or re-boot which should also cause <filename>/etc/resolv.conf</filename>, which is a
366
243
                        symlink to <filename>/run/resolvconf/resolv.conf</filename>, to be re-written.
238
                        symlink to <filename>/run/systemd/resolve/stub-resolv.conf</filename>, to be re-written.
367
244
			</para>
239
			</para>
368
245
			</note>
240
			</note>
369
246
			</sect3>
241
			</sect3>
370
@@ -248,65 +243,57 @@
371
248
			<sect3 id="dynamic-ip-addressing" status="review">
243
			<sect3 id="dynamic-ip-addressing" status="review">
372
249
			<title>Dynamic IP Address Assignment (DHCP Client)</title>
244
			<title>Dynamic IP Address Assignment (DHCP Client)</title>
373
250
			<para>
245
			<para>
379
251
			To configure your server to use DHCP for dynamic address assignment, add the
246
			To configure your server to use DHCP for dynamic address assignment, create a netplan
380
252
			<emphasis role="italic">dhcp</emphasis> method to the inet address family statement 
247
			configuration in the file <filename>/etc/netplan/99_config.yaml</filename>.
381
253
			for the appropriate interface in the file <filename>/etc/network/interfaces</filename>.
248
			The example below assumes you are configuring your first Ethernet interface identified as
382
254
			The example below assumes you are configuring your first Ethernet interface identified as 
249
			<emphasis role="italic">enp3s0</emphasis>.
378
255
			<emphasis role="italic">eth0</emphasis>.
383
256
			</para>
250
			</para>
384
257
<programlisting>
251
<programlisting>
387
258
auto eth0
252
network:
388
259
iface eth0 inet dhcp
253
  version: 2
389
254
  renderer: networkd
390
255
  ethernets:
391
256
    enp3s0:
392
257
      dhcp4: true
393
260
</programlisting>
258
</programlisting>
394
261
			<para>
259
			<para>
409
262
			By adding an interface configuration as shown above, you can manually enable the 
260
			The configuration can then be applied using the
410
263
			interface through the <application>ifup</application> command which initiates the 
261
			<application>netplan</application> command.
411
264
			DHCP process via <application>dhclient</application>.
262
			</para>
412
265
			</para>
263
<screen>
413
266
<screen>
264
<command>sudo netplan apply</command>
400
267
<command>sudo ifup eth0</command>
401
268
</screen>
402
269
			<para>
403
270
			To manually disable the	interface, you can use the <application>ifdown</application> 
404
271
			command, which in turn will initiate the DHCP release process and shut down the 
405
272
			interface.
406
273
			</para>
407
274
<screen>
408
275
<command>sudo ifdown eth0</command>
414
276
</screen>
265
</screen>
415
277
			</sect3>
266
			</sect3>
416
278
267
417
279
			<sect3 id="static-ip-addressing" status="review">
268
			<sect3 id="static-ip-addressing" status="review">
418
280
			<title>Static IP Address Assignment</title>
269
			<title>Static IP Address Assignment</title>
419
281
			<para>
270
			<para>
426
282
			To configure your system to use a static IP address assignment, add the 
271
			To configure your system to use static address assignment, create a netplan
427
283
			<emphasis role="italic">static</emphasis> method to the inet address family statement 
272
			configuration in the file <filename>/etc/netplan/99_config.yaml</filename>.
428
284
			for the appropriate interface in the file <filename>/etc/network/interfaces</filename>. 
273
			The example below assumes you are configuring your first Ethernet interface identified as
429
285
			The example below assumes you are configuring your first Ethernet interface identified as 
274
			<emphasis role="italic">eth0</emphasis>.  Change the <emphasis role="italic">addresses</emphasis>,
430
286
			<emphasis role="italic">eth0</emphasis>.  Change the <emphasis role="italic">address</emphasis>, 
275
			<emphasis role="italic">gateway4</emphasis>, and <emphasis role="italic">nameservers</emphasis>
425
287
			<emphasis role="italic">netmask</emphasis>, and <emphasis role="italic">gateway</emphasis> 
431
288
			values to meet the requirements of your network.
276
			values to meet the requirements of your network.
432
289
			</para>
277
			</para>
433
290
<programlisting>
278
<programlisting>
439
291
auto eth0
279
network:
440
292
iface eth0 inet static
280
  version: 2
441
293
address 10.0.0.100
281
  renderer: networkd
442
294
netmask 255.255.255.0
282
  ethernets:
443
295
gateway 10.0.0.1
283
    eth0:
444
284
      addresses:
445
285
        - 10.10.10.2/24
446
286
      gateway4: 10.10.10.1
447
287
      nameservers:
448
288
          search: [mydomain, otherdomain]
449
289
          addresses: [10.10.10.1, 1.1.1.1]
450
296
</programlisting>
290
</programlisting>
451
297
			<para>
291
			<para>
464
298
			By adding an interface configuration as shown above, you can manually enable the 
292
			The configuration can then be applied using the
465
299
			interface through the <application>ifup</application> command.
293
			<application>netplan</application> command.
466
300
			</para>
294
			</para>
467
301
<screen>
295
<screen>
468
302
<command>sudo ifup eth0</command>
296
<command>sudo netplan apply</command>
457
303
</screen>
458
304
			<para>
459
305
			To manually disable the	interface, you can use the <application>ifdown</application> 
460
306
			command.
461
307
			</para>
462
308
<screen>
463
309
<command>sudo ifdown eth0</command>
469
310
</screen>
297
</screen>
470
311
			</sect3>
298
			</sect3>
471
312
299
472
@@ -314,29 +301,17 @@
473
314
			<title>Loopback Interface</title>
301
			<title>Loopback Interface</title>
474
315
			<para>
302
			<para>
475
316
			The loopback interface is identified by the system as <emphasis role="italic">lo</emphasis>
303
			The loopback interface is identified by the system as <emphasis role="italic">lo</emphasis>
477
317
			and has a default IP address of 127.0.0.1.  It can be viewed using the ifconfig command. 
304
			and has a default IP address of 127.0.0.1.  It can be viewed using the ip command.
478
318
			</para>
305
			</para>
479
319
<screen>
306
<screen>
489
320
<command>ifconfig lo</command>
307
<command>ip address show lo</command>
490
321
<computeroutput>lo        Link encap:Local Loopback  
308
<computeroutput>1: lo: &lt;LOOPBACK,UP,LOWER_UP&gt; mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
491
322
          inet addr:127.0.0.1  Mask:255.0.0.0
309
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
492
323
          inet6 addr: ::1/128 Scope:Host
310
    inet 127.0.0.1/8 scope host lo
493
324
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
311
       valid_lft forever preferred_lft forever
494
325
          RX packets:2718 errors:0 dropped:0 overruns:0 frame:0
312
    inet6 ::1/128 scope host
495
326
          TX packets:2718 errors:0 dropped:0 overruns:0 carrier:0
313
       valid_lft forever preferred_lft forever</computeroutput>
487
327
          collisions:0 txqueuelen:0 
488
328
          RX bytes:183308 (183.3 KB)  TX bytes:183308 (183.3 KB)</computeroutput>
496
329
</screen>
314
</screen>
497
330
			<para>
498
331
			By default, there should be two lines in <filename>/etc/network/interfaces</filename> 
499
332
			responsible for automatically configuring your loopback interface. It is recommended that you 
500
333
			keep the default settings unless you have a specific purpose for changing them.  An example of 
501
334
			the two default lines are shown below.
502
335
			</para>
503
336
<programlisting>
504
337
auto lo
505
338
iface lo inet loopback
506
339
</programlisting>
507
340
			</sect3>
315
			</sect3>
508
341
		</sect2>
316
		</sect2>
509
342
317
510
@@ -344,7 +319,7 @@
511
344
		<sect2 id="name-resolution" status="review">
319
		<sect2 id="name-resolution" status="review">
512
345
		<title>Name Resolution</title>
320
		<title>Name Resolution</title>
513
346
		<para>
321
		<para>
515
347
		Name resolution as it relates to IP networking is the process of mapping IP addresses 
322
		Name resolution as it relates to IP networking is the process of mapping IP addresses
516
348
		to hostnames, making it easier to identify resources on a network.  The following section
323
		to hostnames, making it easier to identify resources on a network.  The following section
517
349
		will explain how to properly configure your system for name resolution using DNS and static
324
		will explain how to properly configure your system for name resolution using DNS and static
518
350
		hostname records.
325
		hostname records.
519
@@ -354,40 +329,38 @@
520
354
			<title>DNS Client Configuration</title>
329
			<title>DNS Client Configuration</title>
521
355
			<para>
330
			<para>
522
356
				Traditionally, the file <filename>/etc/resolv.conf</filename> was a static configuration file that rarely
331
				Traditionally, the file <filename>/etc/resolv.conf</filename> was a static configuration file that rarely
531
357
			needed to be changed or automatically changed via DCHP client hooks. Nowadays, a computer can switch from
332
			needed to be changed or automatically changed via DCHP client hooks. Systemd-resolved handles name server configuration,
532
358
			one network to another quite often and the <emphasis>resolvconf</emphasis> framework is now being used to track
333
			and it should be interacted with through the <command>systemd-resolve</command> command. Netplan configures
533
359
			these changes and update the resolver's configuration automatically.  It acts as an intermediary between programs
334
			systemd-resolved to generate a list of nameservers and domains to put in <filename>/etc/resolv.conf</filename>, which is a symlink:
526
360
			that supply nameserver information and applications that need nameserver information. Resolvconf gets populated with information
527
361
			by a set of hook scripts related to network interface configuration. The most notable difference for the
528
362
			user is that any change manually done to <filename>/etc/resolv.conf</filename> will be lost as it gets overwritten each time
529
363
			something triggers resolvconf. Instead, resolvconf uses DHCP client hooks, and <filename>/etc/network/interfaces</filename> to
530
364
			generate a list of nameservers and domains to put in <filename>/etc/resolv.conf</filename>, which is now a symlink:
534
365
335
535
366
<programlisting>
336
<programlisting>
537
367
/etc/resolv.conf -> ../run/resolvconf/resolv.conf
337
/etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf
538
368
</programlisting>
338
</programlisting>
539
369
339
540
370
			To configure the resolver, add the IP addresses of the nameservers that
340
			To configure the resolver, add the IP addresses of the nameservers that
545
371
			are appropriate for your network in the file <filename>/etc/network/interfaces</filename>. You can also
341
			are appropriate for your network to the netplan configuration file. You can also
546
372
			add an optional DNS suffix search-lists to match your network domain names. For each other valid
342
			add an optional DNS suffix search-lists to match your network domain names. The resulting file might look like the following:
543
373
			resolv.conf configuration option, you can include, in the stanza, one line beginning with that
544
374
			option name with a <emphasis role="bold">dns-</emphasis> prefix. The resulting file might look like the following:
547
375
			</para>
343
			</para>
548
376
344
549
377
<programlisting>
345
<programlisting>
556
378
iface eth0 inet static
346
network:
557
379
    address 192.168.3.3
347
  version: 2
558
380
    netmask 255.255.255.0
348
  renderer: networkd
559
381
    gateway 192.168.3.1
349
  ethernets:
560
382
    dns-search example.com
350
    enp0s25:
561
383
    dns-nameservers 192.168.3.45 192.168.8.10
351
      addresses:
562
352
        - 192.168.0.100/24
563
353
      gateway4: 192.168.0.1
564
354
      nameservers:
565
355
          search: [mydomain, otherdomain]
566
356
          addresses: [1.1.1.1, 8.8.8.8, 4.4.4.4]
567
384
</programlisting>
357
</programlisting>
568
385
358
569
386
			<para>
359
			<para>
572
387
			The <emphasis role="italic">search</emphasis> option can also be used with multiple domain names 
360
			The <emphasis role="italic">search</emphasis> option can also be used with multiple domain names
573
388
			so that DNS queries will be appended in the order in which they are entered. For example, your 
361
			so that DNS queries will be appended in the order in which they are entered. For example, your
574
389
			network may have multiple sub-domains to search; a parent domain of <emphasis role="italic">example.com</emphasis>,
362
			network may have multiple sub-domains to search; a parent domain of <emphasis role="italic">example.com</emphasis>,
576
390
			and two sub-domains, <emphasis role="italic">sales.example.com</emphasis> and <emphasis role="italic">dev.example.com</emphasis>.  
363
			and two sub-domains, <emphasis role="italic">sales.example.com</emphasis> and <emphasis role="italic">dev.example.com</emphasis>.
577
391
			</para>
364
			</para>
578
392
365
579
393
			<para>
366
			<para>
580
@@ -395,16 +368,21 @@
581
395
			</para>
368
			</para>
582
396
369
583
397
<programlisting>
370
<programlisting>
590
398
iface eth0 inet static
371
network:
591
399
    address 192.168.3.3
372
  version: 2
592
400
    netmask 255.255.255.0
373
  renderer: networkd
593
401
    gateway 192.168.3.1
374
  ethernets:
594
402
    dns-search example.com sales.example.com dev.example.com
375
    enp0s25:
595
403
    dns-nameservers 192.168.3.45 192.168.8.10
376
      addresses:
596
377
        - 192.168.0.100/24
597
378
      gateway4: 192.168.0.1
598
379
      nameservers:
599
380
          search: [example.com, sales.example.com, dev.example.com]
600
381
          addresses: [1.1.1.1, 8.8.8.8, 4.4.4.4]
601
404
</programlisting>
382
</programlisting>
602
405
383
603
406
			<para>
384
			<para>
605
407
			If you try to ping a host with the name of <emphasis role="italic">server1</emphasis>, your system 
385
			If you try to ping a host with the name of <emphasis role="italic">server1</emphasis>, your system
606
408
			will automatically query DNS for its Fully Qualified Domain Name (FQDN) in the following order:
386
			will automatically query DNS for its Fully Qualified Domain Name (FQDN) in the following order:
607
409
			</para>
387
			</para>
608
410
388
609
@@ -426,7 +404,7 @@
610
426
			</listitem>
404
			</listitem>
611
427
			</orderedlist>
405
			</orderedlist>
612
428
			<para>
406
			<para>
614
429
			If no matches are found, the DNS server will provide a result of 
407
			If no matches are found, the DNS server will provide a result of
615
430
			<emphasis role="italic">notfound</emphasis> and the DNS query will fail.
408
			<emphasis role="italic">notfound</emphasis> and the DNS query will fail.
616
431
			</para>
409
			</para>
617
432
			</sect3>
410
			</sect3>
618
@@ -437,11 +415,11 @@
619
437
			Static hostnames are locally defined hostname-to-IP mappings located in the file <filename>/etc/hosts</filename>.
415
			Static hostnames are locally defined hostname-to-IP mappings located in the file <filename>/etc/hosts</filename>.
620
438
			Entries in the <filename>hosts</filename> file will have precedence over DNS by default. This means that if your
416
			Entries in the <filename>hosts</filename> file will have precedence over DNS by default. This means that if your
621
439
			system tries to resolve a hostname and it matches an entry in /etc/hosts, it will not attempt to look up the
417
			system tries to resolve a hostname and it matches an entry in /etc/hosts, it will not attempt to look up the
623
440
			record in DNS.  In some configurations, especially when Internet access is not required, servers that 
418
			record in DNS.  In some configurations, especially when Internet access is not required, servers that
624
441
			communicate with a limited number of resources can be conveniently set to use static hostnames instead of DNS.
419
			communicate with a limited number of resources can be conveniently set to use static hostnames instead of DNS.
625
442
			</para>
420
			</para>
626
443
			<para>
421
			<para>
628
444
			The following is an example of a <filename>hosts</filename> file where a number of local servers 
422
			The following is an example of a <filename>hosts</filename> file where a number of local servers
629
445
			have been identified by simple hostnames, aliases and their equivalent Fully Qualified Domain Names (FQDN's).
423
			have been identified by simple hostnames, aliases and their equivalent Fully Qualified Domain Names (FQDN's).
630
446
			</para>
424
			</para>
631
447
<programlisting>
425
<programlisting>
632
@@ -454,11 +432,11 @@
633
454
</programlisting>
432
</programlisting>
634
455
			<note>
433
			<note>
635
456
			<para>
434
			<para>
641
457
			In the above example, notice that each of the servers have been given aliases in addition to their 
435
			In the above example, notice that each of the servers have been given aliases in addition to their
642
458
			proper names and FQDN's. <emphasis role="italic">Server1</emphasis> has been mapped to the name 
436
			proper names and FQDN's. <emphasis role="italic">Server1</emphasis> has been mapped to the name
643
459
			<emphasis role="italic">vpn</emphasis>, <emphasis role="italic">server2</emphasis> is referred 
437
			<emphasis role="italic">vpn</emphasis>, <emphasis role="italic">server2</emphasis> is referred
644
460
			to as <emphasis role="italic">mail</emphasis>, <emphasis role="italic">server3</emphasis> as 
438
			to as <emphasis role="italic">mail</emphasis>, <emphasis role="italic">server3</emphasis> as
645
461
			<emphasis role="italic">www</emphasis>, and <emphasis role="italic">server4</emphasis> as 
439
			<emphasis role="italic">www</emphasis>, and <emphasis role="italic">server4</emphasis> as
646
462
			<emphasis role="italic">file</emphasis>.
440
			<emphasis role="italic">file</emphasis>.
647
463
			</para>
441
			</para>
648
464
			</note>
442
			</note>
649
@@ -469,9 +447,9 @@
650
469
			<para>
447
			<para>
651
470
			The order in which your system selects a method of resolving hostnames to IP addresses is
448
			The order in which your system selects a method of resolving hostnames to IP addresses is
652
471
			controlled by the Name Service Switch (NSS) configuration file <filename>/etc/nsswitch.conf</filename>.
449
			controlled by the Name Service Switch (NSS) configuration file <filename>/etc/nsswitch.conf</filename>.
656
472
			As mentioned in the previous section, typically static hostnames defined in the systems 
450
			As mentioned in the previous section, typically static hostnames defined in the systems
657
473
			<filename>/etc/hosts</filename> file have precedence over names resolved from DNS. The following 
451
			<filename>/etc/hosts</filename> file have precedence over names resolved from DNS. The following
658
474
			is an example of the line responsible for this order of hostname lookups in the file 
452
			is an example of the line responsible for this order of hostname lookups in the file
659
475
			<filename>/etc/nsswitch.conf</filename>.
453
			<filename>/etc/nsswitch.conf</filename>.
660
476
			</para>
454
			</para>
661
477
<programlisting>
455
<programlisting>
662
@@ -481,7 +459,7 @@
663
481
			<itemizedlist>
459
			<itemizedlist>
664
482
			<listitem>
460
			<listitem>
665
483
			<para>
461
			<para>
667
484
			<emphasis role="bold">files</emphasis> first tries to resolve static hostnames located in 
462
			<emphasis role="bold">files</emphasis> first tries to resolve static hostnames located in
668
485
			<filename>/etc/hosts</filename>.
463
			<filename>/etc/hosts</filename>.
669
486
			</para>
464
			</para>
670
487
			</listitem>
465
			</listitem>
671
@@ -492,9 +470,9 @@
672
492
			</listitem>
470
			</listitem>
673
493
			<listitem>
471
			<listitem>
674
494
			<para>
472
			<para>
678
495
			<emphasis role="bold">[NOTFOUND=return]</emphasis> means that any response of 
473
			<emphasis role="bold">[NOTFOUND=return]</emphasis> means that any response of
679
496
			<emphasis role="italic">notfound</emphasis> by the preceding 
474
			<emphasis role="italic">notfound</emphasis> by the preceding
680
497
			<emphasis role="italic">mdns4_minimal</emphasis> process should be treated as 
475
			<emphasis role="italic">mdns4_minimal</emphasis> process should be treated as
681
498
			authoritative and that the system should not try to continue hunting for an answer.
476
			authoritative and that the system should not try to continue hunting for an answer.
682
499
			</para>
477
			</para>
683
500
			</listitem>
478
			</listitem>
684
@@ -512,9 +490,9 @@
685
512
490
686
513
			<para>
491
			<para>
687
514
			To modify the order of the above mentioned name resolution methods, you can
492
			To modify the order of the above mentioned name resolution methods, you can
691
515
			simply change the <emphasis role="italic">hosts:</emphasis> string to the value 
493
			simply change the <emphasis role="italic">hosts:</emphasis> string to the value
692
516
			of your choosing. For example, if you prefer to use legacy Unicast DNS versus 
494
			of your choosing. For example, if you prefer to use legacy Unicast DNS versus
693
517
			Multicast DNS, you can change the string in <filename>/etc/nsswitch.conf</filename> 
495
			Multicast DNS, you can change the string in <filename>/etc/nsswitch.conf</filename>
694
518
			as shown below.
496
			as shown below.
695
519
			</para>
497
			</para>
696
520
<programlisting>
498
<programlisting>
697
@@ -527,41 +505,26 @@
698
527
      <title>Bridging</title>
505
      <title>Bridging</title>
699
528
506
700
529
      <para>
507
      <para>
702
530
      Bridging multiple interfaces is a more advanced configuration, but is very useful in multiple scenarios.  
508
      Bridging multiple interfaces is a more advanced configuration, but is very useful in multiple scenarios.
703
531
      One scenario is setting up a bridge with multiple network interfaces, then using a firewall to filter traffic
509
      One scenario is setting up a bridge with multiple network interfaces, then using a firewall to filter traffic
704
532
      between two network segments.  Another scenario is using bridge on a system with one interface to allow virtual
510
      between two network segments.  Another scenario is using bridge on a system with one interface to allow virtual
705
533
      machines direct access to the outside network.  The following example covers the latter scenario.
511
      machines direct access to the outside network.  The following example covers the latter scenario.
706
534
      </para>
512
      </para>
707
535
513
708
536
      <para>
514
      <para>
719
537
      Before configuring a bridge you will need to install the <application>bridge-utils</application> package.  To install the 
515
      Configure the bridge by editing your netplan configuration found
720
538
      package, in a terminal enter:
516
	  in <filename>/etc/netplan/</filename>:
711
539
      </para>
712
540
713
541
<screen>
714
542
<command>sudo apt install bridge-utils</command>
715
543
</screen>
716
544
717
545
      <para>
718
546
      Next, configure the bridge by editing <filename>/etc/network/interfaces</filename>:
721
547
      </para>
517
      </para>
722
548
518
723
549
<programlisting>
519
<programlisting>
739
550
auto lo
520
network:
740
551
iface lo inet loopback
521
  version: 2
741
552
522
  renderer: networkd
742
553
auto br0
523
  bridges:
743
554
iface br0 inet static
524
    br0:
744
555
        address 192.168.0.10
525
      dhcp4: yes
745
556
        network 192.168.0.0
526
      interfaces:
746
557
        netmask 255.255.255.0
527
        - enp3s0
732
558
        broadcast 192.168.0.255
733
559
        gateway 192.168.0.1
734
560
        bridge_ports eth0
735
561
        bridge_fd 9
736
562
        bridge_hello 2
737
563
        bridge_maxage 12
738
564
        bridge_stp off
747
565
</programlisting>
528
</programlisting>
748
566
529
749
567
      <note>
530
      <note>
750
@@ -571,63 +534,60 @@
751
571
      </note>
534
      </note>
752
572
535
753
573
      <para>
536
      <para>
755
574
      Now bring up the bridge:
537
      Now apply the configuration to enable the bridge:
756
575
      </para>
538
      </para>
757
576
539
758
577
<screen>
540
<screen>
760
578
<command>sudo ifup br0</command>
541
<command>sudo netplan apply</command>
761
579
</screen>
542
</screen>
762
580
        <para>
543
        <para>
763
581
        The new bridge interface should now be up and running.  The <application>brctl</application> provides useful information
544
        The new bridge interface should now be up and running.  The <application>brctl</application> provides useful information
766
582
        about the state of the bridge, controls which interfaces are part of the bridge, etc.  See <command>man brctl</command> 
545
        about the state of the bridge, controls which interfaces are part of the bridge, etc.  See <command>man brctl</command>
767
583
        for more information.        
546
        for more information.
768
584
        </para>
547
        </para>
769
585
548
770
586
      </sect2>
549
      </sect2>
771
587
      <sect2 id="network-config-resources" status="review">
550
      <sect2 id="network-config-resources" status="review">
772
588
        <title>Resources</title>
551
        <title>Resources</title>
774
589
    
552
775
590
        <para>
553
        <para>
777
591
        
554
778
592
        </para>
555
        </para>
779
593
556
780
594
        <itemizedlist>
557
        <itemizedlist>
781
595
          <listitem>
558
          <listitem>
782
596
            <para>
559
            <para>
784
597
            The <ulink url="https://help.ubuntu.com/community/Network">Ubuntu Wiki Network page</ulink> has 
560
            The <ulink url="https://help.ubuntu.com/community/Network">Ubuntu Wiki Network page</ulink> has
785
598
            links to articles covering more advanced network configuration.
561
            links to articles covering more advanced network configuration.
786
599
            </para>
562
            </para>
787
600
          </listitem>
563
          </listitem>
788
601
          <listitem>
564
          <listitem>
789
602
            <para>
565
            <para>
818
603
            The <ulink url="http://manpages.ubuntu.com/manpages/man8/resolvconf.8.html">resolvconf man page</ulink> has 
566
            The <ulink url="https://netplan.io">netplan website</ulink> has additional examples and documentation.
819
604
            more information on resolvconf.
567
            </para>
820
605
            </para>
568
          </listitem>
821
606
          </listitem>
569
          <listitem>
822
607
          <listitem>
570
            <para>
823
608
            <para>
571
            The <ulink url="http://manpages.ubuntu.com/manpages/man8/netplan.8.html">netplan man page</ulink> has
824
609
            The <ulink url="http://manpages.ubuntu.com/manpages/man5/interfaces.5.html">interfaces man page</ulink> has 
572
            more information on netplan.
825
610
            details on more options for <filename>/etc/network/interfaces</filename>.
573
            </para>
826
611
            </para>
574
          </listitem>
827
612
          </listitem>
575
          <listitem>
828
613
          <listitem>
576
            <para>
829
614
            <para>
577
            The <ulink url="http://manpages.ubuntu.com/manpages/man1/systemd-resolve.1.html">systemd-resolve man page</ulink> has
830
615
            The <ulink url="http://manpages.ubuntu.com/manpages/man8/dhclient.8.html">dhclient man page</ulink> has 
578
            details on systemd-resolve command.
831
616
            details on more options for configuring DHCP client settings.
579
            </para>
832
617
            </para>
580
          </listitem>
833
618
          </listitem>
581
          <listitem>
834
619
          <listitem>
582
            <para>
835
620
            <para>
583
            The <ulink url="http://manpages.ubuntu.com/manpages/man8/systemd-resolved.8.html">systemd-resolved man page</ulink> has
836
621
            For more information on DNS client configuration see the 
584
            more information on systemd-resolved service.
837
622
            <ulink url="http://manpages.ubuntu.com/manpages/man5/resolver.5.html">resolver man page</ulink>.  Also, Chapter 
585
            </para>
838
623
            6 of O'Reilly's <ulink url="http://oreilly.com/catalog/linag2/book/ch06.html">Linux Network Administrator's Guide</ulink> is 
586
          </listitem>
839
624
            a good source of resolver and name service configuration information.
587
          <listitem>
840
625
            </para>
588
            <para>
841
626
          </listitem>
589
            For more information on <emphasis>bridging</emphasis> see the
842
627
          <listitem>
590
            <ulink url="https://netplan.io/examples">netplan.io examples page</ulink> and the Linux Foundation's
815
628
            <para>
816
629
            For more information on <emphasis>bridging</emphasis> see the 
817
630
            <ulink url="http://manpages.ubuntu.com/manpages/man8/brctl.8.html">brctl man page</ulink> and the Linux Foundation's
843
631
            <ulink url="http://www.linuxfoundation.org/collaborate/workgroups/networking/bridge">Networking-Bridge</ulink> page.
591
            <ulink url="http://www.linuxfoundation.org/collaborate/workgroups/networking/bridge">Networking-Bridge</ulink> page.
844
632
            </para>
592
            </para>
845
633
          </listitem>
593
          </listitem>
846
@@ -638,34 +598,34 @@
847
638
	<sect1 id="tcpip" status="review">
598
	<sect1 id="tcpip" status="review">
848
639
		<title>TCP/IP</title>
599
		<title>TCP/IP</title>
849
640
          <para>
600
          <para>
855
641
            The Transmission Control Protocol and Internet Protocol (TCP/IP) is a standard 
601
            The Transmission Control Protocol and Internet Protocol (TCP/IP) is a standard
856
642
			set of protocols developed in the late 1970s by the Defense Advanced Research 
602
			set of protocols developed in the late 1970s by the Defense Advanced Research
857
643
			Projects Agency (DARPA) as a means of communication between different types of 
603
			Projects Agency (DARPA) as a means of communication between different types of
858
644
			computers and computer networks. TCP/IP is the driving force of the Internet, 
604
			computers and computer networks. TCP/IP is the driving force of the Internet,
859
645
			and thus it is the most popular set of network protocols on Earth. 
605
			and thus it is the most popular set of network protocols on Earth.
860
646
          </para>
606
          </para>
861
647
      <sect2 id="tcpip-introduction" status="review">
607
      <sect2 id="tcpip-introduction" status="review">
863
648
        <title>TCP/IP Introduction</title> 
608
        <title>TCP/IP Introduction</title>
864
649
          <para>
609
          <para>
865
650
            The two protocol components of TCP/IP deal with different aspects of computer networking.
610
            The two protocol components of TCP/IP deal with different aspects of computer networking.
869
651
            <emphasis>Internet Protocol</emphasis>, the "IP" of TCP/IP is a 
611
            <emphasis>Internet Protocol</emphasis>, the "IP" of TCP/IP is a
870
652
			connectionless protocol which deals only with network packet routing using the <emphasis 
612
			connectionless protocol which deals only with network packet routing using the <emphasis
871
653
			role="italics">IP Datagram</emphasis> as the basic unit of networking information.  The 
613
			role="italics">IP Datagram</emphasis> as the basic unit of networking information.  The
872
654
			IP Datagram consists of a header followed by a message.  The <emphasis>
614
			IP Datagram consists of a header followed by a message.  The <emphasis>
876
655
			Transmission Control Protocol</emphasis> is the "TCP" of TCP/IP and enables network hosts 
615
			Transmission Control Protocol</emphasis> is the "TCP" of TCP/IP and enables network hosts
877
656
			to establish connections which may be used to exchange data streams.  TCP also guarantees 
616
			to establish connections which may be used to exchange data streams.  TCP also guarantees
878
657
			that the data between connections is delivered and that it arrives at one network host in 
617
			that the data between connections is delivered and that it arrives at one network host in
879
658
			the same order as sent from another network host.
618
			the same order as sent from another network host.
880
659
          </para>
619
          </para>
881
660
          </sect2>
620
          </sect2>
882
661
        <sect2 id="tcpip-configuration" status="review">
621
        <sect2 id="tcpip-configuration" status="review">
883
662
          <title>TCP/IP Configuration</title>
622
          <title>TCP/IP Configuration</title>
884
663
            <para>
623
            <para>
890
664
            The TCP/IP protocol configuration consists of several elements which must be set by 
624
            The TCP/IP protocol configuration consists of several elements which must be set by
891
665
			editing the appropriate configuration files, or deploying solutions such as the Dynamic 
625
			editing the appropriate configuration files, or deploying solutions such as the Dynamic
892
666
			Host Configuration Protocol (DHCP) server which in turn, can be configured to provide the 
626
			Host Configuration Protocol (DHCP) server which in turn, can be configured to provide the
893
667
			proper TCP/IP configuration settings to network clients automatically. These 
627
			proper TCP/IP configuration settings to network clients automatically. These
894
668
			configuration values must be set correctly in order to facilitate the proper network 
628
			configuration values must be set correctly in order to facilitate the proper network
895
669
			operation of your Ubuntu system.
629
			operation of your Ubuntu system.
896
670
            </para>
630
            </para>
897
671
            <para>
631
            <para>
898
@@ -697,7 +657,7 @@
899
697
                  <emphasis role="bold">Network Address</emphasis> The Network Address represents the
657
                  <emphasis role="bold">Network Address</emphasis> The Network Address represents the
900
698
                  bytes comprising the network portion of an IP address.  For example, the host 12.128.1.2
658
                  bytes comprising the network portion of an IP address.  For example, the host 12.128.1.2
901
699
                  in a Class A network would use 12.0.0.0 as the network address, where twelve (12)
659
                  in a Class A network would use 12.0.0.0 as the network address, where twelve (12)
903
700
                  represents the first byte of the IP address, (the network part) and zeroes (0) 
660
                  represents the first byte of the IP address, (the network part) and zeroes (0)
904
701
                  in all of the remaining three bytes to represent the potential host values.  A network
661
                  in all of the remaining three bytes to represent the potential host values.  A network
905
702
                  host using the private IP address 192.168.1.100
662
                  host using the private IP address 192.168.1.100
906
703
                  would in turn use a Network Address of 192.168.1.0, which specifies the first three
663
                  would in turn use a Network Address of 192.168.1.0, which specifies the first three
907
@@ -714,28 +674,28 @@
908
714
                  every host on the Internet because routers block it.  A more appropriate broadcast address
674
                  every host on the Internet because routers block it.  A more appropriate broadcast address
909
715
                  is set to match a specific subnetwork.  For example, on the private Class C IP network,
675
                  is set to match a specific subnetwork.  For example, on the private Class C IP network,
910
716
                  192.168.1.0, the broadcast address is 192.168.1.255. Broadcast messages are
676
                  192.168.1.0, the broadcast address is 192.168.1.255. Broadcast messages are
913
717
                  typically produced by network protocols such as the Address Resolution Protocol (ARP) and the 
677
                  typically produced by network protocols such as the Address Resolution Protocol (ARP) and the
914
718
                  Routing Information Protocol (RIP).             
678
                  Routing Information Protocol (RIP).
915
719
                  </para>
679
                  </para>
916
720
               </listitem>
680
               </listitem>
917
721
               <listitem>
681
               <listitem>
918
722
                  <para>
682
                  <para>
919
723
                  <emphasis role="bold">Gateway Address</emphasis> A Gateway Address is the IP address through which
683
                  <emphasis role="bold">Gateway Address</emphasis> A Gateway Address is the IP address through which
920
724
                  a particular network, or host on a network, may be reached.  If one network host wishes to communicate
684
                  a particular network, or host on a network, may be reached.  If one network host wishes to communicate
922
725
                  with another network host, and that host is not located on the same network, then a 
685
                  with another network host, and that host is not located on the same network, then a
923
726
                  <emphasis>gateway</emphasis> must be used. In many cases, the Gateway Address will be that
686
                  <emphasis>gateway</emphasis> must be used. In many cases, the Gateway Address will be that
924
727
                  of a router on the same network, which will in turn pass traffic on to other networks or hosts, such as
687
                  of a router on the same network, which will in turn pass traffic on to other networks or hosts, such as
925
728
                  Internet hosts.  The value of the Gateway Address setting must be correct, or your system will not be able
688
                  Internet hosts.  The value of the Gateway Address setting must be correct, or your system will not be able
927
729
                  to reach any hosts beyond those on the same network.                  
689
                  to reach any hosts beyond those on the same network.
928
730
                  </para>
690
                  </para>
929
731
               </listitem>
691
               </listitem>
930
732
               <listitem>
692
               <listitem>
931
733
                  <para>
693
                  <para>
932
734
                  <emphasis role="bold">Nameserver Address</emphasis> Nameserver Addresses represent the IP addresses of
694
                  <emphasis role="bold">Nameserver Address</emphasis> Nameserver Addresses represent the IP addresses of
933
735
                  Domain Name Service (DNS) systems, which resolve network hostnames into IP addresses.  There are three levels of
695
                  Domain Name Service (DNS) systems, which resolve network hostnames into IP addresses.  There are three levels of
935
736
                  Nameserver Addresses, which may be specified in order of precedence: The 
696
                  Nameserver Addresses, which may be specified in order of precedence: The
936
737
                  <emphasis>Primary</emphasis>
697
                  <emphasis>Primary</emphasis>
938
738
                  Nameserver, the <emphasis>Secondary</emphasis> Nameserver, and the 
698
                  Nameserver, the <emphasis>Secondary</emphasis> Nameserver, and the
939
739
                  <emphasis>Tertiary</emphasis>
699
                  <emphasis>Tertiary</emphasis>
940
740
                  Nameserver. In order for your system to be able to resolve network hostnames into their
700
                  Nameserver. In order for your system to be able to resolve network hostnames into their
941
741
                  corresponding IP addresses, you must specify valid Nameserver Addresses which you are authorized to use
701
                  corresponding IP addresses, you must specify valid Nameserver Addresses which you are authorized to use
942
@@ -771,18 +731,18 @@
943
771
              to direct the forwarding of network data packets from their source to the destination, often
731
              to direct the forwarding of network data packets from their source to the destination, often
944
772
              via many intermediary network nodes known as <emphasis>routers</emphasis>.
732
              via many intermediary network nodes known as <emphasis>routers</emphasis>.
945
773
              There are two primary forms of
733
              There are two primary forms of
947
774
              IP routing: <emphasis>Static Routing</emphasis> and 
734
              IP routing: <emphasis>Static Routing</emphasis> and
948
775
              <emphasis>Dynamic Routing.</emphasis>
735
              <emphasis>Dynamic Routing.</emphasis>
949
776
            </para>
736
            </para>
950
777
            <para>
737
            <para>
951
778
            Static routing involves manually adding IP routes to the system's routing table, and this is usually
738
            Static routing involves manually adding IP routes to the system's routing table, and this is usually
952
779
            done by manipulating the routing table with the <application>route</application> command. Static routing enjoys
739
            done by manipulating the routing table with the <application>route</application> command. Static routing enjoys
955
780
            many advantages over dynamic routing, such as simplicity of implementation on smaller networks, 
740
            many advantages over dynamic routing, such as simplicity of implementation on smaller networks,
956
781
            predictability (the routing table is always computed in advance, and thus the route is precisely the 
741
            predictability (the routing table is always computed in advance, and thus the route is precisely the
957
782
            same each time it is used), and low overhead on other routers and network links due to the lack of a
742
            same each time it is used), and low overhead on other routers and network links due to the lack of a
958
783
            dynamic routing protocol.  However, static routing does present some disadvantages as well.  For example,
743
            dynamic routing protocol.  However, static routing does present some disadvantages as well.  For example,
959
784
            static routing is limited to small networks and does not scale well.  Static routing also fails completely
744
            static routing is limited to small networks and does not scale well.  Static routing also fails completely
961
785
            to adapt to network outages and failures along the route due to the fixed nature of the route. 
745
            to adapt to network outages and failures along the route due to the fixed nature of the route.
962
786
            </para>
746
            </para>
963
787
            <para>
747
            <para>
964
788
            Dynamic routing depends on large networks with multiple possible IP routes from a source to a destination
748
            Dynamic routing depends on large networks with multiple possible IP routes from a source to a destination
965
@@ -805,7 +765,7 @@
966
805
              determines when the flow of a data stream needs to be stopped, and previously sent data
765
              determines when the flow of a data stream needs to be stopped, and previously sent data
967
806
              packets should to be re-sent due to problems such as <emphasis>collisions</emphasis>,
766
              packets should to be re-sent due to problems such as <emphasis>collisions</emphasis>,
968
807
              for example, thus ensuring complete and accurate delivery of the data.  TCP is typically
767
              for example, thus ensuring complete and accurate delivery of the data.  TCP is typically
970
808
              used in the exchange of important information such as database transactions. 
768
              used in the exchange of important information such as database transactions.
971
809
            </para>
769
            </para>
972
810
            <para>
770
            <para>
973
811
              The User Datagram Protocol (UDP), on the other hand, is a <emphasis>connectionless</emphasis>
771
              The User Datagram Protocol (UDP), on the other hand, is a <emphasis>connectionless</emphasis>
974
@@ -823,7 +783,7 @@
975
823
              in the Request For Comments (RFC) #792 and supports network packets containing control, error, and
783
              in the Request For Comments (RFC) #792 and supports network packets containing control, error, and
976
824
              informational messages.  ICMP is used by such network applications as the <application>ping</application>
784
              informational messages.  ICMP is used by such network applications as the <application>ping</application>
977
825
              utility, which can determine the availability of a network host or device.  Examples of some error messages
785
              utility, which can determine the availability of a network host or device.  Examples of some error messages
979
826
              returned by ICMP which are useful to both network hosts and devices such as routers, include 
786
              returned by ICMP which are useful to both network hosts and devices such as routers, include
980
827
              <emphasis>Destination Unreachable</emphasis> and <emphasis>Time Exceeded</emphasis>.
787
              <emphasis>Destination Unreachable</emphasis> and <emphasis>Time Exceeded</emphasis>.
981
828
            </para>
788
            </para>
982
829
        </sect2>
789
        </sect2>
983
@@ -833,9 +793,9 @@
984
833
              Daemons are special system applications which typically execute continuously in the background and
793
              Daemons are special system applications which typically execute continuously in the background and
985
834
              await requests for the functions they provide from other applications.  Many daemons are network-centric; that is,
794
              await requests for the functions they provide from other applications.  Many daemons are network-centric; that is,
986
835
              a large number of daemons executing in the background on an Ubuntu system may provide network-related functionality.
795
              a large number of daemons executing in the background on an Ubuntu system may provide network-related functionality.
988
836
              Some examples of such network daemons include the <emphasis>Hyper Text Transport Protocol Daemon</emphasis> 
796
              Some examples of such network daemons include the <emphasis>Hyper Text Transport Protocol Daemon</emphasis>
989
837
              (httpd), which provides web server functionality; the <emphasis>Secure SHell Daemon</emphasis> (sshd), which
797
              (httpd), which provides web server functionality; the <emphasis>Secure SHell Daemon</emphasis> (sshd), which
991
838
              provides secure remote login shell and file transfer capabilities; and the <emphasis>Internet Message Access 
798
              provides secure remote login shell and file transfer capabilities; and the <emphasis>Internet Message Access
992
839
              Protocol Daemon</emphasis> (imapd), which provides E-Mail services.
799
              Protocol Daemon</emphasis> (imapd), which provides E-Mail services.
993
840
            </para>
800
            </para>
994
841
        </sect2>
801
        </sect2>
995
@@ -867,10 +827,10 @@
996
867
	<sect1 id="dhcp" status="review">
827
	<sect1 id="dhcp" status="review">
997
868
		<title>Dynamic Host Configuration Protocol (DHCP)</title>
828
		<title>Dynamic Host Configuration Protocol (DHCP)</title>
998
869
            <para>
829
            <para>
1000
870
	    The Dynamic Host Configuration Protocol (DHCP) is a network service that enables 
830
	    The Dynamic Host Configuration Protocol (DHCP) is a network service that enables
1001
871
	    host computers to be automatically assigned settings from a server as opposed to
831
	    host computers to be automatically assigned settings from a server as opposed to
1002
872
            manually configuring each network host. Computers configured to be DHCP clients have
832
            manually configuring each network host. Computers configured to be DHCP clients have
1004
873
            no control over the settings they receive from the DHCP server, and the 
833
            no control over the settings they receive from the DHCP server, and the
1005
874
	    configuration is transparent to the computer's user.
834
	    configuration is transparent to the computer's user.
1006
875
	    </para>
835
	    </para>
1007
876
            <para>
836
            <para>
1008
@@ -908,8 +868,8 @@
1009
908
	    The advantage of using DHCP is that changes to the network, for example a change
868
	    The advantage of using DHCP is that changes to the network, for example a change
1010
909
            in the address of the DNS server, need only be changed at the DHCP server, and all
869
            in the address of the DNS server, need only be changed at the DHCP server, and all
1011
910
            network hosts will be reconfigured the next time their DHCP clients poll the
870
            network hosts will be reconfigured the next time their DHCP clients poll the
1014
911
            DHCP server. As an added advantage, it is also easier to integrate new computers 
871
            DHCP server. As an added advantage, it is also easier to integrate new computers
1015
912
	    into the network, as there is no need to check for the availability of an IP 
872
	    into the network, as there is no need to check for the availability of an IP
1016
913
	    address.  Conflicts in IP address allocation are also reduced.
873
	    address.  Conflicts in IP address allocation are also reduced.
1017
914
	    </para>
874
	    </para>
1018
915
            <para>
875
            <para>
1019
@@ -924,7 +884,7 @@
1020
924
                        of each network card connected to the network and then continually
884
                        of each network card connected to the network and then continually
1021
925
                        supplying a constant configuration each time the DHCP client makes a
885
                        supplying a constant configuration each time the DHCP client makes a
1022
926
                        request to the DHCP server using that network device. This ensures that
886
                        request to the DHCP server using that network device. This ensures that
1024
927
			a particular address is assigned automatically to that network card, 
887
			a particular address is assigned automatically to that network card,
1025
928
			based on it's MAC address.
888
			based on it's MAC address.
1026
929
			</para>
889
			</para>
1027
930
                    </listitem>
890
                    </listitem>
1028
@@ -934,13 +894,13 @@
1029
934
                    <listitem>
894
                    <listitem>
1030
935
                        <para>
895
                        <para>
1031
936
			In this method, the DHCP server will assign an IP address from a pool of addresses
896
			In this method, the DHCP server will assign an IP address from a pool of addresses
1034
937
			(sometimes also called a range or scope) for a period of time or lease, that is 
897
			(sometimes also called a range or scope) for a period of time or lease, that is
1035
938
			configured on the server or until the client informs the server that it doesn't 
898
			configured on the server or until the client informs the server that it doesn't
1036
939
			need the address anymore. This way, the clients will be receiving their configuration
899
			need the address anymore. This way, the clients will be receiving their configuration
1037
940
			properties dynamically and on a "first come, first served" basis. When a DHCP client
900
			properties dynamically and on a "first come, first served" basis. When a DHCP client
1039
941
			is no longer on the network for a specified period, the configuration is expired and 
901
			is no longer on the network for a specified period, the configuration is expired and
1040
942
			released back to the address pool for use by other DHCP Clients. This way, an address
902
			released back to the address pool for use by other DHCP Clients. This way, an address
1042
943
			can be leased or used for a period of time. After this period, the client has to 
903
			can be leased or used for a period of time. After this period, the client has to
1043
944
			renegociate the lease with the server to maintain use of the address.
904
			renegociate the lease with the server to maintain use of the address.
1044
945
			</para>
905
			</para>
1045
946
                    </listitem>
906
                    </listitem>
1046
@@ -950,7 +910,7 @@
1047
950
                    <listitem>
910
                    <listitem>
1048
951
                        <para>
911
                        <para>
1049
952
			Using this method, the DHCP automatically assigns an IP address permanently to a device,
912
			Using this method, the DHCP automatically assigns an IP address permanently to a device,
1051
953
			selecting it from a pool of available addresses. Usually DHCP is used to assign a 
913
			selecting it from a pool of available addresses. Usually DHCP is used to assign a
1052
954
			temporary address to a client, but a DHCP server can allow an infinite lease time.
914
			temporary address to a client, but a DHCP server can allow an infinite lease time.
1053
955
			</para>
915
			</para>
1054
956
                    </listitem>
916
                    </listitem>
1055
@@ -962,12 +922,9 @@
1056
962
	    is in how long the IP address is leased, in other words whether a client's address varies
922
	    is in how long the IP address is leased, in other words whether a client's address varies
1057
963
	    over time.
923
	    over time.
1058
964
924
1065
965
	    Ubuntu is shipped with both DHCP server and client. The server is
925
	    The DHCP server Ubuntu makes available is
1066
966
            <application>dhcpd</application> (dynamic host configuration protocol daemon).
926
        <application>dhcpd</application> (dynamic host configuration protocol daemon),
1067
967
            The client provided with Ubuntu is <application>dhclient</application> and should 
927
		which is easy to install and configure and will be automatically started at system boot.
1062
968
	    be installed on all computers required to be automatically configured. Both 
1063
969
	    programs are easy to install and configure and will be automatically started at
1064
970
	    system boot.
1068
971
	    </para>
928
	    </para>
1069
972
      <sect2 id="dhcp-installation" status="review">
929
      <sect2 id="dhcp-installation" status="review">
1070
973
        <title>Installation</title>
930
        <title>Installation</title>
1071
@@ -1011,15 +968,15 @@
1072
1011
 option routers 192.168.1.254;
968
 option routers 192.168.1.254;
1073
1012
 option domain-name-servers 192.168.1.1, 192.168.1.2;
969
 option domain-name-servers 192.168.1.1, 192.168.1.2;
1074
1013
 option domain-name "mydomain.example";
970
 option domain-name "mydomain.example";
1076
1014
} 
971
}
1077
1015
</programlisting>
972
</programlisting>
1078
1016
            <para>
973
            <para>
1079
1017
	    This will result in the DHCP server giving clients an IP address from the range
974
	    This will result in the DHCP server giving clients an IP address from the range
1080
1018
            192.168.1.150-192.168.1.200. It will lease an IP
975
            192.168.1.150-192.168.1.200. It will lease an IP
1085
1019
            address for 600 seconds if the client doesn't ask for a specific time frame. 
976
            address for 600 seconds if the client doesn't ask for a specific time frame.
1086
1020
	    Otherwise the maximum (allowed) lease will be 7200 seconds. The server will also 
977
	    Otherwise the maximum (allowed) lease will be 7200 seconds. The server will also
1087
1021
	    "advise" the client to use 192.168.1.254 as the default-gateway and 
978
	    "advise" the client to use 192.168.1.254 as the default-gateway and
1088
1022
	    192.168.1.1 and 192.168.1.2 as its DNS servers. 
979
	    192.168.1.1 and 192.168.1.2 as its DNS servers.
1089
1023
	    </para>
980
	    </para>
1090
1024
          <para>
981
          <para>
1091
1025
	  After changing the config file you have to restart the
982
	  After changing the config file you have to restart the
1092
@@ -1040,7 +997,7 @@
1093
1040
            </listitem>
997
            </listitem>
1094
1041
            <listitem>
998
            <listitem>
1095
1042
              <para>
999
              <para>
1097
1043
              For more <filename>/etc/dhcp/dhcpd.conf</filename> options see the 
1000
              For more <filename>/etc/dhcp/dhcpd.conf</filename> options see the
1098
1044
              <ulink url="http://manpages.ubuntu.com/manpages/&distro-short-codename;/en/man5/dhcpd.conf.5.html">dhcpd.conf man page</ulink>.
1001
              <ulink url="http://manpages.ubuntu.com/manpages/&distro-short-codename;/en/man5/dhcpd.conf.5.html">dhcpd.conf man page</ulink>.
1099
1045
              </para>
1002
              </para>
1100
1046
            </listitem>
1003
            </listitem>
1101
@@ -1057,10 +1014,10 @@
1102
1057
	<sect1 id="NTP" status="review">
1014
	<sect1 id="NTP" status="review">
1103
1058
		<title>Time Synchronization</title>
1015
		<title>Time Synchronization</title>
1104
1059
	<para>
1016
	<para>
1106
1060
NTP is a TCP/IP protocol for synchronizing time over a network. Basically a client requests the current time from a server, and uses it to set its own clock.  
1017
NTP is a TCP/IP protocol for synchronizing time over a network. Basically a client requests the current time from a server, and uses it to set its own clock.
1107
1061
</para>
1018
</para>
1108
1062
	<para>
1019
	<para>
1110
1063
Behind this simple description, there is a lot of complexity - there are tiers of NTP servers, with the tier one NTP servers connected to atomic clocks, and tier two and three servers spreading the load of actually handling requests across the Internet. Also the client software is a lot more complex than you might think - it has to factor out communication delays, and adjust the time in a way that does not upset all the other processes that run on the server. But luckily all that complexity is hidden from you! 
1020
Behind this simple description, there is a lot of complexity - there are tiers of NTP servers, with the tier one NTP servers connected to atomic clocks, and tier two and three servers spreading the load of actually handling requests across the Internet. Also the client software is a lot more complex than you might think - it has to factor out communication delays, and adjust the time in a way that does not upset all the other processes that run on the server. But luckily all that complexity is hidden from you!
1111
1064
</para>
1021
</para>
1112
1065
	<para>
1022
	<para>
1113
1066
        Ubuntu by default uses <emphasis>timedatectl / timesyncd</emphasis> to synchronize time and users can optionally use chrony to <xref linkend="timeservers"/>.
1023
        Ubuntu by default uses <emphasis>timedatectl / timesyncd</emphasis> to synchronize time and users can optionally use chrony to <xref linkend="timeservers"/>.
1114
@@ -1573,10 +1530,10 @@
1115
1573
Network devices using kernel driver
1530
Network devices using kernel driver
1116
1574
===================================
1531
===================================
1117
1575
0000:02:00.0 &apos;NetXtreme BCM5719 Gigabit Ethernet PCIe&apos; if=eth0 drv=tg3 unused=uio_pci_generic *Active*
1532
0000:02:00.0 &apos;NetXtreme BCM5719 Gigabit Ethernet PCIe&apos; if=eth0 drv=tg3 unused=uio_pci_generic *Active*
1122
1576
0000:02:00.1 &apos;NetXtreme BCM5719 Gigabit Ethernet PCIe&apos; if=eth1 drv=tg3 unused=uio_pci_generic 
1533
0000:02:00.1 &apos;NetXtreme BCM5719 Gigabit Ethernet PCIe&apos; if=eth1 drv=tg3 unused=uio_pci_generic
1123
1577
0000:02:00.2 &apos;NetXtreme BCM5719 Gigabit Ethernet PCIe&apos; if=eth2 drv=tg3 unused=uio_pci_generic 
1534
0000:02:00.2 &apos;NetXtreme BCM5719 Gigabit Ethernet PCIe&apos; if=eth2 drv=tg3 unused=uio_pci_generic
1124
1578
0000:02:00.3 &apos;NetXtreme BCM5719 Gigabit Ethernet PCIe&apos; if=eth3 drv=tg3 unused=uio_pci_generic 
1535
0000:02:00.3 &apos;NetXtreme BCM5719 Gigabit Ethernet PCIe&apos; if=eth3 drv=tg3 unused=uio_pci_generic
1125
1579
0000:04:00.1 &apos;Ethernet Controller 10-Gigabit X540-AT2&apos; if=eth5 drv=ixgbe unused=uio_pci_generic 
1536
0000:04:00.1 &apos;Ethernet Controller 10-Gigabit X540-AT2&apos; if=eth5 drv=ixgbe unused=uio_pci_generic
1126
1580
1537
1127
1581
Other network devices
1538
Other network devices
1128
1582
=====================
1539
=====================
Status:	Merged
Approved by:	Doug Smythies on 2018-05-21
Approved revision:	363
Merged at revision:	358
Proposed branch:	lp:~powersj/serverguide/network-revamp-18.04
Merge into:	lp:serverguide/trunk
Diff against target:	1128 lines (+326/-369) 1 file modified serverguide/C/network-config.xml (+326/-369)
To merge this branch:	bzr merge lp:~powersj/serverguide/network-revamp-18.04
Related bugs:	Link a bug report
Reviewer	Date Requested	Status
Doug Smythies	2018-05-17	Approve on 2018-05-21
Mathieu Trudel-Lapierre	2018-05-17	Approve on 2018-05-18
David Britton (community)	2018-05-17	Approve on 2018-05-18
Review via email: mp+345788@code.launchpad.net