1
diff --git a/docs/configure-cellular-connections.md b/docs/configure-cellular-connections.md
2
index 5f9dd3d..215f2dc 100644
3
--- a/docs/configure-cellular-connections.md
4
+++ b/docs/configure-cellular-connections.md
5
@@ -86,10 +86,10 @@ $ nmcli c add type gsm ifname <interface> con-name <name> apn <operator_apn>
6
86
$ nmcli r wwan on
86
$ nmcli r wwan on
7
87
```
87
```
8
88
88
10
89
where <interface> is the string listed as “primary port” in the output from 'sudo mmcli -m <N>'
89
where &lt;interface&gt; is the string listed as “primary port” in the output from 'sudo mmcli -m &lt;N&gt;'
11
90
(as previously described),
90
(as previously described),
14
91
<name> is an arbitrary name used to identify the connection, and <operator_apn> is
91
&lt;name&gt; is an arbitrary name used to identify the connection, and &lt;operator_apn&gt; is
15
92
the APN name for your cellular data plan.  Note that <interface> is usually a serial
92
the APN name for your cellular data plan.  Note that &lt;interface&gt; is usually a serial
16
93
port with pattern /dev/tty*, not a networking interface. The reason for ModemManager
93
port with pattern /dev/tty*, not a networking interface. The reason for ModemManager
17
94
to use that instead of the networking interface is that this last one can appear/disappear
94
to use that instead of the networking interface is that this last one can appear/disappear
18
95
dynamically while the ports do not if the hardware configuration remains unchanged.
95
dynamically while the ports do not if the hardware configuration remains unchanged.
19
@@ -99,7 +99,7 @@ different each time it is possible to have other ppp connections with, say, VPNs
20
99
After executing these commands, NetworkManager will automatically try to bring up
99
After executing these commands, NetworkManager will automatically try to bring up
21
100
the cellular connection whenever ModemManager reports that the modem has
100
the cellular connection whenever ModemManager reports that the modem has
22
101
registered (the state of the modem can be checked with the previously introduced
101
registered (the state of the modem can be checked with the previously introduced
24
102
command “sudo modem-manager.mmcli -m <N>”). When done successfully, NetworkManager
102
command “sudo modem-manager.mmcli -m &lt;N&gt;”). When done successfully, NetworkManager
25
103
will create routes for the new network interface, with less priority than
103
will create routes for the new network interface, with less priority than
26
104
Ethernet or WiFi interfaces. To disable the connection, we can do:
104
Ethernet or WiFi interfaces. To disable the connection, we can do:
27
105
105
28
diff --git a/docs/configure-wifi-connections.md b/docs/configure-wifi-connections.md
29
index fc3a72d..1d5a7fa 100644
30
--- a/docs/configure-wifi-connections.md
31
+++ b/docs/configure-wifi-connections.md
32
@@ -1,10 +1,20 @@
33
1
---
1
---
34
2
title: "Configure WiFi Connections"
2
title: "Configure WiFi Connections"
36
3
table_of_contents: False
3
table_of_contents: True
37
4
---
4
---
38
5
5
39
6
# Configure WiFi Connections
6
# Configure WiFi Connections
40
7
7
41
8
This section explains how to establish a WiFi connection. It covers creating and
42
9
modyfying connections as well as directly connecting.
43
10
44
11
## Establish a Wireless Connection
45
12
46
13
This section will show how to establish a wifi connection to the wireles
47
14
network. Note that directly connecting will implicitly create a connection (that
48
15
can be seen with "nmcli c"). The naming of such will follow "SSID N" pattern,
49
16
where N is a number.
50
17
51
8
First, determine the name of the WiFi interface:
18
First, determine the name of the WiFi interface:
52
9
19
53
10
```
20
```
54
@@ -24,51 +34,48 @@ Then, list the available WiFi networks:
55
24
34
56
25
```
35
```
57
26
$ nmcli d wifi list
36
$ nmcli d wifi list
59
27
*  SSID           MODE   CHAN  RATE       SIGNAL  BARS  SECURITY         
37
*  SSID           MODE   CHAN  RATE       SIGNAL  BARS  SECURITY
60
28
   ...
38
   ...
62
29
   my_wifi      Infra  5     54 Mbit/s  89      ▂▄▆█  WPA2      
39
   my_wifi      Infra  5     54 Mbit/s  89      ▂▄▆█  WPA2
63
30
```
40
```
64
31
41
67
32
As an example, to connect to the access point ‘my_wifi’, you would use the
42
As an example, to connect to the access point 'my_wifi', you would use the
68
33
following commands:
43
following command:
69
34
44
70
35
```
45
```
73
36
$ nmcli c add con-name <name> ifname wlan0 type wifi ssid my_wifi
46
$ nmcli d wifi connect my_wifi password <password>
72
37
$ nmcli c modify <name> wifi-sec.key-mgmt wpa-psk wifi-sec.psk <password>
74
38
```
47
```
75
39
48
80
40
<name> is an arbitrary name given to the connection, and <password> is the
49
&lt;password&gt; is the password for the connection which needs to have 8-63
81
41
password for the connection (this last command can be used to change the
50
characters or 64 hexadecimal characters to specify a full 256-bit key.
82
42
password too). The password needs to have 8-63 characters or 64 hexadecimal characters to specify a full 256-bit key. New connections have DHCP enabled
51
83
43
for both IPv4 and IPv6 by default.
52
## Connect to a Hidden Network
84
44
53
88
45
Once a connection has been created, NetworkManager will consider it for
54
A hidden network is a normal wireless network that simply does not broadcast
89
46
a given connection whenever the device’s WiFi is disconnected and NetworkManager
55
it's SSID unless solicited. This means that its name cannot be searched and
90
47
detects the access point is available via recent scan results.
56
must be known from some other source.
91
48
57
94
49
The autoconnect behaviour of a connection is enabled by default and can be changed
58
Issue the following command to create a connection associated with a hidden
95
50
by modifying the connection’s autoconnect property:
59
network &lt;ssid&gt;:
96
51
60
97
52
```
61
```
99
53
$ nmcli c modify <name> connection.autoconnect [yes|no]
62
$ nmcli c add type wifi con-name <name> ifname wlan0 ssid <ssid>
100
63
$ nmcli c modify <name> wifi-sec.key-mgmt wpa-psk wifi-sec.psk <password>
101
54
```
64
```
102
55
65
106
56
Some other interesting commands follow.
66
Now you can establish a connection by typing:
104
57
105
58
To show the details of a connection:
107
59
67
108
60
```
68
```
110
61
$ nmcli c show <name>
69
$ nmcli c up <name>
111
62
```
70
```
112
63
71
114
64
To trigger a manual WiFi scan:
72
&lt;name&gt; is an arbitrary name given to the connection and &lt;password&gt;
115
73
is the password to the network. It needs to have between 8-63 characters or 64
116
74
hexadecimal characters in order to specify a full 256-bit key.
117
65
75
121
66
```
76
## Further Information
119
67
$ nmcli d wifi rescan
120
68
```
122
69
77
124
70
To delete a connection:
78
You will find further information and more detailed examples on following pages:
125
71
79
129
72
```
80
* <https://developer.gnome.org/NetworkManager/unstable/nmcli.html>
130
73
$ nmcli c delete <name>
81
* <https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html>
128
74
```
131
diff --git a/docs/edit-connections.md b/docs/edit-connections.md
132
75
new file mode 100644
82
new file mode 100644
133
index 0000000..0c9d087
134
--- /dev/null
135
+++ b/docs/edit-connections.md
136
@@ -0,0 +1,155 @@
137
1
---
138
2
title: "Edit Connections"
139
3
table_of_contents: True
140
4
---
141
5
142
6
# Edit Connections
143
7
144
8
This part will show you how to use a network-manager built-in editor to modify
145
9
the connections as well as provide a reference for setting some of the
146
10
settings.
147
11
148
12
## Using nmcli Console
149
13
150
14
Aside from offering the possibility to manage and modify the network connections
151
15
using the command-line, network-manager offers a built-in, interactive
152
16
console to achieve the same. In order to use it type:
153
17
154
18
```
155
19
$ nmcli connection edit
156
20
```
157
21
158
22
It will bring up an interactive console. In the first step you will be prompted
159
23
to enter the connection type. The list of valid connection types will be
160
24
displayed on the screen. Once you select one you will be taken to the nmcli
161
25
console where you have the possibility to modify its parameters.
162
26
163
27
Alternatively, if you know the valid connection types, you could jump straight
164
28
to the nmcli console by providing the type as a parameter:
165
29
166
30
```
167
31
$ nmcli connection edit type <type>
168
32
```
169
33
170
34
where &lt;type&gt;  must be a valid connection type such as 'wifi'.
171
35
172
36
An attempt to edit the wifi connection type would look like:
173
37
174
38
```
175
39
$ nmcli c edit
176
40
177
41
Valid connection types: generic, 802-3-ethernet (ethernet), pppoe,
178
42
802-11-wireless (wifi), wimax, gsm, cdma, infiniband, adsl, bluetooth, vpn,
179
43
802-11-olpc-mesh (olpc-mesh), vlan, bond, team, bridge, bond-slave, team-slave,
180
44
bridge-slave, no-slave, tun, ip-tunnel, macvlan, vxlan
181
45
Enter connection type: wifi
182
46
183
47
===| nmcli interactive connection editor |===
184
48
185
49
Adding a new '802-11-wireless' connection
186
50
187
51
Type 'help' or '?' for available commands.
188
52
Type 'describe [<setting>.<prop>]' for detailed property description.
189
53
190
54
You may edit the following settings: connection, 802-11-wireless (wifi),
191
55
802-11-wireless-security (wifi-sec), 802-1x, ipv4, ipv6
192
56
nmcli>
193
57
```
194
58
195
59
From now on it is possible to edit the wifi connection settings. The list of
196
60
settings is provided as in the example above. The nmcli console offers a set of
197
61
commands that can be used to navigate between settings. To get the list of
198
62
available commands type 'help' or '?'
199
63
200
64
```
201
65
nmcli> ?
202
66
------------------------------------------------------------------------------
203
67
---[ Main menu ]---
204
68
goto     [<setting> | <prop>]        :: go to a setting or property
205
69
remove   <setting>[.<prop>] | <prop> :: remove setting or reset property value
206
70
set      [<setting>.<prop> <value>]  :: set property value
207
71
describe [<setting>.<prop>]          :: describe property
208
72
print    [all | <setting>[.<prop>]]  :: print the connection
209
73
verify   [all | fix]                 :: verify the connection
210
74
save     [persistent|temporary]      :: save the connection
211
75
activate [<ifname>] [/<ap>|<nsp>]    :: activate the connection
212
76
back                                 :: go one level up (back)
213
77
help/?   [<command>]                 :: print this help
214
78
nmcli    <conf-option> <value>       :: nmcli configuration
215
79
quit                                 :: exit nmcli
216
80
------------------------------------------------------------------------------
217
81
nmcli> 
218
82
```
219
83
220
84
## Change Connection Details
221
85
222
86
This section will show how to change some of the connection details including
223
87
IPv4 and IPv6 settings.
224
88
225
89
It is important to understand that every option can be modified using either the
226
90
command-line or the editor. The advantage of the editor is that it shows which
227
91
options are availabe for modification in contrast to the command-line which does
228
92
not.
229
93
230
94
It is possible however to learn about the available settings from the
231
95
command-line by printing the connection details. Type:
232
96
233
97
```
234
98
$ nmcli c show <name>
235
99
```
236
100
237
101
where &lt;name&gt; is the connection name.
238
102
239
103
The above will bring a fairly long list of text on the terminal, therefore it is
240
104
best to either use a pager or grep to make the results manageable.
241
105
242
106
### IPv4 and IPv6 Options
243
107
244
108
For example for IPv4 settings one would do:
245
109
246
110
```
247
111
$ nmcli c show <name> | grep ipv4
248
112
ipv4.method:                            auto
249
113
ipv4.dns:
250
114
ipv4.dns-search:
251
115
ipv4.dns-options:                       (default)
252
116
ipv4.addresses:
253
117
ipv4.gateway:                           --
254
118
ipv4.routes:
255
119
ipv4.route-metric:                      -1
256
120
ipv4.ignore-auto-routes:                no
257
121
ipv4.ignore-auto-dns:                   no
258
122
ipv4.dhcp-client-id:                    --
259
123
ipv4.dhcp-timeout:                      0
260
124
ipv4.dhcp-send-hostname:                yes
261
125
ipv4.dhcp-hostname:                     --
262
126
ipv4.dhcp-fqdn:                         --
263
127
ipv4.never-default:                     no
264
128
ipv4.may-fail:                          yes
265
129
ipv4.dad-timeout:                       -1 (default)
266
130
```
267
131
268
132
For example setting up the DNS server would require typing:
269
133
270
134
```
271
135
$ nmcli c modify <name> ipv4.dns "8.8.8.8"
272
136
```
273
137
274
138
The rest of the settings can be modified in the same fashion.
275
139
276
140
### WiFi Powersave Option
277
141
278
142
The WiFi powersave option can have one of the following values:
279
143
280
144
| Value | Meaning                                           |
281
145
|-------|---------------------------------------------------|
282
146
| 0     | Default                                           |
283
147
| 1     | Ignore, do not touch currently configured setting |
284
148
| 2     | Disable                                           |
285
149
| 3     | Enable                                            |
286
150
287
151
Changing it is as simple as:
288
152
289
153
```
290
154
$ nmcli c modify <name> 802-11-wireless.powersave 2
291
155
```
292
diff --git a/docs/installation.md b/docs/installation.md
293
index 2f6872d..6169238 100644
294
--- a/docs/installation.md
295
+++ b/docs/installation.md
296
@@ -56,3 +56,6 @@ Now you have NetworkManager successfully installed.
297
56
 * [Explore Network Status](explore-network-status.md)
56
 * [Explore Network Status](explore-network-status.md)
298
57
 * [Configure WiFi Connections](configure-wifi-connections.md)
57
 * [Configure WiFi Connections](configure-wifi-connections.md)
299
58
 * [Configure Cellular Connections](configure-cellular-connections.md)
58
 * [Configure Cellular Connections](configure-cellular-connections.md)
300
59
 * [Edit Network Connections](edit-connections.md)
301
60
 * [Routing Tables](routing-tables.md)
302
61
 * [Logging Messages](logging-messages.md)
303
diff --git a/docs/logging-messages.md b/docs/logging-messages.md
304
59
new file mode 100644
62
new file mode 100644
305
index 0000000..d242808
306
--- /dev/null
307
+++ b/docs/logging-messages.md
308
@@ -0,0 +1,43 @@
309
1
---
310
2
title: "Logging Messages"
311
3
table_of_contents: False
312
4
---
313
5
314
6
# Logging Messages
315
7
316
8
This section will show how to modify the logging levels by NetworkManager.
317
9
318
10
NetworkManager supports on the fly changing of the logging levels and allows for
319
11
a fine control over what is logged.
320
12
321
13
First check what is the current logging setup, type:
322
14
323
15
```
324
16
$ nmcli general logging
325
17
```
326
18
327
19
As a result you will be presented with the information about the current
328
20
configuration:
329
21
330
22
```
331
23
LEVEL  DOMAINS                                                                                                                                                                                                                 
332
24
INFO   PLATFORM,RFKILL,ETHER,WIFI,BT,MB,DHCP4,DHCP6,PPP,IP4,IP6,AUTOIP4,DNS,VPN,SHARING,SUPPLICANT,AGENTS,SETTINGS,SUSPEND,CORE,DEVICE,OLPC,INFINIBAND,FIREWALL,ADSL,BOND,VLAN,BRIDGE,TEAM,CONCHECK,DCB,DISPATCH,AUDIT,SYSTEMD 
333
25
```
334
26
335
27
It is possible to change the level either globally or for each domain
336
28
separately. The command to achieve this is:
337
29
338
30
```
339
31
$ nmcli general logging [level <level> [domain <domain>]]
340
32
```
341
33
342
34
The &lt;level&gt; is the desired log level. You can choose from the following:
343
35
344
36
* **ERR:** will log only critical errors
345
37
* **WARN:** will log warnin messages
346
38
* **INFO:** will log various informational messages
347
39
* **DEBUG:** enables verbose logging for debugging purposes
348
40
349
41
&lt;domain&gt; is the category of messages that shall be logged with given
350
42
severity. **WIFI** will include only WiFi related messages, **IP4** will include
351
43
only IPv4 related messages and so on..
352
diff --git a/docs/metadata.yaml b/docs/metadata.yaml
353
index 477b29d..b9c4f41 100644
354
--- a/docs/metadata.yaml
355
+++ b/docs/metadata.yaml
356
@@ -17,12 +17,20 @@ navigation:
357
17
        location: configure-cellular-connections.md
17
        location: configure-cellular-connections.md
358
18
      - title: Enable Ethernet Support
18
      - title: Enable Ethernet Support
359
19
        location: enable-ethernet-support.md
19
        location: enable-ethernet-support.md
360
20
      - title: Edit Connections
361
21
        location: edit-connections.md
362
22
      - title: Routing Tables
363
23
        location: routing-tables.md
364
24
      - title: Logging Messages
365
25
        location: logging-messages.md
366
20
  - title: Reference
26
  - title: Reference
367
21
    children:
27
    children:
368
22
      - title: Snap Configuration
28
      - title: Snap Configuration
369
23
        children:
29
        children:
370
24
          - title: Wake on WLAN
30
          - title: Wake on WLAN
371
25
            location: reference/snap-configuration/wowlan.md
31
            location: reference/snap-configuration/wowlan.md
372
32
          - title: WiFi Powersave
373
33
            location: reference/snap-configuration/wifi-powersave.md
374
26
      - title: Available Commands
34
      - title: Available Commands
375
27
        location: reference/available-commands.md
35
        location: reference/available-commands.md
376
28
      - title: DBUS API
36
      - title: DBUS API
377
diff --git a/docs/reference/snap-configuration/wifi-powersave.md b/docs/reference/snap-configuration/wifi-powersave.md
378
29
new file mode 100644
37
new file mode 100644
379
index 0000000..8b9e68f
380
--- /dev/null
381
+++ b/docs/reference/snap-configuration/wifi-powersave.md
382
@@ -0,0 +1,38 @@
383
1
---
384
2
title: WiFi Powersave
385
3
table_of_contents: True
386
4
---
387
5
388
6
# WiFi Powersave
389
7
390
8
WiFi Powersave is a feature that allows a device to suspend its radio activity
391
9
after a fixed period of inactivity. The device remains idle for a fixed time,
392
10
usualy about 100ms, and once it is reached it wakes up to check if the
393
11
infrastructure has any packets queued up for it.
394
12
395
13
The NetworkManager snap allows to configure this option by either enabling or
396
14
disabling the powersave feature.
397
15
398
16
You can read more about the WiFi Powersave feature on the following sites:
399
17
400
18
*
401
19
<https://wireless.wiki.kernel.org/en/developers/documentation/ieee80211/power-savings>
402
20
403
21
### Enable WiFi Powersave
404
22
405
23
To allow users to enable or disable WiFi Powersave, the snap provides a single
406
24
configuration option:
407
25
408
26
* wifi.powersave
409
27
410
28
Option can be set via the configuration API snaps provide. See
411
29
<https://docs.ubuntu.com/core/en/guides/build-device/config-hooks> for more
412
30
details.
413
31
414
32
#### wifi.powersave
415
33
416
34
This configuration option accepts the following values:
417
35
418
36
* **disabled (default):** WiFi powersaving is disabled
419
37
* **enabled:** WiFi powersaving is enabled
420
38
421
diff --git a/docs/report-bug.md b/docs/report-bug.md
422
index 9ec4b89..faa9853 100644
423
--- a/docs/report-bug.md
424
+++ b/docs/report-bug.md
425
@@ -18,6 +18,10 @@ $ nmcli d
426
18
$ nmcli c
18
$ nmcli c
427
19
```
19
```
428
20
20
429
21
It is a good idea to set the log level to DEBUG so that the verbose information
430
22
is provided. To do this for NetworkManager please see the [Logging Messages](logging-messages.md)
431
23
page.
432
24
433
21
If there is a modem and the modem-manager snap is installed, also add the output
25
If there is a modem and the modem-manager snap is installed, also add the output
434
22
of
26
of
435
23
27
436
diff --git a/docs/routing-tables.md b/docs/routing-tables.md
437
24
new file mode 100644
28
new file mode 100644
438
index 0000000..85b4ff8
439
--- /dev/null
440
+++ b/docs/routing-tables.md
441
@@ -0,0 +1,96 @@
442
1
---
443
2
title: "Routing Tables"
444
3
table_of_contents: True
445
4
---
446
5
447
6
# Routing Tables
448
7
449
8
This section describes the way to setup routing table as well as it explains the
450
9
logic used to prioritize interfaces.
451
10
452
11
The routing table is stored in the kernel which merely acts upon it. The route
453
12
itself is set by the user-space tools. There is no preference as any tool
454
13
created for this reason will do. It can be either a DHCP client, ip command or
455
14
route command.
456
15
457
16
It is important to understand that NetworkManager changes the routing table
458
17
whenever it creates a new connection.
459
18
460
19
Routing table acts as a junction and is there to show where the different
461
20
network subnets will be routed to. An example of a routing table is shown below.
462
21
463
22
```
464
23
$ ip route
465
24
default via 10.0.0.1 dev wlp3s0  proto static  metric 600
466
25
10.0.0.0/24 dev wlp3s0  proto kernel  scope link  src 10.0.0.73  metric 600
467
26
10.0.1.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.1.1
468
27
169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown
469
28
172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown
470
29
192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 linkdown
471
30
```
472
31
473
32
The first column is the &lt;Destination&gt; subnet with the "default" being a
474
33
wildcard for everything else. The "via" fragment points to the &lt;Gateway&gt;
475
34
however when it is missing it indicates that that network is connected directly
476
35
and instead it describes a source address.
477
36
478
37
The &lt;Metric&gt; column translates to the number of hops required to reach the
479
38
destination and is used to determine which route shall be preferred when there
480
39
are more than one route available for a specific destination. Since it
481
40
reassembles the concept of distance the lower it's value is the better.
482
41
483
42
The &lt;Metric&gt; value can be set manually however when NetworkManager creates
484
43
a connection the following defaults are applied:
485
44
486
45
* Ethernet is preferred over WiFi
487
46
* WiFi is preferred over WWAN
488
47
489
48
# Editing the Routing Tables
490
49
491
50
The routing table can be added or modified using the standard *ip* command which
492
51
is available on Ubuntu Core.
493
52
494
53
You can find more information on it on the following page:
495
54
496
55
* <https://linux.die.net/man/8/ip?>
497
56
498
57
Separately it is possible to modify routing information per single connection
499
58
using the nmcli tool. The parameters such as: gateway, routes and metrics can be
500
59
modified.
501
60
502
61
The following options are responsible:
503
62
504
63
```
505
64
ipv4.gateway:
506
65
ipv4.routes:
507
66
ipv4.route-metric:
508
67
509
68
ipv6.gateway:
510
69
ipv6.routes:
511
70
ipv6.route-metric:
512
71
```
513
72
514
73
These options can be modified in a following way:
515
74
516
75
```
517
76
$ nmcli connection modify <name> +ipv4.routes <destination> ipv4.gateway <gateway>
518
77
$ nmcli connection modify <name> ipv4.route-metric <metric>
519
78
```
520
79
521
80
Where &lt;name&gt; is the connection name. You can obtain it by listing
522
81
available connections on the system:
523
82
524
83
```
525
84
$ nmcli c show
526
85
```
527
86
528
87
&lt;destination&gt; is the destination network provided as a static IP address,
529
88
subnet or "default". &lt;gateway&gt; is the new gateway information.
530
89
&lt;metric&gt; is the new metric information.
531
90
532
91
Note that this kind of changes can be made separately for each connection thus
533
92
it is possible to provide a fine grained control over how the packets directed
534
93
to different networks are routed.
535
94
536
95
It is also important to understand that bringing up and down connections with
537
96
different values set for these options is in fact changing the routing table.
Status:	Merged
Approved by:	Simon Fels on 2017-05-09
Approved revision:	7f5338830414ce8dd2c8fb1cb1048c1c98115608
Merged at revision:	5f2abc005bf79be8167bd54f5f8f66331576aecc
Proposed branch:	~kzapalowicz/snappy-hwe-snaps/+git/network-manager:feature/update-documentation
Merge into:	~snappy-hwe-team/snappy-hwe-snaps/+git/network-manager:master
Diff against target:	537 lines (+387/-33) 9 files modified docs/configure-cellular-connections.md (+4/-4) docs/configure-wifi-connections.md (+36/-29) docs/edit-connections.md (+155/-0) docs/installation.md (+3/-0) docs/logging-messages.md (+43/-0) docs/metadata.yaml (+8/-0) docs/reference/snap-configuration/wifi-powersave.md (+38/-0) docs/report-bug.md (+4/-0) docs/routing-tables.md (+96/-0)
Related bugs:	Link a bug report
Reviewer	Review Type	Date Requested	Status
Simon Fels			Approve on 2017-05-09
Jim Hodapp (community)			Approve on 2017-05-08
System Enablement Bot	continuous-integration	2017-04-28	Approve on 2017-05-08
Alfonso Sanchez-Beato			Approve on 2017-05-08
Review via email: mp+323381@code.launchpad.net